Dear Stefano, all, Overall, the draft looks good. I added some comments online. Let me share my main concern here, so that people have time to think/discuss before the meeting tomorrow. It would be critical to clearly distinguish between FIWARE Community/Foundation and other existing open source Communities and Foundations, such as OpenStack, Apache, etc. We need to make sure that FIWARE can live in harmony with them, and build on top -- with minimal or no overlap & overhead. Surely not to 'fork' the code -- but rather to contribute back to those communities, and maybe focus on maintaining some sort of 'distro' of the corresponding assets, if/when necessary. So, for example, FIWARE may comprise an OpenStack distro (like Canonical or Rackspace do) and a Hadoop distro (like Cloudera or Hortonworks), with some value-add enhancements, and with a clear approach to 'upstream' and 'downstream' development. Alternatively, we may also build on top of an existing open source distro rather than creating our own from scratch. I suggest making a statement with this regard an explicit part of the government model. Regards, Alex ==================================================================================== Alex Glikson Manager, Cloud Infrastructure Solutions, IBM Haifa Research Lab Email: glikson at il.ibm.com | Phone: +972-4-8281085 | Mobile: +972-54-6466667 | Fax: +972-4-8296112 From: stefano de panfilis <stefano.depanfilis at eng.it> To: "RIGA Joel IMT/OLPS" <joel.riga at orange.com>, "Fiware-sust-found at lists.fi-ware.org" <Fiware-sust-found at lists.fi-ware.org> Date: 30/03/2015 08:18 PM Subject: Re: [Fiware-sust-found] Fiware community desing principles Rd1 Sent by: fiware-sust-found-bounces at lists.fi-ware.org dear joel and all, you should have received an email from google drive to the link of the document for the tomorrow meeting either to your gmail account (preferred) or to your business account when i did not have the gmail account. of course it would be better for privacy isseus to use only the gmail account. for those active in this list who would like to have acces to the document please send me your email (gmail) address. ciao, stefano 2015-03-30 15:58 GMT+02:00 <joel.riga at orange.com>: Kickoff meeting led by Stefano - Start to update the document of Design principles for the Fiware community. _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. _______________________________________________ Fiware-sust-found mailing list Fiware-sust-found at lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-sust-found -- Stefano De Panfilis Chief Innovation Officer Engineering Ingegneria Informatica S.p.A. via Riccardo Morandi 32 00148 Roma Italy tel (direct): +39-06-8759-4253 tel (secr.): +39-068307-4513 fax: +39-068307-4200 cell: +39-335-7542-567 skype: depa01 twitter: @depa01 _______________________________________________ Fiware-sust-found mailing list Fiware-sust-found at lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-sust-found -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/fiware-sust-found/attachments/20150330/11dccbef/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy