We should have news about dedicated tracker systems per GE before the end of the week. So we can prepare how to split and transfer the relevant EPICs/Features and workitems for the beginning of next week. BR Thierry De : Tobias Jacobs [mailto:Tobias.Jacobs at neclab.eu] Envoyé : lundi 10 décembre 2012 10:08 À : Fermín Galán Márquez Cc : fiware-iot at lists.fi-ware.eu; Juanjo Hierro; NAGELLEN Thierry OLNC/OLPS Objet : RE: [Fiware-iot] [GE splitting] Hi Fermin, About the Tracker items: I am not sure if we should rename them. Maybe another approach would be to close them all and mention that there are now new tracker items for the new GEs. Then every one of us can create new tracker items for his GE. Also, I would not keep "ThingsManagement" in the name. I did it in the wiki, but this is only for better keeping track of the splitting process. After it is finished and moved to the public wiki, I would recommend to remove the "ThingsManagement." part. Best regards Tobias From: Fermín Galán Márquez [mailto:fermin at tid.es] Sent: Freitag, 7. Dezember 2012 11:47 To: Tobias Jacobs Cc: fiware-iot at lists.fi-ware.eu<mailto:fiware-iot at lists.fi-ware.eu>; Juanjo Hierro; thierry.nagellen at orange.com<mailto:thierry.nagellen at orange.com> Subject: Re: [Fiware-iot] [GE splitting] Dear Tobias, In order to ease the "Tracker items" task, I've taken an snapshoot of the trac (attached). For each one of the currently existing issues, we should define a new name, using the following rule: X.IoT.Backend.ThingsManagement.Y -> X.IoT.Backend.ThingsManagement.IoTBroker.Y or X.IoT.Backend.ThingsManagement.ConfigMan.Y Tobias, could you please do a first pass to the attached Excel completing the new_name column for the issues related with IoT Broker, please? I'm not sure which they are... In addition, if we are splitting the Thing Management GE into two GEs (IoT Broker and ConfMan) we should define where Discovery Engine and Geo-Discover components are located. Considering the internal structure (see attachment) I tend to think that they would belong to ConfMan, but I would like to confirm if the other partners in Thing Managament GE (NEC and USurrey) think the same. Best regards, ------ Fermín PD. I've created a backlog entry (workitem) for the wiki and trac work on splitting: FIWARE.WorkItem.IoT.Backend.ThingsManagement.Splitting<https://forge.fi-ware.eu/tracker/index.php?func=detail&aid=3250&group_id=11&atid=193> . It should be assigned to both TID and NEC (as we are doing this splitting), but given that AFAIK our trac doesn't allow assign a ticket to two different people, asignee is set to "Nobody". El 03/12/2012 11:37, Fermín Galán Márquez escribió: Dear Tobias, I think is a good approach. I will take care of the ConfMan pages. Best regards, ------ Fermín El 26/11/2012 16:27, Tobias Jacobs escribió: Dear all, We are about to start implementing the split between the Things Management GE and the Configuration Management GE. What we have done up to now is to create an overview of the places where there are changes that need to be done: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Things_Management_GE_splitting_page The page also contains placeholders for the modified pages. The question now is how much of the old Things Management GE to leave in these pages. What we would propose is to bring everything into a status which simulates that the TM GE has never existed, and only mention at certain places that the TM GE now is actually two GEs. Although this might create some confusion, the alternative would be to have some things described in terms of the old GE and other things described in terms of the new GE - where the confusion would be considerably greater, I think. In particular. - All tracker items become associated to one of the new GEs, or both - All Things Management GE features/epics/... become features of one of the new GEs, or of both - In the technical roadmap the release 1 could stay like it is, but the linked features are changed to the new features. - In the catalogue the old TM GE will stay at least until the 2nd release, but the documentation links need to be updated. Please let me know your opinion. Best regards Tobias _______________________________________________ Fiware-iot mailing list Fiware-iot at lists.fi-ware.eu<mailto:Fiware-iot at lists.fi-ware.eu> http://lists.fi-ware.eu/listinfo/fiware-iot ________________________________ 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 _________________________________________________________________________________________________________________________ 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-iot/attachments/20121210/aab34763/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy