From gianmario.bollano at telecomitalia.it Tue Sep 1 10:18:42 2015 From: gianmario.bollano at telecomitalia.it (Bollano Gianmario) Date: Tue, 1 Sep 2015 08:18:42 +0000 Subject: [Fiware-robotics] Robotics call? Message-ID: <7E649CBD84A947498203DAF8F098B1F642AADD2F@telmbb003ba020.telecomitalia.local> Hi all, I've came back to office this morning; are we going to have a Robotics call today or is it skipped? Gianmario ------------------------------------------------------------------------------------ Telecom Italia Gianmario Bollano Innovation - Mobile Devices & Sim Applications Via Reiss Romoli, n? 274 Cap 10151 Torino Phone 011 228 7103 Cell Phone 3316015048 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia2.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia2.jpg URL: From fabio.dibenedetto at consoft.it Tue Sep 1 10:22:50 2015 From: fabio.dibenedetto at consoft.it (fabio.dibenedetto at consoft.it) Date: Tue, 1 Sep 2015 08:22:50 +0000 Subject: [Fiware-robotics] R: Robotics call? In-Reply-To: <7E649CBD84A947498203DAF8F098B1F642AADD2F@telmbb003ba020.telecomitalia.local> References: <7E649CBD84A947498203DAF8F098B1F642AADD2F@telmbb003ba020.telecomitalia.local> Message-ID: We are waiting in the call if you join us Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Bollano Gianmario Inviato: marted? 1 settembre 2015 10:19 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] Robotics call? Hi all, I've came back to office this morning; are we going to have a Robotics call today or is it skipped? Gianmario ------------------------------------------------------------------------------------ Telecom Italia Gianmario Bollano Innovation - Mobile Devices & Sim Applications Via Reiss Romoli, n? 274 Cap 10151 Torino Phone 011 228 7103 Cell Phone 3316015048 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: From gianmario.bollano at telecomitalia.it Tue Sep 1 10:27:34 2015 From: gianmario.bollano at telecomitalia.it (Bollano Gianmario) Date: Tue, 1 Sep 2015 08:27:34 +0000 Subject: [Fiware-robotics] R: Robotics call? In-Reply-To: References: <7E649CBD84A947498203DAF8F098B1F642AADD2F@telmbb003ba020.telecomitalia.local> Message-ID: <7E649CBD84A947498203DAF8F098B1F642AADD4D@telmbb003ba020.telecomitalia.local> I haven't yet received any notification from hangout... Da: fabio.dibenedetto at consoft.it [mailto:fabio.dibenedetto at consoft.it] Inviato: marted? 1 settembre 2015 10:23 A: Bollano Gianmario; fiware-robotics at lists.fi-ware.org Oggetto: R: Robotics call? We are waiting in the call if you join us Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Bollano Gianmario Inviato: marted? 1 settembre 2015 10:19 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] Robotics call? Hi all, I've came back to office this morning; are we going to have a Robotics call today or is it skipped? Gianmario ------------------------------------------------------------------------------------ Telecom Italia Gianmario Bollano Innovation - Mobile Devices & Sim Applications Via Reiss Romoli, n? 274 Cap 10151 Torino Phone 011 228 7103 Cell Phone 3316015048 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: From fabio.dibenedetto at consoft.it Tue Sep 1 10:30:45 2015 From: fabio.dibenedetto at consoft.it (fabio.dibenedetto at consoft.it) Date: Tue, 1 Sep 2015 08:30:45 +0000 Subject: [Fiware-robotics] R: Robotics call? In-Reply-To: <7E649CBD84A947498203DAF8F098B1F642AADD4D@telmbb003ba020.telecomitalia.local> References: <7E649CBD84A947498203DAF8F098B1F642AADD2F@telmbb003ba020.telecomitalia.local> <7E649CBD84A947498203DAF8F098B1F642AADD4D@telmbb003ba020.telecomitalia.local> Message-ID: <3648bc21a9404b2f9c5b7aeaed90e2c7@EXCHMBX2.consoft.it> If you have the hangout history (the icon at the right of the contacts) you can click on Robotics and join Da: Bollano Gianmario [mailto:gianmario.bollano at telecomitalia.it] Inviato: marted? 1 settembre 2015 10:28 A: fabio.dibenedetto at consoft.it; fiware-robotics at lists.fi-ware.org Oggetto: R: Robotics call? I haven't yet received any notification from hangout... Da: fabio.dibenedetto at consoft.it [mailto:fabio.dibenedetto at consoft.it] Inviato: marted? 1 settembre 2015 10:23 A: Bollano Gianmario; fiware-robotics at lists.fi-ware.org Oggetto: R: Robotics call? We are waiting in the call if you join us Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Bollano Gianmario Inviato: marted? 1 settembre 2015 10:19 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] Robotics call? Hi all, I've came back to office this morning; are we going to have a Robotics call today or is it skipped? Gianmario ------------------------------------------------------------------------------------ Telecom Italia Gianmario Bollano Innovation - Mobile Devices & Sim Applications Via Reiss Romoli, n? 274 Cap 10151 Torino Phone 011 228 7103 Cell Phone 3316015048 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: From roberto1.antonini at telecomitalia.it Tue Sep 1 11:38:06 2015 From: roberto1.antonini at telecomitalia.it (Antonini Roberto) Date: Tue, 1 Sep 2015 09:38:06 +0000 Subject: [Fiware-robotics] R: common github repos In-Reply-To: <246C286B275B1B46A255552CD236DA8644CAE20A@TELMBB001BA020.telecomitalia.local> References: <246C286B275B1B46A255552CD236DA8644CAE20A@TELMBB001BA020.telecomitalia.local> Message-ID: <246C286B275B1B46A255552CD236DA8644CAF52C@TELMBB001BA020.telecomitalia.local> Hi all, Just a summary of actions done and to do for the next deadline (4/9): ? Creation common Robotics GE github https://github.com/FIWARE-RoboticsGE (TI) - done ? Document RDAPI to APIARY http://docs.rdapi.apiary.io/# (not yet public, if you want have a look of them, ask for invitation) (TI) - done ? Fork ikergune/firos github repo to common github (see above) (TI) - done ? Taking care of syncing firos repos to our common github (ET) - to do ? Document FGFCAPI and CBAPI to APIARY (ET) - to do ? Convert apiary format to github format in order to link APIs to github (ET, TI) - to do o For this task, we are waiting for the conversion tool the FIWARE coordination has to provide us. The APs listed above are also reported on the minute, in order to keep track of them. Besides you should have been notified with JIRA issues. Let me know if something is missing. Thanks, R Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Antonini Roberto Inviato: venerd? 28 agosto 2015 14:20 A: I?igo Gonzalez; Angel Hernandez (ahernandez at ikergune.com); Jose Jaime Ariza (jjaime at ikergune.com); fabio.dibenedetto at consoft.it Cc: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] common github repos Hi all, as said previously, I created a common github account https://github.com/FIWARE-RoboticsGE, where I created two repos: FIROS and RCM If you tell me your github account, I can add you as a members so that we can share our components and links to apiary docs. Besides, I include the architecture description section into openSpecs specification wiki page (http://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/FIWARE.OpenSPecification.I2ND.Robotics_R4) in the detailed specification section and I already put both github repos address above, as Manuel suggested, Thanks, R 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: From roberto1.antonini at telecomitalia.it Tue Sep 1 11:40:12 2015 From: roberto1.antonini at telecomitalia.it (Antonini Roberto) Date: Tue, 1 Sep 2015 09:40:12 +0000 Subject: [Fiware-robotics] R: common github repos In-Reply-To: <246C286B275B1B46A255552CD236DA8644CAF52C@TELMBB001BA020.telecomitalia.local> References: <246C286B275B1B46A255552CD236DA8644CAE20A@TELMBB001BA020.telecomitalia.local> <246C286B275B1B46A255552CD236DA8644CAF52C@TELMBB001BA020.telecomitalia.local> Message-ID: <246C286B275B1B46A255552CD236DA8644CAF546@TELMBB001BA020.telecomitalia.local> An action I missed before: ? Add RCM component to common github (CONSOFT) - done R Da: Antonini Roberto Inviato: marted? 1 settembre 2015 11:38 A: Antonini Roberto; I?igo Gonzalez; Angel Hernandez (ahernandez at ikergune.com); Jose Jaime Ariza (jjaime at ikergune.com); fabio.dibenedetto at consoft.it Cc: fiware-robotics at lists.fi-ware.org; Bollano Gianmario; Garino Pierangelo Oggetto: R: common github repos Hi all, Just a summary of actions done and to do for the next deadline (4/9): ? Creation common Robotics GE github https://github.com/FIWARE-RoboticsGE (TI) - done ? Document RDAPI to APIARY http://docs.rdapi.apiary.io/# (not yet public, if you want have a look of them, ask for invitation) (TI) - done ? Fork ikergune/firos github repo to common github (see above) (TI) - done ? Taking care of syncing firos repos to our common github (ET) - to do ? Document FGFCAPI and CBAPI to APIARY (ET) - to do ? Convert apiary format to github format in order to link APIs to github (ET, TI) - to do o For this task, we are waiting for the conversion tool the FIWARE coordination has to provide us. The APs listed above are also reported on the minute, in order to keep track of them. Besides you should have been notified with JIRA issues. Let me know if something is missing. Thanks, R Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Antonini Roberto Inviato: venerd? 28 agosto 2015 14:20 A: I?igo Gonzalez; Angel Hernandez (ahernandez at ikergune.com); Jose Jaime Ariza (jjaime at ikergune.com); fabio.dibenedetto at consoft.it Cc: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] common github repos Hi all, as said previously, I created a common github account https://github.com/FIWARE-RoboticsGE, where I created two repos: FIROS and RCM If you tell me your github account, I can add you as a members so that we can share our components and links to apiary docs. Besides, I include the architecture description section into openSpecs specification wiki page (http://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/FIWARE.OpenSPecification.I2ND.Robotics_R4) in the detailed specification section and I already put both github repos address above, as Manuel suggested, Thanks, R 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: From roberto1.antonini at telecomitalia.it Thu Sep 3 08:30:40 2015 From: roberto1.antonini at telecomitalia.it (Antonini Roberto) Date: Thu, 3 Sep 2015 06:30:40 +0000 Subject: [Fiware-robotics] R: common github repos In-Reply-To: <246C286B275B1B46A255552CD236DA8644CAF546@TELMBB001BA020.telecomitalia.local> References: <246C286B275B1B46A255552CD236DA8644CAE20A@TELMBB001BA020.telecomitalia.local> <246C286B275B1B46A255552CD236DA8644CAF52C@TELMBB001BA020.telecomitalia.local> <246C286B275B1B46A255552CD236DA8644CAF546@TELMBB001BA020.telecomitalia.local> Message-ID: <246C286B275B1B46A255552CD236DA8644CBB093@TELMBA001BA020.telecomitalia.local> Hi ET guys, as all my mail got answered so far, I kindly remind you to update things on common repo github https://github.com/FIWARE-RoboticsGE, for this you need to be added as a member. So could you please provide me a reference person fort that? Thanks, Roberto. Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Antonini Roberto Inviato: marted? 1 settembre 2015 11:40 A: I?igo Gonzalez; Angel Hernandez (ahernandez at ikergune.com); Jose Jaime Ariza (jjaime at ikergune.com); fabio.dibenedetto at consoft.it Cc: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] R: common github repos An action I missed before: ? Add RCM component to common github (CONSOFT) - done R Da: Antonini Roberto Inviato: marted? 1 settembre 2015 11:38 A: Antonini Roberto; I?igo Gonzalez; Angel Hernandez (ahernandez at ikergune.com); Jose Jaime Ariza (jjaime at ikergune.com); fabio.dibenedetto at consoft.it Cc: fiware-robotics at lists.fi-ware.org; Bollano Gianmario; Garino Pierangelo Oggetto: R: common github repos Hi all, Just a summary of actions done and to do for the next deadline (4/9): ? Creation common Robotics GE github https://github.com/FIWARE-RoboticsGE (TI) - done ? Document RDAPI to APIARY http://docs.rdapi.apiary.io/# (not yet public, if you want have a look of them, ask for invitation) (TI) - done ? Fork ikergune/firos github repo to common github (see above) (TI) - done ? Taking care of syncing firos repos to our common github (ET) - to do ? Document FGFCAPI and CBAPI to APIARY (ET) - to do ? Convert apiary format to github format in order to link APIs to github (ET, TI) - to do o For this task, we are waiting for the conversion tool the FIWARE coordination has to provide us. The APs listed above are also reported on the minute, in order to keep track of them. Besides you should have been notified with JIRA issues. Let me know if something is missing. Thanks, R Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Antonini Roberto Inviato: venerd? 28 agosto 2015 14:20 A: I?igo Gonzalez; Angel Hernandez (ahernandez at ikergune.com); Jose Jaime Ariza (jjaime at ikergune.com); fabio.dibenedetto at consoft.it Cc: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] common github repos Hi all, as said previously, I created a common github account https://github.com/FIWARE-RoboticsGE, where I created two repos: FIROS and RCM If you tell me your github account, I can add you as a members so that we can share our components and links to apiary docs. Besides, I include the architecture description section into openSpecs specification wiki page (http://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/FIWARE.OpenSPecification.I2ND.Robotics_R4) in the detailed specification section and I already put both github repos address above, as Manuel suggested, Thanks, R 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: From jjaime at ikergune.com Thu Sep 3 10:56:48 2015 From: jjaime at ikergune.com (Jose Jaime Ariza) Date: Thu, 3 Sep 2015 10:56:48 +0200 Subject: [Fiware-robotics] R: common github repos References: <246C286B275B1B46A255552CD236DA8644CAE20A@TELMBB001BA020.telecomitalia.local> <246C286B275B1B46A255552CD236DA8644CAF52C@TELMBB001BA020.telecomitalia.local> <246C286B275B1B46A255552CD236DA8644CAF546@TELMBB001BA020.telecomitalia.local> <246C286B275B1B46A255552CD236DA8644CBB093@TELMBA001BA020.telecomitalia.local> Message-ID: Hi, Could you add firos at ikergune.com as a user of https://github.com/FIWARE-RoboticsGE? Thanks :) Pepe. On 03/09/15 08:30, Antonini Roberto wrote: Hi ET guys, as all my mail got answered so far, I kindly remind you to update things on common repo github https://github.com/FIWARE-RoboticsGE, for this you need to be added as a member. So could you please provide me a reference person fort that? Thanks, Roberto. Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Antonini Roberto Inviato: marted? 1 settembre 2015 11:40 A: I?igo Gonzalez; Angel Hernandez (ahernandez at ikergune.com); Jose Jaime Ariza (jjaime at ikergune.com); fabio.dibenedetto at consoft.it Cc: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] R: common github repos An action I missed before: ? Add RCM component to common github (CONSOFT) - done R Da: Antonini Roberto Inviato: marted? 1 settembre 2015 11:38 A: Antonini Roberto; I?igo Gonzalez; Angel Hernandez (ahernandez at ikergune.com); Jose Jaime Ariza (jjaime at ikergune.com); fabio.dibenedetto at consoft.it Cc: fiware-robotics at lists.fi-ware.org; Bollano Gianmario; Garino Pierangelo Oggetto: R: common github repos Hi all, Just a summary of actions done and to do for the next deadline (4/9): ? Creation common Robotics GE github https://github.com/FIWARE-RoboticsGE (TI) - done ? Document RDAPI to APIARY http://docs.rdapi.apiary.io/# (not yet public, if you want have a look of them, ask for invitation) (TI) - done ? Fork ikergune/firos github repo to common github (see above) (TI) ? done ? Taking care of syncing firos repos to our common github (ET) ? to do ? Document FGFCAPI and CBAPI to APIARY (ET) ? to do ? Convert apiary format to github format in order to link APIs to github (ET, TI) ? to do o For this task, we are waiting for the conversion tool the FIWARE coordination has to provide us. The APs listed above are also reported on the minute, in order to keep track of them. Besides you should have been notified with JIRA issues. Let me know if something is missing. Thanks, R Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Antonini Roberto Inviato: venerd? 28 agosto 2015 14:20 A: I?igo Gonzalez; Angel Hernandez (ahernandez at ikergune.com); Jose Jaime Ariza (jjaime at ikergune.com); fabio.dibenedetto at consoft.it Cc: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] common github repos Hi all, as said previously, I created a common github account https://github.com/FIWARE-RoboticsGE, where I created two repos: FIROS and RCM If you tell me your github account, I can add you as a members so that we can share our components and links to apiary docs. Besides, I include the architecture description section into openSpecs specification wiki page (http://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/FIWARE.OpenSPecification.I2ND.Robotics_R4) in the detailed specification section and I already put both github repos address above, as Manuel suggested, Thanks, R 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. [data:image/gif;base64,R0lGODlhGgAoANU5AEiFNnikNyRvNcvYOafCOEOEW3DO3jB2NqjGs9ny9o+zOIOrN+L1+G+ggbzo8GCUN1SNNv///zx+NrPJOL/ROYPV44zY5YuzmrfQwCZxQlKNaMXZzOfy8NTi2TV6TuLs5vX8/ez5+4yzmtTj2cXr8mCXdKni62ycN5/f6aDf6X2qjrPl7rLl7Zu6OJbb53nS4PH188bs8sXZzfH18pq9p0SDWxhnNWbL3NfgOf///wAAAAAAAAAAAAAAAAAAAAAAACH5BAEAADkALAAAAAAaACgAAAb/wJxwSBQ6WMWkMmm6kZbQ5OvmjFoT1JuBYYWmsrcXqJvEgm8WctFypnI66pyjfXMhCmqGgR4r2S5dIBV0FjI2h3BRX20VHAUCEjZ4UHNtFo42BA+HCEskbQYOIwU2CjgBNgAZM0kMbSYcIjYCBDg4LTYLf0V6YCghNBk2DwO2OASZqkS9VBYMCB6pE8bGucidOYJUoaOptdQTFDg2ATgHGkIs2wyyAqbUtgICCwfluh8ge1sNNhDF8LYiHYKAg4INBJUS8FsAEF6AA6lsHWjg4gYKDDZONGwIAIAtCAX2hPAgYSNHj6ds3KiA8V3DAQGm2epoS4HKFQ0EmMRhc97Mwge2kN1IoIGgyQECD5wQUO6YygTkdtpCdSgqDl0VoDaVOmDBpm+oTCQoABQgBZfGbIrDAUBDAgcNDnDs98/WA504Buxa0RKgzVkB/h0oi+pDjgQhHtU1RgDioY6l8gpAJyTBCBsSFtuC6XjWTBuJhIRAgFkmwAmoAkM4mCQCBmEB1sIDIKAFRGytYfDrt4CAuAknqnrYYCXCBxGkqlYtgbtLhOcbMNSw0SBOEmg2VFj/sGHDhRLCNBC3fqFqARWhowQBADs=]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -- Jos? Jaime Ariza R&D Engineer +34 696604288 Ikergune, Etxe-Tar group -------------- next part -------------- An HTML attachment was scrubbed... URL: From roberto1.antonini at telecomitalia.it Thu Sep 3 12:07:52 2015 From: roberto1.antonini at telecomitalia.it (Antonini Roberto) Date: Thu, 3 Sep 2015 10:07:52 +0000 Subject: [Fiware-robotics] R: R: common github repos In-Reply-To: References: <246C286B275B1B46A255552CD236DA8644CAE20A@TELMBB001BA020.telecomitalia.local> <246C286B275B1B46A255552CD236DA8644CAF52C@TELMBB001BA020.telecomitalia.local> <246C286B275B1B46A255552CD236DA8644CAF546@TELMBB001BA020.telecomitalia.local> <246C286B275B1B46A255552CD236DA8644CBB093@TELMBA001BA020.telecomitalia.local> Message-ID: <246C286B275B1B46A255552CD236DA8644CBD359@TELMBA001BA020.telecomitalia.local> I need a github user, among the ones you are using for managing your personal repos, i.e. haas85. May I use it? R Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Jose Jaime Ariza Inviato: gioved? 3 settembre 2015 10:57 A: fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] R: common github repos Hi, Could you add firos at ikergune.com as a user of https://github.com/FIWARE-RoboticsGE? Thanks :) Pepe. On 03/09/15 08:30, Antonini Roberto wrote: Hi ET guys, as all my mail got answered so far, I kindly remind you to update things on common repo github https://github.com/FIWARE-RoboticsGE, for this you need to be added as a member. So could you please provide me a reference person fort that? Thanks, Roberto. Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Antonini Roberto Inviato: marted? 1 settembre 2015 11:40 A: I?igo Gonzalez; Angel Hernandez (ahernandez at ikergune.com); Jose Jaime Ariza (jjaime at ikergune.com); fabio.dibenedetto at consoft.it Cc: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] R: common github repos An action I missed before: ? Add RCM component to common github (CONSOFT) - done R Da: Antonini Roberto Inviato: marted? 1 settembre 2015 11:38 A: Antonini Roberto; I?igo Gonzalez; Angel Hernandez (ahernandez at ikergune.com); Jose Jaime Ariza (jjaime at ikergune.com); fabio.dibenedetto at consoft.it Cc: fiware-robotics at lists.fi-ware.org; Bollano Gianmario; Garino Pierangelo Oggetto: R: common github repos Hi all, Just a summary of actions done and to do for the next deadline (4/9): ? Creation common Robotics GE github https://github.com/FIWARE-RoboticsGE (TI) - done ? Document RDAPI to APIARY http://docs.rdapi.apiary.io/# (not yet public, if you want have a look of them, ask for invitation) (TI) - done ? Fork ikergune/firos github repo to common github (see above) (TI) - done ? Taking care of syncing firos repos to our common github (ET) - to do ? Document FGFCAPI and CBAPI to APIARY (ET) - to do ? Convert apiary format to github format in order to link APIs to github (ET, TI) - to do o For this task, we are waiting for the conversion tool the FIWARE coordination has to provide us. The APs listed above are also reported on the minute, in order to keep track of them. Besides you should have been notified with JIRA issues. Let me know if something is missing. Thanks, R Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Antonini Roberto Inviato: venerd? 28 agosto 2015 14:20 A: I?igo Gonzalez; Angel Hernandez (ahernandez at ikergune.com); Jose Jaime Ariza (jjaime at ikergune.com); fabio.dibenedetto at consoft.it Cc: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] common github repos Hi all, as said previously, I created a common github account https://github.com/FIWARE-RoboticsGE, where I created two repos: FIROS and RCM If you tell me your github account, I can add you as a members so that we can share our components and links to apiary docs. Besides, I include the architecture description section into openSpecs specification wiki page (http://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/FIWARE.OpenSPecification.I2ND.Robotics_R4) in the detailed specification section and I already put both github repos address above, as Manuel suggested, Thanks, R 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. -- Jos? Jaime Ariza R&D Engineer +34 696604288 Ikergune, Etxe-Tar group -------------- next part -------------- An HTML attachment was scrubbed... URL: From jjaime at ikergune.com Thu Sep 3 12:33:59 2015 From: jjaime at ikergune.com (Jose Jaime Ariza) Date: Thu, 3 Sep 2015 12:33:59 +0200 Subject: [Fiware-robotics] R: R: common github repos References: <246C286B275B1B46A255552CD236DA8644CAE20A@TELMBB001BA020.telecomitalia.local> <246C286B275B1B46A255552CD236DA8644CAF52C@TELMBB001BA020.telecomitalia.local> <246C286B275B1B46A255552CD236DA8644CAF546@TELMBB001BA020.telecomitalia.local> <246C286B275B1B46A255552CD236DA8644CBB093@TELMBA001BA020.telecomitalia.local> <246C286B275B1B46A255552CD236DA8644CBD359@TELMBA001BA020.telecomitalia.local> Message-ID: firos at ikergune.com is the mail of the user who owns our Github, the username is Ikergune, could you use this? Thank you, Pepe On 03/09/15 12:07, Antonini Roberto wrote: I need a github user, among the ones you are using for managing your personal repos, i.e. haas85. May I use it? R Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Jose Jaime Ariza Inviato: gioved? 3 settembre 2015 10:57 A: fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] R: common github repos Hi, Could you add firos at ikergune.com as a user of https://github.com/FIWARE-RoboticsGE? Thanks :) Pepe. On 03/09/15 08:30, Antonini Roberto wrote: Hi ET guys, as all my mail got answered so far, I kindly remind you to update things on common repo github https://github.com/FIWARE-RoboticsGE, for this you need to be added as a member. So could you please provide me a reference person fort that? Thanks, Roberto. Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Antonini Roberto Inviato: marted? 1 settembre 2015 11:40 A: I?igo Gonzalez; Angel Hernandez (ahernandez at ikergune.com); Jose Jaime Ariza (jjaime at ikergune.com); fabio.dibenedetto at consoft.it Cc: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] R: common github repos An action I missed before: ? Add RCM component to common github (CONSOFT) - done R Da: Antonini Roberto Inviato: marted? 1 settembre 2015 11:38 A: Antonini Roberto; I?igo Gonzalez; Angel Hernandez (ahernandez at ikergune.com); Jose Jaime Ariza (jjaime at ikergune.com); fabio.dibenedetto at consoft.it Cc: fiware-robotics at lists.fi-ware.org; Bollano Gianmario; Garino Pierangelo Oggetto: R: common github repos Hi all, Just a summary of actions done and to do for the next deadline (4/9): ? Creation common Robotics GE github https://github.com/FIWARE-RoboticsGE (TI) - done ? Document RDAPI to APIARY http://docs.rdapi.apiary.io/# (not yet public, if you want have a look of them, ask for invitation) (TI) - done ? Fork ikergune/firos github repo to common github (see above) (TI) ? done ? Taking care of syncing firos repos to our common github (ET) ? to do ? Document FGFCAPI and CBAPI to APIARY (ET) ? to do ? Convert apiary format to github format in order to link APIs to github (ET, TI) ? to do o For this task, we are waiting for the conversion tool the FIWARE coordination has to provide us. The APs listed above are also reported on the minute, in order to keep track of them. Besides you should have been notified with JIRA issues. Let me know if something is missing. Thanks, R Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Antonini Roberto Inviato: venerd? 28 agosto 2015 14:20 A: I?igo Gonzalez; Angel Hernandez (ahernandez at ikergune.com); Jose Jaime Ariza (jjaime at ikergune.com); fabio.dibenedetto at consoft.it Cc: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] common github repos Hi all, as said previously, I created a common github account https://github.com/FIWARE-RoboticsGE, where I created two repos: FIROS and RCM If you tell me your github account, I can add you as a members so that we can share our components and links to apiary docs. Besides, I include the architecture description section into openSpecs specification wiki page (http://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/FIWARE.OpenSPecification.I2ND.Robotics_R4) in the detailed specification section and I already put both github repos address above, as Manuel suggested, Thanks, R 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. [data:image/gif;base64,R0lGODlhGgAoANU5AEiFNnikNyRvNcvYOafCOEOEW3DO3jB2NqjGs9ny9o+zOIOrN+L1+G+ggbzo8GCUN1SNNv///zx+NrPJOL/ROYPV44zY5YuzmrfQwCZxQlKNaMXZzOfy8NTi2TV6TuLs5vX8/ez5+4yzmtTj2cXr8mCXdKni62ycN5/f6aDf6X2qjrPl7rLl7Zu6OJbb53nS4PH188bs8sXZzfH18pq9p0SDWxhnNWbL3NfgOf///wAAAAAAAAAAAAAAAAAAAAAAACH5BAEAADkALAAAAAAaACgAAAb/wJxwSBQ6WMWkMmm6kZbQ5OvmjFoT1JuBYYWmsrcXqJvEgm8WctFypnI66pyjfXMhCmqGgR4r2S5dIBV0FjI2h3BRX20VHAUCEjZ4UHNtFo42BA+HCEskbQYOIwU2CjgBNgAZM0kMbSYcIjYCBDg4LTYLf0V6YCghNBk2DwO2OASZqkS9VBYMCB6pE8bGucidOYJUoaOptdQTFDg2ATgHGkIs2wyyAqbUtgICCwfluh8ge1sNNhDF8LYiHYKAg4INBJUS8FsAEF6AA6lsHWjg4gYKDDZONGwIAIAtCAX2hPAgYSNHj6ds3KiA8V3DAQGm2epoS4HKFQ0EmMRhc97Mwge2kN1IoIGgyQECD5wQUO6YygTkdtpCdSgqDl0VoDaVOmDBpm+oTCQoABQgBZfGbIrDAUBDAgcNDnDs98/WA504Buxa0RKgzVkB/h0oi+pDjgQhHtU1RgDioY6l8gpAJyTBCBsSFtuC6XjWTBuJhIRAgFkmwAmoAkM4mCQCBmEB1sIDIKAFRGytYfDrt4CAuAknqnrYYCXCBxGkqlYtgbtLhOcbMNSw0SBOEmg2VFj/sGHDhRLCNBC3fqFqARWhowQBADs=]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -- Jos? Jaime Ariza R&D Engineer +34 696604288 Ikergune, Etxe-Tar group -- Jos? Jaime Ariza R&D Engineer +34 696604288 Ikergune, Etxe-Tar group -------------- next part -------------- An HTML attachment was scrubbed... URL: From roberto1.antonini at telecomitalia.it Thu Sep 3 13:13:30 2015 From: roberto1.antonini at telecomitalia.it (Antonini Roberto) Date: Thu, 3 Sep 2015 11:13:30 +0000 Subject: [Fiware-robotics] R: R: R: common github repos In-Reply-To: References: <246C286B275B1B46A255552CD236DA8644CAE20A@TELMBB001BA020.telecomitalia.local> <246C286B275B1B46A255552CD236DA8644CAF52C@TELMBB001BA020.telecomitalia.local> <246C286B275B1B46A255552CD236DA8644CAF546@TELMBB001BA020.telecomitalia.local> <246C286B275B1B46A255552CD236DA8644CBB093@TELMBA001BA020.telecomitalia.local> <246C286B275B1B46A255552CD236DA8644CBD359@TELMBA001BA020.telecomitalia.local> Message-ID: <246C286B275B1B46A255552CD236DA8644CBD3CC@TELMBA001BA020.telecomitalia.local> Ikergune is accepted. Inviation sent. Thanks. R Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Jose Jaime Ariza Inviato: gioved? 3 settembre 2015 12:34 A: fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] R: R: common github repos firos at ikergune.com is the mail of the user who owns our Github, the username is Ikergune, could you use this? Thank you, Pepe On 03/09/15 12:07, Antonini Roberto wrote: I need a github user, among the ones you are using for managing your personal repos, i.e. haas85. May I use it? R Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Jose Jaime Ariza Inviato: gioved? 3 settembre 2015 10:57 A: fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] R: common github repos Hi, Could you add firos at ikergune.com as a user of https://github.com/FIWARE-RoboticsGE? Thanks :) Pepe. On 03/09/15 08:30, Antonini Roberto wrote: Hi ET guys, as all my mail got answered so far, I kindly remind you to update things on common repo github https://github.com/FIWARE-RoboticsGE, for this you need to be added as a member. So could you please provide me a reference person fort that? Thanks, Roberto. Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Antonini Roberto Inviato: marted? 1 settembre 2015 11:40 A: I?igo Gonzalez; Angel Hernandez (ahernandez at ikergune.com); Jose Jaime Ariza (jjaime at ikergune.com); fabio.dibenedetto at consoft.it Cc: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] R: common github repos An action I missed before: ? Add RCM component to common github (CONSOFT) - done R Da: Antonini Roberto Inviato: marted? 1 settembre 2015 11:38 A: Antonini Roberto; I?igo Gonzalez; Angel Hernandez (ahernandez at ikergune.com); Jose Jaime Ariza (jjaime at ikergune.com); fabio.dibenedetto at consoft.it Cc: fiware-robotics at lists.fi-ware.org; Bollano Gianmario; Garino Pierangelo Oggetto: R: common github repos Hi all, Just a summary of actions done and to do for the next deadline (4/9): ? Creation common Robotics GE github https://github.com/FIWARE-RoboticsGE (TI) - done ? Document RDAPI to APIARY http://docs.rdapi.apiary.io/# (not yet public, if you want have a look of them, ask for invitation) (TI) - done ? Fork ikergune/firos github repo to common github (see above) (TI) - done ? Taking care of syncing firos repos to our common github (ET) - to do ? Document FGFCAPI and CBAPI to APIARY (ET) - to do ? Convert apiary format to github format in order to link APIs to github (ET, TI) - to do o For this task, we are waiting for the conversion tool the FIWARE coordination has to provide us. The APs listed above are also reported on the minute, in order to keep track of them. Besides you should have been notified with JIRA issues. Let me know if something is missing. Thanks, R Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Antonini Roberto Inviato: venerd? 28 agosto 2015 14:20 A: I?igo Gonzalez; Angel Hernandez (ahernandez at ikergune.com); Jose Jaime Ariza (jjaime at ikergune.com); fabio.dibenedetto at consoft.it Cc: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] common github repos Hi all, as said previously, I created a common github account https://github.com/FIWARE-RoboticsGE, where I created two repos: FIROS and RCM If you tell me your github account, I can add you as a members so that we can share our components and links to apiary docs. Besides, I include the architecture description section into openSpecs specification wiki page (http://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/FIWARE.OpenSPecification.I2ND.Robotics_R4) in the detailed specification section and I already put both github repos address above, as Manuel suggested, Thanks, R 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. -- Jos? Jaime Ariza R&D Engineer +34 696604288 Ikergune, Etxe-Tar group -- Jos? Jaime Ariza R&D Engineer +34 696604288 Ikergune, Etxe-Tar group -------------- next part -------------- An HTML attachment was scrubbed... URL: From jjaime at ikergune.com Thu Sep 3 17:42:32 2015 From: jjaime at ikergune.com (Jose Jaime Ariza) Date: Thu, 3 Sep 2015 17:42:32 +0200 Subject: [Fiware-robotics] Slides for sprint demo Message-ID: Hi, I've made some updates to the slides. In the first slide appears this sentence: "Features listed in demo slides". It's related with the slides of the demo performed in the last demo meeting? BR Pepe -- Jos? Jaime Ariza R&D Engineer +34 696604288 Ikergune, Etxe-Tar group -------------- next part -------------- An HTML attachment was scrubbed... URL: From pierangelo.garino at telecomitalia.it Fri Sep 4 08:34:34 2015 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Fri, 4 Sep 2015 06:34:34 +0000 Subject: [Fiware-robotics] R: Slides for sprint demo In-Reply-To: References: Message-ID: Hi Pepe, Yes it is. Features developed in the last two sprints should be described here this time. BR Pier Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Jose Jaime Ariza Inviato: gioved? 3 settembre 2015 17:43 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] Slides for sprint demo Hi, I've made some updates to the slides. In the first slide appears this sentence: "Features listed in demo slides". It's related with the slides of the demo performed in the last demo meeting? BR Pepe -- Jos? Jaime Ariza R&D Engineer +34 696604288 Ikergune, Etxe-Tar group 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia2.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia2.jpg URL: From davide.colombatto at telecomitalia.it Fri Sep 4 09:52:59 2015 From: davide.colombatto at telecomitalia.it (Colombatto Davide) Date: Fri, 4 Sep 2015 07:52:59 +0000 Subject: [Fiware-robotics] R: Slides for sprint demo In-Reply-To: References: Message-ID: <069906BED271EB4A883BD9578DCDD3542812BD88@TELMBB006RM001.telecomitalia.local> Hi, I also added updates of our side. Davide Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Garino Pierangelo Inviato: venerd? 4 settembre 2015 08:35 A: Jose Jaime Ariza Cc: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] R: Slides for sprint demo Hi Pepe, Yes it is. Features developed in the last two sprints should be described here this time. BR Pier Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Jose Jaime Ariza Inviato: gioved? 3 settembre 2015 17:43 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] Slides for sprint demo Hi, I've made some updates to the slides. In the first slide appears this sentence: "Features listed in demo slides". It's related with the slides of the demo performed in the last demo meeting? BR Pepe -- Jos? Jaime Ariza R&D Engineer +34 696604288 Ikergune, Etxe-Tar group 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: From jjaime at ikergune.com Fri Sep 4 11:33:14 2015 From: jjaime at ikergune.com (Jose Jaime Ariza) Date: Fri, 4 Sep 2015 11:33:14 +0200 Subject: [Fiware-robotics] R: Slides for sprint demo References: <069906BED271EB4A883BD9578DCDD3542812BD88@TELMBB006RM001.telecomitalia.local> Message-ID: Hi, Thank you, Pier. I've just added the feature developed in S441-S442. BR -- Jos? Jaime Ariza R&D Engineer +34 696604288 Ikergune, Etxe-Tar group On 04/09/15 09:52, Colombatto Davide wrote: Hi, I also added updates of our side. Davide Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Garino Pierangelo Inviato: venerd? 4 settembre 2015 08:35 A: Jose Jaime Ariza Cc: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] R: Slides for sprint demo Hi Pepe, Yes it is. Features developed in the last two sprints should be described here this time. BR Pier Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Jose Jaime Ariza Inviato: gioved? 3 settembre 2015 17:43 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] Slides for sprint demo Hi, I've made some updates to the slides. In the first slide appears this sentence: "Features listed in demo slides". It's related with the slides of the demo performed in the last demo meeting? BR Pepe -- Jos? Jaime Ariza R&D Engineer +34 696604288 Ikergune, Etxe-Tar group 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. [data:image/gif;base64,R0lGODlhGgAoANU5AEiFNnikNyRvNcvYOafCOEOEW3DO3jB2NqjGs9ny9o+zOIOrN+L1+G+ggbzo8GCUN1SNNv///zx+NrPJOL/ROYPV44zY5YuzmrfQwCZxQlKNaMXZzOfy8NTi2TV6TuLs5vX8/ez5+4yzmtTj2cXr8mCXdKni62ycN5/f6aDf6X2qjrPl7rLl7Zu6OJbb53nS4PH188bs8sXZzfH18pq9p0SDWxhnNWbL3NfgOf///wAAAAAAAAAAAAAAAAAAAAAAACH5BAEAADkALAAAAAAaACgAAAb/wJxwSBQ6WMWkMmm6kZbQ5OvmjFoT1JuBYYWmsrcXqJvEgm8WctFypnI66pyjfXMhCmqGgR4r2S5dIBV0FjI2h3BRX20VHAUCEjZ4UHNtFo42BA+HCEskbQYOIwU2CjgBNgAZM0kMbSYcIjYCBDg4LTYLf0V6YCghNBk2DwO2OASZqkS9VBYMCB6pE8bGucidOYJUoaOptdQTFDg2ATgHGkIs2wyyAqbUtgICCwfluh8ge1sNNhDF8LYiHYKAg4INBJUS8FsAEF6AA6lsHWjg4gYKDDZONGwIAIAtCAX2hPAgYSNHj6ds3KiA8V3DAQGm2epoS4HKFQ0EmMRhc97Mwge2kN1IoIGgyQECD5wQUO6YygTkdtpCdSgqDl0VoDaVOmDBpm+oTCQoABQgBZfGbIrDAUBDAgcNDnDs98/WA504Buxa0RKgzVkB/h0oi+pDjgQhHtU1RgDioY6l8gpAJyTBCBsSFtuC6XjWTBuJhIRAgFkmwAmoAkM4mCQCBmEB1sIDIKAFRGytYfDrt4CAuAknqnrYYCXCBxGkqlYtgbtLhOcbMNSw0SBOEmg2VFj/sGHDhRLCNBC3fqFqARWhowQBADs=]Rispetta l'ambiente. Non stampare questa mail se non ? necessario. -------------- next part -------------- An HTML attachment was scrubbed... URL: From jjaime at ikergune.com Mon Sep 7 17:42:30 2015 From: jjaime at ikergune.com (Jose Jaime Ariza) Date: Mon, 7 Sep 2015 17:42:30 +0200 Subject: [Fiware-robotics] OpenSpecs Message-ID: Hi, I'm going to send FIROS Apiary link and metadata file. Please, let me know if you want me to include RDAPI Apiary link in the same mail (I'll need the metadata file) or if you have sent it yet. BR Pepe -- Jos? Jaime Ariza R&D Engineer +34 696604288 Ikergune, Etxe-Tar group From pierangelo.garino at telecomitalia.it Tue Sep 8 10:04:34 2015 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Tue, 8 Sep 2015 08:04:34 +0000 Subject: R: OpenSpecs In-Reply-To: References: Message-ID: Hi All, I suggest to work in a synchronised way, i.e. providing the whole set of Robotics GE API files to Miguel. Besides the API, all the Robotics GE contributions must be a single set of output (one inst&admin manual, one user&progr manual, one SW, etc). BR Pier -----Messaggio originale----- Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Jose Jaime Ariza Inviato: luned? 7 settembre 2015 17:43 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] OpenSpecs Hi, I'm going to send FIROS Apiary link and metadata file. Please, let me know if you want me to include RDAPI Apiary link in the same mail (I'll need the metadata file) or if you have sent it yet. BR Pepe -- Jos? Jaime Ariza R&D Engineer +34 696604288 Ikergune, Etxe-Tar group _______________________________________________ Fiware-robotics mailing list Fiware-robotics at lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-robotics 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. From roberto1.antonini at telecomitalia.it Tue Sep 8 10:19:25 2015 From: roberto1.antonini at telecomitalia.it (Antonini Roberto) Date: Tue, 8 Sep 2015 08:19:25 +0000 Subject: R: OpenSpecs In-Reply-To: References: Message-ID: <246C286B275B1B46A255552CD236DA8644CC3D9F@TELMBA001BA020.telecomitalia.local> Hi Pepe, The metadata has to be insert into apib file, if I'm not wrong? We have compiled our apib file, but we haven't sent it to Miguel yet, as we are waiting info about copyright from Pier and Gianmario. What about your copyright apis? R -----Messaggio originale----- Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Jose Jaime Ariza Inviato: luned? 7 settembre 2015 17:43 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] OpenSpecs Hi, I'm going to send FIROS Apiary link and metadata file. Please, let me know if you want me to include RDAPI Apiary link in the same mail (I'll need the metadata file) or if you have sent it yet. BR Pepe -- Jos? Jaime Ariza R&D Engineer +34 696604288 Ikergune, Etxe-Tar group _______________________________________________ Fiware-robotics mailing list Fiware-robotics at lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-robotics 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. From jjaime at ikergune.com Tue Sep 8 10:30:23 2015 From: jjaime at ikergune.com (Jose Jaime Ariza) Date: Tue, 8 Sep 2015 10:30:23 +0200 Subject: R: OpenSpecs References: <246C286B275B1B46A255552CD236DA8644CC3D9F@TELMBA001BA020.telecomitalia.local> Message-ID: Hi, Since the tracking document has one column for APIB file and another one for the metadata, I understand that they must be I separated files. We are using MIT license for FIROS. You can find our metadata file in http://130.206.122.27/firos-metadata.apib. BTW: since it's 10:30 and there is not any active hangout, I'm supposing that we are not going to have the weekly robotics call. BR, Pepe Jos? Jaime Ariza R&D Engineer +34 696604288 Ikergune, Etxe-Tar group On 08/09/15 10:19, Antonini Roberto wrote: Hi Pepe, The metadata has to be insert into apib file, if I'm not wrong? We have compiled our apib file, but we haven't sent it to Miguel yet, as we are waiting info about copyright from Pier and Gianmario. What about your copyright apis? R -----Messaggio originale----- Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Jose Jaime Ariza Inviato: luned? 7 settembre 2015 17:43 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] OpenSpecs Hi, I'm going to send FIROS Apiary link and metadata file. Please, let me know if you want me to include RDAPI Apiary link in the same mail (I'll need the metadata file) or if you have sent it yet. BR Pepe -- Jos? Jaime Ariza R&D Engineer +34 696604288 Ikergune, Etxe-Tar group _______________________________________________ Fiware-robotics mailing list Fiware-robotics at lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-robotics 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: From fabio.dibenedetto at consoft.it Tue Sep 8 11:00:11 2015 From: fabio.dibenedetto at consoft.it (fabio.dibenedetto at consoft.it) Date: Tue, 8 Sep 2015 09:00:11 +0000 Subject: R: OpenSpecs In-Reply-To: References: Message-ID: <4ee3d723ece84a75a5857582c1453a87@EXCHMBX2.consoft.it> Hi, so this means that the installation package I produced for rcm must contain and install firos too, right? Or the common package should be applied only for the dockerization? The inst&admin guide is available in the common repository created by Roberto under the rst format (used for the readthedocs site as requested in the guideline somewhere) but there is only the rcm part and in any case is under the rcm branch: what should we do in that case? Duplicate it or what? For rcm I did a script for installing all we need except the components used for the interaction (rcm driver and firos): should I extend the script? But this means that the installation of firos will be hidden in the process and so not documented? What about their additional configuration? Fabio -----Messaggio originale----- Da: fiware-robotics-bounces at lists.fiware.org [mailto:fiware-robotics-bounces at lists.fiware.org] Per conto di Garino Pierangelo Inviato: marted? 8 settembre 2015 10:05 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] R: OpenSpecs Hi All, I suggest to work in a synchronised way, i.e. providing the whole set of Robotics GE API files to Miguel. Besides the API, all the Robotics GE contributions must be a single set of output (one inst&admin manual, one user&progr manual, one SW, etc). BR Pier -----Messaggio originale----- Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Jose Jaime Ariza Inviato: luned? 7 settembre 2015 17:43 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] OpenSpecs Hi, I'm going to send FIROS Apiary link and metadata file. Please, let me know if you want me to include RDAPI Apiary link in the same mail (I'll need the metadata file) or if you have sent it yet. BR Pepe -- Jos? Jaime Ariza R&D Engineer +34 696604288 Ikergune, Etxe-Tar group _______________________________________________ Fiware-robotics mailing list Fiware-robotics at lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-robotics 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. _______________________________________________ Fiware-robotics mailing list Fiware-robotics at lists.fiware.org https://lists.fiware.org/listinfo/fiware-robotics-new From pierangelo.garino at telecomitalia.it Tue Sep 8 14:08:59 2015 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Tue, 8 Sep 2015 12:08:59 +0000 Subject: R: OpenSpecs In-Reply-To: <4ee3d723ece84a75a5857582c1453a87@EXCHMBX2.consoft.it> References: <4ee3d723ece84a75a5857582c1453a87@EXCHMBX2.consoft.it> Message-ID: Dear All, By considering the entire process of GE delivery, we must provide a unique set of manuals, SW packages, etc. This means that we need to deliver one installation&administration manual and one user&programmers guide. For those parts which are specific to each component, they should be inserted as specific sections in those documents. At the same time, the SW must be provided as unique package. It is therefore necessary to create a 'Robotics' repository in github where the 'src' folder will contain both RCM and FIROS sources (how to structure the sources is up to you). This will allow creating the single .md, .rst and specific documentation files, and be fully compliant with the guidelines. Finally, I believe it is acceptable to have different API description files, hence you can keep them separate, but as I already said I strongly suggest they are delivered together. Thanks and BR Pier BR Pier -----Messaggio originale----- Da: fiware-robotics-bounces at lists.fiware.org [mailto:fiware-robotics-bounces at lists.fiware.org] Per conto di fabio.dibenedetto at consoft.it Inviato: marted? 8 settembre 2015 11:00 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] R: OpenSpecs Hi, so this means that the installation package I produced for rcm must contain and install firos too, right? Or the common package should be applied only for the dockerization? The inst&admin guide is available in the common repository created by Roberto under the rst format (used for the readthedocs site as requested in the guideline somewhere) but there is only the rcm part and in any case is under the rcm branch: what should we do in that case? Duplicate it or what? For rcm I did a script for installing all we need except the components used for the interaction (rcm driver and firos): should I extend the script? But this means that the installation of firos will be hidden in the process and so not documented? What about their additional configuration? Fabio -----Messaggio originale----- Da: fiware-robotics-bounces at lists.fiware.org [mailto:fiware-robotics-bounces at lists.fiware.org] Per conto di Garino Pierangelo Inviato: marted? 8 settembre 2015 10:05 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] R: OpenSpecs Hi All, I suggest to work in a synchronised way, i.e. providing the whole set of Robotics GE API files to Miguel. Besides the API, all the Robotics GE contributions must be a single set of output (one inst&admin manual, one user&progr manual, one SW, etc). BR Pier -----Messaggio originale----- Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Jose Jaime Ariza Inviato: luned? 7 settembre 2015 17:43 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] OpenSpecs Hi, I'm going to send FIROS Apiary link and metadata file. Please, let me know if you want me to include RDAPI Apiary link in the same mail (I'll need the metadata file) or if you have sent it yet. BR Pepe -- Jos? Jaime Ariza R&D Engineer +34 696604288 Ikergune, Etxe-Tar group _______________________________________________ Fiware-robotics mailing list Fiware-robotics at lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-robotics 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. _______________________________________________ Fiware-robotics mailing list Fiware-robotics at lists.fiware.org https://lists.fiware.org/listinfo/fiware-robotics-new _______________________________________________ Fiware-robotics mailing list Fiware-robotics at lists.fiware.org https://lists.fiware.org/listinfo/fiware-robotics-new From pierangelo.garino at telecomitalia.it Wed Sep 9 14:13:08 2015 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Wed, 9 Sep 2015 12:13:08 +0000 Subject: Fiware Lab account updates Message-ID: Dear All, I'm happy to inform you that we'got two floating IP addresses, i.e. 193.205.211.104 and 193.205.211.102, for the robotics GE account! The snapshot of our VMs are ready to be launched in the 'images' section. However, as far as I was told we might need to recreate the keypairs and the security group list. BR Pier ------------------------------------------------------------------ Telecom Italia Pierangelo Garino Strategy & Innovation 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia2.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia2.jpg URL: From roberto1.antonini at telecomitalia.it Wed Sep 9 17:25:59 2015 From: roberto1.antonini at telecomitalia.it (Antonini Roberto) Date: Wed, 9 Sep 2015 15:25:59 +0000 Subject: R: R: OpenSpecs In-Reply-To: References: <246C286B275B1B46A255552CD236DA8644CC3D9F@TELMBA001BA020.telecomitalia.local> Message-ID: <246C286B275B1B46A255552CD236DA8644CC468C@TELMBA001BA020.telecomitalia.local> Hi Pepe, here attached you can find the APIB file, including also metadatas. As far as I understand, metadatas are in the APIARY format, for this reason we included them in apib file. Besides, the apib file was fetched by apiaryio command, I installed on my laptop https://client.apiary.io/ . Thanks for infos about license. Roberto Da: fiware-robotics-bounces at lists.fiware.org [mailto:fiware-robotics-bounces at lists.fiware.org] Per conto di Jose Jaime Ariza Inviato: marted? 8 settembre 2015 10:30 A: fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] R: OpenSpecs Hi, Since the tracking document has one column for APIB file and another one for the metadata, I understand that they must be I separated files. We are using MIT license for FIROS. You can find our metadata file in http://130.206.122.27/firos-metadata.apib. BTW: since it's 10:30 and there is not any active hangout, I'm supposing that we are not going to have the weekly robotics call. BR, Pepe Jos? Jaime Ariza R&D Engineer +34 696604288 Ikergune, Etxe-Tar group On 08/09/15 10:19, Antonini Roberto wrote: Hi Pepe, The metadata has to be insert into apib file, if I'm not wrong? We have compiled our apib file, but we haven't sent it to Miguel yet, as we are waiting info about copyright from Pier and Gianmario. What about your copyright apis? R -----Messaggio originale----- Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Jose Jaime Ariza Inviato: luned? 7 settembre 2015 17:43 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] OpenSpecs Hi, I'm going to send FIROS Apiary link and metadata file. Please, let me know if you want me to include RDAPI Apiary link in the same mail (I'll need the metadata file) or if you have sent it yet. BR Pepe -- Jos? Jaime Ariza R&D Engineer +34 696604288 Ikergune, Etxe-Tar group _______________________________________________ Fiware-robotics mailing list Fiware-robotics at lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-robotics 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: rdapi.apib Type: application/octet-stream Size: 15742 bytes Desc: rdapi.apib URL: From gianmario.bollano at telecomitalia.it Tue Sep 15 10:08:45 2015 From: gianmario.bollano at telecomitalia.it (Bollano Gianmario) Date: Tue, 15 Sep 2015 08:08:45 +0000 Subject: Robotics call Message-ID: <7E649CBD84A947498203DAF8F098B1F6482EB2E1@telmba003ba020.telecomitalia.local> Hi all, we would like to have the Robotics call as usual with hangout. Minutes as usual here: https://docs.google.com/document/d/1CAwhNqoMf7KnP_yHjITo2gRrVoWCKMsthiWX3ZWWLHo/edit?pli=1 __________________________________________________ Telecom Italia | TIM Gianmario Bollano Strategy & Innovation - Business Positioning Trusted Digital Via Reiss Romoli 274, 10148 Torino, Italy +39 011 2287103 +39 331 6015048 Tim Official: Facebook - Twitter www.tim.it 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia2.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia2.jpg URL: From fabio.dibenedetto at consoft.it Tue Sep 15 13:19:55 2015 From: fabio.dibenedetto at consoft.it (fabio.dibenedetto at consoft.it) Date: Tue, 15 Sep 2015 11:19:55 +0000 Subject: github In-Reply-To: <7E649CBD84A947498203DAF8F098B1F6482EB2E1@telmba003ba020.telecomitalia.local> References: <7E649CBD84A947498203DAF8F098B1F6482EB2E1@telmba003ba020.telecomitalia.local> Message-ID: Hi guys, I've just committed the files I told you this morning (the RCM part and the common files) in github. Now the structure of the repository has 2 main folders with the 2 main components of Robotics (where the firos folder is a submodule and so a link to their main repository), 2 other folders (docs and script) in which there are the common documentation (docs) and the common scripts (scripts). I've put a common LICENSE.txt and a README.md. The docs folder contains what sphinx uses to create epub, html, pdf from rst file: the rst files are the files that we have to import in readthedocs in order to provide the documentation and for now are taken from the RCM part (but in any case even the RCM part is still to be modified). The same thing is for what concern the scripts folder: the files into it are taken from RCM part and are to be modified (I'll update them as soon as possible because from that folder they doesn't do their job): create_rcm_platform_pkg is a python script used to create the packages for the installation (not docker) and tries to create rcm master, rcm robot, rcm driver, robotics_msgs and firos; the shell scripts are for the install (all install_* and sub_inst_*) and uninstall (uninstall and sub_uninstall) where _m is for the rcm master while _r is for the robot: the master asks for the installation of firos in the user interaction. Fabio -------------- next part -------------- An HTML attachment was scrubbed... URL: From davide.colombatto at telecomitalia.it Tue Sep 15 13:48:29 2015 From: davide.colombatto at telecomitalia.it (Colombatto Davide) Date: Tue, 15 Sep 2015 11:48:29 +0000 Subject: Github account Message-ID: <069906BED271EB4A883BD9578DCDD35428132542@TELMBB006RM001.telecomitalia.local> Hi all, we have added Gianmario and Ikergune users as owner of the common github account (https://github.com/FIWARE-RoboticsGE) but we don't see you, yet. Do you have received the invite by email? BR, Davide 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia2.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia2.jpg URL: From gianmario.bollano at telecomitalia.it Tue Sep 15 14:53:17 2015 From: gianmario.bollano at telecomitalia.it (Bollano Gianmario) Date: Tue, 15 Sep 2015 12:53:17 +0000 Subject: R: Github account In-Reply-To: <069906BED271EB4A883BD9578DCDD35428132542@TELMBB006RM001.telecomitalia.local> References: <069906BED271EB4A883BD9578DCDD35428132542@TELMBB006RM001.telecomitalia.local> Message-ID: <7E649CBD84A947498203DAF8F098B1F6482EB57D@telmba003ba020.telecomitalia.local> Hi all, I haven't received any invite by e-mail, however logging-in Github I've seen a button saying "You've Been invited to FIWARE-RoboticsGE" and to accept it. It seems no e-mail will be sent, I guess the invite is displayed and accepted logging in the personal Github account. Gianmario Da: fiware-robotics-bounces at lists.fiware.org [mailto:fiware-robotics-bounces at lists.fiware.org] Per conto di Colombatto Davide Inviato: marted? 15 settembre 2015 13:48 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] Github account Hi all, we have added Gianmario and Ikergune users as owner of the common github account (https://github.com/FIWARE-RoboticsGE) but we don't see you, yet. Do you have received the invite by email? BR, Davide 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. 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia2.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia2.jpg URL: From gianmario.bollano at telecomitalia.it Tue Sep 15 14:57:50 2015 From: gianmario.bollano at telecomitalia.it (Bollano Gianmario) Date: Tue, 15 Sep 2015 12:57:50 +0000 Subject: R: Github RoboticsGE account Message-ID: <7E649CBD84A947498203DAF8F098B1F6482EB59E@telmba003ba020.telecomitalia.local> The instructions says "the invitation is sent by e-mail" (though I don't have received any) and "can be accepted at https://github.com/orgs/FIWARE-RoboticsGE ". Please See the enclosed image (captured from Project page). [cid:image001.png at 01D0EFC6.E03C5DC0] Gianmario Da: fiware-robotics-bounces at lists.fiware.org [mailto:fiware-robotics-bounces at lists.fiware.org] Per conto di Bollano Gianmario Inviato: marted? 15 settembre 2015 14:53 A: Colombatto Davide; fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] R: Github account Hi all, I haven't received any invite by e-mail, however logging-in Github I've seen a button saying "You've Been invited to FIWARE-RoboticsGE" and to accept it. It seems no e-mail will be sent, I guess the invite is displayed and accepted logging in the personal Github account. Gianmario Da: fiware-robotics-bounces at lists.fiware.org [mailto:fiware-robotics-bounces at lists.fiware.org] Per conto di Colombatto Davide Inviato: marted? 15 settembre 2015 13:48 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] Github account Hi all, we have added Gianmario and Ikergune users as owner of the common github account (https://github.com/FIWARE-RoboticsGE) but we don't see you, yet. Do you have received the invite by email? BR, Davide 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. 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. 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 8164 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.gif Type: image/gif Size: 677 bytes Desc: image002.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia2.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia2.jpg URL: From gianmario.bollano at telecomitalia.it Tue Sep 15 15:34:06 2015 From: gianmario.bollano at telecomitalia.it (Bollano Gianmario) Date: Tue, 15 Sep 2015 13:34:06 +0000 Subject: R: github In-Reply-To: References: <7E649CBD84A947498203DAF8F098B1F6482EB2E1@telmba003ba020.telecomitalia.local> Message-ID: <7E649CBD84A947498203DAF8F098B1F6482EB5F5@telmba003ba020.telecomitalia.local> To summarize the structure created and described by Fabio, we have component folders for the code (green color below) and the common folders (red color), as in the picture below: [cid:image001.png at 01D0EFCB.F4B02B10] Editing of the red folders should be done jointly because refers to the Robotics GE. Gianmario Da: fiware-robotics-bounces at lists.fiware.org [mailto:fiware-robotics-bounces at lists.fiware.org] Per conto di fabio.dibenedetto at consoft.it Inviato: marted? 15 settembre 2015 13:20 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] github Hi guys, I've just committed the files I told you this morning (the RCM part and the common files) in github. Now the structure of the repository has 2 main folders with the 2 main components of Robotics (where the firos folder is a submodule and so a link to their main repository), 2 other folders (docs and script) in which there are the common documentation (docs) and the common scripts (scripts). I've put a common LICENSE.txt and a README.md. The docs folder contains what sphinx uses to create epub, html, pdf from rst file: the rst files are the files that we have to import in readthedocs in order to provide the documentation and for now are taken from the RCM part (but in any case even the RCM part is still to be modified). The same thing is for what concern the scripts folder: the files into it are taken from RCM part and are to be modified (I'll update them as soon as possible because from that folder they doesn't do their job): create_rcm_platform_pkg is a python script used to create the packages for the installation (not docker) and tries to create rcm master, rcm robot, rcm driver, robotics_msgs and firos; the shell scripts are for the install (all install_* and sub_inst_*) and uninstall (uninstall and sub_uninstall) where _m is for the rcm master while _r is for the robot: the master asks for the installation of firos in the user interaction. Fabio 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 54119 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia2.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia2.jpg URL: From fabio.dibenedetto at consoft.it Tue Sep 15 16:03:52 2015 From: fabio.dibenedetto at consoft.it (fabio.dibenedetto at consoft.it) Date: Tue, 15 Sep 2015 14:03:52 +0000 Subject: R: github In-Reply-To: <7E649CBD84A947498203DAF8F098B1F6482EB5F5@telmba003ba020.telecomitalia.local> References: <7E649CBD84A947498203DAF8F098B1F6482EB2E1@telmba003ba020.telecomitalia.local> <7E649CBD84A947498203DAF8F098B1F6482EB5F5@telmba003ba020.telecomitalia.local> Message-ID: I've already changed something in scripts folder (more common names and right paths pointing to the elements needed): about that this morning I was speaking about a problem with firos installation that I did; the problem is the following CMake Error at /opt/ros/indigo/share/genmsg/cmake/genmsg-extras.cmake:91 (message): add_message_files() directory not found: /home/fabiog/rcmp_ws/src/firos/msg Call Stack (most recent call first): firos/CMakeLists.txt:59 (add_message_files) -- Configuring incomplete, errors occurred! See also "/home/fabiog/rcmp_ws/build/CMakeFiles/CMakeOutput.log". See also "/home/fabiog/rcmp_ws/build/CMakeFiles/CMakeError.log". Invoking "cmake" failed This happens during the installation when the installer compiles the ros workspace (rcmp_ws/src) where the ros nodes are put. As I said in the call I was trying to not insert the srv and msg folders (because they are the folders useless because we use robotics_msgs package in which there these folders as the common language between rcm and firos into ROS environment). This is the reason why I asked you if you use robotics_msgs. Maybe is only a problem in configuration into the CMakeLists.txt, but it has to be corrected if we want the script to get the files from the code sources and put them into the installation package Da: Bollano Gianmario [mailto:gianmario.bollano at telecomitalia.it] Inviato: marted? 15 settembre 2015 15:34 A: fabio.dibenedetto at consoft.it; fiware-robotics at lists.fi-ware.org Oggetto: R: github To summarize the structure created and described by Fabio, we have component folders for the code (green color below) and the common folders (red color), as in the picture below: [cid:image001.png at 01D0EFCD.7016F030] Editing of the red folders should be done jointly because refers to the Robotics GE. Gianmario Da: fiware-robotics-bounces at lists.fiware.org [mailto:fiware-robotics-bounces at lists.fiware.org] Per conto di fabio.dibenedetto at consoft.it Inviato: marted? 15 settembre 2015 13:20 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] github Hi guys, I've just committed the files I told you this morning (the RCM part and the common files) in github. Now the structure of the repository has 2 main folders with the 2 main components of Robotics (where the firos folder is a submodule and so a link to their main repository), 2 other folders (docs and script) in which there are the common documentation (docs) and the common scripts (scripts). I've put a common LICENSE.txt and a README.md. The docs folder contains what sphinx uses to create epub, html, pdf from rst file: the rst files are the files that we have to import in readthedocs in order to provide the documentation and for now are taken from the RCM part (but in any case even the RCM part is still to be modified). The same thing is for what concern the scripts folder: the files into it are taken from RCM part and are to be modified (I'll update them as soon as possible because from that folder they doesn't do their job): create_rcm_platform_pkg is a python script used to create the packages for the installation (not docker) and tries to create rcm master, rcm robot, rcm driver, robotics_msgs and firos; the shell scripts are for the install (all install_* and sub_inst_*) and uninstall (uninstall and sub_uninstall) where _m is for the rcm master while _r is for the robot: the master asks for the installation of firos in the user interaction. Fabio 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 54119 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.gif Type: image/gif Size: 677 bytes Desc: image002.gif URL: From fabio.dibenedetto at consoft.it Tue Sep 15 17:01:34 2015 From: fabio.dibenedetto at consoft.it (fabio.dibenedetto at consoft.it) Date: Tue, 15 Sep 2015 15:01:34 +0000 Subject: R: github In-Reply-To: References: <7E649CBD84A947498203DAF8F098B1F6482EB2E1@telmba003ba020.telecomitalia.local> <7E649CBD84A947498203DAF8F098B1F6482EB5F5@telmba003ba020.telecomitalia.local> Message-ID: <986111b0c16946668df33582e86e04b6@EXCHMBX2.consoft.it> I've cleaned the CMakeLists.txt and package.xml of rcm_driver and robotics_msgs: if you look at the files in RCM/src/rcm (this is the rcm_driver) you can see how rcm_driver is configured to use the common robotics_msgs (RCM/src/robotics_msgs). Firos should be configured in the same way to use robotics_msgs. As I said before the vacation the code should point to robotics_msgs and not import std_msgs.msg from firos.srv import FIROS_Info from firos.msg import Robot_Event, CB_Event as you do in topicManager.py but from robotics_msgs.msg import Robot_Event from robotics_msgs.msg import CB_Event from robotics_msgs.srv import FIROS_Info, FIROS_InfoResponse robotics_msgs is a common package even if I put it into RCM branch; it is the implementation of what we discussed in the open specs (in fact I put all the partners into its license). Rcm_driver uses it and if you need you can use it as an example for the use of robotics_msgs to update firos accordingly Da: fiware-robotics-bounces at lists.fiware.org [mailto:fiware-robotics-bounces at lists.fiware.org] Per conto di fabio.dibenedetto at consoft.it Inviato: marted? 15 settembre 2015 16:04 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] R: github I've already changed something in scripts folder (more common names and right paths pointing to the elements needed): about that this morning I was speaking about a problem with firos installation that I did; the problem is the following CMake Error at /opt/ros/indigo/share/genmsg/cmake/genmsg-extras.cmake:91 (message): add_message_files() directory not found: /home/fabiog/rcmp_ws/src/firos/msg Call Stack (most recent call first): firos/CMakeLists.txt:59 (add_message_files) -- Configuring incomplete, errors occurred! See also "/home/fabiog/rcmp_ws/build/CMakeFiles/CMakeOutput.log". See also "/home/fabiog/rcmp_ws/build/CMakeFiles/CMakeError.log". Invoking "cmake" failed This happens during the installation when the installer compiles the ros workspace (rcmp_ws/src) where the ros nodes are put. As I said in the call I was trying to not insert the srv and msg folders (because they are the folders useless because we use robotics_msgs package in which there these folders as the common language between rcm and firos into ROS environment). This is the reason why I asked you if you use robotics_msgs. Maybe is only a problem in configuration into the CMakeLists.txt, but it has to be corrected if we want the script to get the files from the code sources and put them into the installation package Da: Bollano Gianmario [mailto:gianmario.bollano at telecomitalia.it] Inviato: marted? 15 settembre 2015 15:34 A: fabio.dibenedetto at consoft.it; fiware-robotics at lists.fi-ware.org Oggetto: R: github To summarize the structure created and described by Fabio, we have component folders for the code (green color below) and the common folders (red color), as in the picture below: [cid:image001.png at 01D0EFD4.80A6BAA0] Editing of the red folders should be done jointly because refers to the Robotics GE. Gianmario Da: fiware-robotics-bounces at lists.fiware.org [mailto:fiware-robotics-bounces at lists.fiware.org] Per conto di fabio.dibenedetto at consoft.it Inviato: marted? 15 settembre 2015 13:20 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] github Hi guys, I've just committed the files I told you this morning (the RCM part and the common files) in github. Now the structure of the repository has 2 main folders with the 2 main components of Robotics (where the firos folder is a submodule and so a link to their main repository), 2 other folders (docs and script) in which there are the common documentation (docs) and the common scripts (scripts). I've put a common LICENSE.txt and a README.md. The docs folder contains what sphinx uses to create epub, html, pdf from rst file: the rst files are the files that we have to import in readthedocs in order to provide the documentation and for now are taken from the RCM part (but in any case even the RCM part is still to be modified). The same thing is for what concern the scripts folder: the files into it are taken from RCM part and are to be modified (I'll update them as soon as possible because from that folder they doesn't do their job): create_rcm_platform_pkg is a python script used to create the packages for the installation (not docker) and tries to create rcm master, rcm robot, rcm driver, robotics_msgs and firos; the shell scripts are for the install (all install_* and sub_inst_*) and uninstall (uninstall and sub_uninstall) where _m is for the rcm master while _r is for the robot: the master asks for the installation of firos in the user interaction. Fabio 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 54119 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.gif Type: image/gif Size: 677 bytes Desc: image002.gif URL: From fabio.dibenedetto at consoft.it Wed Sep 16 10:39:57 2015 From: fabio.dibenedetto at consoft.it (fabio.dibenedetto at consoft.it) Date: Wed, 16 Sep 2015 08:39:57 +0000 Subject: R: github In-Reply-To: References: <7E649CBD84A947498203DAF8F098B1F6482EB2E1@telmba003ba020.telecomitalia.local> <7E649CBD84A947498203DAF8F098B1F6482EB5F5@telmba003ba020.telecomitalia.local> Message-ID: <12e6803998ce4b4ba546455da4101586@EXCHMBX2.consoft.it> Hi guys, I added a new folder into common docs: it is called api and contains the html result of apiary (after the convertion through the fiware tool). I put it in the common docs and in the RCM specific docs so we have both the way to see (as part of a unique robotics component and as rcm specific). If it's ok I'd ask to do the same with firos html; let me know Fabio -------------- next part -------------- An HTML attachment was scrubbed... URL: From pierangelo.garino at telecomitalia.it Thu Sep 17 11:08:34 2015 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Thu, 17 Sep 2015 09:08:34 +0000 Subject: Annullato: FIWARE Robotics Periodic confcall Message-ID: Hi All, this is the periodic reminder for the Robotics Confcall. We'll stay within 1h of call. We'll use powwownow, numbers to dial can be found at link http://www.powwownow.com/International-DialIn-Numbers/ PIN 075102 BR Pier 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 4479 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia2.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia2.jpg URL: From jjaime at ikergune.com Thu Sep 17 16:52:06 2015 From: jjaime at ikergune.com (Jose Jaime Ariza) Date: Thu, 17 Sep 2015 16:52:06 +0200 Subject: [Fiware-robotics] R: github References: <7E649CBD84A947498203DAF8F098B1F6482EB2E1@telmba003ba020.telecomitalia.local> <7E649CBD84A947498203DAF8F098B1F6482EB5F5@telmba003ba020.telecomitalia.local> <12e6803998ce4b4ba546455da4101586@EXCHMBX2.consoft.it> Message-ID: Hi, I've just added the FIROS apiary-generated files. BR, Pepe. Jos? Jaime Ariza R&D Engineer +34 696604288 Ikergune, Etxe-Tar group On 16/09/15 10:41, fabio.dibenedetto at consoft.it wrote: Hi guys, I added a new folder into common docs: it is called api and contains the html result of apiary (after the convertion through the fiware tool). I put it in the common docs and in the RCM specific docs so we have both the way to see (as part of a unique robotics component and as rcm specific). If it?s ok I?d ask to do the same with firos html; let me know Fabio -------------- next part -------------- An HTML attachment was scrubbed... URL: From jjaime at ikergune.com Fri Sep 18 14:02:53 2015 From: jjaime at ikergune.com (Jose Jaime Ariza) Date: Fri, 18 Sep 2015 14:02:53 +0200 Subject: FIWARE standardization Message-ID: Hi Pier, Here you have our proposed standardization activity: Date of activity = Plan SDO as link = http://www.osrfoundation.org (Open Source Robotics Foundation) Relevant FIWARE GE, GEi or Interface = Robotics Contribute or Monitor = Monitor, consider contribution in future SDO work-item or topic to monitor/contribute = ROS 2.0 (http://design.ros2.org/) Responsible Partner(s) and Person(s) = ET Stds-Phase, Comment & Status = ET is monitoring the evolution of ROS 2.0 (currently in alpha stage). We'll consider the implementation of FIROS for ROS 2.0 as soon its stability is improved. If you need me to add it to the wiki, please let me know. BR Pepe -- Jos? Jaime Ariza R&D Engineer +34 696604288 Ikergune, Etxe-Tar group From pierangelo.garino at telecomitalia.it Fri Sep 18 17:08:54 2015 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Fri, 18 Sep 2015 15:08:54 +0000 Subject: R: FIWARE standardization In-Reply-To: References: Message-ID: Hi Pepe, Thanks a lot, I'll integrate myself your contribution in the wiki table. BR Pier -----Messaggio originale----- Da: Jose Jaime Ariza [mailto:jjaime at ikergune.com] Inviato: venerd? 18 settembre 2015 14:03 A: Garino Pierangelo; fiware-robotics at lists.fi-ware.org Oggetto: FIWARE standardization Hi Pier, Here you have our proposed standardization activity: Date of activity = Plan SDO as link = http://www.osrfoundation.org (Open Source Robotics Foundation) Relevant FIWARE GE, GEi or Interface = Robotics Contribute or Monitor = Monitor, consider contribution in future SDO work-item or topic to monitor/contribute = ROS 2.0 (http://design.ros2.org/) Responsible Partner(s) and Person(s) = ET Stds-Phase, Comment & Status = ET is monitoring the evolution of ROS 2.0 (currently in alpha stage). We'll consider the implementation of FIROS for ROS 2.0 as soon its stability is improved. If you need me to add it to the wiki, please let me know. BR Pepe -- Jos? Jaime Ariza R&D Engineer +34 696604288 Ikergune, Etxe-Tar group 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. From gianmario.bollano at telecomitalia.it Tue Sep 22 10:14:01 2015 From: gianmario.bollano at telecomitalia.it (Bollano Gianmario) Date: Tue, 22 Sep 2015 08:14:01 +0000 Subject: Weekly Robotics call Message-ID: <7E649CBD84A947498203DAF8F098B1F6484C77B1@telmbb003ba020.telecomitalia.local> Hi all, I apologize to be late; I'm still having problems at the hangout connection through wi-fi hotspot from my smartphone. I'm calling you now via hangout for the weekly Robotics call. The minutes are , as usual, https://docs.google.com/document/d/1CAwhNqoMf7KnP_yHjITo2gRrVoWCKMsthiWX3ZWWLHo/edit?pli=1 Gianmario 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia2.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia2.jpg URL: From gianmario.bollano at telecomitalia.it Tue Sep 22 10:15:38 2015 From: gianmario.bollano at telecomitalia.it (Bollano Gianmario) Date: Tue, 22 Sep 2015 08:15:38 +0000 Subject: Robotics call Message-ID: <7E649CBD84A947498203DAF8F098B1F6484C77DE@telmbb003ba020.telecomitalia.local> Hi all, You are invited at the weekly Robotics call via hangout. Minutes are as usual here: https://docs.google.com/document/d/1CAwhNqoMf7KnP_yHjITo2gRrVoWCKMsthiWX3ZWWLHo/edit?pli=1 Best, Gianmario 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 2540 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia2.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia2.jpg URL: From gianmario.bollano at telecomitalia.it Tue Sep 22 11:19:35 2015 From: gianmario.bollano at telecomitalia.it (Bollano Gianmario) Date: Tue, 22 Sep 2015 09:19:35 +0000 Subject: Minutes and Actions for Robotics GE Message-ID: <7E649CBD84A947498203DAF8F098B1F6484C78C0@telmbb003ba020.telecomitalia.local> Dear all, please find the minutes of the Robotics call of today. We have few but important Action Points. Please check them. Robotics GE Call - 22/09/15 * Install & Admin Guide : We have a first release of the Inst&Admin Robotics containing a common installation of the Robotics GE. Actions are: * AP0: Anyone check the Guide to commonly agree and improve the Guide (by adding content if needed). The document should contain all the needed information for a complete installation of the Robotics GE * AP1: Two missing sections (strictly required) are "Sanity Check procedures" and "Diagnosis Procedure". These mandatory section should provide a simple test (e.g. running a command with some expected result) that is used by the administrator (programmer) to check that the GE installation was successful. These sections contain some small subsection (e.g. to provide typical resource usage). Please refer to section 3.2.2 of the document Guidelines for R4 (https://docs.google.com/document/d/1wa15t2dSEucSA1xD7FyOLpP0ymihYYry0mhALV6GsXU/edit?pli=1 ) * AP2: Add some simple command to install the library/component dependencies (e.g. OpenVPN) and add link to Web Pages for their configuration * User&Programmer Guide. A first release of User&Programmer Robotics is now available. Content of this guide is free (expected example of commands and snippets of code to be used as example of usage of Robotics GE). Actions are: * AP3: Anyone check and improve/ add content to the Guide. * Images and Dockerization are ongoing . Current actions: * AP4: Agreed to prepare Image that contain all the code but without installation of dependencies (e.g. OpenVPN). The Adminstrator/Programmer will refer to the SW Guides (Install & Admin and User&Programmer) to retrieve instructions to complete the installation and to configure the Robotics GE for his/her needs. * ReadTheDocs: Guides are available not also at a common page at readTheDocs (https://fiware-robotics.readthedocs.org/en/latest/ ). * AP5: Since there is no automatic synchronization between Github and readTheDocs, agreed to edit the Guides in Github only, then to manually import them in ReadTheDocs to avoid misalignment. Best, Gianmario 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia2.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia2.jpg URL: From gianmario.bollano at telecomitalia.it Tue Sep 22 11:23:29 2015 From: gianmario.bollano at telecomitalia.it (Bollano Gianmario) Date: Tue, 22 Sep 2015 09:23:29 +0000 Subject: R: Minutes and Actions for Robotics GE Message-ID: <7E649CBD84A947498203DAF8F098B1F6484C88E0@telmbb003ba020.telecomitalia.local> I apologize for a mistyping in the last bullet: "Guides are now available also at a common page at readTheDocs..." Gianmario Da: Bollano Gianmario Inviato: marted? 22 settembre 2015 11:20 A: fiware-robotics at lists.fi-ware.org Oggetto: Minutes and Actions for Robotics GE Dear all, please find the minutes of the Robotics call of today. We have few but important Action Points. Please check them. Robotics GE Call - 22/09/15 ? Install & Admin Guide : We have a first release of the Inst&Admin Robotics containing a common installation of the Robotics GE. Actions are: ? AP0: Anyone check the Guide to commonly agree and improve the Guide (by adding content if needed). The document should contain all the needed information for a complete installation of the Robotics GE ? AP1: Two missing sections (strictly required) are "Sanity Check procedures" and "Diagnosis Procedure". These mandatory section should provide a simple test (e.g. running a command with some expected result) that is used by the administrator (programmer) to check that the GE installation was successful. These sections contain some small subsection (e.g. to provide typical resource usage). Please refer to section 3.2.2 of the document Guidelines for R4 (https://docs.google.com/document/d/1wa15t2dSEucSA1xD7FyOLpP0ymihYYry0mhALV6GsXU/edit?pli=1 ) ? AP2: Add some simple command to install the library/component dependencies (e.g. OpenVPN) and add link to Web Pages for their configuration ? User&Programmer Guide. A first release of User&Programmer Robotics is now available. Content of this guide is free (expected example of commands and snippets of code to be used as example of usage of Robotics GE). Actions are: ? AP3: Anyone check and improve/ add content to the Guide. ? Images and Dockerization are ongoing . Current actions: ? AP4: Agreed to prepare Image that contain all the code but without installation of dependencies (e.g. OpenVPN). The Adminstrator/Programmer will refer to the SW Guides (Install & Admin and User&Programmer) to retrieve instructions to complete the installation and to configure the Robotics GE for his/her needs. ? ReadTheDocs: Guides are available not also at a common page at readTheDocs (https://fiware-robotics.readthedocs.org/en/latest/ ). ? AP5: Since there is no automatic synchronization between Github and readTheDocs, agreed to edit the Guides in Github only, then to manually import them in ReadTheDocs to avoid misalignment. Best, Gianmario 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: logo Ambiente_foglia2.jpg Type: image/jpeg Size: 677 bytes Desc: logo Ambiente_foglia2.jpg URL: From fabio.dibenedetto at consoft.it Tue Sep 22 11:27:44 2015 From: fabio.dibenedetto at consoft.it (fabio.dibenedetto at consoft.it) Date: Tue, 22 Sep 2015 09:27:44 +0000 Subject: R: Minutes and Actions for Robotics GE In-Reply-To: <7E649CBD84A947498203DAF8F098B1F6484C78C0@telmbb003ba020.telecomitalia.local> References: <7E649CBD84A947498203DAF8F098B1F6484C78C0@telmbb003ba020.telecomitalia.local> Message-ID: I'm already adding the missing sections with all their sub section and I'll try to commit them as soon as possible Fabio Da: fiware-robotics-bounces at lists.fiware.org [mailto:fiware-robotics-bounces at lists.fiware.org] Per conto di Bollano Gianmario Inviato: marted? 22 settembre 2015 11:20 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] Minutes and Actions for Robotics GE Dear all, please find the minutes of the Robotics call of today. We have few but important Action Points. Please check them. Robotics GE Call - 22/09/15 ? Install & Admin Guide : We have a first release of the Inst&Admin Robotics containing a common installation of the Robotics GE. Actions are: ? AP0: Anyone check the Guide to commonly agree and improve the Guide (by adding content if needed). The document should contain all the needed information for a complete installation of the Robotics GE ? AP1: Two missing sections (strictly required) are "Sanity Check procedures" and "Diagnosis Procedure". These mandatory section should provide a simple test (e.g. running a command with some expected result) that is used by the administrator (programmer) to check that the GE installation was successful. These sections contain some small subsection (e.g. to provide typical resource usage). Please refer to section 3.2.2 of the document Guidelines for R4 (https://docs.google.com/document/d/1wa15t2dSEucSA1xD7FyOLpP0ymihYYry0mhALV6GsXU/edit?pli=1 ) ? AP2: Add some simple command to install the library/component dependencies (e.g. OpenVPN) and add link to Web Pages for their configuration ? User&Programmer Guide. A first release of User&Programmer Robotics is now available. Content of this guide is free (expected example of commands and snippets of code to be used as example of usage of Robotics GE). Actions are: ? AP3: Anyone check and improve/ add content to the Guide. ? Images and Dockerization are ongoing . Current actions: ? AP4: Agreed to prepare Image that contain all the code but without installation of dependencies (e.g. OpenVPN). The Adminstrator/Programmer will refer to the SW Guides (Install & Admin and User&Programmer) to retrieve instructions to complete the installation and to configure the Robotics GE for his/her needs. ? ReadTheDocs: Guides are available not also at a common page at readTheDocs (https://fiware-robotics.readthedocs.org/en/latest/ ). ? AP5: Since there is no automatic synchronization between Github and readTheDocs, agreed to edit the Guides in Github only, then to manually import them in ReadTheDocs to avoid misalignment. Best, Gianmario 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: From fabio.dibenedetto at consoft.it Tue Sep 22 11:51:45 2015 From: fabio.dibenedetto at consoft.it (fabio.dibenedetto at consoft.it) Date: Tue, 22 Sep 2015 09:51:45 +0000 Subject: R: Minutes and Actions for Robotics GE In-Reply-To: <7E649CBD84A947498203DAF8F098B1F6484C78C0@telmbb003ba020.telecomitalia.local> References: <7E649CBD84A947498203DAF8F098B1F6484C78C0@telmbb003ba020.telecomitalia.local> Message-ID: <894ff38386dd4296a4dc7d8656244662@EXCHMBX2.consoft.it> I think there are still 2 actions missing: - Check the installation script and update it in case of missing parts (more specifically the firos part should be validated for what concern the configuration if needed, because the script I've done takes what I think is needed from the repository and doesn't do any customization) - again for firos try to use robotics_msgs instead of firos internal type of messages. As I said in the call and in previous mails the package robotics_msgs is the package used to communicate between firos and rcm_driver, so both have to use it (this is only the implementation I made of what we said and agreed in the open spec): you can find the sources under RCM/src/robotics_msgs (it is a common package so in the license all the partners are inserted and if you prefer we can move from the RCM repository and put directly into robotics) Da: fiware-robotics-bounces at lists.fiware.org [mailto:fiware-robotics-bounces at lists.fiware.org] Per conto di Bollano Gianmario Inviato: marted? 22 settembre 2015 11:20 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] Minutes and Actions for Robotics GE Dear all, please find the minutes of the Robotics call of today. We have few but important Action Points. Please check them. Robotics GE Call - 22/09/15 ? Install & Admin Guide : We have a first release of the Inst&Admin Robotics containing a common installation of the Robotics GE. Actions are: ? AP0: Anyone check the Guide to commonly agree and improve the Guide (by adding content if needed). The document should contain all the needed information for a complete installation of the Robotics GE ? AP1: Two missing sections (strictly required) are "Sanity Check procedures" and "Diagnosis Procedure". These mandatory section should provide a simple test (e.g. running a command with some expected result) that is used by the administrator (programmer) to check that the GE installation was successful. These sections contain some small subsection (e.g. to provide typical resource usage). Please refer to section 3.2.2 of the document Guidelines for R4 (https://docs.google.com/document/d/1wa15t2dSEucSA1xD7FyOLpP0ymihYYry0mhALV6GsXU/edit?pli=1 ) ? AP2: Add some simple command to install the library/component dependencies (e.g. OpenVPN) and add link to Web Pages for their configuration ? User&Programmer Guide. A first release of User&Programmer Robotics is now available. Content of this guide is free (expected example of commands and snippets of code to be used as example of usage of Robotics GE). Actions are: ? AP3: Anyone check and improve/ add content to the Guide. ? Images and Dockerization are ongoing . Current actions: ? AP4: Agreed to prepare Image that contain all the code but without installation of dependencies (e.g. OpenVPN). The Adminstrator/Programmer will refer to the SW Guides (Install & Admin and User&Programmer) to retrieve instructions to complete the installation and to configure the Robotics GE for his/her needs. ? ReadTheDocs: Guides are available not also at a common page at readTheDocs (https://fiware-robotics.readthedocs.org/en/latest/ ). ? AP5: Since there is no automatic synchronization between Github and readTheDocs, agreed to edit the Guides in Github only, then to manually import them in ReadTheDocs to avoid misalignment. Best, Gianmario 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: From gianmario.bollano at telecomitalia.it Tue Sep 22 17:24:08 2015 From: gianmario.bollano at telecomitalia.it (Bollano Gianmario) Date: Tue, 22 Sep 2015 15:24:08 +0000 Subject: R: Minutes and Actions for Robotics GE In-Reply-To: <894ff38386dd4296a4dc7d8656244662@EXCHMBX2.consoft.it> References: <7E649CBD84A947498203DAF8F098B1F6484C78C0@telmbb003ba020.telecomitalia.local> <894ff38386dd4296a4dc7d8656244662@EXCHMBX2.consoft.it> Message-ID: <7E649CBD84A947498203DAF8F098B1F6484CAB4F@telmbb003ba020.telecomitalia.local> Thank you Fabio, these points better clarify and give further insight on what is still needed on first point. Gianmario Da: fiware-robotics-bounces at lists.fiware.org [mailto:fiware-robotics-bounces at lists.fiware.org] Per conto di fabio.dibenedetto at consoft.it Inviato: marted? 22 settembre 2015 11:52 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] R: Minutes and Actions for Robotics GE I think there are still 2 actions missing: - Check the installation script and update it in case of missing parts (more specifically the firos part should be validated for what concern the configuration if needed, because the script I've done takes what I think is needed from the repository and doesn't do any customization) - again for firos try to use robotics_msgs instead of firos internal type of messages. As I said in the call and in previous mails the package robotics_msgs is the package used to communicate between firos and rcm_driver, so both have to use it (this is only the implementation I made of what we said and agreed in the open spec): you can find the sources under RCM/src/robotics_msgs (it is a common package so in the license all the partners are inserted and if you prefer we can move from the RCM repository and put directly into robotics) Da: fiware-robotics-bounces at lists.fiware.org [mailto:fiware-robotics-bounces at lists.fiware.org] Per conto di Bollano Gianmario Inviato: marted? 22 settembre 2015 11:20 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] Minutes and Actions for Robotics GE Dear all, please find the minutes of the Robotics call of today. We have few but important Action Points. Please check them. Robotics GE Call - 22/09/15 ? Install & Admin Guide : We have a first release of the Inst&Admin Robotics containing a common installation of the Robotics GE. Actions are: ? AP0: Anyone check the Guide to commonly agree and improve the Guide (by adding content if needed). The document should contain all the needed information for a complete installation of the Robotics GE ? AP1: Two missing sections (strictly required) are "Sanity Check procedures" and "Diagnosis Procedure". These mandatory section should provide a simple test (e.g. running a command with some expected result) that is used by the administrator (programmer) to check that the GE installation was successful. These sections contain some small subsection (e.g. to provide typical resource usage). Please refer to section 3.2.2 of the document Guidelines for R4 (https://docs.google.com/document/d/1wa15t2dSEucSA1xD7FyOLpP0ymihYYry0mhALV6GsXU/edit?pli=1 ) ? AP2: Add some simple command to install the library/component dependencies (e.g. OpenVPN) and add link to Web Pages for their configuration ? User&Programmer Guide. A first release of User&Programmer Robotics is now available. Content of this guide is free (expected example of commands and snippets of code to be used as example of usage of Robotics GE). Actions are: ? AP3: Anyone check and improve/ add content to the Guide. ? Images and Dockerization are ongoing . Current actions: ? AP4: Agreed to prepare Image that contain all the code but without installation of dependencies (e.g. OpenVPN). The Adminstrator/Programmer will refer to the SW Guides (Install & Admin and User&Programmer) to retrieve instructions to complete the installation and to configure the Robotics GE for his/her needs. ? ReadTheDocs: Guides are available not also at a common page at readTheDocs (https://fiware-robotics.readthedocs.org/en/latest/ ). ? AP5: Since there is no automatic synchronization between Github and readTheDocs, agreed to edit the Guides in Github only, then to manually import them in ReadTheDocs to avoid misalignment. Best, Gianmario 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. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 677 bytes Desc: image001.gif URL: From jjaime at ikergune.com Thu Sep 24 13:19:50 2015 From: jjaime at ikergune.com (Jose Jaime Ariza) Date: Thu, 24 Sep 2015 13:19:50 +0200 Subject: Standardization Gap Analysis Message-ID: Hi, Piear, I'm not totally sure about what should we send to you related with this section. The standard that is relevant for FIROS is the evolution of ROS: ROS 2.0. It includes many improvements in several aspects (network usage, zeroconf, stability, etc), take a look to http://design.ros2.org/articles/why_ros2.html. Since it is in alpha stage we don't think that there is a gap in functionality but in stability. I'm not sure if we can ask for changes in NGSI, nut it would be great to... - have some kind of ONCHANGE subscription that only send the las value that has changed. - support keep-alive in HTTP in order to improve the amount of sockets used. Thank you very much, Pepe. -- Jos? Jaime Ariza R&D Engineer +34 696604288 Ikergune, Etxe-Tar group From pierangelo.garino at telecomitalia.it Thu Sep 24 14:35:21 2015 From: pierangelo.garino at telecomitalia.it (Garino Pierangelo) Date: Thu, 24 Sep 2015 12:35:21 +0000 Subject: R: Standardization Gap Analysis In-Reply-To: References: Message-ID: Hi Pepe, Thanks a lot, I believe we can put a short description of ROS and its evolution, smoothing the focus on functionality gaps and mentioning the reliability ones. I'll try to combine together some sentence for this part. BR Pier -----Messaggio originale----- Da: fiware-robotics-bounces at lists.fiware.org [mailto:fiware-robotics-bounces at lists.fiware.org] Per conto di Jose Jaime Ariza Inviato: gioved? 24 settembre 2015 13:20 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] Standardization Gap Analysis Hi, Piear, I'm not totally sure about what should we send to you related with this section. The standard that is relevant for FIROS is the evolution of ROS: ROS 2.0. It includes many improvements in several aspects (network usage, zeroconf, stability, etc), take a look to http://design.ros2.org/articles/why_ros2.html. Since it is in alpha stage we don't think that there is a gap in functionality but in stability. I'm not sure if we can ask for changes in NGSI, nut it would be great to... - have some kind of ONCHANGE subscription that only send the las value that has changed. - support keep-alive in HTTP in order to improve the amount of sockets used. Thank you very much, Pepe. -- Jos? Jaime Ariza R&D Engineer +34 696604288 Ikergune, Etxe-Tar group _______________________________________________ Fiware-robotics mailing list Fiware-robotics at lists.fiware.org https://lists.fiware.org/listinfo/fiware-robotics-new 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. From fabio.dibenedetto at consoft.it Thu Sep 24 15:13:32 2015 From: fabio.dibenedetto at consoft.it (fabio.dibenedetto at consoft.it) Date: Thu, 24 Sep 2015 13:13:32 +0000 Subject: Dockerization In-Reply-To: References: Message-ID: <36ed1964275f4b20a1518b03bbb6352c@EXCHMBX2.consoft.it> Hi all, I looked at the link proposed by Giovanni during the call about the dockerization problem; I don't think that solution can match our GE docker because as process manager you can't specify all the process you'll have to launch in the container. The solution they propose in their post is to add in the container a process supervisor and provide in the dockerfile the processes that will be started by the process supervisor in the container. Our platform is already a process supervisor, but the processes you run are not predetermined and you need the freedom to launch all sub process you need in the container not only a predefined set. As I said in the call the best way to provide a distribution in our case is to provide the compressed files for all the components and let the installer follow the steps specified in the installation guide. In any case I'll add a new directory in the common repository with the name 'dist' and put in it 3 subfolders: 'all', 'platform', 'components'. The first will keep the master platform with the embedded packages, the second will have master and robot platform, and the third will contain only the other components packages (firos, rcm_driver and robotics_msgs). Is it ok for you? For what concern the documentation I updated the file modified by Pepe because there were some lost letters in some words and a wrong rst format in a little section. I added a webhook to our repository in order to have readthedocs automatically updated when you do some changes (I still haven't tried if it works, but I'll do when I'll commit the 'dist' folder) Last question is about the API: the html of both the API are under github the only thing to do is to update the link in openspec (the link should be 2 and not one and they have to point to docs/api/RCM-apiary/RCM-apiary.html and docs/api/FIROS-apiary/firos-apiary.html). Can someone do that or remember me the link of openspec where to change it? Fabio From gianmario.bollano at telecomitalia.it Thu Sep 24 16:26:11 2015 From: gianmario.bollano at telecomitalia.it (Bollano Gianmario) Date: Thu, 24 Sep 2015 14:26:11 +0000 Subject: R: Dockerization In-Reply-To: <36ed1964275f4b20a1518b03bbb6352c@EXCHMBX2.consoft.it> References: <36ed1964275f4b20a1518b03bbb6352c@EXCHMBX2.consoft.it> Message-ID: <7E649CBD84A947498203DAF8F098B1F6484CDCF1@telmbb003ba020.telecomitalia.local> Hi Fabio, my answers: 1) It seems a solution to me, better having one than no one. Don't know however why 3 folders are in "dist": can't we just use the code in other folders? 2) Fine. Any editing to improve/fix is absolutely welcomed. 3) OpenSpecs R4 are : http://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/FIWARE.OpenSPecification.I2ND.Robotics_R4 Best, Gianmario -----Messaggio originale----- Da: fiware-robotics-bounces at lists.fiware.org [mailto:fiware-robotics-bounces at lists.fiware.org] Per conto di fabio.dibenedetto at consoft.it Inviato: gioved? 24 settembre 2015 15:14 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] Dockerization Hi all, I looked at the link proposed by Giovanni during the call about the dockerization problem; I don't think that solution can match our GE docker because as process manager you can't specify all the process you'll have to launch in the container. The solution they propose in their post is to add in the container a process supervisor and provide in the dockerfile the processes that will be started by the process supervisor in the container. Our platform is already a process supervisor, but the processes you run are not predetermined and you need the freedom to launch all sub process you need in the container not only a predefined set. As I said in the call the best way to provide a distribution in our case is to provide the compressed files for all the components and let the installer follow the steps specified in the installation guide. In any case I'll add a new directory in the common repository with the name 'dist' and put in it 3 subfolders: 'all', 'platform', 'components'. The first will keep the master platform with the embedded packages, the second will have master and robot platform, and the third will contain only the other components packages (firos, rcm_driver and robotics_msgs). Is it ok for you? For what concern the documentation I updated the file modified by Pepe because there were some lost letters in some words and a wrong rst format in a little section. I added a webhook to our repository in order to have readthedocs automatically updated when you do some changes (I still haven't tried if it works, but I'll do when I'll commit the 'dist' folder) Last question is about the API: the html of both the API are under github the only thing to do is to update the link in openspec (the link should be 2 and not one and they have to point to docs/api/RCM-apiary/RCM-apiary.html and docs/api/FIROS-apiary/firos-apiary.html). Can someone do that or remember me the link of openspec where to change it? Fabio _______________________________________________ Fiware-robotics mailing list Fiware-robotics at lists.fiware.org https://lists.fiware.org/listinfo/fiware-robotics-new 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. From jjaime at ikergune.com Thu Sep 24 17:12:20 2015 From: jjaime at ikergune.com (Jose Jaime Ariza) Date: Thu, 24 Sep 2015 17:12:20 +0200 Subject: [Fiware-robotics] R: Dockerization References: <36ed1964275f4b20a1518b03bbb6352c@EXCHMBX2.consoft.it> <7E649CBD84A947498203DAF8F098B1F6484CDCF1@telmbb003ba020.telecomitalia.local> Message-ID: Hi, the solution Fabio proposes for the dockerizing the GE sounds great to me. I've updated the I&A and U&P guides. I've added some information related to firos, fixed some missing links (including internal readthedoc links) and made some minor modifications. The webhook works perfectly. Thank you very much, Pepe Jos? Jaime Ariza R&D Engineer +34 696604288 Ikergune, Etxe-Tar group On 24/09/15 16:26, Bollano Gianmario wrote: > Hi Fabio, > my answers: > > 1) It seems a solution to me, better having one than no one. Don't know however why 3 folders are in "dist": can't we just use the code in other folders? > 2) Fine. Any editing to improve/fix is absolutely welcomed. > 3) OpenSpecs R4 are : http://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/FIWARE.OpenSPecification.I2ND.Robotics_R4 > > Best, > Gianmario > > -----Messaggio originale----- > Da: fiware-robotics-bounces at lists.fiware.org [mailto:fiware-robotics-bounces at lists.fiware.org] Per conto di fabio.dibenedetto at consoft.it > Inviato: gioved? 24 settembre 2015 15:14 > A: fiware-robotics at lists.fi-ware.org > Oggetto: [Fiware-robotics] Dockerization > > Hi all, > I looked at the link proposed by Giovanni during the call about the dockerization problem; I don't think that solution can match our GE docker because as process manager you can't specify all the process you'll have to launch in the container. The solution they propose in their post is to add in the container a process supervisor and provide in the dockerfile the processes that will be started by the process supervisor in the container. Our platform is already a process supervisor, but the processes you run are not predetermined and you need the freedom to launch all sub process you need in the container not only a predefined set. As I said in the call the best way to provide a distribution in our case is to provide the compressed files for all the components and let the installer follow the steps specified in the installation guide. > In any case I'll add a new directory in the common repository with the name 'dist' and put in it 3 subfolders: 'all', 'platform', 'components'. The first will keep the master platform with the embedded packages, the second will have master and robot platform, and the third will contain only the other components packages (firos, rcm_driver and robotics_msgs). Is it ok for you? > > > For what concern the documentation I updated the file modified by Pepe because there were some lost letters in some words and a wrong rst format in a little section. I added a webhook to our repository in order to have readthedocs automatically updated when you do some changes (I still haven't tried if it works, but I'll do when I'll commit the 'dist' folder) > > Last question is about the API: the html of both the API are under github the only thing to do is to update the link in openspec (the link should be 2 and not one and they have to point to docs/api/RCM-apiary/RCM-apiary.html and docs/api/FIROS-apiary/firos-apiary.html). Can someone do that or remember me the link of openspec where to change it? > > Fabio > _______________________________________________ > Fiware-robotics mailing list > Fiware-robotics at lists.fiware.org > https://lists.fiware.org/listinfo/fiware-robotics-new > > 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. > > _______________________________________________ > Fiware-robotics mailing list > Fiware-robotics at lists.fiware.org > https://lists.fiware.org/listinfo/fiware-robotics-new > From fabio.dibenedetto at consoft.it Thu Sep 24 17:16:57 2015 From: fabio.dibenedetto at consoft.it (fabio.dibenedetto at consoft.it) Date: Thu, 24 Sep 2015 15:16:57 +0000 Subject: R: Dockerization In-Reply-To: <7E649CBD84A947498203DAF8F098B1F6484CDCF1@telmbb003ba020.telecomitalia.local> References: <36ed1964275f4b20a1518b03bbb6352c@EXCHMBX2.consoft.it> <7E649CBD84A947498203DAF8F098B1F6484CDCF1@telmbb003ba020.telecomitalia.local> Message-ID: Thank you for the link, but I'm having some troubles in updating the link because even if the html is in the repository I can go in that html but only in the source and this is not what we wanted. Does anyone know how to solve that? For what concern the first point the 3 folders are because we don't distribute only one application, we have to distribute all we have and this means that we have 2 types of platforms (master and robot), 3 packages for the communication with fiware (firos, rcm_driver, robotics_msgs). The platforms are distributed without the other components and only in case of the 'all' folder we have a distribution with the master platform and the other packages inside it. These are all the distribution that we can provide using the script 'create_robotics_pkg'. If you use the sources, you have to take the sources and then run this script to create those distributions -----Messaggio originale----- Da: Bollano Gianmario [mailto:gianmario.bollano at telecomitalia.it] Inviato: gioved? 24 settembre 2015 16:26 A: fabio.dibenedetto at consoft.it; fiware-robotics at lists.fi-ware.org Oggetto: R: Dockerization Hi Fabio, my answers: 1) It seems a solution to me, better having one than no one. Don't know however why 3 folders are in "dist": can't we just use the code in other folders? 2) Fine. Any editing to improve/fix is absolutely welcomed. 3) OpenSpecs R4 are : http://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/FIWARE.OpenSPecification.I2ND.Robotics_R4 Best, Gianmario -----Messaggio originale----- Da: fiware-robotics-bounces at lists.fiware.org [mailto:fiware-robotics-bounces at lists.fiware.org] Per conto di fabio.dibenedetto at consoft.it Inviato: gioved? 24 settembre 2015 15:14 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] Dockerization Hi all, I looked at the link proposed by Giovanni during the call about the dockerization problem; I don't think that solution can match our GE docker because as process manager you can't specify all the process you'll have to launch in the container. The solution they propose in their post is to add in the container a process supervisor and provide in the dockerfile the processes that will be started by the process supervisor in the container. Our platform is already a process supervisor, but the processes you run are not predetermined and you need the freedom to launch all sub process you need in the container not only a predefined set. As I said in the call the best way to provide a distribution in our case is to provide the compressed files for all the components and let the installer follow the steps specified in the installation guide. In any case I'll add a new directory in the common repository with the name 'dist' and put in it 3 subfolders: 'all', 'platform', 'components'. The first will keep the master platform with the embedded packages, the second will have master and robot platform, and the third will contain only the other components packages (firos, rcm_driver and robotics_msgs). Is it ok for you? For what concern the documentation I updated the file modified by Pepe because there were some lost letters in some words and a wrong rst format in a little section. I added a webhook to our repository in order to have readthedocs automatically updated when you do some changes (I still haven't tried if it works, but I'll do when I'll commit the 'dist' folder) Last question is about the API: the html of both the API are under github the only thing to do is to update the link in openspec (the link should be 2 and not one and they have to point to docs/api/RCM-apiary/RCM-apiary.html and docs/api/FIROS-apiary/firos-apiary.html). Can someone do that or remember me the link of openspec where to change it? Fabio _______________________________________________ Fiware-robotics mailing list Fiware-robotics at lists.fiware.org https://lists.fiware.org/listinfo/fiware-robotics-new 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. From fabio.dibenedetto at consoft.it Thu Sep 24 17:25:34 2015 From: fabio.dibenedetto at consoft.it (fabio.dibenedetto at consoft.it) Date: Thu, 24 Sep 2015 15:25:34 +0000 Subject: R: [Fiware-robotics] R: Dockerization In-Reply-To: References: <36ed1964275f4b20a1518b03bbb6352c@EXCHMBX2.consoft.it> <7E649CBD84A947498203DAF8F098B1F6484CDCF1@telmbb003ba020.telecomitalia.local> Message-ID: Thank you, to make it easy this kind of non standard version I thought to write a readme.md into the distribution folder, so that the question asked by Gianmario would be available to anyone access that folder. The question is: how can we manage the change of fiware standard? Can we put in jira that we did so and it's ok or do we have to do something else? Fabio PS: about the question of robotics_msgs use in firos: do we have any news? -----Messaggio originale----- Da: fiware-robotics-bounces at lists.fiware.org [mailto:fiware-robotics-bounces at lists.fiware.org] Per conto di Jose Jaime Ariza Inviato: gioved? 24 settembre 2015 17:12 A: fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] R: Dockerization Hi, the solution Fabio proposes for the dockerizing the GE sounds great to me. I've updated the I&A and U&P guides. I've added some information related to firos, fixed some missing links (including internal readthedoc links) and made some minor modifications. The webhook works perfectly. Thank you very much, Pepe Jos? Jaime Ariza R&D Engineer +34 696604288 Ikergune, Etxe-Tar group On 24/09/15 16:26, Bollano Gianmario wrote: > Hi Fabio, > my answers: > > 1) It seems a solution to me, better having one than no one. Don't know however why 3 folders are in "dist": can't we just use the code in other folders? > 2) Fine. Any editing to improve/fix is absolutely welcomed. > 3) OpenSpecs R4 are : > http://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/FIWARE > .OpenSPecification.I2ND.Robotics_R4 > > Best, > Gianmario > > -----Messaggio originale----- > Da: fiware-robotics-bounces at lists.fiware.org > [mailto:fiware-robotics-bounces at lists.fiware.org] Per conto di > fabio.dibenedetto at consoft.it > Inviato: gioved? 24 settembre 2015 15:14 > A: fiware-robotics at lists.fi-ware.org > Oggetto: [Fiware-robotics] Dockerization > > Hi all, > I looked at the link proposed by Giovanni during the call about the dockerization problem; I don't think that solution can match our GE docker because as process manager you can't specify all the process you'll have to launch in the container. The solution they propose in their post is to add in the container a process supervisor and provide in the dockerfile the processes that will be started by the process supervisor in the container. Our platform is already a process supervisor, but the processes you run are not predetermined and you need the freedom to launch all sub process you need in the container not only a predefined set. As I said in the call the best way to provide a distribution in our case is to provide the compressed files for all the components and let the installer follow the steps specified in the installation guide. > In any case I'll add a new directory in the common repository with the name 'dist' and put in it 3 subfolders: 'all', 'platform', 'components'. The first will keep the master platform with the embedded packages, the second will have master and robot platform, and the third will contain only the other components packages (firos, rcm_driver and robotics_msgs). Is it ok for you? > > > For what concern the documentation I updated the file modified by Pepe > because there were some lost letters in some words and a wrong rst > format in a little section. I added a webhook to our repository in > order to have readthedocs automatically updated when you do some > changes (I still haven't tried if it works, but I'll do when I'll > commit the 'dist' folder) > > Last question is about the API: the html of both the API are under github the only thing to do is to update the link in openspec (the link should be 2 and not one and they have to point to docs/api/RCM-apiary/RCM-apiary.html and docs/api/FIROS-apiary/firos-apiary.html). Can someone do that or remember me the link of openspec where to change it? > > Fabio > _______________________________________________ > Fiware-robotics mailing list > Fiware-robotics at lists.fiware.org > https://lists.fiware.org/listinfo/fiware-robotics-new > > 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. > > _______________________________________________ > Fiware-robotics mailing list > Fiware-robotics at lists.fiware.org > https://lists.fiware.org/listinfo/fiware-robotics-new > _______________________________________________ Fiware-robotics mailing list Fiware-robotics at lists.fiware.org https://lists.fiware.org/listinfo/fiware-robotics-new From gianmario.bollano at telecomitalia.it Fri Sep 25 09:18:58 2015 From: gianmario.bollano at telecomitalia.it (Bollano Gianmario) Date: Fri, 25 Sep 2015 07:18:58 +0000 Subject: HTML pages in github Message-ID: <7E649CBD84A947498203DAF8F098B1F6484CE435@telmbb003ba020.telecomitalia.local> Hi Fabio, it seems the trick of publishing HTML pages in github is using the special "gh-pages" branch. Without that branch, github render any file as code instead of passing it to the browser. instructions to commit html pages in a Github repository are here: https://help.github.com/articles/creating-project-pages-manually/ or also here: https://pages.github.com/ After committing in the gh-pages branch, the html pages should be visible as a web page. Gianmario -----Messaggio originale----- Da: fiware-robotics-bounces at lists.fiware.org [mailto:fiware-robotics-bounces at lists.fiware.org] Per conto di fabio.dibenedetto at consoft.it Inviato: gioved? 24 settembre 2015 17:17 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] R: Dockerization Thank you for the link, but I'm having some troubles in updating the link because even if the html is in the repository I can go in that html but only in the source and this is not what we wanted. Does anyone know how to solve that? For what concern the first point the 3 folders are because we don't distribute only one application, we have to distribute all we have and this means that we have 2 types of platforms (master and robot), 3 packages for the communication with fiware (firos, rcm_driver, robotics_msgs). The platforms are distributed without the other components and only in case of the 'all' folder we have a distribution with the master platform and the other packages inside it. These are all the distribution that we can provide using the script 'create_robotics_pkg'. If you use the sources, you have to take the sources and then run this script to create those distributions -----Messaggio originale----- Da: Bollano Gianmario [mailto:gianmario.bollano at telecomitalia.it] Inviato: gioved? 24 settembre 2015 16:26 A: fabio.dibenedetto at consoft.it; fiware-robotics at lists.fi-ware.org Oggetto: R: Dockerization Hi Fabio, my answers: 1) It seems a solution to me, better having one than no one. Don't know however why 3 folders are in "dist": can't we just use the code in other folders? 2) Fine. Any editing to improve/fix is absolutely welcomed. 3) OpenSpecs R4 are : http://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/FIWARE.OpenSPecification.I2ND.Robotics_R4 Best, Gianmario -----Messaggio originale----- Da: fiware-robotics-bounces at lists.fiware.org [mailto:fiware-robotics-bounces at lists.fiware.org] Per conto di fabio.dibenedetto at consoft.it Inviato: gioved? 24 settembre 2015 15:14 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] Dockerization Hi all, I looked at the link proposed by Giovanni during the call about the dockerization problem; I don't think that solution can match our GE docker because as process manager you can't specify all the process you'll have to launch in the container. The solution they propose in their post is to add in the container a process supervisor and provide in the dockerfile the processes that will be started by the process supervisor in the container. Our platform is already a process supervisor, but the processes you run are not predetermined and you need the freedom to launch all sub process you need in the container not only a predefined set. As I said in the call the best way to provide a distribution in our case is to provide the compressed files for all the components and let the installer follow the steps specified in the installation guide. In any case I'll add a new directory in the common repository with the name 'dist' and put in it 3 subfolders: 'all', 'platform', 'components'. The first will keep the master platform with the embedded packages, the second will have master and robot platform, and the third will contain only the other components packages (firos, rcm_driver and robotics_msgs). Is it ok for you? For what concern the documentation I updated the file modified by Pepe because there were some lost letters in some words and a wrong rst format in a little section. I added a webhook to our repository in order to have readthedocs automatically updated when you do some changes (I still haven't tried if it works, but I'll do when I'll commit the 'dist' folder) Last question is about the API: the html of both the API are under github the only thing to do is to update the link in openspec (the link should be 2 and not one and they have to point to docs/api/RCM-apiary/RCM-apiary.html and docs/api/FIROS-apiary/firos-apiary.html). Can someone do that or remember me the link of openspec where to change it? Fabio _______________________________________________ Fiware-robotics mailing list Fiware-robotics at lists.fiware.org https://lists.fiware.org/listinfo/fiware-robotics-new 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. _______________________________________________ Fiware-robotics mailing list Fiware-robotics at lists.fiware.org https://lists.fiware.org/listinfo/fiware-robotics-new From igonzalez at ikergune.com Fri Sep 25 09:40:33 2015 From: igonzalez at ikergune.com (=?iso-8859-1?Q?I=F1igo_Gonzalez?=) Date: Fri, 25 Sep 2015 09:40:33 +0200 Subject: [Fiware-robotics] R: R: Dockerization References: <36ed1964275f4b20a1518b03bbb6352c@EXCHMBX2.consoft.it> <7E649CBD84A947498203DAF8F098B1F6484CDCF1@telmbb003ba020.telecomitalia.local> Message-ID: Hi, we have looking about what to do in the robotics_msgs. The problem is that we also need to have it in our firos folder to work with it, in other way we have had troubles. We think that is late to do any big change only to use the same specification but in different folder. Regards, I?igo On 24/09/15 17:26, fabio.dibenedetto at consoft.it wrote: > Thank you, > to make it easy this kind of non standard version I thought to write a readme.md into the distribution folder, so that the question asked by Gianmario would be available to anyone access that folder. > The question is: how can we manage the change of fiware standard? Can we put in jira that we did so and it's ok or do we have to do something else? > Fabio > > PS: about the question of robotics_msgs use in firos: do we have any news? > > -----Messaggio originale----- > Da: fiware-robotics-bounces at lists.fiware.org [mailto:fiware-robotics-bounces at lists.fiware.org] Per conto di Jose Jaime Ariza > Inviato: gioved? 24 settembre 2015 17:12 > A: fiware-robotics at lists.fi-ware.org > Oggetto: Re: [Fiware-robotics] R: Dockerization > > Hi, > > the solution Fabio proposes for the dockerizing the GE sounds great to me. > > I've updated the I&A and U&P guides. I've added some information related to firos, fixed some missing links (including internal readthedoc links) and made some minor modifications. The webhook works perfectly. > > Thank you very much, > > Pepe > > Jos? Jaime Ariza > R&D Engineer > +34 696604288 > Ikergune, Etxe-Tar group > > On 24/09/15 16:26, Bollano Gianmario wrote: >> Hi Fabio, >> my answers: >> >> 1) It seems a solution to me, better having one than no one. Don't know however why 3 folders are in "dist": can't we just use the code in other folders? >> 2) Fine. Any editing to improve/fix is absolutely welcomed. >> 3) OpenSpecs R4 are : >> http://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/FIWARE >> .OpenSPecification.I2ND.Robotics_R4 >> >> Best, >> Gianmario >> >> -----Messaggio originale----- >> Da: fiware-robotics-bounces at lists.fiware.org >> [mailto:fiware-robotics-bounces at lists.fiware.org] Per conto di >> fabio.dibenedetto at consoft.it >> Inviato: gioved? 24 settembre 2015 15:14 >> A: fiware-robotics at lists.fi-ware.org >> Oggetto: [Fiware-robotics] Dockerization >> >> Hi all, >> I looked at the link proposed by Giovanni during the call about the dockerization problem; I don't think that solution can match our GE docker because as process manager you can't specify all the process you'll have to launch in the container. The solution they propose in their post is to add in the container a process supervisor and provide in the dockerfile the processes that will be started by the process supervisor in the container. Our platform is already a process supervisor, but the processes you run are not predetermined and you need the freedom to launch all sub process you need in the container not only a predefined set. As I said in the call the best way to provide a distribution in our case is to provide the compressed files for all the components and let the installer follow the steps specified in the installation guide. >> In any case I'll add a new directory in the common repository with the name 'dist' and put in it 3 subfolders: 'all', 'platform', 'components'. The first will keep the master platform with the embedded packages, the second will have master and robot platform, and the third will contain only the other components packages (firos, rcm_driver and robotics_msgs). Is it ok for you? >> >> >> For what concern the documentation I updated the file modified by Pepe >> because there were some lost letters in some words and a wrong rst >> format in a little section. I added a webhook to our repository in >> order to have readthedocs automatically updated when you do some >> changes (I still haven't tried if it works, but I'll do when I'll >> commit the 'dist' folder) >> >> Last question is about the API: the html of both the API are under github the only thing to do is to update the link in openspec (the link should be 2 and not one and they have to point to docs/api/RCM-apiary/RCM-apiary.html and docs/api/FIROS-apiary/firos-apiary.html). Can someone do that or remember me the link of openspec where to change it? >> >> Fabio >> _______________________________________________ >> Fiware-robotics mailing list >> Fiware-robotics at lists.fiware.org >> https://lists.fiware.org/listinfo/fiware-robotics-new >> >> 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. >> >> _______________________________________________ >> Fiware-robotics mailing list >> Fiware-robotics at lists.fiware.org >> https://lists.fiware.org/listinfo/fiware-robotics-new >> > _______________________________________________ > Fiware-robotics mailing list > Fiware-robotics at lists.fiware.org > https://lists.fiware.org/listinfo/fiware-robotics-new > _______________________________________________ > Fiware-robotics mailing list > Fiware-robotics at lists.fiware.org > https://lists.fiware.org/listinfo/fiware-robotics-new > From gianmario.bollano at telecomitalia.it Fri Sep 25 10:06:02 2015 From: gianmario.bollano at telecomitalia.it (Bollano Gianmario) Date: Fri, 25 Sep 2015 08:06:02 +0000 Subject: R: [Fiware-robotics] R: R: Dockerization In-Reply-To: References: <36ed1964275f4b20a1518b03bbb6352c@EXCHMBX2.consoft.it> <7E649CBD84A947498203DAF8F098B1F6484CDCF1@telmbb003ba020.telecomitalia.local> Message-ID: <7E649CBD84A947498203DAF8F098B1F6484CE4CD@telmbb003ba020.telecomitalia.local> Hi all. I know instructions for the delivery sound crazy most of the time, however also the README.md has a structure and actually it contains lot of information copied or linked from the SW Guides and the API documentation. Official instructions for the RADME.md are at this page (link is also provided in the Summaary of Guidelines for R4): http://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/Developer_Guidelines These instruction include a long list of sections; I would suggest to try to fit to that structure (section names) using the content already available (or linking to it). The guidelines for Dockerization are here: http://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/Docker These rules do not define how to structure folders for the code, so I think we can use the distribution folders. Instead the Guidelines specify where to put and rename dockerization files and links; please try to respect as much of them as possible (as for the readme.md guidelines above). Please note that a "docker" folder must exist and a README.MD in it, so we could put the distribution folders inside it and add instruction in the README.MD inside that folder. Gianmario -----Messaggio originale----- Da: fiware-robotics-bounces at lists.fiware.org [mailto:fiware-robotics-bounces at lists.fiware.org] Per conto di fabio.dibenedetto at consoft.it Inviato: gioved? 24 settembre 2015 17:26 A: Jose Jaime Ariza; fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] R: R: Dockerization Thank you, to make it easy this kind of non standard version I thought to write a readme.md into the distribution folder, so that the question asked by Gianmario would be available to anyone access that folder. The question is: how can we manage the change of fiware standard? Can we put in jira that we did so and it's ok or do we have to do something else? Fabio PS: about the question of robotics_msgs use in firos: do we have any news? -----Messaggio originale----- Da: fiware-robotics-bounces at lists.fiware.org [mailto:fiware-robotics-bounces at lists.fiware.org] Per conto di Jose Jaime Ariza Inviato: gioved? 24 settembre 2015 17:12 A: fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] R: Dockerization Hi, the solution Fabio proposes for the dockerizing the GE sounds great to me. I've updated the I&A and U&P guides. I've added some information related to firos, fixed some missing links (including internal readthedoc links) and made some minor modifications. The webhook works perfectly. Thank you very much, Pepe Jos? Jaime Ariza R&D Engineer +34 696604288 Ikergune, Etxe-Tar group On 24/09/15 16:26, Bollano Gianmario wrote: > Hi Fabio, > my answers: > > 1) It seems a solution to me, better having one than no one. Don't know however why 3 folders are in "dist": can't we just use the code in other folders? > 2) Fine. Any editing to improve/fix is absolutely welcomed. > 3) OpenSpecs R4 are : > http://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/FIWARE > .OpenSPecification.I2ND.Robotics_R4 > > Best, > Gianmario > > -----Messaggio originale----- > Da: fiware-robotics-bounces at lists.fiware.org > [mailto:fiware-robotics-bounces at lists.fiware.org] Per conto di > fabio.dibenedetto at consoft.it > Inviato: gioved? 24 settembre 2015 15:14 > A: fiware-robotics at lists.fi-ware.org > Oggetto: [Fiware-robotics] Dockerization > > Hi all, > I looked at the link proposed by Giovanni during the call about the dockerization problem; I don't think that solution can match our GE docker because as process manager you can't specify all the process you'll have to launch in the container. The solution they propose in their post is to add in the container a process supervisor and provide in the dockerfile the processes that will be started by the process supervisor in the container. Our platform is already a process supervisor, but the processes you run are not predetermined and you need the freedom to launch all sub process you need in the container not only a predefined set. As I said in the call the best way to provide a distribution in our case is to provide the compressed files for all the components and let the installer follow the steps specified in the installation guide. > In any case I'll add a new directory in the common repository with the name 'dist' and put in it 3 subfolders: 'all', 'platform', 'components'. The first will keep the master platform with the embedded packages, the second will have master and robot platform, and the third will contain only the other components packages (firos, rcm_driver and robotics_msgs). Is it ok for you? > > > For what concern the documentation I updated the file modified by Pepe > because there were some lost letters in some words and a wrong rst > format in a little section. I added a webhook to our repository in > order to have readthedocs automatically updated when you do some > changes (I still haven't tried if it works, but I'll do when I'll > commit the 'dist' folder) > > Last question is about the API: the html of both the API are under github the only thing to do is to update the link in openspec (the link should be 2 and not one and they have to point to docs/api/RCM-apiary/RCM-apiary.html and docs/api/FIROS-apiary/firos-apiary.html). Can someone do that or remember me the link of openspec where to change it? > > Fabio > _______________________________________________ > Fiware-robotics mailing list > Fiware-robotics at lists.fiware.org > https://lists.fiware.org/listinfo/fiware-robotics-new > > 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. > > _______________________________________________ > Fiware-robotics mailing list > Fiware-robotics at lists.fiware.org > https://lists.fiware.org/listinfo/fiware-robotics-new > _______________________________________________ Fiware-robotics mailing list Fiware-robotics at lists.fiware.org https://lists.fiware.org/listinfo/fiware-robotics-new _______________________________________________ Fiware-robotics mailing list Fiware-robotics at lists.fiware.org https://lists.fiware.org/listinfo/fiware-robotics-new From jjaime at ikergune.com Fri Sep 25 10:15:25 2015 From: jjaime at ikergune.com (Jose Jaime Ariza) Date: Fri, 25 Sep 2015 10:15:25 +0200 Subject: [Fiware-robotics] HTML pages in github References: <7E649CBD84A947498203DAF8F098B1F6484CE435@telmbb003ba020.telecomitalia.local> Message-ID: Hi, We could use http://htmlpreview.github.io/, e.g.: https://htmlpreview.github.io/?https://github.com/FIWARE-RoboticsGE/Robotics/blob/master/docs/api/FIROS-apiary/firos-apiary.html https://htmlpreview.github.io/?https://github.com/FIWARE-RoboticsGE/Robotics/blob/master/docs/api/RCM-apiary/RCM-apiary.html BR, Pepe Jos? Jaime Ariza R&D Engineer +34 696604288 Ikergune, Etxe-Tar group On 25/09/15 09:19, Bollano Gianmario wrote: > Hi Fabio, > it seems the trick of publishing HTML pages in github is using the special "gh-pages" branch. > Without that branch, github render any file as code instead of passing it to the browser. > instructions to commit html pages in a Github repository are here: > https://help.github.com/articles/creating-project-pages-manually/ > or also here: > https://pages.github.com/ > > After committing in the gh-pages branch, the html pages should be visible as a web page. > > Gianmario > > -----Messaggio originale----- > Da: fiware-robotics-bounces at lists.fiware.org [mailto:fiware-robotics-bounces at lists.fiware.org] Per conto di fabio.dibenedetto at consoft.it > Inviato: gioved? 24 settembre 2015 17:17 > A: fiware-robotics at lists.fi-ware.org > Oggetto: [Fiware-robotics] R: Dockerization > > Thank you for the link, but I'm having some troubles in updating the link because even if the html is in the repository I can go in that html but only in the source and this is not what we wanted. Does anyone know how to solve that? > For what concern the first point the 3 folders are because we don't distribute only one application, we have to distribute all we have and this means that we have 2 types of platforms (master and robot), 3 packages for the communication with fiware (firos, rcm_driver, robotics_msgs). The platforms are distributed without the other components and only in case of the 'all' folder we have a distribution with the master platform and the other packages inside it. These are all the distribution that we can provide using the script 'create_robotics_pkg'. If you use the sources, you have to take the sources and then run this script to create those distributions > > -----Messaggio originale----- > Da: Bollano Gianmario [mailto:gianmario.bollano at telecomitalia.it] > Inviato: gioved? 24 settembre 2015 16:26 > A: fabio.dibenedetto at consoft.it; fiware-robotics at lists.fi-ware.org > Oggetto: R: Dockerization > > Hi Fabio, > my answers: > > 1) It seems a solution to me, better having one than no one. Don't know however why 3 folders are in "dist": can't we just use the code in other folders? > 2) Fine. Any editing to improve/fix is absolutely welcomed. > 3) OpenSpecs R4 are : http://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/FIWARE.OpenSPecification.I2ND.Robotics_R4 > > Best, > Gianmario > > -----Messaggio originale----- > Da: fiware-robotics-bounces at lists.fiware.org [mailto:fiware-robotics-bounces at lists.fiware.org] Per conto di fabio.dibenedetto at consoft.it > Inviato: gioved? 24 settembre 2015 15:14 > A: fiware-robotics at lists.fi-ware.org > Oggetto: [Fiware-robotics] Dockerization > > Hi all, > I looked at the link proposed by Giovanni during the call about the dockerization problem; I don't think that solution can match our GE docker because as process manager you can't specify all the process you'll have to launch in the container. The solution they propose in their post is to add in the container a process supervisor and provide in the dockerfile the processes that will be started by the process supervisor in the container. Our platform is already a process supervisor, but the processes you run are not predetermined and you need the freedom to launch all sub process you need in the container not only a predefined set. As I said in the call the best way to provide a distribution in our case is to provide the compressed files for all the components and let the installer follow the steps specified in the installation guide. > In any case I'll add a new directory in the common repository with the name 'dist' and put in it 3 subfolders: 'all', 'platform', 'components'. The first will keep the master platform with the embedded packages, the second will have master and robot platform, and the third will contain only the other components packages (firos, rcm_driver and robotics_msgs). Is it ok for you? > > > For what concern the documentation I updated the file modified by Pepe because there were some lost letters in some words and a wrong rst format in a little section. I added a webhook to our repository in order to have readthedocs automatically updated when you do some changes (I still haven't tried if it works, but I'll do when I'll commit the 'dist' folder) > > Last question is about the API: the html of both the API are under github the only thing to do is to update the link in openspec (the link should be 2 and not one and they have to point to docs/api/RCM-apiary/RCM-apiary.html and docs/api/FIROS-apiary/firos-apiary.html). Can someone do that or remember me the link of openspec where to change it? > > Fabio > _______________________________________________ > Fiware-robotics mailing list > Fiware-robotics at lists.fiware.org > https://lists.fiware.org/listinfo/fiware-robotics-new > > 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. > > _______________________________________________ > Fiware-robotics mailing list > Fiware-robotics at lists.fiware.org > https://lists.fiware.org/listinfo/fiware-robotics-new > _______________________________________________ > Fiware-robotics mailing list > Fiware-robotics at lists.fiware.org > https://lists.fiware.org/listinfo/fiware-robotics-new > From fabio.dibenedetto at consoft.it Fri Sep 25 10:52:13 2015 From: fabio.dibenedetto at consoft.it (fabio.dibenedetto at consoft.it) Date: Fri, 25 Sep 2015 08:52:13 +0000 Subject: R: [Fiware-robotics] HTML pages in github In-Reply-To: References: <7E649CBD84A947498203DAF8F098B1F6484CE435@telmbb003ba020.telecomitalia.local> Message-ID: <8dea7f83a336437ab2953d46cb3efcd1@EXCHMBX2.consoft.it> Seems to work, but the result has some strange html elements that are not parsed...but can be the tool that originated the files. I'll try both the proposal and see what is better -----Messaggio originale----- Da: fiware-robotics-bounces at lists.fiware.org [mailto:fiware-robotics-bounces at lists.fiware.org] Per conto di Jose Jaime Ariza Inviato: venerd? 25 settembre 2015 10:15 A: fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] HTML pages in github Hi, We could use http://htmlpreview.github.io/, e.g.: https://htmlpreview.github.io/?https://github.com/FIWARE-RoboticsGE/Robotics/blob/master/docs/api/FIROS-apiary/firos-apiary.html https://htmlpreview.github.io/?https://github.com/FIWARE-RoboticsGE/Robotics/blob/master/docs/api/RCM-apiary/RCM-apiary.html BR, Pepe Jos? Jaime Ariza R&D Engineer +34 696604288 Ikergune, Etxe-Tar group On 25/09/15 09:19, Bollano Gianmario wrote: > Hi Fabio, > it seems the trick of publishing HTML pages in github is using the special "gh-pages" branch. > Without that branch, github render any file as code instead of passing it to the browser. > instructions to commit html pages in a Github repository are here: > https://help.github.com/articles/creating-project-pages-manually/ > or also here: > https://pages.github.com/ > > After committing in the gh-pages branch, the html pages should be visible as a web page. > > Gianmario > > -----Messaggio originale----- > Da: fiware-robotics-bounces at lists.fiware.org [mailto:fiware-robotics-bounces at lists.fiware.org] Per conto di fabio.dibenedetto at consoft.it > Inviato: gioved? 24 settembre 2015 17:17 > A: fiware-robotics at lists.fi-ware.org > Oggetto: [Fiware-robotics] R: Dockerization > > Thank you for the link, but I'm having some troubles in updating the link because even if the html is in the repository I can go in that html but only in the source and this is not what we wanted. Does anyone know how to solve that? > For what concern the first point the 3 folders are because we don't distribute only one application, we have to distribute all we have and this means that we have 2 types of platforms (master and robot), 3 packages for the communication with fiware (firos, rcm_driver, robotics_msgs). The platforms are distributed without the other components and only in case of the 'all' folder we have a distribution with the master platform and the other packages inside it. These are all the distribution that we can provide using the script 'create_robotics_pkg'. If you use the sources, you have to take the sources and then run this script to create those distributions > > -----Messaggio originale----- > Da: Bollano Gianmario [mailto:gianmario.bollano at telecomitalia.it] > Inviato: gioved? 24 settembre 2015 16:26 > A: fabio.dibenedetto at consoft.it; fiware-robotics at lists.fi-ware.org > Oggetto: R: Dockerization > > Hi Fabio, > my answers: > > 1) It seems a solution to me, better having one than no one. Don't know however why 3 folders are in "dist": can't we just use the code in other folders? > 2) Fine. Any editing to improve/fix is absolutely welcomed. > 3) OpenSpecs R4 are : http://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/FIWARE.OpenSPecification.I2ND.Robotics_R4 > > Best, > Gianmario > > -----Messaggio originale----- > Da: fiware-robotics-bounces at lists.fiware.org [mailto:fiware-robotics-bounces at lists.fiware.org] Per conto di fabio.dibenedetto at consoft.it > Inviato: gioved? 24 settembre 2015 15:14 > A: fiware-robotics at lists.fi-ware.org > Oggetto: [Fiware-robotics] Dockerization > > Hi all, > I looked at the link proposed by Giovanni during the call about the dockerization problem; I don't think that solution can match our GE docker because as process manager you can't specify all the process you'll have to launch in the container. The solution they propose in their post is to add in the container a process supervisor and provide in the dockerfile the processes that will be started by the process supervisor in the container. Our platform is already a process supervisor, but the processes you run are not predetermined and you need the freedom to launch all sub process you need in the container not only a predefined set. As I said in the call the best way to provide a distribution in our case is to provide the compressed files for all the components and let the installer follow the steps specified in the installation guide. > In any case I'll add a new directory in the common repository with the name 'dist' and put in it 3 subfolders: 'all', 'platform', 'components'. The first will keep the master platform with the embedded packages, the second will have master and robot platform, and the third will contain only the other components packages (firos, rcm_driver and robotics_msgs). Is it ok for you? > > > For what concern the documentation I updated the file modified by Pepe because there were some lost letters in some words and a wrong rst format in a little section. I added a webhook to our repository in order to have readthedocs automatically updated when you do some changes (I still haven't tried if it works, but I'll do when I'll commit the 'dist' folder) > > Last question is about the API: the html of both the API are under github the only thing to do is to update the link in openspec (the link should be 2 and not one and they have to point to docs/api/RCM-apiary/RCM-apiary.html and docs/api/FIROS-apiary/firos-apiary.html). Can someone do that or remember me the link of openspec where to change it? > > Fabio > _______________________________________________ > Fiware-robotics mailing list > Fiware-robotics at lists.fiware.org > https://lists.fiware.org/listinfo/fiware-robotics-new > > 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. > > _______________________________________________ > Fiware-robotics mailing list > Fiware-robotics at lists.fiware.org > https://lists.fiware.org/listinfo/fiware-robotics-new > _______________________________________________ > Fiware-robotics mailing list > Fiware-robotics at lists.fiware.org > https://lists.fiware.org/listinfo/fiware-robotics-new > _______________________________________________ Fiware-robotics mailing list Fiware-robotics at lists.fiware.org https://lists.fiware.org/listinfo/fiware-robotics-new From fabio.dibenedetto at consoft.it Fri Sep 25 11:15:41 2015 From: fabio.dibenedetto at consoft.it (fabio.dibenedetto at consoft.it) Date: Fri, 25 Sep 2015 09:15:41 +0000 Subject: R: [Fiware-robotics] R: R: Dockerization In-Reply-To: References: <36ed1964275f4b20a1518b03bbb6352c@EXCHMBX2.consoft.it> <7E649CBD84A947498203DAF8F098B1F6484CDCF1@telmbb003ba020.telecomitalia.local> Message-ID: <3447f1b829b94cce803d12df29f2b54d@EXCHMBX2.consoft.it> Hi I?igo, I don't understand why you need in your folder; if you use robotics_msgs as you use standard_msgs you only need it in the workspace where firos is. Is the same as rcm_driver, it hasn't in his folder, but works with it. I don't know if there is another reason but what I wrote in all the documents is wrong if there isn't the connection between rcm_driver and firos. I know that there is no time to do changes, but we spoke about this before the vacation: there was time back there. In any case for me is not a problem because we are closing but what can I put in my jira issue about firos_rcm_interaction? I cannot say finished because if someone tries our solution and see that doesn't work can say: is this guy that said he tested stupid? And I am the stupid guy that tested it and don't like that much. Pier or Gianmario, can you suggest what to do? Put it finished with a comment or impediment arose? Fabio -----Messaggio originale----- Da: I?igo Gonzalez [mailto:igonzalez at ikergune.com] Inviato: venerd? 25 settembre 2015 09:41 A: fabio.dibenedetto at consoft.it; Jose Jaime Ariza; fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] R: R: Dockerization Hi, we have looking about what to do in the robotics_msgs. The problem is that we also need to have it in our firos folder to work with it, in other way we have had troubles. We think that is late to do any big change only to use the same specification but in different folder. Regards, I?igo On 24/09/15 17:26, fabio.dibenedetto at consoft.it wrote: > Thank you, > to make it easy this kind of non standard version I thought to write a readme.md into the distribution folder, so that the question asked by Gianmario would be available to anyone access that folder. > The question is: how can we manage the change of fiware standard? Can we put in jira that we did so and it's ok or do we have to do something else? > Fabio > > PS: about the question of robotics_msgs use in firos: do we have any news? > > -----Messaggio originale----- > Da: fiware-robotics-bounces at lists.fiware.org > [mailto:fiware-robotics-bounces at lists.fiware.org] Per conto di Jose > Jaime Ariza > Inviato: gioved? 24 settembre 2015 17:12 > A: fiware-robotics at lists.fi-ware.org > Oggetto: Re: [Fiware-robotics] R: Dockerization > > Hi, > > the solution Fabio proposes for the dockerizing the GE sounds great to me. > > I've updated the I&A and U&P guides. I've added some information related to firos, fixed some missing links (including internal readthedoc links) and made some minor modifications. The webhook works perfectly. > > Thank you very much, > > Pepe > > Jos? Jaime Ariza > R&D Engineer > +34 696604288 > Ikergune, Etxe-Tar group > > On 24/09/15 16:26, Bollano Gianmario wrote: >> Hi Fabio, >> my answers: >> >> 1) It seems a solution to me, better having one than no one. Don't know however why 3 folders are in "dist": can't we just use the code in other folders? >> 2) Fine. Any editing to improve/fix is absolutely welcomed. >> 3) OpenSpecs R4 are : >> http://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/FIWAR >> E >> .OpenSPecification.I2ND.Robotics_R4 >> >> Best, >> Gianmario >> >> -----Messaggio originale----- >> Da: fiware-robotics-bounces at lists.fiware.org >> [mailto:fiware-robotics-bounces at lists.fiware.org] Per conto di >> fabio.dibenedetto at consoft.it >> Inviato: gioved? 24 settembre 2015 15:14 >> A: fiware-robotics at lists.fi-ware.org >> Oggetto: [Fiware-robotics] Dockerization >> >> Hi all, >> I looked at the link proposed by Giovanni during the call about the dockerization problem; I don't think that solution can match our GE docker because as process manager you can't specify all the process you'll have to launch in the container. The solution they propose in their post is to add in the container a process supervisor and provide in the dockerfile the processes that will be started by the process supervisor in the container. Our platform is already a process supervisor, but the processes you run are not predetermined and you need the freedom to launch all sub process you need in the container not only a predefined set. As I said in the call the best way to provide a distribution in our case is to provide the compressed files for all the components and let the installer follow the steps specified in the installation guide. >> In any case I'll add a new directory in the common repository with the name 'dist' and put in it 3 subfolders: 'all', 'platform', 'components'. The first will keep the master platform with the embedded packages, the second will have master and robot platform, and the third will contain only the other components packages (firos, rcm_driver and robotics_msgs). Is it ok for you? >> >> >> For what concern the documentation I updated the file modified by >> Pepe because there were some lost letters in some words and a wrong >> rst format in a little section. I added a webhook to our repository >> in order to have readthedocs automatically updated when you do some >> changes (I still haven't tried if it works, but I'll do when I'll >> commit the 'dist' folder) >> >> Last question is about the API: the html of both the API are under github the only thing to do is to update the link in openspec (the link should be 2 and not one and they have to point to docs/api/RCM-apiary/RCM-apiary.html and docs/api/FIROS-apiary/firos-apiary.html). Can someone do that or remember me the link of openspec where to change it? >> >> Fabio >> _______________________________________________ >> Fiware-robotics mailing list >> Fiware-robotics at lists.fiware.org >> https://lists.fiware.org/listinfo/fiware-robotics-new >> >> 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. >> >> _______________________________________________ >> Fiware-robotics mailing list >> Fiware-robotics at lists.fiware.org >> https://lists.fiware.org/listinfo/fiware-robotics-new >> > _______________________________________________ > Fiware-robotics mailing list > Fiware-robotics at lists.fiware.org > https://lists.fiware.org/listinfo/fiware-robotics-new > _______________________________________________ > Fiware-robotics mailing list > Fiware-robotics at lists.fiware.org > https://lists.fiware.org/listinfo/fiware-robotics-new > From gianmario.bollano at telecomitalia.it Fri Sep 25 11:44:52 2015 From: gianmario.bollano at telecomitalia.it (Bollano Gianmario) Date: Fri, 25 Sep 2015 09:44:52 +0000 Subject: R: [Fiware-robotics] R: HTML pages in github In-Reply-To: <8dea7f83a336437ab2953d46cb3efcd1@EXCHMBX2.consoft.it> References: <7E649CBD84A947498203DAF8F098B1F6484CE435@telmbb003ba020.telecomitalia.local> <8dea7f83a336437ab2953d46cb3efcd1@EXCHMBX2.consoft.it> Message-ID: <7E649CBD84A947498203DAF8F098B1F6484CE5E3@telmbb003ba020.telecomitalia.local> It might be a workaround but it has problems: - The Buttons "View in Apiary" do not work - Ugly wrong messing text at the botton of the page (after "References") Then I would avoid htmlpreview and commit to gh-pages instead. I've also downloaded the html code in my PC; the page is OK but the URL for the "View in Apiary" buttons of RCM are wrong and link to non-existent pages in Apiary. For instance the URL for the "read-service-logic" is: http://docs.test_rdapi_01.apiary.io/#reference/service-logics/read-service-logics/read-service-logics Instead of: http://docs.rdapi.apiary.io/#reference/service-logics/read-service-logics/read-service-logics Likely a problem in the conversion from Apiary... Can we maybe just fix manually the links in the html code? Gianmario -----Messaggio originale----- Da: fiware-robotics-bounces at lists.fiware.org [mailto:fiware-robotics-bounces at lists.fiware.org] Per conto di fabio.dibenedetto at consoft.it Inviato: venerd? 25 settembre 2015 10:52 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] R: HTML pages in github Seems to work, but the result has some strange html elements that are not parsed...but can be the tool that originated the files. I'll try both the proposal and see what is better -----Messaggio originale----- Da: fiware-robotics-bounces at lists.fiware.org [mailto:fiware-robotics-bounces at lists.fiware.org] Per conto di Jose Jaime Ariza Inviato: venerd? 25 settembre 2015 10:15 A: fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] HTML pages in github Hi, We could use http://htmlpreview.github.io/, e.g.: https://htmlpreview.github.io/?https://github.com/FIWARE-RoboticsGE/Robotics/blob/master/docs/api/FIROS-apiary/firos-apiary.html https://htmlpreview.github.io/?https://github.com/FIWARE-RoboticsGE/Robotics/blob/master/docs/api/RCM-apiary/RCM-apiary.html BR, Pepe Jos? Jaime Ariza R&D Engineer +34 696604288 Ikergune, Etxe-Tar group On 25/09/15 09:19, Bollano Gianmario wrote: > Hi Fabio, > it seems the trick of publishing HTML pages in github is using the special "gh-pages" branch. > Without that branch, github render any file as code instead of passing it to the browser. > instructions to commit html pages in a Github repository are here: > https://help.github.com/articles/creating-project-pages-manually/ > or also here: > https://pages.github.com/ > > After committing in the gh-pages branch, the html pages should be visible as a web page. > > Gianmario > > -----Messaggio originale----- > Da: fiware-robotics-bounces at lists.fiware.org [mailto:fiware-robotics-bounces at lists.fiware.org] Per conto di fabio.dibenedetto at consoft.it > Inviato: gioved? 24 settembre 2015 17:17 > A: fiware-robotics at lists.fi-ware.org > Oggetto: [Fiware-robotics] R: Dockerization > > Thank you for the link, but I'm having some troubles in updating the link because even if the html is in the repository I can go in that html but only in the source and this is not what we wanted. Does anyone know how to solve that? > For what concern the first point the 3 folders are because we don't distribute only one application, we have to distribute all we have and this means that we have 2 types of platforms (master and robot), 3 packages for the communication with fiware (firos, rcm_driver, robotics_msgs). The platforms are distributed without the other components and only in case of the 'all' folder we have a distribution with the master platform and the other packages inside it. These are all the distribution that we can provide using the script 'create_robotics_pkg'. If you use the sources, you have to take the sources and then run this script to create those distributions > > -----Messaggio originale----- > Da: Bollano Gianmario [mailto:gianmario.bollano at telecomitalia.it] > Inviato: gioved? 24 settembre 2015 16:26 > A: fabio.dibenedetto at consoft.it; fiware-robotics at lists.fi-ware.org > Oggetto: R: Dockerization > > Hi Fabio, > my answers: > > 1) It seems a solution to me, better having one than no one. Don't know however why 3 folders are in "dist": can't we just use the code in other folders? > 2) Fine. Any editing to improve/fix is absolutely welcomed. > 3) OpenSpecs R4 are : http://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/FIWARE.OpenSPecification.I2ND.Robotics_R4 > > Best, > Gianmario > > -----Messaggio originale----- > Da: fiware-robotics-bounces at lists.fiware.org [mailto:fiware-robotics-bounces at lists.fiware.org] Per conto di fabio.dibenedetto at consoft.it > Inviato: gioved? 24 settembre 2015 15:14 > A: fiware-robotics at lists.fi-ware.org > Oggetto: [Fiware-robotics] Dockerization > > Hi all, > I looked at the link proposed by Giovanni during the call about the dockerization problem; I don't think that solution can match our GE docker because as process manager you can't specify all the process you'll have to launch in the container. The solution they propose in their post is to add in the container a process supervisor and provide in the dockerfile the processes that will be started by the process supervisor in the container. Our platform is already a process supervisor, but the processes you run are not predetermined and you need the freedom to launch all sub process you need in the container not only a predefined set. As I said in the call the best way to provide a distribution in our case is to provide the compressed files for all the components and let the installer follow the steps specified in the installation guide. > In any case I'll add a new directory in the common repository with the name 'dist' and put in it 3 subfolders: 'all', 'platform', 'components'. The first will keep the master platform with the embedded packages, the second will have master and robot platform, and the third will contain only the other components packages (firos, rcm_driver and robotics_msgs). Is it ok for you? > > > For what concern the documentation I updated the file modified by Pepe because there were some lost letters in some words and a wrong rst format in a little section. I added a webhook to our repository in order to have readthedocs automatically updated when you do some changes (I still haven't tried if it works, but I'll do when I'll commit the 'dist' folder) > > Last question is about the API: the html of both the API are under github the only thing to do is to update the link in openspec (the link should be 2 and not one and they have to point to docs/api/RCM-apiary/RCM-apiary.html and docs/api/FIROS-apiary/firos-apiary.html). Can someone do that or remember me the link of openspec where to change it? > > Fabio > _______________________________________________ > Fiware-robotics mailing list > Fiware-robotics at lists.fiware.org > https://lists.fiware.org/listinfo/fiware-robotics-new > > 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. > > _______________________________________________ > Fiware-robotics mailing list > Fiware-robotics at lists.fiware.org > https://lists.fiware.org/listinfo/fiware-robotics-new > _______________________________________________ > Fiware-robotics mailing list > Fiware-robotics at lists.fiware.org > https://lists.fiware.org/listinfo/fiware-robotics-new > _______________________________________________ Fiware-robotics mailing list Fiware-robotics at lists.fiware.org https://lists.fiware.org/listinfo/fiware-robotics-new _______________________________________________ Fiware-robotics mailing list Fiware-robotics at lists.fiware.org https://lists.fiware.org/listinfo/fiware-robotics-new From gianmario.bollano at telecomitalia.it Fri Sep 25 12:02:53 2015 From: gianmario.bollano at telecomitalia.it (Bollano Gianmario) Date: Fri, 25 Sep 2015 10:02:53 +0000 Subject: R: [Fiware-robotics] R: R: HTML pages in github In-Reply-To: <7E649CBD84A947498203DAF8F098B1F6484CE5E3@telmbb003ba020.telecomitalia.local> References: <7E649CBD84A947498203DAF8F098B1F6484CE435@telmbb003ba020.telecomitalia.local> <8dea7f83a336437ab2953d46cb3efcd1@EXCHMBX2.consoft.it> <7E649CBD84A947498203DAF8F098B1F6484CE5E3@telmbb003ba020.telecomitalia.local> Message-ID: <7E649CBD84A947498203DAF8F098B1F6484CE623@telmbb003ba020.telecomitalia.local> I've just fixed the url for buttons "View in Apiary". It is sufficient to replace " docs.test_rdapi_01.apiary.io" with " docs.rdapi.apiary.io". They work in a browser. Please notice that anyway these buttons DO NOT work however with htmlpreview (neither firos nor RCM) We need to commit to gh-pages . -----Messaggio originale----- Da: fiware-robotics-bounces at lists.fiware.org [mailto:fiware-robotics-bounces at lists.fiware.org] Per conto di Bollano Gianmario Inviato: venerd? 25 settembre 2015 11:45 A: fabio.dibenedetto at consoft.it; fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] R: R: HTML pages in github It might be a workaround but it has problems: - The Buttons "View in Apiary" do not work - Ugly wrong messing text at the botton of the page (after "References") Then I would avoid htmlpreview and commit to gh-pages instead. I've also downloaded the html code in my PC; the page is OK but the URL for the "View in Apiary" buttons of RCM are wrong and link to non-existent pages in Apiary. For instance the URL for the "read-service-logic" is: http://docs.test_rdapi_01.apiary.io/#reference/service-logics/read-service-logics/read-service-logics Instead of: http://docs.rdapi.apiary.io/#reference/service-logics/read-service-logics/read-service-logics Likely a problem in the conversion from Apiary... Can we maybe just fix manually the links in the html code? Gianmario -----Messaggio originale----- Da: fiware-robotics-bounces at lists.fiware.org [mailto:fiware-robotics-bounces at lists.fiware.org] Per conto di fabio.dibenedetto at consoft.it Inviato: venerd? 25 settembre 2015 10:52 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] R: HTML pages in github Seems to work, but the result has some strange html elements that are not parsed...but can be the tool that originated the files. I'll try both the proposal and see what is better -----Messaggio originale----- Da: fiware-robotics-bounces at lists.fiware.org [mailto:fiware-robotics-bounces at lists.fiware.org] Per conto di Jose Jaime Ariza Inviato: venerd? 25 settembre 2015 10:15 A: fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] HTML pages in github Hi, We could use http://htmlpreview.github.io/, e.g.: https://htmlpreview.github.io/?https://github.com/FIWARE-RoboticsGE/Robotics/blob/master/docs/api/FIROS-apiary/firos-apiary.html https://htmlpreview.github.io/?https://github.com/FIWARE-RoboticsGE/Robotics/blob/master/docs/api/RCM-apiary/RCM-apiary.html BR, Pepe Jos? Jaime Ariza R&D Engineer +34 696604288 Ikergune, Etxe-Tar group On 25/09/15 09:19, Bollano Gianmario wrote: > Hi Fabio, > it seems the trick of publishing HTML pages in github is using the special "gh-pages" branch. > Without that branch, github render any file as code instead of passing it to the browser. > instructions to commit html pages in a Github repository are here: > https://help.github.com/articles/creating-project-pages-manually/ > or also here: > https://pages.github.com/ > > After committing in the gh-pages branch, the html pages should be visible as a web page. > > Gianmario > > -----Messaggio originale----- > Da: fiware-robotics-bounces at lists.fiware.org [mailto:fiware-robotics-bounces at lists.fiware.org] Per conto di fabio.dibenedetto at consoft.it > Inviato: gioved? 24 settembre 2015 17:17 > A: fiware-robotics at lists.fi-ware.org > Oggetto: [Fiware-robotics] R: Dockerization > > Thank you for the link, but I'm having some troubles in updating the link because even if the html is in the repository I can go in that html but only in the source and this is not what we wanted. Does anyone know how to solve that? > For what concern the first point the 3 folders are because we don't distribute only one application, we have to distribute all we have and this means that we have 2 types of platforms (master and robot), 3 packages for the communication with fiware (firos, rcm_driver, robotics_msgs). The platforms are distributed without the other components and only in case of the 'all' folder we have a distribution with the master platform and the other packages inside it. These are all the distribution that we can provide using the script 'create_robotics_pkg'. If you use the sources, you have to take the sources and then run this script to create those distributions > > -----Messaggio originale----- > Da: Bollano Gianmario [mailto:gianmario.bollano at telecomitalia.it] > Inviato: gioved? 24 settembre 2015 16:26 > A: fabio.dibenedetto at consoft.it; fiware-robotics at lists.fi-ware.org > Oggetto: R: Dockerization > > Hi Fabio, > my answers: > > 1) It seems a solution to me, better having one than no one. Don't know however why 3 folders are in "dist": can't we just use the code in other folders? > 2) Fine. Any editing to improve/fix is absolutely welcomed. > 3) OpenSpecs R4 are : http://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/FIWARE.OpenSPecification.I2ND.Robotics_R4 > > Best, > Gianmario > > -----Messaggio originale----- > Da: fiware-robotics-bounces at lists.fiware.org [mailto:fiware-robotics-bounces at lists.fiware.org] Per conto di fabio.dibenedetto at consoft.it > Inviato: gioved? 24 settembre 2015 15:14 > A: fiware-robotics at lists.fi-ware.org > Oggetto: [Fiware-robotics] Dockerization > > Hi all, > I looked at the link proposed by Giovanni during the call about the dockerization problem; I don't think that solution can match our GE docker because as process manager you can't specify all the process you'll have to launch in the container. The solution they propose in their post is to add in the container a process supervisor and provide in the dockerfile the processes that will be started by the process supervisor in the container. Our platform is already a process supervisor, but the processes you run are not predetermined and you need the freedom to launch all sub process you need in the container not only a predefined set. As I said in the call the best way to provide a distribution in our case is to provide the compressed files for all the components and let the installer follow the steps specified in the installation guide. > In any case I'll add a new directory in the common repository with the name 'dist' and put in it 3 subfolders: 'all', 'platform', 'components'. The first will keep the master platform with the embedded packages, the second will have master and robot platform, and the third will contain only the other components packages (firos, rcm_driver and robotics_msgs). Is it ok for you? > > > For what concern the documentation I updated the file modified by Pepe because there were some lost letters in some words and a wrong rst format in a little section. I added a webhook to our repository in order to have readthedocs automatically updated when you do some changes (I still haven't tried if it works, but I'll do when I'll commit the 'dist' folder) > > Last question is about the API: the html of both the API are under github the only thing to do is to update the link in openspec (the link should be 2 and not one and they have to point to docs/api/RCM-apiary/RCM-apiary.html and docs/api/FIROS-apiary/firos-apiary.html). Can someone do that or remember me the link of openspec where to change it? > > Fabio > _______________________________________________ > Fiware-robotics mailing list > Fiware-robotics at lists.fiware.org > https://lists.fiware.org/listinfo/fiware-robotics-new > > 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. > > _______________________________________________ > Fiware-robotics mailing list > Fiware-robotics at lists.fiware.org > https://lists.fiware.org/listinfo/fiware-robotics-new > _______________________________________________ > Fiware-robotics mailing list > Fiware-robotics at lists.fiware.org > https://lists.fiware.org/listinfo/fiware-robotics-new > _______________________________________________ Fiware-robotics mailing list Fiware-robotics at lists.fiware.org https://lists.fiware.org/listinfo/fiware-robotics-new _______________________________________________ Fiware-robotics mailing list Fiware-robotics at lists.fiware.org https://lists.fiware.org/listinfo/fiware-robotics-new _______________________________________________ Fiware-robotics mailing list Fiware-robotics at lists.fiware.org https://lists.fiware.org/listinfo/fiware-robotics-new From fabio.dibenedetto at consoft.it Fri Sep 25 16:45:32 2015 From: fabio.dibenedetto at consoft.it (fabio.dibenedetto at consoft.it) Date: Fri, 25 Sep 2015 14:45:32 +0000 Subject: R: [Fiware-robotics] R: R: R: HTML pages in github In-Reply-To: <7E649CBD84A947498203DAF8F098B1F6484CE623@telmbb003ba020.telecomitalia.local> References: <7E649CBD84A947498203DAF8F098B1F6484CE435@telmbb003ba020.telecomitalia.local> <8dea7f83a336437ab2953d46cb3efcd1@EXCHMBX2.consoft.it> <7E649CBD84A947498203DAF8F098B1F6484CE5E3@telmbb003ba020.telecomitalia.local> <7E649CBD84A947498203DAF8F098B1F6484CE623@telmbb003ba020.telecomitalia.local> Message-ID: Hi guys, I updated our repository with a new branch gh-pages and I put there a fake page as main page (loading the readme in an ugly template of github); I've added all the documents and api in this branch so you can see them directly as html as said by Gianmario. I've updated the links in all the documents I remember (open specs now points to this pages for what concern the api's but to readthedocs for what concern the other documents because I didn't have a fiware template to apply in sphinx and the classic template is uglier than the one used for the github page). Check if it is ok I'm still waiting to know how to close my jira issue about the firos-rcm-interaction, but in any case I'll close that today so let me know before I'll go out of the office -----Messaggio originale----- Da: fiware-robotics-bounces at lists.fiware.org [mailto:fiware-robotics-bounces at lists.fiware.org] Per conto di Bollano Gianmario Inviato: venerd? 25 settembre 2015 12:03 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] R: R: R: HTML pages in github I've just fixed the url for buttons "View in Apiary". It is sufficient to replace " docs.test_rdapi_01.apiary.io" with " docs.rdapi.apiary.io". They work in a browser. Please notice that anyway these buttons DO NOT work however with htmlpreview (neither firos nor RCM) We need to commit to gh-pages . -----Messaggio originale----- Da: fiware-robotics-bounces at lists.fiware.org [mailto:fiware-robotics-bounces at lists.fiware.org] Per conto di Bollano Gianmario Inviato: venerd? 25 settembre 2015 11:45 A: fabio.dibenedetto at consoft.it; fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] R: R: HTML pages in github It might be a workaround but it has problems: - The Buttons "View in Apiary" do not work - Ugly wrong messing text at the botton of the page (after "References") Then I would avoid htmlpreview and commit to gh-pages instead. I've also downloaded the html code in my PC; the page is OK but the URL for the "View in Apiary" buttons of RCM are wrong and link to non-existent pages in Apiary. For instance the URL for the "read-service-logic" is: http://docs.test_rdapi_01.apiary.io/#reference/service-logics/read-service-logics/read-service-logics Instead of: http://docs.rdapi.apiary.io/#reference/service-logics/read-service-logics/read-service-logics Likely a problem in the conversion from Apiary... Can we maybe just fix manually the links in the html code? Gianmario -----Messaggio originale----- Da: fiware-robotics-bounces at lists.fiware.org [mailto:fiware-robotics-bounces at lists.fiware.org] Per conto di fabio.dibenedetto at consoft.it Inviato: venerd? 25 settembre 2015 10:52 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] R: HTML pages in github Seems to work, but the result has some strange html elements that are not parsed...but can be the tool that originated the files. I'll try both the proposal and see what is better -----Messaggio originale----- Da: fiware-robotics-bounces at lists.fiware.org [mailto:fiware-robotics-bounces at lists.fiware.org] Per conto di Jose Jaime Ariza Inviato: venerd? 25 settembre 2015 10:15 A: fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] HTML pages in github Hi, We could use http://htmlpreview.github.io/, e.g.: https://htmlpreview.github.io/?https://github.com/FIWARE-RoboticsGE/Robotics/blob/master/docs/api/FIROS-apiary/firos-apiary.html https://htmlpreview.github.io/?https://github.com/FIWARE-RoboticsGE/Robotics/blob/master/docs/api/RCM-apiary/RCM-apiary.html BR, Pepe Jos? Jaime Ariza R&D Engineer +34 696604288 Ikergune, Etxe-Tar group On 25/09/15 09:19, Bollano Gianmario wrote: > Hi Fabio, > it seems the trick of publishing HTML pages in github is using the special "gh-pages" branch. > Without that branch, github render any file as code instead of passing it to the browser. > instructions to commit html pages in a Github repository are here: > https://help.github.com/articles/creating-project-pages-manually/ > or also here: > https://pages.github.com/ > > After committing in the gh-pages branch, the html pages should be visible as a web page. > > Gianmario > > -----Messaggio originale----- > Da: fiware-robotics-bounces at lists.fiware.org > [mailto:fiware-robotics-bounces at lists.fiware.org] Per conto di > fabio.dibenedetto at consoft.it > Inviato: gioved? 24 settembre 2015 17:17 > A: fiware-robotics at lists.fi-ware.org > Oggetto: [Fiware-robotics] R: Dockerization > > Thank you for the link, but I'm having some troubles in updating the link because even if the html is in the repository I can go in that html but only in the source and this is not what we wanted. Does anyone know how to solve that? > For what concern the first point the 3 folders are because we don't > distribute only one application, we have to distribute all we have and > this means that we have 2 types of platforms (master and robot), 3 > packages for the communication with fiware (firos, rcm_driver, > robotics_msgs). The platforms are distributed without the other > components and only in case of the 'all' folder we have a distribution > with the master platform and the other packages inside it. These are > all the distribution that we can provide using the script > 'create_robotics_pkg'. If you use the sources, you have to take the > sources and then run this script to create those distributions > > -----Messaggio originale----- > Da: Bollano Gianmario [mailto:gianmario.bollano at telecomitalia.it] > Inviato: gioved? 24 settembre 2015 16:26 > A: fabio.dibenedetto at consoft.it; fiware-robotics at lists.fi-ware.org > Oggetto: R: Dockerization > > Hi Fabio, > my answers: > > 1) It seems a solution to me, better having one than no one. Don't know however why 3 folders are in "dist": can't we just use the code in other folders? > 2) Fine. Any editing to improve/fix is absolutely welcomed. > 3) OpenSpecs R4 are : > http://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/FIWARE > .OpenSPecification.I2ND.Robotics_R4 > > Best, > Gianmario > > -----Messaggio originale----- > Da: fiware-robotics-bounces at lists.fiware.org > [mailto:fiware-robotics-bounces at lists.fiware.org] Per conto di > fabio.dibenedetto at consoft.it > Inviato: gioved? 24 settembre 2015 15:14 > A: fiware-robotics at lists.fi-ware.org > Oggetto: [Fiware-robotics] Dockerization > > Hi all, > I looked at the link proposed by Giovanni during the call about the dockerization problem; I don't think that solution can match our GE docker because as process manager you can't specify all the process you'll have to launch in the container. The solution they propose in their post is to add in the container a process supervisor and provide in the dockerfile the processes that will be started by the process supervisor in the container. Our platform is already a process supervisor, but the processes you run are not predetermined and you need the freedom to launch all sub process you need in the container not only a predefined set. As I said in the call the best way to provide a distribution in our case is to provide the compressed files for all the components and let the installer follow the steps specified in the installation guide. > In any case I'll add a new directory in the common repository with the name 'dist' and put in it 3 subfolders: 'all', 'platform', 'components'. The first will keep the master platform with the embedded packages, the second will have master and robot platform, and the third will contain only the other components packages (firos, rcm_driver and robotics_msgs). Is it ok for you? > > > For what concern the documentation I updated the file modified by Pepe > because there were some lost letters in some words and a wrong rst > format in a little section. I added a webhook to our repository in > order to have readthedocs automatically updated when you do some > changes (I still haven't tried if it works, but I'll do when I'll > commit the 'dist' folder) > > Last question is about the API: the html of both the API are under github the only thing to do is to update the link in openspec (the link should be 2 and not one and they have to point to docs/api/RCM-apiary/RCM-apiary.html and docs/api/FIROS-apiary/firos-apiary.html). Can someone do that or remember me the link of openspec where to change it? > > Fabio > _______________________________________________ > Fiware-robotics mailing list > Fiware-robotics at lists.fiware.org > https://lists.fiware.org/listinfo/fiware-robotics-new > > 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. > > _______________________________________________ > Fiware-robotics mailing list > Fiware-robotics at lists.fiware.org > https://lists.fiware.org/listinfo/fiware-robotics-new > _______________________________________________ > Fiware-robotics mailing list > Fiware-robotics at lists.fiware.org > https://lists.fiware.org/listinfo/fiware-robotics-new > _______________________________________________ Fiware-robotics mailing list Fiware-robotics at lists.fiware.org https://lists.fiware.org/listinfo/fiware-robotics-new _______________________________________________ Fiware-robotics mailing list Fiware-robotics at lists.fiware.org https://lists.fiware.org/listinfo/fiware-robotics-new _______________________________________________ Fiware-robotics mailing list Fiware-robotics at lists.fiware.org https://lists.fiware.org/listinfo/fiware-robotics-new _______________________________________________ Fiware-robotics mailing list Fiware-robotics at lists.fiware.org https://lists.fiware.org/listinfo/fiware-robotics-new From gianmario.bollano at telecomitalia.it Fri Sep 25 17:20:34 2015 From: gianmario.bollano at telecomitalia.it (Bollano Gianmario) Date: Fri, 25 Sep 2015 15:20:34 +0000 Subject: R: [Fiware-robotics] R: R: R: R: HTML pages in github In-Reply-To: References: <7E649CBD84A947498203DAF8F098B1F6484CE435@telmbb003ba020.telecomitalia.local> <8dea7f83a336437ab2953d46cb3efcd1@EXCHMBX2.consoft.it> <7E649CBD84A947498203DAF8F098B1F6484CE5E3@telmbb003ba020.telecomitalia.local> <7E649CBD84A947498203DAF8F098B1F6484CE623@telmbb003ba020.telecomitalia.local> Message-ID: <7E649CBD84A947498203DAF8F098B1F6484CE7B5@telmbb003ba020.telecomitalia.local> I've tested the updated pages and links , anything works fine now, great! About the jira better to close it adding notes explaining details. Gianmario -----Messaggio originale----- Da: fiware-robotics-bounces at lists.fiware.org [mailto:fiware-robotics-bounces at lists.fiware.org] Per conto di fabio.dibenedetto at consoft.it Inviato: venerd? 25 settembre 2015 16:46 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] R: R: R: R: HTML pages in github Hi guys, I updated our repository with a new branch gh-pages and I put there a fake page as main page (loading the readme in an ugly template of github); I've added all the documents and api in this branch so you can see them directly as html as said by Gianmario. I've updated the links in all the documents I remember (open specs now points to this pages for what concern the api's but to readthedocs for what concern the other documents because I didn't have a fiware template to apply in sphinx and the classic template is uglier than the one used for the github page). Check if it is ok I'm still waiting to know how to close my jira issue about the firos-rcm-interaction, but in any case I'll close that today so let me know before I'll go out of the office -----Messaggio originale----- Da: fiware-robotics-bounces at lists.fiware.org [mailto:fiware-robotics-bounces at lists.fiware.org] Per conto di Bollano Gianmario Inviato: venerd? 25 settembre 2015 12:03 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] R: R: R: HTML pages in github I've just fixed the url for buttons "View in Apiary". It is sufficient to replace " docs.test_rdapi_01.apiary.io" with " docs.rdapi.apiary.io". They work in a browser. Please notice that anyway these buttons DO NOT work however with htmlpreview (neither firos nor RCM) We need to commit to gh-pages . -----Messaggio originale----- Da: fiware-robotics-bounces at lists.fiware.org [mailto:fiware-robotics-bounces at lists.fiware.org] Per conto di Bollano Gianmario Inviato: venerd? 25 settembre 2015 11:45 A: fabio.dibenedetto at consoft.it; fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] R: R: HTML pages in github It might be a workaround but it has problems: - The Buttons "View in Apiary" do not work - Ugly wrong messing text at the botton of the page (after "References") Then I would avoid htmlpreview and commit to gh-pages instead. I've also downloaded the html code in my PC; the page is OK but the URL for the "View in Apiary" buttons of RCM are wrong and link to non-existent pages in Apiary. For instance the URL for the "read-service-logic" is: http://docs.test_rdapi_01.apiary.io/#reference/service-logics/read-service-logics/read-service-logics Instead of: http://docs.rdapi.apiary.io/#reference/service-logics/read-service-logics/read-service-logics Likely a problem in the conversion from Apiary... Can we maybe just fix manually the links in the html code? Gianmario -----Messaggio originale----- Da: fiware-robotics-bounces at lists.fiware.org [mailto:fiware-robotics-bounces at lists.fiware.org] Per conto di fabio.dibenedetto at consoft.it Inviato: venerd? 25 settembre 2015 10:52 A: fiware-robotics at lists.fi-ware.org Oggetto: [Fiware-robotics] R: HTML pages in github Seems to work, but the result has some strange html elements that are not parsed...but can be the tool that originated the files. I'll try both the proposal and see what is better -----Messaggio originale----- Da: fiware-robotics-bounces at lists.fiware.org [mailto:fiware-robotics-bounces at lists.fiware.org] Per conto di Jose Jaime Ariza Inviato: venerd? 25 settembre 2015 10:15 A: fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] HTML pages in github Hi, We could use http://htmlpreview.github.io/, e.g.: https://htmlpreview.github.io/?https://github.com/FIWARE-RoboticsGE/Robotics/blob/master/docs/api/FIROS-apiary/firos-apiary.html https://htmlpreview.github.io/?https://github.com/FIWARE-RoboticsGE/Robotics/blob/master/docs/api/RCM-apiary/RCM-apiary.html BR, Pepe Jos? Jaime Ariza R&D Engineer +34 696604288 Ikergune, Etxe-Tar group On 25/09/15 09:19, Bollano Gianmario wrote: > Hi Fabio, > it seems the trick of publishing HTML pages in github is using the special "gh-pages" branch. > Without that branch, github render any file as code instead of passing it to the browser. > instructions to commit html pages in a Github repository are here: > https://help.github.com/articles/creating-project-pages-manually/ > or also here: > https://pages.github.com/ > > After committing in the gh-pages branch, the html pages should be visible as a web page. > > Gianmario > > -----Messaggio originale----- > Da: fiware-robotics-bounces at lists.fiware.org > [mailto:fiware-robotics-bounces at lists.fiware.org] Per conto di > fabio.dibenedetto at consoft.it > Inviato: gioved? 24 settembre 2015 17:17 > A: fiware-robotics at lists.fi-ware.org > Oggetto: [Fiware-robotics] R: Dockerization > > Thank you for the link, but I'm having some troubles in updating the link because even if the html is in the repository I can go in that html but only in the source and this is not what we wanted. Does anyone know how to solve that? > For what concern the first point the 3 folders are because we don't > distribute only one application, we have to distribute all we have and > this means that we have 2 types of platforms (master and robot), 3 > packages for the communication with fiware (firos, rcm_driver, > robotics_msgs). The platforms are distributed without the other > components and only in case of the 'all' folder we have a distribution > with the master platform and the other packages inside it. These are > all the distribution that we can provide using the script > 'create_robotics_pkg'. If you use the sources, you have to take the > sources and then run this script to create those distributions > > -----Messaggio originale----- > Da: Bollano Gianmario [mailto:gianmario.bollano at telecomitalia.it] > Inviato: gioved? 24 settembre 2015 16:26 > A: fabio.dibenedetto at consoft.it; fiware-robotics at lists.fi-ware.org > Oggetto: R: Dockerization > > Hi Fabio, > my answers: > > 1) It seems a solution to me, better having one than no one. Don't know however why 3 folders are in "dist": can't we just use the code in other folders? > 2) Fine. Any editing to improve/fix is absolutely welcomed. > 3) OpenSpecs R4 are : > http://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/FIWARE > .OpenSPecification.I2ND.Robotics_R4 > > Best, > Gianmario > > -----Messaggio originale----- > Da: fiware-robotics-bounces at lists.fiware.org > [mailto:fiware-robotics-bounces at lists.fiware.org] Per conto di > fabio.dibenedetto at consoft.it > Inviato: gioved? 24 settembre 2015 15:14 > A: fiware-robotics at lists.fi-ware.org > Oggetto: [Fiware-robotics] Dockerization > > Hi all, > I looked at the link proposed by Giovanni during the call about the dockerization problem; I don't think that solution can match our GE docker because as process manager you can't specify all the process you'll have to launch in the container. The solution they propose in their post is to add in the container a process supervisor and provide in the dockerfile the processes that will be started by the process supervisor in the container. Our platform is already a process supervisor, but the processes you run are not predetermined and you need the freedom to launch all sub process you need in the container not only a predefined set. As I said in the call the best way to provide a distribution in our case is to provide the compressed files for all the components and let the installer follow the steps specified in the installation guide. > In any case I'll add a new directory in the common repository with the name 'dist' and put in it 3 subfolders: 'all', 'platform', 'components'. The first will keep the master platform with the embedded packages, the second will have master and robot platform, and the third will contain only the other components packages (firos, rcm_driver and robotics_msgs). Is it ok for you? > > > For what concern the documentation I updated the file modified by Pepe > because there were some lost letters in some words and a wrong rst > format in a little section. I added a webhook to our repository in > order to have readthedocs automatically updated when you do some > changes (I still haven't tried if it works, but I'll do when I'll > commit the 'dist' folder) > > Last question is about the API: the html of both the API are under github the only thing to do is to update the link in openspec (the link should be 2 and not one and they have to point to docs/api/RCM-apiary/RCM-apiary.html and docs/api/FIROS-apiary/firos-apiary.html). Can someone do that or remember me the link of openspec where to change it? > > Fabio > _______________________________________________ > Fiware-robotics mailing list > Fiware-robotics at lists.fiware.org > https://lists.fiware.org/listinfo/fiware-robotics-new > > 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. > > _______________________________________________ > Fiware-robotics mailing list > Fiware-robotics at lists.fiware.org > https://lists.fiware.org/listinfo/fiware-robotics-new > _______________________________________________ > Fiware-robotics mailing list > Fiware-robotics at lists.fiware.org > https://lists.fiware.org/listinfo/fiware-robotics-new > _______________________________________________ Fiware-robotics mailing list Fiware-robotics at lists.fiware.org https://lists.fiware.org/listinfo/fiware-robotics-new _______________________________________________ Fiware-robotics mailing list Fiware-robotics at lists.fiware.org https://lists.fiware.org/listinfo/fiware-robotics-new _______________________________________________ Fiware-robotics mailing list Fiware-robotics at lists.fiware.org https://lists.fiware.org/listinfo/fiware-robotics-new _______________________________________________ Fiware-robotics mailing list Fiware-robotics at lists.fiware.org https://lists.fiware.org/listinfo/fiware-robotics-new _______________________________________________ Fiware-robotics mailing list Fiware-robotics at lists.fiware.org https://lists.fiware.org/listinfo/fiware-robotics-new