[Fiware-i2nd] I2ND Tracker tickets to be updated

jeanpierre.lerouzic at orange.com jeanpierre.lerouzic at orange.com
Fri Feb 8 10:49:10 CET 2013


Hi all,

Just to verify that we are in sync about Orange trackers:
There are four of them: Api mediation, SMS/MMS OneAPI, Telecom enabler and WSC.


·         There will be no more work on WSC. I changed the workflow state to close. If need arise I can provide the code. https://forge.fi-ware.eu/tracker/?func=detail&aid=249&group_id=10&atid=192

·         The Telecom enabler/easy API, at last is hosted in our premise here in Rennes. It's a matter of a few days/weeks to offer access to Fi-Ware people. There is no sprint assigned to it as I had no news from this team for nearly all of 2012, so I was not sure about what to do about it. Now the situation seems more stable so I suggest that Pier (as you suggest in the email below) you assign this tracker to R2 because it is hosted now here in Orange premise in Rennes and people that I trust, care for it. https://forge.fi-ware.eu/tracker/?func=detail&aid=247&group_id=10&atid=192

·         SMS/MMS OneAPI is also up and running in our premise, therefore it's a matter of days/weeks to give access to it to Fi-Ware people. I trust the people who designed and implemented it so I suggest to let it assigned to R2 as it is now. https://forge.fi-ware.eu/tracker/?func=detail&aid=246&group_id=10&atid=192

·         The API mediation layer is the core business of my old team, there is code but no implementation (even if I ask for one). But it must not be too complicated to set it up (it's an Apache module) and offer access to it to Fi-Ware people. I suggest to let it to R2 as it is right now. I remarked that the workflow is on closed. I think It's a mistake from my side, please someone who have a better understanding of procedures, don't hesitate to change this workflow state. https://forge.fi-ware.eu/tracker/?func=detail&aid=248&group_id=10&atid=192

About documentation.
I was asked to provide documentation for Orange's enablers in December. I asked for this internally in December and as for today I didn't received any consistent documentation from the various Orange groups. Probably it has something to do with reluctance to offer business documentation to a collaborative project. I am sorry for that, but we work to improve the situation.

Best regards,

Jean-Pierre


De : Garino Pierangelo [mailto:pierangelo.garino at telecomitalia.it]
Envoyé : jeudi 7 février 2013 17:29
À : LE ROUZIC Jean-Pierre OLNC/OLN; Kay.Haensge at telekom.de
Cc : Matthias.Baumgart at telekom.de; Mohamed.Salem at telekom.de; Roman.Szczepanski at telekom.de
Objet : R: I2ND Tracker tickets to be updated

Hi All,

this is perhaps a mistake on my side, I dind't find that there were Epics in the tracker for Orange contributions when I sent the file to Kay, and therefore there were those 'missing' items in the excel sheet.
After I sent it to Kay I turned the Epics into Features and assigned them to some minor release/Sprint inside R2.
The situation is now the following:

-          Tracker seems ok (Please J.P. confirm it)

-          I'm going to change back the tech roadmap page to have those features in the R2 table

Please don't do anything on your side, but let me know of any problems you can find.

This shows up that the main issue for all of us is to take care of our own items (Features, tickets) in a consistent way: the old tickets mentioning Epics had to be turned into Features long time ago, when the activity was under development. However now it seems the alignment is ok.

Thanks and BR
Pier




Da: jeanpierre.lerouzic at orange.com<mailto:jeanpierre.lerouzic at orange.com> [mailto:jeanpierre.lerouzic at orange.com]
Inviato: giovedì 7 febbraio 2013 16:16
A: Kay.Haensge at telekom.de<mailto:Kay.Haensge at telekom.de>; Garino Pierangelo
Cc: Matthias.Baumgart at telekom.de<mailto:Matthias.Baumgart at telekom.de>; Mohamed.Salem at telekom.de<mailto:Mohamed.Salem at telekom.de>; Roman.Szczepanski at telekom.de<mailto:Roman.Szczepanski at telekom.de>
Oggetto: RE: I2ND Tracker tickets to be updated

Hi Kay and all,

Please can you give any rational why you move the Orange features in R3?

Best regards,

Jean-Pierre



De : Kay.Haensge at telekom.de<mailto:Kay.Haensge at telekom.de> [mailto:Kay.Haensge at telekom.de]
Envoyé : jeudi 7 février 2013 15:50
À : pierangelo.garino at telecomitalia.it<mailto:pierangelo.garino at telecomitalia.it>
Cc : Matthias.Baumgart at telekom.de<mailto:Matthias.Baumgart at telekom.de>; Mohamed.Salem at telekom.de<mailto:Mohamed.Salem at telekom.de>; LE ROUZIC Jean-Pierre OLNC/OLN; Roman.Szczepanski at telekom.de<mailto:Roman.Szczepanski at telekom.de>
Objet : RE: I2ND Tracker tickets to be updated

Hi Pier,
I tried to call you but nevertheless, I have updated the wiki pages als tried to log the changes in the excel sheet.

The Orange's Features are moved to R3.  Therefore there are out of the Technical Roadmap of R2.

I have added the FIWARE.Feature.I2ND.S3C.NetworkPositioningEnabler.PositioningAccuracy<https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.Feature.I2ND.S3C.NetworkPositioningEnabler.PositioningAccuracy> and FIWARE.Epic.I2ND.S3C.NetworkLevelDataDelivery<https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.Epic.I2ND.S3C.NetworkLevelDataDelivery> to the Materializing page.

FIWARE.Feature.I2ND.S3C.SeamlessNetworkConnectivity.FlowController is moved to R3.

Regarding the last Feature
FIWARE.Feature.I2ND.S3C.SeamlessNetworkConnectivity.NetworkTunnelConnectivity,
this one is no longer used in the development process. Therefore it was closed and had no entries in the epic or roadmap list.
Shall we delete this?


Now, please have a look again and give me some feedback if still something is wrong.


Thank you in advance
Kay Hänsge
Deutsche Telekom AG
T-Labs (Research & Innovation)
Kay Hänsge
Winterfeldtstr. 21, 10781 Berlin
+4930835354269 (Tel.)
+4930835358408 (Fax)
E-Mail: kay.haensge at telekom.de<mailto:kay.haensge at telekom.de>
www.telekom.com

Erleben, was verbindet.

Deutsche Telekom AG
Aufsichtsrat: Prof. Dr. Ulrich Lehner (Vorsitzender)
Vorstand: René Obermann (Vorsitzender),
Reinhard Clemens, Niek Jan van Damme,
Timotheus Höttges, Dr. Thomas Kremer, Claudia Nemat, Prof. Dr. Marion Schick
Handelsregister: Amtsgericht Bonn HRB 6794
Sitz der Gesellschaft: Bonn
WEEE-Reg.-Nr. DE50478376

Große Veränderungen fangen klein an - Ressourcen schonen und nicht jede E-Mail drucken.

Hinweis: Diese E-Mail und/oder die Anhänge sind vertraulich und ausschließlich für den bezeichneten Adressaten bestimmt. Die Weitergabe oder Kopieren dieser E-Mail ist strengstens verboten. Wenn Sie diese E-Mail irrtümlich erhalten haben, informieren Sie bitte unverzüglich den Absender und vernichten Sie die Nachricht und alle Anhänge. Vielen Dank.
From: Garino Pierangelo [mailto:pierangelo.garino at telecomitalia.it]
Sent: Donnerstag, 7. Februar 2013 11:45
To: Szczepanski, Roman; Hänsge, Kay
Cc: Baumgart, Matthias
Subject: R: I2ND Tracker tickets to be updated

Hi All,

here is an excel sheet (see S3C tab) with the current situation of materialising wiki VS tech roadmap wiki VS I2ND tracker.
I have highlighted the points not aligned with yellow and pink (see explanation below the list), if by today you can provide at least the yellow updates to the pages and tracker, it would be great.

Thanks and BR
Pier


Da: Garino Pierangelo
Inviato: mercoledì 6 febbraio 2013 16:17
A: Roman.Szczepanski at telekom.de<mailto:Roman.Szczepanski at telekom.de>
Cc: Kay.Haensge at telekom.de<mailto:Kay.Haensge at telekom.de>; Matthias.Baumgart at telekom.de<mailto:Matthias.Baumgart at telekom.de>
Oggetto: I2ND Tracker tickets to be updated

Hello Roman,

I have to give the ok for the delivery of the backlog and I found that in the I2ND tracker there are tickets with wrong numbering assigned to you (I assume by Matthias).
As the OK for the delivery is rather urgent, could you please check them and correct the numbering asap?

I provide you below a list (link) of tickets to be managed, along with the following two 'rules of thumb' to update them:

-          We have to take a snapshot concerning month 21, i.e. Jan 2013

-          We are currently in FIWARE.Release.2.2 and FIWARE.Sprint.2.2.2 (corresponding to February, so for January snapshot it was 2.2.1), as shown in http://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/Releases_and_Sprints_numbering,_with_mapping_to_calendar_dates

-          I expect that only the release ID is assigned to all the tickets not belonging to current Sprint or the following one. That is: I expect that there are Sprint ID assigned only up to 2.2.3  and no higher, according to the Agile methodology. It there are others, please remove them (but do not remove the Release ID...).

Here are the tickets:
3429<https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=3429&group_id=10&atid=192>
3428<https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=3428&group_id=10&atid=192>

3427<https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=3427&group_id=10&atid=192>



3426<https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=3426&group_id=10&atid=192>



3423<https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=3423&group_id=10&atid=192>



3422<https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=3422&group_id=10&atid=192>



3420<https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=3420&group_id=10&atid=192>




3416<https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=3416&group_id=10&atid=192> (assigned to Kay)



3180<https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=3180&group_id=10&atid=192>



They have ReleaseID =  2.3 but they already have a Sprint ID (to be removed)

3425<https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=3425&group_id=10&atid=192>
3424<https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=3424&group_id=10&atid=192>
3421<https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=3421&group_id=10&atid=192>
3419<https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=3419&group_id=10&atid=192>
3418<https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=3418&group_id=10&atid=192>

3417<https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=3417&group_id=10&atid=192>   (assigned to Kay)
3322<https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=3322&group_id=10&atid=192>   (assigned to Kay)
3301<https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=3301&group_id=10&atid=192>  (assigned to Kay)

Inconsistency between ReleaseID and SprintID: they have ReleaseID=2.3 and SprintID=2.2.x, please check whether they are done or under execution, so ReleaseID must be 2.2, otherwise cancel SprintID

Thanks a lot for your help!

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.
[rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non è necessario.



_________________________________________________________________________________________________________________________



Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc

pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler

a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,

France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.



This message and its attachments may contain confidential or privileged information that may be protected by law;

they should not be distributed, used or copied without authorisation.

If you have received this email in error, please notify the sender and delete this message and its attachments.

As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified.

Thank you.

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified.
Thank you.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/old-fiware-i2nd/attachments/20130208/de01e739/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/20130208/de01e739/attachment.gif>


More information about the Old-Fiware-i2nd mailing list

You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy   Cookies policy