[Fiware-sustainability-proposal] Thoughts regarding approach on the description of the FIWARE evolution and technical support WP

[stefano de panfilis]

dear juanjo,

the idea of goal orientation is certainly better although we need to define
why such goals and not others, text which certainly requires a lot of good
effort and brain.
let's understand where this direction will drive us, but i'm positive with
this approach.

a question: is this wp also responsible for level 3 support? if yes we need
a task for this which by definition cannot be connected to the "goals"
tasks. eventually such support should be accounted to wp1.

ciao,
stefano

2016-03-27 21:00 GMT+02:00 Juanjo Hierro <juanjose.hierro at telefonica.com>:

> Hi all,
>
>   I would like to share my thoughts regarding the approach on the "FIWARE
> Evolution and Technical Support" WP prior to the confcall tomorrow.
>
>   In the very first approach, we were considering to structure this WP so
> that tasks were defined for each of the most relevant WPs within FIWARE
> were indeed still we considere there were aspects about which further
> evolution (including better integration among chapters) was required.
>
>   This might be a coherent way to organize contents but, on the other
> hand, I believe we all agree like it sounds very much like "continuation of
> FI-Core", i.e., it sounds like we ask for funding of chapter activities, no
> matter what, and then we try to cover what can be achieved with the
> requested funding.
>
>   As an alternative proposal, we may go for defining a WP where we define
> tasks that are linked to identified needs regarding FIWARE evolution.
> After giving it a though, I believe that this approach is more sensible: we
> know what still requires evolution and what areas should be tackle and
> therefore we require funding for them, independently on what is the chapter
> where work would need to be carried out.   Another benefit is that it would
> not mean an issue if there is work not planned regarding certain FIWARE GEs
> or even FIWARE chapters.   Actually, following this approach this would
> mean that we simply do not foreseen major work in evolution regarding some
> FIWARE GEs and chapters.  Following the task<->chapter approach we had
> initially suggested, the fact that we were not assigning funding to
> evolution of some FIWARE GEs or chapter was something that looked a bit
> weird.
>
>   I have created a new tab "Tasks linked to FIWARE evolution" within the
> spreadsheet we initially created to estimate the funding distribution, and
> defined my list of tasks to be done regarding FIWARE evolution.  I also
> identify the partners involved:
>
>
> https://docs.google.com/spreadsheets/d/1D7LeAkW5IQ-eoFzNhmU5mEbjFHZFZ08adiQfBpG3lPs/edit?usp=sharing
>
>
>
>   I look forward your feedback.  I rather believe that the proposal would
> be more convincing in front of evaluators this way.
>
>   Cheers,
>
> -- 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-sustainability-proposal mailing list
> Fiware-sustainability-proposal at lists.fiware.org
> https://lists.fiware.org/listinfo/fiware-sustainability-proposal
>
>


-- 
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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-sustainability-proposal/attachments/20160328/d3612bc4/attachment.html>