Responses are in-line
-----------
Dear Franck,
I have several questions about FIWARE and its platform. I hope you can help me to answer these questions.
* Are there any opportunities for us to help on the development of enablers?
* Please explain how this can be achieved and if there is any form of compensation.
-> Such processes are not defined today, despite they are under discussion, starting with the possible integration of enablers from phase 2 projects. However, you are still free to contact enablers development teams directly and propose your contribution.
* Can anyone use FIWARE and FI-STAR?
* Can we start our own FIWARE project without the use of a acceleration program?
-> FIWARE is open to everybody so any use, outside of the acceleration program is much welcome.
* Can we start a traineeship around FIWARE?
-> http://edu.fiware.org aims at providing a starting point. To go further, developers weeks are organized regularly. Next one will be in Vienna on May 26-28: http://www.fiware.org/event/fiware-developers-week-vienna/
* FI-LAB: How long do we have access to our node/instance?
* Do we have to pay after the FICHe program is over?
-> FIWARE overall intends to be sustainable. FIWARE lab will at least remains accessible in the current conditions until the end of the on-going-projects (~end 2016). Conditions for follow-up are under discussion.
* Do we need to use the FI-LAB during the PoC phase?
-> It is intended to accelerate your development but there are no obligations.
* Questions regarding enablers
* A lot of enablers are still in alpha/beta phases. What is the roadmap for these enablers? When do you expect to have a stable release for these enablers?
-> Enablers roadmap is available here : http://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/FI-WARE_Technical_Roadmap
* It seems that some enablers have been removed from the catalogue. Why did this happen and will they return?
-> Some enablers were removed at the end of last year when the release of at least one implementation as open-source as be put as mandatory. Some enablers contributors stepped back at that time.
* What are the risks when a enabler receives an update? Could it be possible that our implementation needs an update as well?
-> Yes, this is a high risk. I have not seen yet systematic non-regression testing on enablers.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-fiche-coaching/attachments/20150520/718b219c/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy