Dear Stefano,
Yes this discussion happens again and again because first we have a request from EC and it is also expected to provide answer at the steering board level regarding exchange with IERC and explaining that something will happen sometimes is clearly not the right answer. Explaining that decision and processes are planned for the end of the year while we have the request from EC since October 2014 is not ok and we have to show that we are working on it. And explanations are expected for Net Future event at least for IoT as explained many times. There is here another issue which has nothing to do with GEis but also how it could be possible for FIWARE to host IERC projects like we did for Accelerators… And I do not have any answer for this point.
I do not expect that we have already processes in place for that but relying on some documents that nobody commented (and I ‘m really not sure that all WPL received them with the point to comment them) and that sharing good practices is a positive issues to define how we could deal with this issue. Dealing with Architecture which has no more activity in the programme and waiting for new processes to be define and to be tested with some example is also not a clear decision the project took previously because the point was never really discuss. The different point of view from Philippe or Alex is an answer that this point is unclear and I’m asking for a concrete meeting to discuss this issue.
BR
Thierry
De : stefano de panfilis [mailto:stefano.depanfilis at eng.it]
Envoyé : lundi 9 mars 2015 10:21
À : NAGELLEN Thierry IMT/OLPS
Cc : Philipp Slusallek; Alex Glikson; fiware-chapter-architects at lists.fi-ware.org; fiware-chapter-leaders at lists.fi-ware.org
Objet : Re: [Fiware-chapter-leaders] How to integrate other GEis into FIWARE
dear thierry and all,
i'm surprised about this discussion again and again .... and again.
i mean severak time we have discussed this and some principles have been already agreed when we discontinued some old geis and not allowing them to be geris.
the principles are:
1. we have created two categories of gei: fiware and incubated. incubated are those who will be put in a different section of the catalogue and and only if the architecture board will consider them suitable to ge fiware they can be fully integrated. of course before the ab will take them on bord they must comply with all the fiware standard rules, i.e. they must be os not viral licence and allowing free usage as a service, they must have royalty free specs, and where applicable they can offer rest apis.
2. in the incubated category also fall the "seis" whishing to be geis coming from the uc projects.
3. the architecture board is not us, but that of the fiware opens source community which will be operative within june. in the principles of such community which you, and alex, should well know as the doc is available since 8 oct 2014 i is clearly stated that the the ab will composed by election from the base of active contributors, i.e. not the fi-ware projectm, but the fiware community: i.e. openness and transparency.
concerning the other questions, which somehow involve also philip although he should know the situation as discussed and agreed during various wpl calls, the hosting of training material, the fiware academy is already ready to host courses from the ucs, and thus from other sources, but still nobody provided material of good quality...
this clarifies the status of discussion since now as also many times already made clear by juanjo, and this also is my personal thinking.
ciao,
stefano
2015-03-09 8:55 GMT+01:00 <thierry.nagellen at orange.com<mailto:thierry.nagellen at orange.com>>:
Hi All
To answer Alex, for IoT side we cannot wait because EC was asking me and Carlos how IERC projects could be hosted behind FIWARE. What I have emphasized is that we could have GEis (this is planned with GEris) so first step is to analyze how some of these results could be GEis. For sure we need a process and a board to validate these components which are not new but replicate what we have described.
Integration of new GEs is much more complex because of new functionalities/features and Architecture impact. The FIWARE technical board should be able to evaluate and discuss these points but again we need a clear process and we can use also current project to check how this process will work properly in future federation.
I fully agree with Philip that some results from UCs should also be integrated but I'm not so sure that FIWARE is the only one which did no effort for integration. I think that UCs were also part of this false equation but things are evolving and with Accelertors and SMEs, I expect we could be on the same page.
But we have some difficulties to manage our own GEris so the first issue is really to define the process with internal actors who have to contribute. I think this could be a task for Sustainability WG.
BR
Thierry
-----Message d'origine-----
De : fiware-chapter-leaders-bounces at lists.fi-ware.org<mailto:fiware-chapter-leaders-bounces at lists.fi-ware.org> [mailto:fiware-chapter-leaders-bounces at lists.fi-ware.org<mailto:fiware-chapter-leaders-bounces at lists.fi-ware.org>] De la part de Philipp Slusallek
Envoyé : dimanche 8 mars 2015 15:16
À : Alex Glikson; fiware-chapter-architects at lists.fi-ware.org<mailto:fiware-chapter-architects at lists.fi-ware.org>; fiware-chapter-leaders at lists.fi-ware.org<mailto:fiware-chapter-leaders at lists.fi-ware.org>
Objet : Re: [Fiware-chapter-leaders] How to integrate other GEis into FIWARE
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<mailto:glikson at il.ibm.com> | Phone: +972-4-8281085<tel:%2B972-4-8281085> | Mobile:
> +972-54-6466667<tel:%2B972-54-6466667> | Fax: +972-4-8296112<tel:%2B972-4-8296112>
>
>
>
>
>
> From: Philipp Slusallek <philipp.slusallek at dfki.de<mailto:philipp.slusallek at dfki.de>>
> To: thierry.nagellen at orange.com<mailto:thierry.nagellen at orange.com>,
> "fiware-chapter-leaders at lists.fi-ware.org<mailto:fiware-chapter-leaders at lists.fi-ware.org>"
> <fiware-chapter-leaders at lists.fi-ware.org<mailto:fiware-chapter-leaders at lists.fi-ware.org>>,
> "fiware-chapter-architects at lists.fi-ware.org<mailto:fiware-chapter-architects at lists.fi-ware.org>"
> <fiware-chapter-architects at lists.fi-ware.org<mailto: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<mailto: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<mailto: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<mailto: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<mailto: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<mailto: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
---------------------------------------------------------------------------
_________________________________________________________________________________________________________________________
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<mailto:Fiware-chapter-leaders at lists.fi-ware.org>
https://lists.fi-ware.org/listinfo/fiware-chapter-leaders
--
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
_________________________________________________________________________________________________________________________
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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-chapter-architects/attachments/20150309/53697808/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy