Hi all, Please find below the minutes of our follow-up confcall last Friday. Any comment or feedback is welcome. Cheers, -- Juanjo Attendees: Laurant (NSN), Denes (NSN), Thierry (Orange), Pier (TI), Maarten (Atos), Juan (Atos), Torsten (SAP), TMB (SAP), Juanjo (TID) Goal: Present the tool and process that has been identified for managing requests on technical support (doubts, feedback) to UC projects (and external world) as well as for managing creation and lifecycle of entries in the uncategorized and FI-WARE backlog. Background: A tool was required for interaction / management of requests to FI-WARE by any external organization (clarification on doubts, delivery of feedback, to the FI-WARE Product Vision and any other topic. A tool was also rerquired for implementing / supporting the FI-WARE Agile approach. AgileFant was initially chosen, proved of little added value and was thus dropped. The current approach is a slim combination of the tracker+wiki approach proposed / implemented so far. Demo: Thomas made a demo of the process/tools to be put in place regarding: + Global Technical Support + Request for entries to the FI-WARE Backlog A tracker tool has been defined for both so that for any request (technical support or for entries to be added in the backlog) a ticket is created. Trackers in FusionForge allow to manage the lifecycle of a ticket and create tasks a given points in time. Thomas elaborated on both trackers, starting first with the one dealing with Global Technical Support. Questions during demo about Global Technical Support: * Who should receive the automatic email once a ticket has been opened ? After some discussion, we agreed to go for a centralized approach in a first approach (tickets are assigned to caretakers by Admin users that will be Juanjo, Thomas and another person from TID who will join to support management activities in the project) and then decentralize (caretakers can assign/re-assign tickets themselves) if we find out the approach doesn't scale * Concern about combining task management tool and tracker instead of just a tracker was raised by Torsten. Why isn't a ticket to be handled by each WP created in their tracker system once a ticket for Global Technical Support is created ? Answer: that is actually the approach we would recommend for handling requests for features in the FI-WARE Backlog (see below), but we didn't want to go so far regarding handling of Global Technical Support requests. It would be up to the WPLs to decide whether handling of the tasks assigned to them should lead to creation of a ticket on their own WP tracker or not. Agreed to follow this approach for the time being. If it happens that all tickets on the Global Technical Support tracker lead to creation of a ticket in a tracker defined by WP project, then we will reconsider and check how to automate the ticket transference. Then a demo about management of requests for entries in the FI-WARE Backlog was made. A tracker linked to the FI-WARE project in FusionForge will be configured that will deal with request for features regarding Platform Enablers (still uncategorized). UC projects will be allowed to create tickets on that tracker and these tickets will be assigned to caretakers (WPLs/WPAs) by Juanjo, Thomas or the TID person mentioned before. Also a task to be carried out by caretakers will be linked to the ticket which will consist in discussing with the UC projects whatever is needed to first determine whether the feature fit within the scope of FI-WARE or not (i.e., should be considered as a feature of a "Common Specific Enabler" as opposed to "Generic Enabler"). If it is agreed that it may be linked to a FI-WARE GE, a ticket should be created in the corresponding FI-WARE Chapter's backlog (to be setup at the corresponding chapter project in FusionForge). It was pointed out that there will be several trackers. Backlogs will map to Trackers and Backlog entries will map to tickets on the corresponding trackers. Linked tasks may well map to tasks in Agile methodologies. There will be one for "uncategorized platform enablers" which will be the one where requests will be gathered and analyzed (request may come from UC projects as well as any other community) . On the other hand, there will be a tracker for the backlog linked to each of the FI-WARE chapters. One of the advantages to have separate trackers/backlog linked to "uncategorized platform enablers" and to "FI-WARE Chapters" is that we can assign different roles and privileges for UC projects in one case and the other. Thus, for instance, UC projects will be able to create tickets on the tracker helping to handle requests for entries in the FI-WARE Backlog (that is, the "uncategorized platform enablers" backlog) but not directly in the FI-WARE backlog(s) itself. The WPLs/WPAs present at the confcall provided a positive feedback on the solution that was presented during the confcall. So no objection to follow with the plan to implement the proposed processes and tools was raised. Thomas and Juanjo expect to get a final configuration setup during the week starting on September 5 and be able to make a general presentation to all members of FI-WARE during the plenary meeting in Turin. ________________________________ 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/20110905/c0e1196f/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: jhierro.vcf Type: text/x-vcard Size: 429 bytes Desc: not available URL: <https://lists.fiware.org/private/fiware-wpa/attachments/20110905/c0e1196f/attachment.vcf>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy