Dear partners, We are still missing inputs from some partners that have effort allocation in task 3.3.4 as per the current DoW. Notice that lack of contribution to this deliverable may impact your effort recognition in task 3.3.4. Of course, the contributions should comprise *relevant* information! Unfortunately, it seems that some of the partners who did contribute to the Google doc misinterpreted the intention of this deliverable and included details about GEri's that have been contributed to open source (i.e., uploaded to github with an open source license), but not to *existing* & *established* communities. Let me remind everyone that ALL the GEris are now delivered as open source on github, and there is no point repeating all of them here. This deliverable is about influencing *existing* & *established* open source projects. Few examples of contributions which do not meet this criteria (based on the currently available details): - TID / Orion Context Broker - TID / IDAS - TID / Cosmos - UPM / Openstack Keystone Oauth2 extension - DFKI / FiVES This doesn't mean that they are less important - they just don't fit this particular deliverable. Also, some of the contributions don't provide the necessary details about specific code contributions from the past year (e.g., no link to PR/commit). For example: - Adminotech / WebTundra & three.js - DFKI / XML3D The information provided in the deliverable should be easily traceable, so we need to have pointers to specific code contributions. Please, provide your input by the end of this week. We will work on cleaning up the missing/wrong entries and producing the consolidated deliverable document early next week. Thanks, Alex & Kenneth ==================================================================================== Alex Glikson Manager, Cloud Infrastructure Solutions, IBM Haifa Research Lab; FIWARE Cloud Leader & Architect Email: glikson at il.ibm.com | Phone: +972-4-8281085 | Mobile: +972-54-6466667 | Fax: +972-4-8296112 ----- Forwarded by Alex Glikson/Haifa/IBM on 01/10/2015 08:42 PM ----- From: Kenneth Nagin/Haifa/IBM at IBMIL To: fiware-chapter-leaders at lists.fiware.org, fiware-chapter-architects at lists.fiware.org Date: 18/09/2015 11:00 AM Subject: [Fiware-chapter-leaders] D33.4.1: FIWARE Contribution to Open Source Communities report. due Friday, September 25, 2015. Sent by: fiware-chapter-leaders-bounces at lists.fiware.org Dear chapter leaders, It is again time to describe your FIWARE Open Source contributions to satisfy the deliverable: D33.4.1: FIWARE Contribution to Open Source Communities report. Please provide you input to the open source deliverable by Friday, September 25, 2015. As you will need the input of your chapter?s partners to this, please distribute this information as soon as possible within your chapter. How to provide input: IBM has prepared a document skeleton to be found at: https://docs.google.com/document/d/13VgQML1235lNAJGwpvkOAHmDKHJN_KibXffoCnmHf-k/edit# Each partner should include zero or more sub-sections with os community name that include description of contributions, URL to code, URLs to specific contributions, status (in progress, under review, merged, in release, etc). IBM has described their contributions so you can use it as a guide, Thank you very much in advance for you cooperation. Best Regards, Kenneth Nagin Ph: +972-4-8296227 Cell: 054-6976227 Fx: +972-4- 8296114 http://researcher.ibm.com/view.php?person=il-NAGIN _______________________________________________ Fiware-chapter-leaders mailing list Fiware-chapter-leaders at lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-chapter-leaders _______________________________________________ Fiware-chapter-leaders mailing list Fiware-chapter-leaders at lists.fiware.org https://lists.fiware.org/listinfo/fiware-chapter-leaders-new -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/fiware/attachments/20151001/1fb6b81c/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy