[Fiware-sust-found] Fiware Community principles

Philipp Slusallek philipp.slusallek at dfki.de
Sun May 24 22:53:46 CEST 2015


Hi Juanjo,

I am fully with you here, particularly also with respect to quality and
support (to the same level as we are applying it to FIWARE, of course!).
An yes, we have talked about this many time, what I am missing is some
action :-).

Why not send an official offer to the UCs right now. I know that there
are some potential GEs that are more than willing to start working with
FIWARE right away. We can collect a list, prioritize, and start with a
few as guinea pigs to get the process of the ground and gather some
experience instead of continue doing more "paper work" (some of that is
required, do not get me wrong, but at the end "show me the code
(results)" is a key motto in open source and we can still adapt as we go).

The UCs will not be around much longer. Yes, ideally thing should just
continue as is but we all know that a large disruption of no longer
having a working relation ship will influence things. So setting up some
other structure (not necessarily funded) is important to smooth the step
and create bridges.

I agree also that some of the content SEs are more suited as GEs (some
of them could actually be integrated nicely into the existing GEs). I am
not so sure about the separation of SEs from FIWARE. I actually believe
that one of the biggest issues of the FI-PPP is exactly this separation.
If  we had had a more tight integration between the UCs and FIWARE a lot
more and better results would have been possible.

Maybe this can be organized in other ways as well. But this is certainly
something that can be discussed.


Best,

	Philipp

Am 22.05.2015 um 16:20 schrieb Juanjo Hierro:
>   Importing enablers developed in Use Case projects as FIWARE GEs
> require that they enter the incubation process we are defining.    I
> believe that we have talked about this many times.
> 
>   The decision about the transition from an incubated GE to FIWARE GE
> will be governed by the FIWARE TC although we plan to make it a
> transparent process.   Note that we will introduce some assessment
> regarding sustainability.   As an example, we were thinking in ideas
> like integrating organizations committing to support incubated GEs in
> the Help Desk system so that we can assess their performance responding
> issues raised by the community.   We will also ask for publicly
> available statements about  commitment as well as commercial plans.   
> 
>   It has been a big effort and depuration of the FIWARE GEs catalogue to
> end with a comprehensive set of FIWARE GEs that have a relevant
> commercial support.   We cannot lower the level of ambition/demand on
> new GEs.
> 
>   Of course, a different course of action can be taken for SEs.   There
> I believe things can actually be more flexible.   My personal opinion
> here is that development in specific domains should be placed in the
> hands of organizations who can drive/lead the take up of FIWARE in the
> domains.   In other words, implement some short of delegation.   Of
> course, overall coherence should be monitored (e.g., avoid that enablers
> that may be considered generic and even overlap with existing FIWARE
> GEs, or even incubated GEs, start to be developed in a given domain
> without doing anything).   A good example would be the CSC-OASC in the
> domain of Smart Cities.   Note that I don't believe that some
> content-related enablers should be considered SEs.  Enablers supporting
> Content Management/Processing/Analysis can be mostly considered generic
> enablers and I see then clear candidates for the incubation process.
> 
>   A last work about SEs: they would be searchable in the FIWARE
> Catalogue (you can see this has been taken into consideration in the
> current version in production).   But they won't be FIWARE Generic
> Enablers.   I wouldn't even use the label "FIWARE" to qualify them.   I
> would use the name of the domain (e.g., "Smart Cities SE" or "eHealth SE")
> 
>   I hope we are on the same page.
> 
>   Cheers,
> 
> -- Juanjo
> 
> On 22/05/15 07:36, Philipp Slusallek wrote:
>> Hi Stefano,
>>
>> Excellent, I am looking forward to it.
>>
>> BTW, sorry, if I am raising the topic of UC collaboration repeatedly.
>> But from what I have seen, we are wasting a lot of potential by not
>> integrating the already existing FI-PPP partners as well as we should
>> (of course only where they are willing and prepared -- at least some of
>> them really are!). Those that are interesting (from my perspective) had
>> to (also) look for alternative strategies as there was no clear offer
>> from FIWARE on the table.
>>
>> Instead of waiting to set up the overall structure for external
>> partners, we should already be moving forward, trailblaze, and evaluate
>> with the existing partners the processes we plan to set in place.
>>
>> Just for example FIcontent (as I am most familier with it): There is a
>> lot of feedback and experience in FIcontent trying to set up their
>> FIC2-Lab within the context of FIWARE-Lab (e.g. also including Docker).
>> Both their Web-Based Developer Playground for real-time
>> editing/running/sharing via social networks of GE/SE usage examples or
>> their One-Click deployment of entire arrangements of GEs/SEs (via
>> Docker) is something that would be very interesting also for FIWARE. We
>> should -- at least -- be talking to them about that and planning if and
>> how we can take on board the best of those ideas.
>>
>> I am missing this discussion being driven be FIWARE. However, we must
>> ensure that any such integration is based on an equal playing field.
>>
>> FIcontent has sent to Juanjo an email requesting such closer
>> collaboration, suggesting setting up some direkt links and discussion of
>> the way forward. I very much hope that we as FIWARE will be engaging here.
>>
>>
>> Best,
>>
>> 	Philipp
>>
>> P.S.: For full disclosure, I am involved in FIcontent and (to a much
>> lesser degree) in FITMAN and have co-signed the FIC2 letter to Juanjo.
>>
>>
>> Am 21.05.2015 um 15:55 schrieb stefano de panfilis:
>>> Dear philipp,
>>>
>>> sorry your email lost in the thread....
>>>
>>> as said by joel yesterday was the first interaction with uc projects
>>> and, as an outcome of the meeting, it was agreed us to communicate the
>>> plan we intend to follow to publish and launch the fiware oss community.
>>>
>>> this way they can contribute if they wish.
>>> it is expected to communicate the plan at the very most tomorrow.
>>>
>>> ciao,
>>> stefano
>>>
>>> 2015-05-20 15:37 GMT+02:00 <joel.riga at orange.com
>>> <mailto:joel.riga at orange.com>>:
>>>
>>>     Dear Philipp,
>>>
>>>     Yesterday was the first interaction with other projects (including
>>>     usecase projects ? Stefano could tell us I think).
>>>
>>>     Joel
>>>
>>>     -----Message d'origine-----
>>>     De : Philipp Slusallek [mailto:philipp.slusallek at dfki.de
>>>     <mailto:philipp.slusallek at dfki.de>]
>>>     Envoyé : mercredi 20 mai 2015 13:31
>>>     À : RIGA Joel IMT/OLPS
>>>     Cc : Fiware-sust-found at lists.fi-ware.org
>>>     <mailto:Fiware-sust-found at lists.fi-ware.org>
>>>     Objet : Re: [Fiware-sust-found] Fiware Community principles
>>>
>>>     Hi,
>>>
>>>     Quick question: To what degree has have these plans be communicated
>>>     and coordinated with the use-case projects yet?
>>>
>>>
>>>     Best,
>>>
>>>             Philipp
>>>
>>>     Am 20.05.2015 um 11:36 schrieb joel.riga at orange.com
>>>     <mailto:joel.riga at orange.com>:
>>>     > Dear all,
>>>     >
>>>     >
>>>     >
>>>     > Please find (finally) the document that have been showed yesterday in
>>>     > Brussels during a meeting concerning Sustainability (cross projects).
>>>     > The next coming phase is to take your remarks and expectation into
>>>     > account so that we can be aligned before the creation of such a
>>>     > community. The calendar for the launch of the Fiware community will be
>>>     > distribute soon.
>>>     >
>>>     >
>>>     >
>>>     > Now I will ask to the FIWARE Core Industry Group what method to use
>>>     > for your contribution to enrich the basic elements that are mentioned
>>>     > in the joined document, but also in the reference document that we are
>>>     > still waiting for.
>>>     >
>>>     >
>>>     >
>>>     > Joel
>>>     >
>>>     >
>>>     >
>>>     > logo Orange <http://www.orange.com/>
>>>     >
>>>     >
>>>     >
>>>     > *Joël RIGA *
>>>     > Projets collaboratifs Europe Futur Internet Orange/IMT/OLPS/GS
>>>     >
>>>     >
>>>     >
>>>     > mobile : 0679641748
>>>     > <https://monsi.sso.francetelecom.fr/index.asp?target=http%3A%2F%2Fclic
>>>     > voice.sso.francetelecom.fr
>>>     <http://voice.sso.francetelecom.fr>%2FClicvoiceV2%2FToolBar.do%3Faction%3Ddefau
>>>     > lt%26rootservice%3DSIGNATURE%26to%3D0679641748>
>>>     >
>>>     > joel.riga at orange.com <mailto:joel.riga at orange.com>
>>>     <mailto:joel.riga at orange.com <mailto:joel.riga at orange.com>>
>>>     >
>>>     >
>>>     >
>>>     >
>>>     >
>>>     > ______________________________________________________________________
>>>     > ___________________________________________________
>>>     >
>>>     > 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
>>>     <mailto:Fiware-sust-found at lists.fi-ware.org>
>>>     > https://lists.fi-ware.org/listinfo/fiware-sust-found
>>>     >
>>>
>>>     --
>>>
>>>     -------------------------------------------------------------------------
>>>     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-sust-found mailing list
>>>     Fiware-sust-found at lists.fi-ware.org
>>>     <mailto: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
> 
> -- 
> 
> ______________________________________________________
> 
> Coordinator and Chief Architect, FIWARE platform
> CTO Industrial IoT, Telefónica
> 
> email: juanjose.hierro at telefonica.com
> twitter: @JuanjoHierro
> 
> You can follow FIWARE at:
>   website:  http://www.fiware.org
>   twitter:  @FIWARE
>   facebook: http://www.facebook.com/pages/FI-WARE/251366491587242
>   linkedIn: http://www.linkedin.com/groups/FIWARE-4239932
> 
> 
> ------------------------------------------------------------------------
> 
> Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario,
> puede contener información privilegiada o confidencial y es para uso
> exclusivo de la persona o entidad de destino. Si no es usted. el
> destinatario indicado, queda notificado de que la lectura, utilización,
> divulgación y/o copia sin autorización puede estar prohibida en virtud
> de la legislación vigente. Si ha recibido este mensaje por error, le
> rogamos que nos lo comunique inmediatamente por esta misma vía y proceda
> a su destrucción.
> 
> The information contained in this transmission is privileged and
> confidential information intended only for the use of the individual or
> entity named above. If the reader of this message is not the intended
> recipient, you are hereby notified that any dissemination, distribution
> or copying of this communication is strictly prohibited. If you have
> received this transmission in error, do not read it. Please immediately
> reply to the sender that you have received this communication in error
> and then delete it.
> 
> Esta mensagem e seus anexos se dirigem exclusivamente ao seu
> destinatário, pode conter informação privilegiada ou confidencial e é
> para uso exclusivo da pessoa ou entidade de destino. Se não é vossa
> senhoria o destinatário indicado, fica notificado de que a leitura,
> utilização, divulgação e/ou cópia sem autorização pode estar proibida em
> virtude da legislação vigente. Se recebeu esta mensagem por erro,
> rogamos-lhe que nos o comunique imediatamente por esta mesma via e
> proceda a sua destruição

-- 

-------------------------------------------------------------------------
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-sust-found/attachments/20150524/993b9b75/attachment.vcf>


More information about the Fiware-sust-found mailing list

You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy   Cookies policy