Hi Torsten, This mail is just to inform you that we (Yosu and me) have finished backlog entries upto Release 2.2. All the tickets in the tracker (Use Cases, Features and Epics) has been created, assigned and planned as open, closed or under execution. If i am right, the only activity relating backlog entries pending for us is the creation of Workintems, as it was said in some of the meetings these are created just to inform in which part is working each partner. We also have start working in our open specs, keep waiting instructions from T3.1 Leader since we will have to put in common all composition editor, mediation and execution engine specifications. PD: i dont know why any ticket created in Apps.Mediation is not well assigned to this, since if you filter the tracker by Apps-Mediation you don't get any result, you must filter by "Default" to get the tickets assigned to Mediation... B.R. *Miguel Ángel Huerta * Software Architect Service Engineering & IT Platforms Lab IT Sector Telecom, IT & Media Market Research & Innovation T +34 912148718 F +34 917543252 miguel.huerta at atosresearch.eu <jose-maria.cavanillas at atosresearch.eu> Albarracín 25 28037 Madrid Spain www.atosresearch.eu On 01/31/2012 11:26 AM, Leidig, Torsten wrote: > > FYI > > *From:*fiware-wpa-bounces at lists.fi-ware.eu > [mailto:fiware-wpa-bounces at lists.fi-ware.eu] *On Behalf Of *Juanjo Hierro > *Sent:* Dienstag, 31. Januar 2012 11:22 > *To:* fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu > *Subject:* [Fiware-wpa] Actions Points to be Done > > Dear WPLs/WPAs, > > I plan to deliver more precise guidelines, including some templates > sometime today but probably very late in the evening, effectively to > be ready tomorrow morning because I'm currently very busy finalization > of the publication of the first Open Call which was due by today. > > Apologize for any problem this may cause, but I hope you will > understand. In the meantime, please try to deal with the couple of > urgent points that we revised during last week WPL/WPA meeting (some > of them commented during our joint confcall yesterday). We should > not forget to address them: > > * Provide complete and accurate minutes of the f2f meeting last > week. As announced, Miguel sent detailed instructions to follow > regarding this (based on feedback by some partners, we will change > the place where you should upload them, Miguel will send an email > updating on this). PLEASE don't forget to transform Actions > Points you identified into WorkItems in the corresponding tracker > (your chapter tracker or the FI-WARE-Private tracker). Miguel > will setup a Backlog Management tracker on the "FI-WARE Private" > project so that you will be able to create WorkItems you believe > that need to be addressed and followed-up at FI-WARE global level. > * Complete response to questionnaire distributed by the Testbed > team. This is urgent in order to complete the Testbed design. > * SAP: complete revision of Epics linked to BM&BE GE being > considered in the first Open Call. > * Planning of sprint 4 (this requires the first point regarding > identification of WorkItems to be done) > * Address APs identified during Security plenary session: > o Each Chapter to provide their answers to the questions raised > by the Security team for each of the Security GEs (the sooner, > the better and no later than by end of this week so 3/02/2012) > o Each Chapters to consider integration of Security GEs within > their Chapter architecture and whenever those are needed and > at appropriate level (i.e. architecture level, GE level). As > a first step, this should lead to definition of at least one > Epic by chapter and GEs to reflect this as ongoing work > o Each Chapter to analyze the interaction (sequence) diagram > with the Security Monitoring GE to check, amend/complete and > validate them (there is one for each of the Chapters that was > elaborated by the Security team). This is needed prior > delivery of the information requested by the Security Chapter > (i.e. log, security events, countermeasures, ....) by Security > Monitoring GE (also gets the architecture of the chapter ready > to have this information delivered). The Security chapter will > provide other chapters with information needed by Security > Monitoring GE (also format under which this information has to > be provided) > * Review status of UC project tickets to update them or make some > progress. Don't forget to change the assignee of a ticket to be > the issuer whenever you change the state to "Needs revision by the > issuer". > * Standardization Plan: please check latest requests on the matter > ... there is info pending ! > > Best regards, > > -- Juanjo > > ------------- > Product Development and Innovation (PDI) - Telefonica Digital > website:www.tid.es <http://www.tid.es> > email:jhierro at tid.es <mailto:jhierro at tid.es> > twitter: twitter.com/JuanjoHierro > > FI-WARE (European Future Internet Core Platform) Chief Architect > > You can follow FI-WARE at: > website:http://www.fi-ware.eu > facebook:http://www.facebook.com/pages/FI-WARE/251366491587242 > twitter:http://twitter.com/FIware > linkedIn:http://www.linkedin.com/groups/FIWARE-4239932 > > ------------------------------------------------------------------------ > > Este mensaje se dirige exclusivamente a su destinatario. Puede > consultar nuestra política de envío y recepción de correo electrónico > en el enlace situado más abajo. > This message is intended exclusively for its addressee. We only send > and receive email on the basis of the terms set out at > http://www.tid.es/ES/PAGINAS/disclaimer.aspx > > > > _______________________________________________ > Fiware-apps mailing list > Fiware-apps at lists.fi-ware.eu > http://lists.fi-ware.eu/listinfo/fiware-apps ------------------------------------------------------------------ This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Este mensaje y los ficheros adjuntos pueden contener informacion confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente pueden estar protegidos por secreto profesional. Si usted recibe este correo electronico por error, gracias por informar inmediatamente al remitente y destruir el mensaje. Al no estar asegurada la integridad de este mensaje sobre la red, Atos no se hace responsable por su contenido. Su contenido no constituye ningun compromiso para el grupo Atos, salvo ratificacion escrita por ambas partes. Aunque se esfuerza al maximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no sera responsable de cualesquiera danos que puedan resultar de una transmision de virus. ------------------------------------------------------------------ -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/old-fiware-apps/attachments/20120202/298f02ae/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: blue_strip.gif Type: image/gif Size: 78 bytes Desc: not available URL: <https://lists.fiware.org/private/old-fiware-apps/attachments/20120202/298f02ae/attachment.gif> -------------- next part -------------- A non-text attachment was scrubbed... Name: atos_logotype.gif Type: image/gif Size: 816 bytes Desc: not available URL: <https://lists.fiware.org/private/old-fiware-apps/attachments/20120202/298f02ae/attachment-0001.gif>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy