Dear All, I would propose the following, concerning EPICs: 1. In Wiki the EPICs are introduced by task leaders or the persons delegated by the task leaders, according to this tutorial: http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/How_to_u pload_the_full_description_of_backlog_entries_to_the_Wiki 2. When the entry was submitted to the Wiki, the submitting person informs Thierry/Lorant/Denes about the recent submission 3. In forge the associated ticket will be created by Thierry/Lorant/Denes where the ticket will be assigned to the task leader of the respective chapter. This tutorial http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/How_to_c reate_entries_in_the_%22Backlog_Management%22_Tracker_of_a_FI-WARE_Chapt er describes how that is done This means some centralization but would keep us up-to-date with EPICs that are submitted by requiring from us to take action (so we can't avoid reading the EPIC you created). Concerning what the assignee should do with the ticket, I am still thinking what would be the best approach, but let's concentrate for the moment on EPICs. So the action item following up this e-mail would be for task leaders to: -check the currently existing EPICs in Wiki -make them complete (fill the sections that were not filled yet) -check the EPICs in their entirety and think what is missing from their task perspective (task leader might delegate this to asset owner), include new EPICs if needed and inform Thierry/Lorant/Denes about this Thanks & Br, Lorant -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/old-fiware-iot/attachments/20111005/cffed36d/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy