Thanks Philipp for all your considerations!!
1 - About sound I informed we are using the regular voice channel, which is powwownow. So everybody attending the demo sessions can connect there. This sound channel is stable along the sessions. No need to change. There shouldn't be eco problems since we use it very frequently. Anyway, I'll request attendees to mute their mics when connecting. I also assume we are trying to cooperate, and do things to overcome difficulties and not the other way around.
2 - About image: screen-sharing, I'm attending meetings with all groups, and they all have their own tools for this purpose. Normally it's an endpoint to which you can get connected, so I don't see why it's so difficult to connect to the next end point with your browser 5 minutes before the next presentation starts.
Perhaps it's more different for your chapter with specific requirement. Then, hang-out might not work, then I'd appreciate you find a solution instead of imposing them to all others.
3 - Well, it's the first time we do it. We need to keep a learning attitude. I doubt everything will go perfect.
4 - Attendees: I don't want to make attendance mandatory. If you are attending all sessions, it's fine you write your name in the first session and add ALL-SESSIONS.
I think partners should have a natural interest for the demos. Ilknur already subscribed to all of them in advance. I've already done it but I add as an example the scheme just mentioned.
For example, FIOPS is sharing a demo on how to create a FILAB from scratch, and how to deploy GEIs with the tool. It should catch attention by itself immediately. Or IOT is presenting FIGWAY tools showing how to create and connect virtual sensors, which I find very interesting as well. I hope to collect all input about presentations during today.
5 - Demo's focus is on progress and to highlight what is news, obviously. But at the same time we want to make them interesting to the audience. So it's a balance of values.
I hope I expressed myself clearer now, and this approach can be shared, at least until I get evidence it doesn't work.
Thanks for cooperation!!
Kind regards,
Manuel
-----Original Message-----
From: Philipp Slusallek [mailto:philipp.slusallek at dfki.de]
Sent: viernes, 28 de noviembre de 2014 6:39
To: MANUEL ESCRICHE VICENTE; fiware-chapter-leaders at lists.fi-ware.org
Cc: fiware-chapter-architects at lists.fi-ware.org
Subject: Re: [Fiware-chapter-architects] Demo Sprint 4.1.2 Meeting organisation
Hi,
Sorry, one more thing:
I have asked before but am still not really sure what demos you would like to see and who should attend: In the WebUI call, I understood you that this is to update all the other chapters on what kind of NEW stuff is happening in each chapter. This only makes sense if everyone is there for all the presentations.
However, this is inconsistent with having us to sign up for each of sessions individually. So you have me confused: Do you want all chapter leader/architects to be there for all presentations or should we just select what we are most interested in?
The latter might help with the screen sharing by lowering the number of people attending but might run counter to what I thought the goal of the meeting is.
So for completeness, here is what I think would make sense:
Everyone of us attend all other sessions (requiring only a single list of attendees). The demos are to highlight what is NEW and what the other might not know yet. This can be rather short in some cases and might be longer for some of the recent additions, others know little about yet (e.g. robotics). In particular that might means that not all chapters will be using all the alloted time for their demos.
Is this what you want?
Then I would actually argue for running the demos next to each other instead of distributing them over the entire time. This makes sense, particularly, if all of us would attend all of the sessions and would minimize dead time in between them. But that might be to late now?
Just my 2 cents.
Philipp
Am 26.11.2014 um 18:07 schrieb MANUEL ESCRICHE VICENTE:
> Dear Partners,
>
>
>
> Let's try to progress on organising the demo meeting.
>
>
>
> Please, find below the link to the draft agenda
>
> https://docs.google.com/document/d/1d9rAI-Ysluuht-B_aDschH7AT2m8CX1XSj
> d71CIgeQU/edit?usp=sharing
>
>
>
> It proposes time and structure for the demos.
>
> It identifies partners involved for each chapter.
>
>
>
> By Friday I'd appreciate knowing from the chapter leaders who are the
> presenters, the demo details as title or brief description of what
> will be presented, links to any material needed for the presentation,
> and the connection end point.
>
>
>
> I propose holding the regular voice channel open, and to connect to
> the tools used by presenters offered in the connection end points as
> the sessions advance.
>
> Doing it this way, it will allow attendees to connect them 5 minutes
> before swapping presentations. This preparatory step can be done silently.
>
>
>
> I understand that depending on the presentations the screen-sharing
> tool's requirement can be different. Philipp made me aware that normal
> screen-sharing tools refresh content each half a second. So some tools
> may not be appropriate depending on the demo's content.
>
>
>
> Please, select the tool appropriate for your demo. Additionally, you
> can provide in the document links to videos for partners to download
> and see by themselves while the presenter gives explanations.
>
>
>
> Besides, screen-sharing tools have also a limit for connections; being
> 25 users the number for regular Joinme and GoToMeeting licences.
> Please, state your attendance to the sessions so that we can try to
> organise it better.
>
>
>
> Well, It's the first time we organise it. Let's see how we do and try
> to learn and improve as we go.
>
>
>
> On Friday, if requested I'll be available for trials during some time
> slots, others I have already scheduled some sprint closing meetings.
>
>
>
> I hope you find sensible this first approach.
>
> Thanks for cooperation!!
>
> Kind regards,
>
> Manuel
>
>
>
> ----------------------------
>
> Manuel Escriche Vicente
> Agile Project Manager/Leader
>
> FI-WAREInitiative
> Telefónica Digital
>
> Parque Tecnológico
>
> C/ Abraham Zacuto, 10
> 47151 - Boecillo
> Valladolid - Spain
> Tfno: +34.91.312.99.72
> Fax: +34.983.36.75.64
> http://www.tid.es <http://www.tid.es/>
>
>
>
>
> ----------------------------------------------------------------------
> --
>
> 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-chapter-architects mailing list
> Fiware-chapter-architects at lists.fi-ware.org<mailto:Fiware-chapter-architects at lists.fi-ware.org>
> https://lists.fi-ware.org/listinfo/fiware-chapter-architects
>
--
-------------------------------------------------------------------------
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
---------------------------------------------------------------------------
________________________________
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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-chapter-architects/attachments/20141128/70efcbae/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy