Hi all, As I already mentioned to you, the FI-PPP AB will meet on December 15th and this meeting will be focused on trying to select a number of topics for the first Open Call to be issued by FI-WARE by the end of January. Following there are a couple of emails I have sent to members of the FI-PPP AB as preparation for this meeting (please read them bottom up) . Note that there is not just homework for UC projects but also for us regarding identification of topics for the Open Call. Therefore, those chapters that had identified some topics for the first Open Call are requested to provide their input following the proposed schedule. As I have already mentioned to the UC projects, please try to be pragmatic and include only those things that are rather clear to you. Don't hesitate to ask any question you may have. Best regards, -- Juanjo -------- Original Message -------- Subject: Re: Next FI-PPP AB agenda and IMPORTANT homework related to identification of topics for the first Open Call Date: Tue, 06 Dec 2011 22:44:46 +0100 From: Juanjo Hierro <jhierro at tid.es><mailto:jhierro at tid.es> To: ab at fi-ppp.eu<mailto:ab at fi-ppp.eu> <ab at fi-ppp.eu><mailto:ab at fi-ppp.eu> Hi, Note that I have created a separate sheet per project within the spreadsheet. Columns are for voting. You should create the entries in the corresponding sheet. IMPORTANT: Please try to concentrate on what is the highest priority for you and be selective. It's not just a matter of copying all your requests in the FI-WARE tracker. We are going to use this tool in order to find the first list of topics that will go to the first Open Call. But there will be others as you know (at least one, I'm looking for more). Selecting a topic also implies a commitment on behalf of both FI-WARE and the supporting UC projects to work on the related Themes/Epic (*) up to refine them into Features that a) would become part of FI-WARE backlog and b) would be part of the documentation available to submitters of the Open Call. Best regards, -- Juanjo (*) - In general, entries in the "Unclassified Themes/Epics/Features backlog" should have been labeled as either Themes or Epics. Labeling an entry as a Feature or a Story means that there is a development team that can commit to deliver a product that implements the described functionality within the duration of a FI-WARE Release (three consecutive Sprints long) or the duration of a Sprint (one month long), respectively. UC projects should be careful labeling entries in the Unclassified Themes/Epics/Features backlog as Features or Stories because it would be interpreted as the UC project can actually deliver a product in a Release/Sprint timeframe, even if FI-WARE partners were not able to do so. On 06/12/11 20:54, Juanjo Hierro wrote: Hi all, As you know, the next FI-PPP AB (virtual) meeting is scheduled for Dec 15th. It was scheduled to start at 09:00am CET but I belive that duration was not established. I believe that, due to the relevance of the topics, we should spent 4 hours, with a programmed break of about 20 mins in between. So please plan it to take place from 09:00am CET until 13:20pm CET. I believe we should just focus on agreeing on a list of topics for the first Open Call, leaving other potential topics aside. Therefore, my proposal for the agenda is that we cover one proposed topic after another, in a similar way we made it for some of the topics during our last face2face meeting, trying to make a decision on whether we should include each topic in this first Open Call or not. In order to be effective, I would suggest that we place the topics to discuss in a shared Google docs spreasheet prior to the meeting. I have created one inspired in the excel spreadsheet we used during our face2face meeting in Munich: https://docs.google.com/spreadsheet/ccc?key=0AqGGeaQGro3fdHFLUXozQU9lem5rWVRBeS02czJmNlE (note: anyone who gets access to this URL link will be able to edit the contents, so please bear this in mind when sharing it !) Following are the ACTION POINTs we have to complete prior to the meeting: * UC projects and FI-WARE: * to create entries in this spreadsheet linked to proposed topics * sharp deadline: Monday Dec 12, 09:00am CET (better if earlier, so that rest can evaluate, note that FI-WARE is already evaluating several of your requests) * UC projects and FI-WARE: * to cast their positioning in the spreadsheet regarding updloaded topics (must-, should-, would-, won't- use) * sharp deadline: Wednesday Dec 14, 19:00pm CET Please complete the info about each row in the spreadsheet so that we can easily navigate to the more detailed info from there. One IMPORTANT remark: I believe we should be rather strict and just select those topics for which we can actually formulate a complete and detailed request for proposal. I mean topics for which we can provide a detailed description, in terms of list of well-described Feature entries in the FI-WARE backlog, before the call is issued, that is, end of January 2012. Note that not including a topic in this first Open Call doesn't mean that we refuse to include it in FI-WARE. We may go for postponing a given topic to the next call, thus devoting enough time to refine the features. I have formally asked to our PO whether it would be feasible to split the first Open Call into two subsequents subcalls, the first still planned by end of January and the second by end of February or mid-March. This would be, IMHO, the most pragmatic way to go. Cheers, -- Juanjo ________________________________ 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/fiware-wpa/attachments/20111206/07a0acd1/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy