Hi Javier, unfortunately today's coordination call has been postponed to tomorrow at 4pm. I will be traveling, so it would be worth that you UPM attend it, otherwise Davide is going to join in place of me anyway. Probably it will be the right moment to ask the questions below... Cheers, Monica *Monica Franceschini* Solution Architecture Manager *Big Data Competence Center Engineering Group* Corso Stati Uniti 23/C, 35127 Padova, Italia Tel: +39 049.8283547 Fax: +39 049.8692566 Twitter: @twittmonique www.spagobi.org <http://www.spagobi.org> - www.eng.it <http://www.eng.it/web/eng_en/home> *proud SpagoBI supporter and contributor* SpagoBI Respect the environment. Please don't print this e-mail unless you really need to. The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer. Il 05/10/2015 14:27, Davide Zerbetto ha scritto: > > > > -------- Messaggio Inoltrato -------- > Oggetto: Re: [Fiware-apps] [Fiware-chapter-architects] > [Fiware-chapter-leaders] Agile: Planning Sprint 5.1.1 - Proposed Schedule > Data: Fri, 2 Oct 2015 13:47:46 +0200 > Mittente: Javier Soriano <jsoriano at fi.upm.es> > A: Monica Franceschini <Monica.Franceschini at eng.it> > CC: fiw >> FI-WARE Apps (fiware-apps at lists.fi-ware.org) > <fiware-apps at lists.fi-ware.org> > > > > Hi Monica, > > Our main concern about the release 4 is the fact that some Workitems > regarding the delivery of the GE (Image, Blueprint, Academy, Catalogue > and FIWARE Lab deployment) have been removed from Jira. The > justification given to this decision is that we should not make this > work since the GEs will not be maintained in Release 5 (which is not > true in this case, indeed). > > The point is that this work is part of the Release 4, and not making > it may result in a cost rejection of the work done so far. Moreover, > according to the review report, the release 4 must continue as > originally planned: > > /The reviewers recognise the potential value of several GEs that must > not receive FI-Core > funding beyond end of September 2015. By that time, open source > reference implementations > are planned to be made publicly available for all GEs that received > funding, and this is > worthwhile and must therefore go ahead as planned, also for GEs for > which FI-Core funding > will be discontinued at the end of September 2015./ > > In case it is confirmed that we should not make the "FIWAREf Lab" and > "FIWARE Catalogue" parts of release 4 of the Business Framework GEs, > please try to force them to include it in the minutes so that we can > be sure that it is not our fault. > > Please try to emphasize that: > > - The BF GEs will continue receiving support > - The BF GEs are already in the catalogue and it has been said that a > separate section of the catalogue should be assigned to those GES for > which development is stopped by the end of September, so... they will > remain in the catalogue one way or another, won't them? > > /For GEs for which development is stopped by the end of September, the > results must be > kept and published, but it should be clearly communicated that they > are no longer > maintained. A separate section of the catalogue should be assigned to > such enablers (e.g. > in combination with the GEs that are in the incubation process). Until > the end of > September, efforts should be spent in order for these GEs to be > cleaned up, and > documented, in order to increase their chances for sustainability > outside the FI-Core > context (for being taken up by the OSC)./ > > Regarding the Release 5, we want to know how to proceed with the new > "Business API Ecosystem GE" (Business Framework GE) from the point of > view of the FIWARE management (Jira, Backlog items, Roadmap, etc). > This is quite urgent since we are now in the first sprint of the > release 5 and next Tuesday we will have the sprint planning meeting > with Manuel. > > Best regards, > Javier > > > > 2015-10-01 21:58 GMT+02:00 Javier Soriano <jsoriano at fi.upm.es > <mailto:jsoriano at fi.upm.es>>: > > Hi Monica, > > Tomorrow I plan to send to you some questions regarding the way we > should proceed with the "old" Business Framework GEs wrt Release 4 > of FIWARE and how we should proceed with the new Business API > Ecosystem GE wrt Release 5 of FIWARE (i.e. wrt next sprint). > > I tried to ask these questions to Manuel repeatedly during last > week, but he redirected me to Juanjo, who still hasn't give me an > answer. I am very worry about it because at this moment it has > been impossible for us to accomplish with Release 4. > > I would appreciate it very much if you could raise them during > next monday WPL coordination conference call. > > Best regards, > Javier > > ---------- Forwarded message ---------- > From: *MANUEL ESCRICHE VICENTE* > <manuel.escrichevicente at telefonica.com> > Date: 2015-10-01 18:02 GMT+02:00 > Subject: Re: [Fiware-chapter-architects] [Fiware-chapter-leaders] > Agile: Planning Sprint 5.1.1 - Proposed Schedule > To: "fiware-chapter-leaders at lists.fiware.org > <mailto:fiware-chapter-leaders at lists.fiware.org>" > <fiware-chapter-leaders at lists.fiware.org > <mailto:fiware-chapter-leaders at lists.fiware.org>>, > "fiware-chapter-architects at lists.fiware.org > <mailto:fiware-chapter-architects at lists.fiware.org>" > <fiware-chapter-architects at lists.fiware.org > <mailto:fiware-chapter-architects at lists.fiware.org>>, > "gilles.privat at orange.com <mailto:gilles.privat at orange.com>" > <gilles.privat at orange.com <mailto:gilles.privat at orange.com>>, > Pedro Luis Chas Alonso <pedrochas at dit.upm.es> > > > Pedro, Gilles, I’d appreciate receiving confirmation for > proposed meetings scheduled tomorrow > > All other inputs are also welcome! Thanks. > >  > >  > > *From:*fiware-chapter-leaders-bounces at lists.fiware.org > [mailto:fiware-chapter-leaders-bounces at lists.fiware.org > <mailto:fiware-chapter-leaders-bounces at lists.fiware.org>] *On > Behalf Of *MANUEL ESCRICHE VICENTE > *Sent:* lunes, 28 de septiembre de 2015 18:46 > *To:* fiware-chapter-leaders at lists.fiware.org > <mailto:fiware-chapter-leaders at lists.fiware.org>; > fiware-chapter-architects at lists.fiware.org > <mailto:fiware-chapter-architects at lists.fiware.org> > *Subject:* [Fiware-chapter-leaders] Agile: Planning Sprint 5.1.1 - > Proposed Schedule > >  > > Dear Chapter Leaders, > >  > > Please, find below the proposal schedule for the sprint planning > meetings. > >  > > If they weren’t suitable for you, please, propose alternative > sessions on free time slots. > >  > > 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 <tel:%2B34.91.312.99.72> > Fax: +34.983.36.75.64 <tel:%2B34.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 > > > ------------------------------------------------------------------------ > > 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.fiware.org > <mailto:Fiware-chapter-architects at lists.fiware.org> > https://lists.fiware.org/listinfo/fiware-chapter-architects > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/fiware-apps/attachments/20151005/90737231/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: spagobi.jpg Type: image/jpeg Size: 3639 bytes Desc: not available URL: <https://lists.fiware.org/private/fiware-apps/attachments/20151005/90737231/attachment.jpg> -------------- next part -------------- A non-text attachment was scrubbed... Name: Green.jpg Type: image/jpeg Size: 4716 bytes Desc: not available URL: <https://lists.fiware.org/private/fiware-apps/attachments/20151005/90737231/attachment-0001.jpg> -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/png Size: 34380 bytes Desc: not available URL: <https://lists.fiware.org/private/fiware-apps/attachments/20151005/90737231/attachment.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/png Size: 35282 bytes Desc: not available URL: <https://lists.fiware.org/private/fiware-apps/attachments/20151005/90737231/attachment-0001.png>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy