[Fiware-chapter-architects] Software delivery rules: closing this and communicating it to the consortium

[JOSE MANUEL CANTERA FONSECA]

Hello,

You can find a draft template for creating Open API Specs at [1]using API Blueprint Format [2]. Specifications, for the moment, can be generated using the standard Apiary generation tool [3]. ULPGC is working on a generation tool that will leverage the Apiary default one and will give us more flexibility, enabling us to generate specs with FIWARE Look & Feel (we will ask Ogilvy to create nice designs for them).

Our plan, Miguel will provide further details, is to use Github Gh Pages facility (provided for each GE's Repo) to host the Open API Spec Pages and to link them from the Wiki.

Should you have any doubt please do not hesitate to contact us.

All the best

[1] https://github.com/jmcanterafonseca/fiware-specs-template/blob/master/template-fiware-open-spec2.apib
[2] https://github.com/apiaryio/api-blueprint/blob/master/API%20Blueprint%20Specification.md
[3] https://github.com/apiaryio/apiary-client

De: MIGUEL CARRILLO PACHECO <miguel.carrillopacheco at telefonica.com<mailto:miguel.carrillopacheco at telefonica.com>>
Fecha: miércoles, 8 de julio de 2015, 12:47
Para: "fiware-chapter-leaders at lists.fi-ware.org<mailto:fiware-chapter-leaders at lists.fi-ware.org>" <fiware-chapter-leaders at lists.fi-ware.org<mailto:fiware-chapter-leaders at lists.fi-ware.org>>, "fiware-chapter-architects at lists.fi-ware.org<mailto:fiware-chapter-architects at lists.fi-ware.org>" <fiware-chapter-architects at lists.fi-ware.org<mailto:fiware-chapter-architects at lists.fi-ware.org>>
CC: JUAN JOSE HIERRO SUREDA <juanjose.hierro at telefonica.com<mailto:juanjose.hierro at telefonica.com>>, MANUEL ESCRICHE VICENTE <manuel.escrichevicente at telefonica.com<mailto:manuel.escrichevicente at telefonica.com>>, Jose Manuel Cantera Fonseca <josemanuel.canterafonseca at telefonica.com<mailto:josemanuel.canterafonseca at telefonica.com>>
Asunto: Software delivery rules: closing this and communicating it to the consortium

Hi all,

It is urgent to close all open points to enable people to start creating the deliverables for September. They must have been working on it following the agile dynamics with Manuel but now they should know how to prepare the delivery for the end of the summer.

Let us try to give it a formal shape:

1) Finalization of first version of GE implementation guidelines (ALL - leader: J.M. Cantera)
    * Thursday, 9/July (tomorrow!)
    * The reference is here: https://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/Developer_Guidelines
    * In order to relieve the pressure on you and to smooth out the transition to github, we have exceptionally decided to allow snapshots of Release 4 on github. Of course, it is advisable to use the guidelines for github in R4 as well! For the future work in the coming releases (from October onwards) we expect you to strictly work as stated in the developer guidelines.

2) Availability of tools & templates to create docs using APIary specs and markdown docs  on Github  (ULPGC)
        (this has nothing to do with the wiki delivery generation tool)
    * End of July

3) Definition of guidelines & structure to produce the open specs - send to the whole consortium (TID)
    * Thursday, 9/July (tomorrow!)

Regards,

José Manuel & Miguel



--

Please update your address book with my new e-mail address: miguel.carrillopacheco at telefonica.com<mailto:miguel.carrillopacheco at telefonica.com>

----------------------------------------------------------------------
     _/          _/_/                     Miguel Carrillo Pacheco
    _/   _/     _/  _/   Telefónica       Distrito Telefónica
   _/ _/_/_/   _/   _/   Investigación y  Edifico Oeste 1, Planta 6
  _/   _/     _/  _/     Desarrollo       Ronda de la Comunicación S/N
 _/          _/_/                         28050 Madrid (Spain)
                                          Tel:  (+34) 91 483 26 77

                         e-mail: miguel.carrillopacheco at telefonica.com<mailto:miguel.carrillopacheco at telefonica.com>

Follow FIWARE on the net

        Website:  http://www.fiware.org
        Facebook: https://www.facebook.com/eu.fiware
        Twitter:  http://twitter.com/Fiware
        LinkedIn: https://www.linkedin.com/groups/FIWARE-4239932
----------------------------------------------------------------------

________________________________

Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener información privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilización, divulgación y/o copia sin autorización puede estar prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción.

The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it.

Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, pode conter informação privilegiada ou confidencial e é para uso exclusivo da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário indicado, fica notificado de que a leitura, utilização, divulgação e/ou cópia sem autorização pode estar proibida em virtude da legislação vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destruição
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-chapter-architects/attachments/20150709/54e44165/attachment.html>