[Fiware-technical-committee] Questions before launching the call for candidatures to be elected as member of the FIWARE TSC

[Philipp Slusallek]

Hi,

Am 06.06.2016 um 11:58 schrieb Juanjo Hierro:
>   * How do we expect that the "Interface to Networks and Devices"
>     Chapter will evolve?  I haven't seen any active participation in
>     FIWARE TSC meetings so far ...

I may be a bit biased here, so take it with a grain of salt:

We (DFKI) have pulled back from the Middleware activities as we saw that
it will not be broadly useful within FIWARE and was not addressing were
we wanted to go originally. We are pursuing these original ideas in
German projects now. Also, there seems to be little to no involvement in
FIWARE from those partners as far as I can see.

The Network aspects seem to gone completely now

Originally, I was trying to get into closer context with the robotics
guys but that was never successful.

So in summary, it seems that there is too little activity and commitment
to maintain this chapter. To be blunt: I am not even sure it is worth
maintaining these GEs in the context of FIWARE.

>   * Shouldn't we integrate the FIWARE Ops chapter into the FIWARE Lab
>     chapter?   I tend to see activities within the FIWARE Ops chapter as
>     activities very much linked to the FIWARE Lab, actually dealing with
>     creation of tools used in FIWARE Lab operations.

This suggestion seems to make much sense to me, in general, but I do not
know the internal very well.

>   * I understand that the FIWARE Community Support Tools chapter
>     comprises both the FIWARE Catalogue and Academy

Makes sense. I think there is more we could do here to promote FIWARE to
the wider developer community. The QA testing seems very important as
well and should be better advertised.

But at the end what we need are more great examples, success stories,
etc. I have seem few thing come out from the Accelerators in terms of
reusable code examples, libraries, etc. This is understandable as the
Startups do not want to publish what they have done. However, our demo
activities in FI-Core where killed because it was argued that others
where doing it and they did not.

I see this as a main issues in promoting FIWARE in the past and still
right now. I would argue that we should invest in creating more exciting
demo and other examples and publish them widely. Can we allocate
resources for that?

>   * Shouldn't we define a FIWARE QA Lab chapter since we aim at carrying
>     out this QA activities aside (although obviously connected) to the
>     chapters? 

I think this is a really good idea and we should push for more of that.
This would actually have nice synergy with the demo activities as we
would get more examples code for testing and such.

I think such activities would bring GEs and partners in FIWARE much
close together as well.

BTW, there are really nice research approaches for automated testing of
even unknown code (e.g. here in Saarbrücken by Andreas Zeller). This
might be interesting for a future call in the context of FIWARE.

>   Please feel free to share any other question you believe it is worth
> discussing regarding the taxonomy of FIWARE Chapters.  

It seems useful to jointly explore the upcoming EU deadlines for joint
proposals from within FIWARE.


Best,

	Philipp
> 
>   Best regards,
> 
> -- Juanjo
> 
> ______________________________________________________
> 
> Coordinator and Chief Architect, FIWARE platform
> IoT Unit, 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
> 
> 
> _______________________________________________
> Fiware-technical-committee mailing list
> Fiware-technical-committee at lists.fiware.org
> https://lists.fiware.org/listinfo/fiware-technical-committee
> 

-- 

-------------------------------------------------------------------------
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)
VAT/USt-Id.Nr.: DE 148 646 973, 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-technical-committee/attachments/20160608/d9238a12/attachment.vcf>