R: OpenSpecs

Garino Pierangelo pierangelo.garino at telecomitalia.it
Tue Sep 8 14:08:59 CEST 2015


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



More information about the Fiware-robotics mailing list

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