Hi Miguel, yes I understand the situation and I really don't want to compromised all the others deadlines. I undestand that mixed situation is maybe the worst scenario, and I would not go for that. I would propose to postpone deadlines for all the Apps GEs, even if they not need more time. And at the end of August provide content for all the three GEs. With "slight" I meant like below: Let us know if this is applicable for you, or if there are other feasible ways. Regards, Alessandro On Tue, Jul 26, 2016 at 8:36 AM, MIGUEL CARRILLO PACHECO < miguel.carrillopacheco at telefonica.com> wrote: > Dear Alessandro, > > The schedule cascades dates, it is not just the dates that you capture but > the whole lot that maybe compromised by a change. In other words, if the > open specs are late, presumable so will be the manuals, sw delivery etc. a > month later. And although the project finishes in December, the development > chapters come to halt in September. I fear that what you propose is a > mixed situation where we review things when part of the development teams > of the GEris are gone and others are still working. This could result in a > managerial mess - or not, but let us see if the change can be qualified as > "slight":). Can you please explain what the full proposal is? (for all the > deadlines) > > Thanks, > > Miguel > > El 22/07/2016 a las 16:35, Alessandro Portosa escribió: > > Dear Miguel, > in our last Apps weekly call, we discussed about the R5 deadline which we > have to deal with for the next months. > > Most of them are very applicable and we believe there will be no worries > on achive those targets, but we have some doubts on the ones below: > > > > As you know, in Apps chapter we have a new GE (BusinessAPIEcosystem). And > most of its documentation and other related activites, has to be done from > scratch. Also, people cannot work for the entire remaining period because > of their holidays. About other GEs, I think we can handle it more easily, > but I'm not sure if we can match this deadline at the whole chapter level. > > I'm not sure if it is possible to extend this, but I would ask to postpone > these deadline at the end of August. I understand this could > slightly change the deliverable master plan. > > Please let me know if this is applicable for you, and how. > > Many thanks, > Alessandro > > On Thu, Jun 2, 2016 at 12:15 PM, MIGUEL CARRILLO PACHECO < > miguel.carrillopacheco at telefonica.com> wrote: > >> Dear all, >> >> As you are aware, we are getting closer to Release 5 and although there >> are signs that things are moving, it is time to send a reminder >> particularly when the summer holidays are here. >> >> In R4 we needed to explore new ways to deliver results in a more modern >> and saleable format. This motivated changes on the way , and this is >> something that we want to avoid now. We are happy with the results and we >> will keep guidelines as stable as we can; this is why we will basically use >> the same instructions as last year: >> >> - >> https://docs.google.com/document/d/1wa15t2dSEucSA1xD7FyOLpP0ymihYYry0mhALV6GsXU(please >> re-read it, the changes are not major but there are some) >> >> Last year was the transition to a new way of working and we exceptionally >> admitted snapshots on github. As it was warned at the time (also mentioned >> in the guidelines), R5 was expected to be developed working on a day by >> day basis on github. >> >> We have prepared a list of high level deliverables *with the deadlines* >> and the associated guidelines in case it helps to understand what's needed >> at a glance: >> >> - >> https://docs.google.com/spreadsheets/d/1I5UTqhUn86ForyAsk6BMOw6sK9iBkL_SARuE3DvwUss >> >> Manuel will keep his role of agile coach, José Manuel will continue as >> the owner of the software development guidelines and I will be delivering >> to the EC those deliverables not directly managed by Manuel. >> >> Please note that significant deviations from these dates may result in >> negative observations from the coordination for the EC - also if we >> receive results that are not acceptable (example: a template that does not >> work) >> >> Best regards, >> >> Miguel >> >> >> >> -- >> >> Please update your address book with my new e-mail address: miguel.carrillopacheco at telefonica.com >> >> ---------------------------------------------------------------------- >> _/ _/_/ Miguel Carrillo Pacheco >> _/ _/ _/ _/ Telefónica Distrito Telefónica >> _/ _/_/_/ _/ _/ Investigación y Edifico Oeste 1, Planta 6 >> _/ _/ _/ _/ Desarrollo Ronda de la Comunicación S/N >> _/ _/_/ 28050 Madrid (Spain) >> Tel: (+34) 91 312 94 15 >> >> e-mail: miguel.carrillopacheco at telefonica.com >> >> Follow FIWARE on the net >> >> Website: http://www.fiware.org >> Facebook: https://www.facebook.com/eu.fiware >> Twitter: http://twitter.com/Fiware >> LinkedIn: https://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-leaders mailing list >> Fiware-chapter-leaders at lists.fiware.org >> https://lists.fiware.org/listinfo/fiware-chapter-leaders >> > > > -- > > Please update your address book with my new e-mail address: miguel.carrillopacheco at telefonica.com > > ---------------------------------------------------------------------- > _/ _/_/ Miguel Carrillo Pacheco > _/ _/ _/ _/ Telefónica Distrito Telefónica > _/ _/_/_/ _/ _/ Investigación y Edifico Oeste 1, Planta 6 > _/ _/ _/ _/ Desarrollo Ronda de la Comunicación S/N > _/ _/_/ 28050 Madrid (Spain) > Tel: (+34) 91 312 94 15 > > e-mail: miguel.carrillopacheco at telefonica.com > > Follow FIWARE on the net > > Website: http://www.fiware.org > Facebook: https://www.facebook.com/eu.fiware > Twitter: http://twitter.com/Fiware > LinkedIn: https://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 > -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/fiware-apps/attachments/20160726/4d77ca88/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: Cattura.PNG Type: image/png Size: 54209 bytes Desc: not available URL: <https://lists.fiware.org/private/fiware-apps/attachments/20160726/4d77ca88/attachment.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/png Size: 24457 bytes Desc: not available URL: <https://lists.fiware.org/private/fiware-apps/attachments/20160726/4d77ca88/attachment-0001.png>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy