[Fiware-i2nd] R: Items to be addressed

[Garino Pierangelo]

Hi Jean-Pierre,

I admit that there are aspects not completely clear to me too...
I'll try to provide you an answer to (almost) all questions and issues you raise.

Frist of all, there are deliverables that do not belong to WP7, but e.g. to WP2, WP10, WP11 or WP12. If you go to the DoW, nearly all the partners have resources allocated to those WPs, and therefore it is required that technical chapters contribute to them, because most of the times the information requested strongly refers to their activity technical activity. Other times the request is to the single partners, so in this case if there should resources allocated to those WPs only. As a matter of fact, for most of the partners, there is a superposition of people working both on the technical and on the general WPs.


(1)    Your're right, work on deliverables should be planned well in advance, e.g. two months, so that we could prepare all the contributions not in a hurry. We highlighted this in a recent WPL/WPA. We hope to have more efficient planning for next deliverables.

(2)    That's a good point: sometimes however it happens that, after a request to contribute to some activity, we don't get the necessary feedback on time, which creates troubles in managing the work to be done. Second thing, the extreme heterogeneous nature of our GEs calls for specific knowledge on a lot of different technical aspects, which are not always part of own background (myself too have some trouble in understanding  all such details for all four GEs). Moreover, in some cases it seems to me there is not (yet) a good integration of the contributions of single partners, leading to uncertainty in the definition of a clear objective, and consequently a workplan. We'll try and improve anyway this aspects, because they are of extreme importance. Probably now that we finish the set of contributions for the first release, it should be easier to organize the activities.

(3)    This is another critical topic. First of all, the Forge repository is ok for minutes, presentations, etc. It is NOT the tool to manage the deliverables. It was decided (well imposed...) to use the wiki as means to contribute to the creation of documents, so each deliverable is living in thoe wiki(es). And here comes the actual trouble: too many different wikies: I2ND private, fi-ware-wiki-private, fi-ware public, exploitation, integration...   This creates confusion. We'll need to address it, however it is expected that all the public deliverables will be created in the fiware public wiki (we need to define where to provide the drafts/working copies, i.e. in fi-ware-private wiki or I2ND private one) and not in Forge folders.

Finally about your suggestions:

If I have understood well your proposal, I don't agree to have a unique set of APIs for the WP: I find it already difficult to have a homogeneous set of APIs per GE, I cannot imagine that we have a uniform and simple set of API per the entire WP7! I see that even in S3C there is not a uniform APIs description, according to the architecture defined so far. This is propbably because we artificially decided to keep different, heterogenous functionalities together in a single GE, while we should have split them into separate GEs. We can still decide to go for this solution, but definitely I cannot see a unique kind of APIs for all the GEs.

Anyway, discussion on these points is open, I invite all to provide other views and contributions. We those of you present in Zurich next week, we can try to analyse the different comments and proposals.

Have all a nice week-end!
Pier




Da: jeanpierre.lerouzic at orange.com [mailto:jeanpierre.lerouzic at orange.com]
Inviato: venerdì 18 maggio 2012 11:15
A: Garino Pierangelo; Hans.Einsiedler at telekom.de
Cc: fiware-i2nd at lists.fi-ware.eu
Oggetto: RE: [Fiware-i2nd] Items to be addressed

Hi Pier, Hans and all,

I am sorry but I am loosing track of what this project is about and what Orange has to provide. For example in the DoW D12 is not a WP7 deliverable. I apologize also for not attending physical meetings which probably would have helped.

May I have three kind requests that in fact are not specific to Fi-Ware WP7, and also one suggestion?

(1) In other projects were I was involved, the work on deliverable starts at least two months before the official deadline, and often we took two weeks more just to review the deliverable internally before releasing it to the Project Management Team. We took also extra time in case holidays were in the middle of the planned work time.

(2) We had also a clear view of who needs to work, what she had to do, and when it is due.

(3) My last request is that I am lost in all documents, where they are, what is important or not. In addition the number of documents to read just as informative documents or "how to" is really huge. One shouldn't expect us to read all that. I suggest that we decide to have a clear structure for documents and only one place to find all WP7 important documents. Here is a proposal:

·         Folder for WP7 conf-call and physical  minutes

o   Currently conf-call can be accessed at https://forge.fi-ware.eu/docman/?group_id=10#<https://forge.fi-ware.eu/docman/?group_id=10> and I am fine with that, but the folder structure is not explicit.



