Hi,
Following are my notes on our last joint WPL/WPA follow-up confcall. Please make any comment if you find there was something missing or wrong.
Best regards,
-- Juanjo
1. Briefing on status of FI-PPP Use Case projects joining FusionForge/FI-WARE and submitting requests
Everything has been setup for Use Case project to join FusionForge/FI-WARE and start submitting their requests for Themes/Epics/Features or simply formulate questions.
The first accounts have been created, but no relevant activity seems to be taking place for the time being.
2. Quick revision of APs identified as next steps during our last joint confcall which has been done:
The following APs have been covered:
* Creation of FI-WARE Private project: soon there will be instructions on how to deal with it.
* Contents of first release of the FI-WARE Product Vision uploaded to the Wiki
* Tutorials defined on the Wiki as part of "Project Handbook" section (which will become the "Project Management Handbook" deliverable)
3. Work still on progress (meaning delay):
We haven't yet finished the work on:
* Description of assets
* Full description of backlog entries (including entries linked to "Question Marks")
* Creation of backlog tickets on chapter trackers
We made a round table briefing on status, each pointing to issues for joint discussion or barriers found we have to solve
Data/Context (Juanjo):
Work in progress. We expect to get everything finished by EOB Tuesday Oct 11.
No issue regarding Wiki, Tracker, tools overall
IoT (Thierry):
No assest description because they are still fully devoted to selection of assets. Expect to reach a conclusion on selection of
assets (first take at least) by end of this week. Consequently, description of assets will not be available until all of this process finishes.
Dealing with creation of entries linked to the Backlog. Could meet deadline on Wednesday October 12th morning.
Team is trying to document a rationale for the selection of assets
Issue with the Wiki: Some partners do not agree that description/documentation of assets become available on the Wiki
Juanjo asked whether there is any task dealing with definition of positioning with regard to relevant standardization efforts (mostly OMA, OGC). Thierry commented this was being addressed.
Apps/Service:
Working in process. No major issue. Fine with deadline Wednesday October 12th morning.
Recommendation: Adopt a convention for the title of the page describing an asset.
Interface to Network and Device:
Late on description of assets. Just a placeholder at this point.
Addressing issue on Cloud-proxy. Should all activities be covered just in the I2ND chapter ? This will affect at least Technicolor because they have to know where to upload information about entries in the backlog.
AP on Juanjo: to comment on mail sent by Technicolor.
Still some concerns about what should be considered as an Epic despite the explanations. Intel partner with skills in Agile has joined that may help so he can be helpful.
Juanjo: please review the hints provided in several emails.
Issue with the Wiki: Sometimes navigation, specially going back to the previous page is a bit cumbersome.
AP on Juanjo: Try to find out whether there is something we can configured on the Wiki for this.
Feel confident to get backlogs entries uploaded on to the Wiki plus tickets on the tracker by Wednesday. Not sure about description of assets which may require a few more days (end of this week).
Security:
Team working to complete the work. Description of assets ongoing driven by the task leads. Also work on Backlog entries ongoing.
Issue with the Wiki: concerns about the fact that some of the info becomes publicly available:
* description of some assets
* detailed description linked to some user stories
Believe that deadline on Wednesday Oct 12 could be met. Major issue is the fact that problems with making some info publicly available on the Wiki may mean some entries may look still empty.
Joint discussion on issues mentioned during the round table and how to solve identified barriers
The main issue is that about public access to information published on the wiki.
Juanjo: We can differentiate and have information not disclosed (the how) while other parts are open (the what). A given entry in the backlog may have contents in the detailed description that
is public (that one we consider enough for a user to understand what we are talking about) while links to hints on the how that will not work if you don't have the proper privileges (e.g., will
navigate to another website that only developers can access to). This shouldn't be a problem.
Everyone seems to feel comfortable with such approach. Still it would be nice to have some resources linked to FusionForge that can be only visible to members of the FI-WARE project.
AP: Juanjo to explain what tools the chapter teams can use to keep part of the information private (e.g., private Wikis)
Some people raised during the discussion the need to have a unstable version of the Wiki which would be private to FI-WARE partners and where editing of the Wiki continuously takes place, while the current become
more stable since it will be available to anyone on the Internet.
AP: Juanjo to come with a process for reviewing contents of the Wiki previous to publish, combining unstable and stable versions of the Wiki.
4. APs on Security Chapter (Pascal):
4.1 Update on revision of Security section within FI-WARE Product Vision by the different chapters
Pascal has no receive any input from the Chapter teams but IoT. AP: Juanjo to send a URGENT reminder to the chapter
leaders
4.2 Pascal to give us update on revised sections dealing description of overall solution for Identity, Access Control and Privacy Management in FI-WARE Product Vision document
Have reviewed but still continue being reviewed. Today EOB will the content of the Product Vision document on the
Wiki will be updated.
4.3 Pascal to provide proposal about date at which virtual workshop with UC projects may be celebrated so that we can call UC projects.
No date yet. Expect to be able to setup a virtual workshops: monday Oct 17, Oct 19, Oct 20. AP: Juanjo to share with
UC projects and create a doodle for them to cast their availability.
5. Additional APs (not still critical, probably best to be handled in FI-WARE Private Wiki from their start):
5.1 Proposal on where to fit it the Dev Tools chapter in the FI-WARE Product Vision (Davide):
Dealing with revision of the document. Still configuring the tracker within their chapter.
They have sent an email making a proposal on where the document would fit within the overall Product Vision.
AP: Juanjo to make sure that specific sections on the Wiki are available for uploading the Dev Tool contents
Ericsson will not host the catalogue linked to the Ericsson Lab. Therefore, we have to develop our own catalogue. Ericsson
will help to design this, which is the phase where we are.
5. 2 Answer on Questionnaire on Dev Tools
No answer has been received by the other chapter teams
AP: Juanjo to send a reminder to chapters to fill the questionnaire distributed by the Dev Tool team
The following questions couldn't be address for lack of time and will be postponed until next joint WPL/WPA follow-up confcall:
* Dissemination and Standardization entries on the Wiki
* Exploitation
* Confcall between TID/Engineering regarding planning of activities/milestones regarding the FI-WARE Testbed
6. AOB (Any Other Business)
No other business identified so we closed the confcall
________________________________
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-wpl/attachments/20111011/430b389a/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy