[Fiware-sustainability-proposal] Status and next steps (about Communication and Dissemiantion)

Silvio Cretti silvio.cretti at create-net.org
Sun Apr 10 12:41:28 CEST 2016


Yes task descriptions are aligned with respect to this. So no problem. My
comment was only on the opportunity to have 2 tasks.
  silvio

On Sun, Apr 10, 2016 at 11:53 AM, Juanjo Hierro <
juanjose.hierro at telefonica.com> wrote:

>
>   I believe there are big differences between communication and
> dissemination (whether these differences are outlined in the current text
> description is another story):
>
>   Communication covers:
>
>    - Maintenance of the website
>    - Design and production of contents for the website: pages, blog, news
>    - Activity on Social Networks (Twitter, YouTube, Facebook, LinkedIn,
>    ...)
>    - Design and production of marketing material: flyers, posters, vídeos
>    - Creation of communications (to be published further in news but also
>    to distribute to the press)
>    - Digital Newsletter (although I'm not very fan, I believe nobody
>    reads electronic newsletters :-)
>    - Brand strategy
>
>
>   Dissemination covers:
>
>    - Presence in booths in market events (e.g., Smart City Expo)
>    - Presence as speaker in events
>    - Presence in workshops (e.g., with the EC, to influence on policy
>    WGs, like the ones being setup within the Digital Single Market strategy)
>    - Meeting with other stakeholders to sell them FIWARE, etc. (e.g., a
>    meeting with other industry players to become part of the Foundation, a
>    meeting with an association of SMEs in the agrifood sector to convince them
>    to use FIWARE)
>    - Presence in networking and collaboration events (e.g. collaboration
>    among Horizon 2020 projects)
>
>
>   Within communication, you produce CONTENT.   Within Dissemination you go
> to an event and spread the word.  Flyers you deliver to an event belong to
> communication because they can be reused.
>
>   Hope it helps and I would kindly ask Nuria to double-check whether we
> are on the same page and if task descriptions shouldn't be reviewed
> accordingly.
>
>   We still have to think whether to place "Standardization" as a specific
> task or not.  I'm starting to be more in favour to place a task about
> Standardization in this WP.  Feedback is welcome.
>
>   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
>
> On 10/04/16 11:36, Silvio Cretti wrote:
>
> Dear all,
> completed revision of WP5.
> Main issue I found (just reporting here the comment I put in the doc):
> (there a 2 task one on Dissemination and one on Communication)
>
> *"I have a general comment on the tasks. I am not an expert but do not see
> big differences between Communication and Dissemination. I would suggest to
> keep only one task for both. What I would do instead is to add another task
> on Training if it is not considered in other WP and maybe (but this is more
> a "strategic decision") a task on Exploitation, Innovation and technology
> transfer."*
>
> Now I am waiting for Stefano to funish the editing of WP4. @Stefano,
> please ping me when you completed it.
>   silvio
>
> On Sun, Apr 10, 2016 at 9:29 AM, Juanjo Hierro <
> juanjose.hierro at telefonica.com> 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
>>
>>
>
>
> --
> Silvio Cretti,
> Distributed Computing and Information Processing (DISCO)
> Area Head
> CREATE-NET Research Center
> Via alla Cascata 56 D
> 38123 Povo, Trento - Italy
> email:  <silvio.cretti at create-net.org>silvio.cretti at create-net.org
> Tel: +39-0461-312433
> Mobile: +39-338-6738175
> <http://www.create-net.org>www.create-net.org
>
>
>
> ------------------------------
>
> 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
>



-- 
Silvio Cretti,
Distributed Computing and Information Processing (DISCO)
Area Head
CREATE-NET Research Center
Via alla Cascata 56 D
38123 Povo, Trento - Italy
email: silvio.cretti at create-net.org
Tel: +39-0461-312433
Mobile: +39-338-6738175
www.create-net.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-sustainability-proposal/attachments/20160410/cd591542/attachment.html>


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