o   Physical meeting minutes are elsewhere  in the same page in the structure and do not include all meetings (Turin and Madrid are missing)

·         Folder for deliverables where W7 is involved. There is no dedicated folder at the moment.

o   D1,

o   D2,

o   ...


Suggestion:
                My understanding is that there is some mismatch between what WP7 wants to provide, what service projects wait from us and what the Dow states.

Therefore I suggest that we have some thoughts about making our diverse sets of APIs, one unique set at the WP level and being  much more simple, homogeneous, and canonical. I think we have to take in account the connectivity problem also (contrary to our previous stance on the subject).
This will result has having the two following advantage for us:

o   Internally I am pretty sure it will show non functional aspects that certainly exist but are not addressed at the moment. It will also help in relation to other WPs (security?).

o   Externally our APIs will be much more easy to understand and it will be easier to sell them to stakeholders.

Best regards,

Jean-Pierre


De : fiware-i2nd-bounces at lists.fi-ware.eu [mailto:fiware-i2nd-bounces at lists.fi-ware.eu] De la part de Garino Pierangelo
Envoyé : mercredi 16 mai 2012 10:21
À : fiware-i2nd at lists.fi-ware.eu
Objet : [Fiware-i2nd] Items to be addressed
Importance : Haute

Dear All,

the list of things to do in FI-WARE has enormously grown in the last days, involving of course also I2ND Team.
Here is an attempt to summarise the most important points, along with some initial split of responsibility between Hans and myself, and some proposal for appointing responsibles for other topics:

·         Most urgent item: Open Specs: translate pages to public wiki --> mail of Juanjo  '[Fiware-wpl] GUIDELINES on how to publish Open Specifications' 15/5 11:13
o    Verify contents of CDI, NetIC and S3C pages --> ask for modifications --> Hans for S3C (revise arch, + open specs), Pier to check the other two with GE owners
o    Deadline Thursday morning --> Pier to port to public wiki on Wednesday
o    CE will be unique page for both cloud and I2ND --> Pier


·         Check requested info for D10.3 (Integration Plan) about CE --> Ask Stefano Pier
o    Any partner failing to submit the expected contribution will not be allowed to declare manpower in this chapter

·         Send comments on Admin/inst guide by end of week!!

-          Pier to check if feedback from Chris, then send the feedback (by Kay) concerning NetIC and S3C

·         Complete exploitation plans deliverabl contributions
o    Any partner failing to submit the expected contribution will not be allowed to declare manpower in this chapter
o    11.3: Market and Policy Awareness

-          Pier to talk to Ericsson/Henrik is proposed to manage contributions for I2ND

·         Revise review report comments

-          Create Task Force: Pier to Ask Task Coords

·         Ticket Management

-          Hans to coordinate

·         Deliverables due in month 12. Dissemination & Collaboration.
o    As per month 12, Fi-WARE 'Collaboration & Dissemination' chapter committed to deliver the following two deliverables:
- D12.2b Report on Communication and Dissemination activities (M12).
- D12.3.b Report on Collaboration activities (M12).
·         All Partners are expected to contribute to 'Disseminations activities' (4th) section with scientific/technical/standards presentations before this Fri May 18th EoB.
·         WPL are expected to update 'Communication Activities' (2nd) section with Press releases, Interviews, Newsletters, Infodays and support to other projects/initiatives before this Fri May 18th EoB.
·         AP on all: send proposal for topics by end of this week.

-          Responsible to be appointed

 *   Slides for Educ weeks

-          GE owners/Task Coords to provide

Please provide us a feedback about this work splitting asap, later I'll start contacting the relevant people (e.g. GE owners and proposed appointed people) to get the approval/information about contributions they should provide/update.

BR
Pier


------------------------------------------------------------------
Telecom Italia
Pierangelo Garino
Innovation & Industry Relations - Research & Prototyping
Via G. Reiss Romoli 274, I-10148 TORINO
Tel: +39 011 228 7142

Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie.

This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks.
[cid:image001.gif at 01CD3522.3F3E9A80]Rispetta l'ambiente. Non stampare questa mail se non è necessario.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/old-fiware-i2nd/attachments/20120518/823631eb/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.gif
Type: image/gif
Size: 677 bytes
Desc: image001.gif
URL: <https://lists.fiware.org/private/old-fiware-i2nd/attachments/20120518/823631eb/attachment.gif>