Thanks for the infos and notes Torsten, despite being ill even -- I hope you get better soon! Manuel, about the errors the backlog review system reports: What is the GEi name we should use for WebTundra? It seems to give an error when I use WebTundra. In JIRA the component seems to be named that. I tried to fix the naming for this old work item that reports the traffic visualization work made in the FIDEMO project / amendment for old FIWARE last year: https://jira.fiware.org:8443/browse/WEB-123 FIWARE.WorkItem.WebUI.WebTundra.CreateTrafficVisualizationForDemo The review for that says: WEB-123WorkItemWebUI.WebTundra.CreateTrafficVisualizationForDemo Closed Major Sprint 4.1.3Toni Alatalo >>> Reference.5 > Test for reference - 4th field: GE-GEI keyword The 4th field is 'WebTundra' so seems that it does not accept it as a GE-GEI keyword? Perhaps there is a bug in the review system? For XML3D it seems to work as for example WEB-248 shows as green and it has the implementation name there similarily (and no GE i.e. 3DUI name anywhere): FIWARE.WorkItem.WebUI.XML3D.Backlog.Review I was checking Torsten's instructions and also the documentation for the naming in https://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/How_to_assign_identifiers_to_FI-WARE_Backlog_entries_%28convention_to_follow%29 But so far have no way to make the checker happy. Also, Tiina just emailed me to inform that they'd gone through Adminotech's all entries with Manuel before her holiday (1,5 weeks ago) and I understood that they'd been in shape then. I don't understand how though as most the WebTundra entries are not according to the naming convention yet -- unless work was lost in the JIRA corruption that happened at one point. For e.g. Synchronization (Tundra) it seems to work, in http://backlog.fiware.org/enabler/Synch-Tundra/dashboard -- those are also named according to the pattern. BTW for the demo deliverables I was also trying to understand how to use the software.create, .deliver etc. but concluded that those are only for actual GE releases. For workitems the documentation says simply: "WorkItem: FIWARE.WorkItem.Chapter.Enabler.WorkItemId" so i went with that single term as the WorkItemId, CreateTrafficVisualizationForDemo .. lacking better ideas. ~Toni On Wed, Mar 11, 2015 at 7:14 AM, Torsten Spieldenner <torsten.spieldenner at dfki.de> wrote: > Good morning, > > I have to cancel today's call. > > Philipp is travelling, and I got ill yesterday. > > I still prepared the minutes. You can find the topics that were planned for > today here: > https://docs.google.com/document/d/1sfUYTdo6DugZeXwQCzd9UYYO_hGAY0k6OOqahi42_To/edit#heading=h.rt0nkx8hmxxg > > Please have a look at it and check what is on the agenda for this week. > > Main topics for today's call would have been: > > > Backlog Review: As already explained by Manuel last week, the the backlogs > of our Enablers (http://backlog.fiware.org) are delivered for review this > month. Please check that your backlog entries are correct and consistent. I > have summarized the steps that need to be done in the minutes document. Some > of the GE already look very good (e.g. GIS Data Provider, RealVirtual > Interaction). Some others still need some updates, as for example WebTundra. > More information in the minutes document > > Demo for Sprint 4.2.3, Release 4.2: As already addressed in the call last > week, the current sprint also concludes minor Release 4.2. We should come up > with a nice demo to demonstrate the features that were implemented in this > sprint. For this, I am going to set up a Google Doc to collect ideas and > plan a possible application. > > POI-Discussion: As Philipp and Stefan are still travelling, this discussion > has to be postponed again. But in one of the last meetings, we started to > consolidate the ideas that were collected in different documents by Oulu and > DFKI in one joint document. We should continue work on this document, so > that as soon as everyone is back, we can just go through this document as > preparation for the discussion > > > > Best, > Torsten > > _______________________________________________ > Fiware-webui mailing list > Fiware-webui at lists.fi-ware.org > https://lists.fi-ware.org/listinfo/fiware-webui >
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy