[Fiware-sustainability-proposal] Status and next steps

Thomas Michael Bohnert thomas.bohnert at zhaw.ch
Sun Apr 10 20:05:36 CEST 2016


HI Philipp,

Just went over it, looks nicely in line with my thoughts, i.e. perfectly 
in line with the structure that I pasted in. Your application of those 
concepts (i.e. from the papers) looks nice and make sense.

Cheers, Thomas

Prof-Dr. Thomas Michael Bohnert (TMB)
Head of Service Engineering (ICCLab, SPLab)
Zurich University of Applied Sciences
eMail: thomas.bohnert at zhaw.ch
mobile: +41791758136
web: blog.zhaw.ch/icclab, tmb.nginet.de
twitter: tmbohnert
skype: tbohnert

On 04/10/2016 04:29 PM, Philipp Slusallek wrote:
> Hi,
>
> I have written a first full text version for 1.1.2.1 (now called:
> "Transition from an EU project to a stable, true Open Source community").
>
> Because I was not sure where Thomas wanted to go with his list of bullet
> points (apparent mostly from
> http://www.sciencedirect.com/science/article/pii/S0164121213002744), I
> just started from scratch but taking on board some of his points.
>
> Thomas, all please check and feel free to change as you see necessary.
> The direct link is here:
> https://docs.google.com/document/d/1QTuEMSt2Kw1pgD6lVB8tt1KUEFf_nYhi3xiJF50TGIE/edit#heading=h.4hvy4rfs4bbg
>
>
> I have also reviewed the state of Task 3.1 a bit earlier today, which
> looks pretty good already. Will continue working on this.
>
>
> I have a few other things to do now but will be back later.
>
>
> Best,
>
> 	Philipp
>
>
> Am 10.04.2016 um 15:08 schrieb Juanjo Hierro:
>> Hi,
>>
>>    I have integrated the several sections provided by Fraunhofer and
>> Grassroots
>>
>>    I will be dealing with my new assignments as per the ToDos.
>>
>>    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
>>
>> On 10/04/16 09:29, Juanjo Hierro wrote:
>>> Dear all,
>>>
>>>    I have double-checked the status of the proposal and, despite there
>>> are still a lot of content pending, we will get on track if we spend
>>> the necessary time along today.    When all the contributions get
>>> finalized, I'm sure we will be a bit above the 70 pages of limit, but
>>> should not be that difficult to compress.
>>>
>>>    To be more effective in this last phase, I have created a table
>>> where I list the current editors and identify: what they should be
>>> doing NOW, what is next in their duties and what is their queue of
>>> pending tasks.   It is in the Edition cockpit under tab "ToDos editors":
>>>
>>>      https://docs.google.com/spreadsheets/d/1A-TPr4j4b47D4Uye4pAAvuMqaRlOMNmX6Hd2zbUF9Vk/edit?usp=sharing
>>>
>>>
>>>    Based on the above, I believe we don't need the confcall scheduled
>>> for this morning (revision of Section 1, 2 and 3) so I have cancelled
>>> it.   Let's concentrate on writing and proceed as follows:
>>>
>>>    * Everyone is expected to be working in what is declared as "What
>>>      NOW".  If not the case, come to me or place the task they were
>>>      assigned in their queue and replace it for something else.   If
>>>      you are not working on it at the moment and do not plan to work on
>>>      it in the next two hours, please place the task in the placehoder
>>>      for "unasigned taks" and place the time at which you plan to
>>>      resume work in the "What NOW" column.
>>>
>>>    * What comes immediately next in the ToDos of anyone should be in
>>>      the "What next" column.  Rest of pending ToDos will be listed in
>>>      the "In queue" column, in the order you plan to work on them.
>>>
>>>    * If you don't have any current task assigned and feel with forces
>>>      to deal with one of the unassigned tasks, please drop it from the
>>>      list of unassigned tasks and place it in your "What NOW" column
>>>      and start working!
>>>
>>>    * If you feel you are in delay (or will be so that you cannot deal
>>>      with pending items in the queue), then drop them from your lists
>>>      and place them in the list of unassigned tasks.
>>>
>>>    * Whenever you have complete what you had as ToDo in "What NOW",
>>>      please place the item in the list of "Tasks already done" and
>>>      please send an email reporting so the rest of the world know what
>>>      is the task you have completed and what task you will start
>>>      doing.  Then update the spreadsheet accordingly.
>>>
>>>    * I will be double-checking the table to make adjustments as we move on
>>>
>>>
>>>    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
>>
>>
>> ------------------------------------------------------------------------
>>
>> 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
>>
>
>
>
> _______________________________________________
> Fiware-sustainability-proposal mailing list
> Fiware-sustainability-proposal at lists.fiware.org
> https://lists.fiware.org/listinfo/fiware-sustainability-proposal
>



More information about the Fiware-sustainability-proposal mailing list

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