Dear all, An important clarification to this mail from Miguel. The planning that leads to delivering of GE Open Specifications by Feb 28 applies: * To GEs implemented by GEis whose owner will stop contributing to activities of the project in month 36 (the list of partners who will leave early was provided by Miguel, please check whether it is accurate) or * To GEs implemented by GEis for which development/packaging activities have been asked to stop as a result of the month 30 review. For the rest of GEs, the planning that leads to delivering of GE Open Specifications by May 5 applies. GEis which were declared that they were not going to be open source or for which the exploitation plan communicated by the owner was not considered convincing enough by the reviewers are the GEis for which development/packaging activities must be stopped. Regarding exploitation plans, Arian clarified me that the only exploitation plans regarding GEis not declared to be open source that were considered convincing enough by the reviewers where those coming from Thales. In other words, the EC and reviewers have asked to stop development/packaging activities on all GEis that had been declared to be non open source at the month 30 review, with the exception of those from Thales. Open Specifications of GEs implemented by GEis in this category should follow the plan that means that the owner should deliver their contribution to the specs by Feb 28. Note that GEis which were not declared to be open source by end of November but whose owner arrived at the month 30 review meeting stating their commitment to deliver them as open source by month 36 were requested to stop development of new features by end of December. However, they were asked to carry out the activities dealing with making the software be available as open source as well as packaging activities. Such activities should be planned to finish by end of March (end of release 3.3) so that an official delivery of the software and related documentation will be planned by month 36. Open Specifications of GEs implemented by GEis in this category can follow the planning that ends by May 5 unless the owner has planned to stop contributing to activities of the project by month 36 in which case they have to deliver their contribution to the specs by Feb 28. GEis which where declared to be open source by end of November or the non-open source GEis developed by Thales (whose exploitation plans were considered convincing enough by the reviewers) are allowed to continue development of pending features. Open Specifications of GEs implemented by GEis in this category can follow the planning that ends by May 5 unless the owner have planned to stop contributing to activities of the project by month 36 in which case they have to deliver their contribution to the specs by Feb 28. I hope this clarifies now who should follow which planning regarding delivery of open specifications Best regards, -- Juanjo ------------- Product Development and Innovation (PDI) - Telefonica Digital website: www.tid.es<http://www.tid.es> email: jhierro at tid.es<mailto:jhierro at tid.es> twitter: twitter.com/JuanjoHierro FI-WARE (European Future Internet Core Platform) Coordinator and Chief Architect FI-PPP Architecture Board chairman You can follow FI-WARE at: website: http://www.fi-ware.eu facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 twitter: http://twitter.com/FIware linkedIn: http://www.linkedin.com/groups/FIWARE-4239932 On 28/01/14 12:23, Miguel Carrillo wrote: Dear all, It is time to update the Open Specs and the Open specs APIs to prepare the delivery for the EC. I will try to put all the needed info in one message. We have two different groups of GEs with different schedules: * Those who will extend their activity until M40 (August 2014) * Those who will stop the development of GEs in M36(April 2014) Those leaving on M36 are basically: * the ones who voted to leave early (see attachment) * or those who did not offer their GE under an open source license when the M30 review took place(later changes are not relevant for this) Most of you know where you are. In any cases, as there might be confusions, I will try to add a column to the GE list stating the termination date: * https://docs.google.com/spreadsheet/ccc?key=0AqLSWp0KXaaDdEpLT0RmXzhzbXEtSTVvSE5wX3oyWXc#gid=0 Schedule for those leaving on M36: * 3/Feb/2014 - First draft of contributions by chapter ready for peer review * Edition on PRIVATE WIKI * WPL to generate word doc for review * 4/Feb/2014 - .docx first version of chapter ready * 7/Feb/2014 - Comments on first draft (.docx with traced changes) * 13/Feb/2014 - .docx second version of chapters ready for the review of the coordinator * From 13 to 21, interactions with the coordinator to refine the docs. * 21/Feb/2014 - Final .docx version ready for delivery + delivery to the EC (WPL to put it together) * 28/Feb/2014 - Public wiki updated 100% with new architecture & Open Specs contents Schedule for those staying until M40: * 14/Mar/2014 - First draft of contributions by chapter ready for peer review * Edition in PRIVATE WIKI * Generate word doc for review * 17/Mar/2014 - .docx first version of chapter ready * 24/Mar/2014 - Comments on first draft (.docx with traced changes) * 31/Mar/2014 - .docx second version of chapters ready for the review of the coordinator * From 31/Mar to 28/April, interactions with the coordinator to refine the docs. (note the that Easter is in this interval) * 28/Apr/2014 - Final .docx version ready for delivery + delivery to the EC (WPL to put it together) * 5/May/2014 - Public wiki updated 100% with new architecture & Open Specs contents You can start editing this now on : * https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/OpenSpecs_v3 I am assuming that the WPL/WPAs will coordinate their WPs and resolve internally the doubts that may arise. All direct edits on the public wiki will be reverted without asking. We will prepare a submission cockpit shortly. Best regards, Miguel -- ---------------------------------------------------------------------- _/ _/_/ Miguel Carrillo Pacheco _/ _/ _/ _/ Telefónica Distrito Telefónica _/ _/_/_/ _/ _/ Investigación y Edifico Oeste 1, Planta 9 _/ _/ _/ _/ Desarrollo Ronda de la Comunicación S/N _/ _/_/ 28050 Madrid (Spain) Tel: (+34) 91 483 26 77 e-mail: mcp at tid.es<mailto:mcp at tid.es> Follow FI-WARE on the net Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: http://twitter.com/Fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ---------------------------------------------------------------------- ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx _______________________________________________ Fiware-wpa mailing list Fiware-wpa at lists.fi-ware.eu<mailto:Fiware-wpa at lists.fi-ware.eu> https://lists.fi-ware.eu/listinfo/fiware-wpa ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/fiware-wpa/attachments/20140129/c165398e/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy