[Fiware-chapter-leaders] [Fiware-chapter-architects] Demo Sprint 4.1.2 Meeting organisation

Philipp Slusallek philipp.slusallek at dfki.de
Fri Nov 28 06:09:59 CET 2014


Hi,

Sorry, I was traveling all day yesterday.

I am very surprised by this "solution". I was actually expecting that
someone tries to centrally do the research and come up with a meaningful
solutions. Since we have several big telcos among the partners, there
should be plenty of expertise on that topic, no?

Are you really sure that it is a good idea to have each partner try to
figure out what is the best method for sharing the demo screen with a
large group of likely 30-40 people (we might get quite some additional
"demo pilots" for this call) and possible also have us buy N separate
licenses to do so?

As I told you, I have some ideas about possible tools but I certainly do
not know what works, have never tried it, and there is little time now
to figure that out until today.

In particular, it will also mean that EACH ONE of us has to set up EACH
ONE of the different tools selected by the other partners between
sometime Friday (likely afternoon) and Monday morning and know how to
use it. A challenge in my perspective.


So may I make a suggestion to better deal with the situation: Since some
partners likely may have experience with such matters already, can those
please send suggestions and pointers to tools that can be used for such
things? In particular, the tool needs to share the screen for fast
full-screen updates to likely 30-40 participants, e.g. running
interactive 3D demos or videos on the screen for some of the demos. As
an important bonus, it should support many of our platforms (Win, OS-X,
ideally including Linux and mobile devices too!).

Please be sure to clearly state requirements (like OS or browser on the
sending and the receiving side, licenses required and cost of them,
limits on the number of simultaneous users, etc.). Maybe this way we can
still try to come up with a good solution and agree on (ideally) a
single one (or at least as few of them as possible). Maybe some partner
also has a license/subscription so others do not have to pay a
subscription/license for this call.


BTW, a very practical issue: Connecting simultaneously through multiple
audio connections (typically on be default in many tools) will create
all sort of nice acoustic feedback loops. Even a single such feedback
loop for one participant will screw up the entire call badly. So with
this "solution" EVERY SINGLE ONE OF US has to make ABSOLUTELY sure that
at most one audio connection (including telephone) is active at all times.

In particular, this means muting the telephone line (generally a good
idea) while starting a new tool that possibly/likely has audio on by
default. Then -- as the first thing -- mute audio manually in that tool.


Best,

	Philipp

BTW, I did not say that all screen sharing tools are that slow but that
some are simply not created for sharing real-time screen content, like
videos or interactive demos -- and especially not with large groups.


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_aDschH7AT2m8CX1XSjd71CIgeQU/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
> 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
---------------------------------------------------------------------------
-------------- 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-chapter-leaders/attachments/20141128/fa28b23e/attachment.vcf>


More information about the Fiware-chapter-leaders mailing list

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