Hi, Well I would argue we should be addressing this sooner than later: The UCs will cease to exist towards the end of this year and while it lasts existing funding could be used to integrate with FIWARE. Of course, support would have to be provided later as well, but this is a general problem that FI-Core partners face as well (only a little later). Additionally, in WebUI we are working with partners that are no longer officially in FI-Core but which still contribute to the development of some of the GEs. This has turned out to be more difficult that originally discussed with Juanjo and others, mainly due to legal reasons (they cannot get access to all FI-Core documents etc.). BTW, there are some really interesting technologies in those UCs. We are jointly using them in WebUI without any issues. I still do not understand why the UCs keep being ignored by FIWARE proper (such as no joint Catalog, ignorance or even active discouragement for using their technology in A16, no joint events like CeBIT, any many other examples). Once we know where we want to go with this, all those issues should be much easier to deal with. Best, Philipp Am 08.03.2015 um 15:03 schrieb Alex Glikson: > Indeed, openness to new GEs and GEis is an important aspect of the > FIWARE Governance model, to be defined.. > Looks like this questionnaire might be a good candidate for an initial > draft of the corresponding section of the model. > By the way, this looks like an extremely important AND extremely > difficult topic. Do we even have an initial understanding of desired > guiding principles for accepting new GEs, especially when there is > overlap in functionality with existing GEs? I know that OpenStack > community is struggling with a similar dilemma for many months, and the > solution being discussed is non-trivial. > Or maybe this even doesn't need to be discussed until a Foundation is > established, and the roles, actors and decision making processes are > outlined? > > 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: Philipp Slusallek <philipp.slusallek at dfki.de> > To: thierry.nagellen at orange.com, > "fiware-chapter-leaders at lists.fi-ware.org" > <fiware-chapter-leaders at lists.fi-ware.org>, > "fiware-chapter-architects at lists.fi-ware.org" > <fiware-chapter-architects at lists.fi-ware.org> > Date: 08/03/2015 03:27 PM > Subject: Re: [Fiware-chapter-leaders] How to integrate other GEis > into FIWARE > Sent by: fiware-chapter-leaders-bounces at lists.fi-ware.org > ------------------------------------------------------------------------ > > > > Hi Thierry, all, > > Similar aspects apply to the Use-Case projects which have developed SW > largely in line with the FIWARE program (I know this at least for > FI-Content and FITMAN). > > It seems that they should be the first to be asked for making their SW > available via the commong FIWARE catalog. Essentially all the > information asked for in the document does exist already in those cases. > > I wonder how we should go about this? I suggest this is a good topic to > discuss this Monday. > > > Best, > > Philipp > > Am 02.03.2015 um 14:16 schrieb thierry.nagellen at orange.com: >> Dear all, >> >> >> >> As explained previously, in the IoT area we have pressure from the >> Commission to be able to integrate some of their results and projects >> into FIWARE website and I have to provide some feedback during the Net >> Futures conference end of March. >> >> >> >> I have prepare a first document with a list of question that external >> 3^rd parties should answer if they want to submit a Generic Enabler >> instance, which covers only a small part of EC expectations. >> >> >> >> We have now good guidelines for documentation and we are also aware of >> the support we have to provide if a new software is included in the >> catalogue. >> >> >> >> You will find here the answers from CEA, a French partner involved in >> Butler project (an IERC project: FP7 IoT cluster) because the Smart >> gateway from Butler could be similar to FIWARE IoT Gateway on many points. >> >> >> >> There is no big surprise: the questions we had 1 year ago regarding Open >> Source license are crucial and not so easy to solve but I think that for >> the other issues we can expect some good answers. The opened key points >> are evaluation of code (quality) and documentation (there is a good >> documentation in this case but clearly not in the FIWARE format and Unit >> Testing Plan, if no more required by EC is important to evaluate what is >> really delivered). >> >> >> >> Your comments are welcome on the document and the answers provided by >> CEA especially if you think that information is missing. >> >> >> >> Regarding the 2 other points: >> >> · Is FIWARE able to host some IERC projects in its website >> (dedicated pages and how we would refer to them)? >> >> · Are we able to host some contents for GEis or SE in FIWARE > Academy? >> >> >> >> I do not have any clear answer. Do you have any idea how to progress on >> these 2 issues? >> >> >> >> Thanks for your support. >> >> BR >> >> Thierry >> >> > _________________________________________________________________________________________________________________________ >> >> 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-chapter-leaders mailing list >> Fiware-chapter-leaders at lists.fi-ware.org >> https://lists.fi-ware.org/listinfo/fiware-chapter-leaders >> > > > -- > > ------------------------------------------------------------------------- > Deutsches Forschungszentrum für Künstliche Intelligenz (DFKI) GmbH > Trippstadter Strasse 122, D-67663 Kaiserslautern > > Geschäftsführung: > Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster (Vorsitzender) > Dr. Walter Olthoff > Vorsitzender des Aufsichtsrats: > Prof. Dr. h.c. Hans A. Aukes > > Sitz der Gesellschaft: Kaiserslautern (HRB 2313) > USt-Id.Nr.: DE 148646973, Steuernummer: 19/673/0060/3 > --------------------------------------------------------------------------- > [attachment "philipp_slusallek.vcf" deleted by Alex Glikson/Haifa/IBM] > _______________________________________________ > 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.fi-ware.org > https://lists.fi-ware.org/listinfo/fiware-chapter-leaders > -- ------------------------------------------------------------------------- Deutsches Forschungszentrum für Künstliche Intelligenz (DFKI) GmbH Trippstadter Strasse 122, D-67663 Kaiserslautern Geschäftsführung: Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster (Vorsitzender) Dr. Walter Olthoff Vorsitzender des Aufsichtsrats: Prof. Dr. h.c. Hans A. Aukes Sitz der Gesellschaft: Kaiserslautern (HRB 2313) USt-Id.Nr.: DE 148646973, Steuernummer: 19/673/0060/3 --------------------------------------------------------------------------- -------------- next part -------------- A non-text attachment was scrubbed... Name: philipp_slusallek.vcf Type: text/x-vcard Size: 441 bytes Desc: not available URL: <https://lists.fiware.org/private/fiware-chapter-architects/attachments/20150308/19b8aa73/attachment.vcf>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy