Good morning, Agreed. We should also make sure that the right people would be able to join on the 1st as they may also not be available. Best, Philipp Am 27.05.2015 um 07:07 schrieb Alex Glikson: > I understand that the review/demo meeting might move from 1st to 8th, > due to expected unavailability on the 1st of some key participants > (Manuel published a doodle to verify). Let's see what the final decision > regarding the review/demo meeting is, and then decide accordingly. In > any case, we may need more than one meeting, at this or different time > slot. > > Thanks, > Alex > > > > > > From: Juanjo Hierro <juanjose.hierro at telefonica.com> > To: "fiware-chapter-architects at lists.fi-ware.org" > <fiware-chapter-architects at lists.fi-ware.org>, > "fiware-chapter-leaders at lists.fi-ware.org" > <fiware-chapter-leaders at lists.fi-ware.org> > Date: 27/05/2015 07:57 AM > Subject: Re: [Fiware-chapter-architects] Next FIWARE Architects > meetings > Sent by: fiware-chapter-architects-bounces at lists.fi-ware.org > ------------------------------------------------------------------------ > > > > Hi, > > I have found that the meeting on June 1st would collide with the Sprint > 4.3.2 Review/Demo Meeting ... > > I see two options here: > 1. Move the scheduled meeting to June 15th (we have setup a > mailing list to kick-off discussions in the meantime) > 2. Take the slot from 10:00 to 10:30 assigned to Cloud and merge > it with a discussion that may start at 09:00am so, effectively, we run > the discussion on Cloud containers from 09:00 to 10:30. We can even > start at 08:30. > > > I can live with either option with a slight preference for option 2. > Please Alex, Philipp decide. > > Cheers, > > -- Juanjo > > > > On 25/05/15 08:05, Juanjo Hierro wrote: > Hi all, > > Due to the fact that many of the people relevant for the discussion > planned for today's FIWARE Architects' meeting is traveling this morning > to the FIWARE Developers Week in Vienna, I have moved the meeting to > Wednesday from 11:30 to 13:30. It may happen that we start at 12:00 > rather than 11:30 but this will be confirmed later. > > The two other FIWARE Architects meeting remain the same. > > As summary, for the avoidance of doubts: > > * Wednesday May 27th, 11:30/12:00 - 13:30: revision of architecture to > support federated user account management on the FIWARE Lab > * Monday June 1st, 10:30 - 12:30: support of dockers in FIWARE > Architecture > * Monday June 8th, 10:30 - 12:30: 2nd meeting about POIs > > > Once again, feel free to invite anyone you believe can add value to the > discussions. FIWARE chapter leaders are of course welcome to join. > > Cheers, > > -- Juanjo > > > On 22/05/15 11:20, Juanjo Hierro wrote: > Dear FIWARE architects, > > This is to summarize the topics that will be covered in our next FIWARE > Architecs calls (monday mornings, from 09:30am to 11:00am CET): > > * Monday May 25th: revision of architecture to support federated user > account management on the FIWARE Lab > * Monday June 1st: support of dockers in FIWARE Architecture > * Monday June 8th: 2nd meeting about POIs > > Feel free to invite anyone you believe can add value to the > discussions. FIWARE chapter leaders are of course welcome to join. > > Best regards, > > -- Juanjo > > ______________________________________________________ > > Coordinator and Chief Architect, FIWARE platform > CTO Industrial IoT, Telefónica > > email: _juanjose.hierro at telefonica.com_ > <mailto:juanjose.hierro at telefonica.com> > twitter: @JuanjoHierro > > You can follow FIWARE at: > website: _http://www.fiware.org_ <http://www.fiware.org/> > twitter: @FIWARE > facebook: _http://www.facebook.com/pages/FI-WARE/251366491587242_ > linkedIn: _http://www.linkedin.com/groups/FIWARE-4239932_ > > > -- > > ______________________________________________________ > > Coordinator and Chief Architect, FIWARE platform > CTO Industrial IoT, Telefónica > > email: _juanjose.hierro at telefonica.com_ > <mailto:juanjose.hierro at telefonica.com> > twitter: @JuanjoHierro > > You can follow FIWARE at: > website: _http://www.fiware.org_ <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-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_ > > > -- > > ______________________________________________________ > > Coordinator and Chief Architect, FIWARE platform > CTO Industrial IoT, Telefónica > > email: _juanjose.hierro at telefonica.com_ > <mailto:juanjose.hierro at telefonica.com> > twitter: @JuanjoHierro > > You can follow FIWARE at: > website: _http://www.fiware.org_ <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-chapter-architects mailing list > Fiware-chapter-architects at lists.fi-ware.org > https://lists.fi-ware.org/listinfo/fiware-chapter-architects > > > > _______________________________________________ > Fiware-chapter-leaders mailing list > Fiware-chapter-leaders at lists.fi-ware.org > https://lists.fi-ware.org/listinfo/fiware-chapter-leaders > -- ------------------------------------------------------------------------- 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/20150527/0737ddd8/attachment.vcf>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy