[Fiware-miwi] Agenda for WP13 (now WP1.5) Meetings at Kickoff

Toni Alatalo toni at playsign.net
Sun Sep 7 11:30:53 CEST 2014


Thanks Philipp for setting those up back then! The basic agenda seems
good to me. We had a meeting with some of the Oulu fi-core folks
during the week and it seemed that basics / main points for the work
that's important for us are in the DoW (Jarkko noted that several
times in the talks).

There sure are many things to discuss .. asset formats, protocols,
different integrations, good optimizations to do next etc. as you
know, what we always talk about :) . Certainly good to think of
relevant issues and how to organize work on them etc.

And ok, we'll think now from the outreach / phase3 pov .. should be
quite clear once get the head around it, i mean because an important
part of realxtend activities also earlier has been to get adoption,
make videos, organize courses, get pilots going etc. Now that happens
in normal business already somewhat ok (also non-reX-core companies,
but application companies like eVocons with UKI architects use in
normal biz hospital planning etc.) and is sure interesting to see how
we get things going with use case projects from elsewhere.

And indeed to think how we should make things good for devs using the
libs, there are many possibilities for improvements on all fronts I
think, but also questions how the already good current things would be
good to present and explain and doc etc.

~Toni

On Tue, Sep 2, 2014 at 9:35 AM, Philipp Slusallek
<philipp.slusallek at dfki.de> wrote:
> Hi all,
>
> Below you find the current allocation of time for our WP1.5 sessions (2x
> 4h). I actually have no idea what we should do in this long time frame
> and would expect us to use more like 2x 2-3h, see agenda at the link
> below, we can extend it if we expect to need more time).
>
> So please let me know if there are specific topics that you would like
> to discuss for FI-Core. Remember that the focus in this project is on
> support for Phase-3 partners.
>
> A first draft of our agenda is now at
> https://docs.google.com/spreadsheets/d/1ARSL4SG1APBYcvLC_o3Blz2UWv3N_MC_m7rgkT8DeFQ/edit#gid=76347424
>
> From my perspective after a general startup and review of what we plan
> to be doing, we should focus in the first part on how we would like to
> interact with the IoT, the Media, the App, and the Robotics/Middleware
> groups in FI-CORE, which seem to be the ones most relevant for us. This
> will also help us having a meaningful discussion in the joint sessions,
> which will take place between the first and the second time slot for our WP.
>
> I have set up a few joint session with those other groups already so we
> can first discuss this briefly internally, then go into the discussion
> with the other groups, and finally have a review and possible decisions
> intenally again.
>
> For more info on the Kickoff please see the (master) document at:
> https://docs.google.com/spreadsheets/d/1jdKXMES-b4Vp3jb8612qn53psXzmyygP8yqAFmR2EJo/edit#gid=1273878550
>
>
> Best,
>
>         Philipp
>
> -------- Weitergeleitete Nachricht --------
> Betreff: [Ficore-kick-off] Proposed WPs Time Slots (Sessions) and
> Progressing on Agendas - request for action
> Datum: Mon, 01 Sep 2014 13:33:28 +0000
> Von: MANUEL ESCRICHE VICENTE <manuel.escrichevicente at telefonica.com>
> An: ficore-kick-off at tid.es <ficore-kick-off at tid.es>
>
> Dear Work Package Leaders,
>
> Please, access the link below to outline your WP's agenda.
> https://docs.google.com/spreadsheets/d/1ARSL4SG1APBYcvLC_o3Blz2UWv3N_MC_m7rgkT8DeFQ/edit#gid=1429886323
>
> Time slots: First proposal:
> WP 1.4 and WP 1.1 are running on Tuesday afternoon, in plenary sessions.
> Stream 1 - From WP1.2 to WP1.8 are running in parallel Wednesday and
> Thursday Morning. Their time slot is 8 hours, 4 hours each day.
> WP2.1, WP2.2, WP3.1, WP3.2 and WP3.3 are running in parallel Wednesday
> and Thursday Afternoon. Their time slot is 6 hours, 3 hours each day.
> WP 4.2 - 2 hours in plenary session, Friday morning, last day
>
> Cross Session, they are pending of allocation.
>
> Request:
> I need WP Leaders to assess the initial time slots are fine for you, or
> you wish to make them shorter (o... larger).
> Once WP session length are estimated, please, update the agendas "Time
> Slots" fields so that I can propose time slots for Cross work package
> sessions.
> Please, WP Leaders, you can state/propose topics for your Work Package.
> I assume on Tuesday Morning you'll be reviewing them with Juanjo during
> the WPL/WPA Work Session.
>
> Let me refresh that I plan to update the number of attendees, and
> allocate concrete room numbers depending on your input on the Attendee
> List (column E) in the link below read this afternoon at 16:00 CET as
> informed this morning.
> https://docs.google.com/spreadsheets/d/1jdKXMES-b4Vp3jb8612qn53psXzmyygP8yqAFmR2EJo/edit#gid=1953510570
>
> Thanks for cooperation!!
>
> Kind regards,
> Manuel
>
>
>
> ----------------------------
> Manuel Escriche Vicente
> Agile Project Manager/Leader
> FI-WARE Initiative
> 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/>
>
>
>
> --
>
> -------------------------------------------------------------------------
> 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
> ---------------------------------------------------------------------------
>
>
>
> _______________________________________________
> Fiware-miwi mailing list
> Fiware-miwi at lists.fi-ware.org
> https://lists.fi-ware.org/listinfo/fiware-miwi
>



More information about the Fiware-miwi mailing list

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