Hi Carlos, Yes, we have it already included in one of the audio-conference I participated and finally didn't discussed. Anyway, I will be available for the tomorrow call, and not in the following one. BR, B From: CARLOS RALLI UCENDO [mailto:ralli at tid.es] Sent: Wednesday, April 18, 2012 11:16 AM To: Moltchanov Boris Cc: fiware-data at lists.fi-ware.eu Subject: Re: [Fiware-data] Update on the deadlines related to software delivery and testbed & other topics for this week call Boris, And that is exactly the reason why we have the 'suggested items' in the follow-up agenda for every week call. Maybe your absence in some previous calls has lead me/us to overlook these issues. Apologies for this. Tomorrow we'll be discussing the tickets to review Siemens proposal (they included this in the agenda and generated an excel file with a proposal for splitting) I encourage you to follow a similar process as I understand it should be easy at this point. In the meanwhile. I'll rescue this thread for next week call and I hope you'll be available then. Thanks in advance for your cooperation. Best regards, -- ------------------------------------------------------------------------------------------------------------------------ Carlos Ralli Ucendo (ralli at tid.es<mailto:ralli at tid.es>) Cell: +34696923588 Twitter: @carlosralli Product Development & Innovation (Telefónica Digital) Telefónica I+D SAU Madrid, Spain ------------------------------------------------------------------------------------------------------------------------ Follow FI-WARE project (Future Internet Services Core Platform): Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: @fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ------------------------------------------------------------------------------------------------------------------------ El 18/04/2012, a las 10:57, Moltchanov Boris escribió: Hi Carlos, Sorry, a wrong misunderstanding that my first phrase of the previous message below may induce. I mean we never have accomplished a discussion about the entries within the backlog starting with IBM and then suspended with no reason despite my reminders. In my case TI tickets are still open to discuss and my mail with suggestion to consider an eventual split into two or more ones remained unanswered. We have still to understand how to answer some tickets, how to edit them in order to reflect the real WP6 situation (split into relevant parts and send the resulting tickets to their respective addressed GE). What is the procedure there, leave the original ticket and create new ones, or close the original ticket and create the new once. Who is in charge to do it? I believe as far as a first grain sorting is done on PL or WPL level such action could be undertaken by the same entity (PL or WPL) or, as from my suggestion very long time ago additionally to a preliminary WPL/PL assignment also to move all the tickets announcement toward entire WP mailing lists, it could be done by a partner leading target GE. In my concrete case the last tickets I've got are related to Pub/Sub GE + a high level application intelligence or IoT specific flavor, thus, logically, I should close those tickets and create new ones with only high level application intelligence or IoT rests respectively and move them to the App.Ecosystem or IoT WPs respectively. Or WPL/PL will take a decision what to do with those tickets once they are closed by me. I remind that leaving the tickets unanswered, unaddressed or with a high-level not relevant comment (so no concrete AP after that and no analysis and/or development) will create a BAD EXPERIENCE shadow to entire FI-WARE due to misuse or "fake" use of tools we're promoting and advertising outside of the project. BR, B From: fiware-data-bounces at lists.fi-ware.eu<mailto:fiware-data-bounces at lists.fi-ware.eu> [mailto:fiware-data-bounces at lists.fi-ware.eu] On Behalf Of Moltchanov Boris Sent: Tuesday, April 17, 2012 6:06 PM To: CARLOS RALLI UCENDO Cc: fiware-data at lists.fi-ware.eu<mailto:fiware-data at lists.fi-ware.eu> Subject: Re: [Fiware-data] Update on the deadlines related to software delivery and testbed & other topics for this week call Dear Carlos, just to remind you - we never have discussed the UC tickets in the backlog, starting with an attempt and then despite my reminders abandoned this. This issue is still open, I think maybe not only for TI. An answer to your&JJ email wrt Loc follows, probably tomorrow. BR, Boris From: fiware-data-bounces at lists.fi-ware.eu<mailto:fiware-data-bounces at lists.fi-ware.eu> [mailto:fiware-data-bounces at lists.fi-ware.eu] On Behalf Of CARLOS RALLI UCENDO Sent: Tuesday, April 17, 2012 5:47 PM To: Fiware-data at lists.fi-ware.eu<mailto:Fiware-data at lists.fi-ware.eu> Subject: [Fiware-data] Update on the deadlines related to software delivery and testbed & other topics for this week call Dear WP Colleagues, As you can check in the mail enclosed below, we have already got the reply from the PO regarding Juanjo's new dates proposal. In comparison to what we discussed in our previous call, software delivery and testbed availability for us are delayed for 2 months. However, for the UC projects it was pretty hard to accept so long delay on our testbed and therefore the current proposal is to shorten the 3 months period that we initially have for the installation from 3 to 1month although I personally believe we will have some extra delay anyway. That would mean that we have basically some 30 days for the installation at some point within Jul-Aug. In the conference this week I will show the final dates for all milestones/deliverables dates that we discussed last week. BTW, I am also taking care of Siemens reminder to me on their proposal for UC project tickets split. After discussing with Juanjo Boris/Tanguy's proposals, he sent an e-mail with some questions regarding the Location platform API. We will discuss this too. All these 3 topics will be part of the agenda of our call on Thu 10:30-12:00. I'll be providing the googledoc tomorrow. Best regards, -- ------------------------------------------------------------------------------------------------------------------------ Carlos Ralli Ucendo (ralli at tid.es<mailto:ralli at tid.es>) Cell: +34696923588 Twitter: @carlosralli Product Development & Innovation (Telefónica Digital) Telefónica I+D SAU Madrid, Spain ------------------------------------------------------------------------------------------------------------------------ Follow FI-WARE project (Future Internet Services Core Platform): Website: http://www.fi-ware.eu Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242 Twitter: @fiware LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932 ------------------------------------------------------------------------------------------------------------------------ Inicio del mensaje reenviado: De: JUAN JOSE HIERRO SUREDA <jhierro at tid.es<mailto:jhierro at tid.es>> Fecha: 16 de abril de 2012 20:03:51 GMT+02:00 Para: "fiware-wpl at lists.fi-ware.eu<mailto:fiware-wpl at lists.fi-ware.eu>" <fiware-wpl at lists.fi-ware.eu<mailto:fiware-wpl at lists.fi-ware.eu>>, "fiware-wpa at lists.fi-ware.eu<mailto:fiware-wpa at lists.fi-ware.eu>" <fiware-wpa at lists.fi-ware.eu<mailto:fiware-wpa at lists.fi-ware.eu>> Asunto: [Fiware-wpa] VERY URGENT AND IMPORTANT: Confirming what in the FI-WARE First Release goes in the testbed by end of July vs end of September Hi all, During the FI-PPP AB confcall today, UC projects' representatives have asked us to confirm that the contents of the Technical Roadmap available on the public wiki rather reflect what we will make available on the FI-WARE Testbed after considering the impact of our proposed FI-WARE overall re-planning. As indicated in the official email I sent to UC projects regarding FI-WARE replanning (was subject "FI-WARE replanning proposal" sent on April 13th), our proposal is that FI-WARE will: Keep delivery of the FI-WARE Testbed in month 15 (end of July) but split deployment of the first FI-WARE Release into two steps, so that a first set of GEs will become available by end of July, but a second set of GEs will become available in an upgrade of the testbed to take place by end of September. Indeed, subsequent upgrades will be planned every three months after end of September, or even more frequently after each FI-WARE Sprint, following an Agile approach. What would come by end of July instead of end of September is described in the FI-WARE Technical Roadmap (http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FI-WARE_Technical_Roadmap). Note that this split into two steps would not apply to all chapters. If no split is declared in the Technical Roadmap for a given Chapter, it means that all GEs in the first release for that chapter are planned to be available by end of July. I have agreed with UC projects that I will send you this mail with a request to confirm contents of the FI-WARE Technical Roadmap on your side. Also that unless no flag is raised by Wednesday EOB, contents for a given chapter will be considered final by Thursday. Please take this request seriously ... changes will be hard to justify afterwards !! Cheers, -- 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<http://twitter.com/JuanjoHierro> FI-WARE (European Future Internet Core Platform) Chief Architect You can follow FI-WARE at: website: http://www.fi-ware.eu<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 ________________________________ 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 Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. <image001.gif>Rispetta l'ambiente. Non stampare questa mail se non è necessario. ________________________________ 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/old-fiware-data/attachments/20120418/7ad19b14/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy