[Fiware-iot] R4 delivery

[t.elsaleh at surrey.ac.uk]

Dear Gilles,

I have populated the table as required for IoT Discovery. The pdf files for the guides are attached. These are “print” PDF versions of the documentation on readthedocs. I was not able to use the PDF generator that readthedocs uses because of the type of configuration file used, i.e. mkdocs. This link<http://read-the-docs.readthedocs.org/en/latest/builds.html?highlight=pdf#mkdocs> explains that PDF are not supported for this kind. From what I have noticed from other GE github repos, they also use mkdocs.

So the question is how are we expected to generate the PDF files??? I thought FABRE was only used for API blueprints only, and not markdown.

Best regards,
Tarek

From: fiware-iot-bounces at lists.fiware.org [mailto:fiware-iot-bounces at lists.fiware.org] On Behalf Of gilles.privat at orange.com
Sent: 11 December 2015 18:06
To: fiware-iot at lists.fiware.org
Subject: [Fiware-iot] R4 delivery

Dear colleagues


Could you complete the table below for your GE and send it back to me with the 2 pdfs for

     *   Installation & Admin Manual
     *   User and Programmers Manual

as requested by Miguel


Cordially



GE Name


GE implementation


FIWARE Partner

<short name>


Github Release  for R4

<Release in  github that corresponds to R4>


Software repository

<Links to github>


Installation and Administration Guide

<Links to readthedocs -  to the version associated to R4>


User and Programmers Guide

<Links to readthedocs -  to the version associated to R4>

Backend Device Manager

IDAS

TID









Backend IoT Broker

IoT Broker

NEC









IoT Discovery

IoT Discovery

UNIS

https://github.com/UniSurreyIoT/fiware-iot-discovery-s2w/tree/master
https://github.com/UniSurreyIoT/fiware-iot-discovery-ngsi9/tree/master

https://github.com/UniSurreyIoT/fiware-iot-discovery-ngsi9
https://github.com/UniSurreyIoT/fiware-iot-discovery-s2w

http://fiware-iot-discovery-ngsi9.readthedocs.org/en/latest/install/install/index.html

http://fiware-iot-discovery-ngsi9.readthedocs.org/en/latest/user/user/index.html

IoT Data Edge Consolidation

Cepheus

Orange











From: fiware-chapter-leaders-bounces at lists.fiware.org<mailto:fiware-chapter-leaders-bounces at lists.fiware.org> [mailto:fiware-chapter-leaders-bounces at lists.fiware.org] On Behalf Of MIGUEL CARRILLO PACHECO
Sent: Thursday, December 10, 2015 6:44 PM
To: fiware-chapter-leaders at lists.fi-ware.org<mailto:fiware-chapter-leaders at lists.fi-ware.org>
Cc: JUAN JOSE HIERRO SUREDA; fiware-chapter-architects at lists.fi-ware.org<mailto:fiware-chapter-architects at lists.fi-ware.org>; fiware-wg-leaders at lists.fi-ware.org<mailto:fiware-wg-leaders at lists.fi-ware.org>
Subject: [Fiware-chapter-leaders] Template for R4 delivery

Dear all,

It seems that many chapters are about to close the open specs so let us unblock a new chunk of deliverables. It is time to deliver R4 as such.

We have prepared a template to deliver R4. Each chapter leader is expected to fill in a copy and return it to us. The red letters are either instructions (that you will delete before delivering!) or places where we expect your inputs.

This is what I expect from you:

  *   Send me back this template with the deliverable in its final state (something I could deliver to the EC with eyes closed if I did not have the time to review it)
  *   Send me the pdf versions of these manuals per GEri in a single zip files to deliver it jointly with the report:
     *   Installation & Admin Manual
     *   User and Programmers Manual
We will allow Friday for comments if something doesn't make sense in the template or if there are really really serious improvements that we could add. As you see, it is something really light to fill in and we intend to reduce paperwork to a minimum. The deliverable itself is the software! I will make a point of reminding this in the delivery to the EC.

Summary: if there are comments/complaints, please do so before the end of Friday. Complaints later than that may not get too much attention.

Best regards,

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

_________________________________________________________________________________________________________________________



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

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

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

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



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

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

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

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

Thank you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-iot/attachments/20151211/2d4f7e6a/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: guides _fiware-iot-discovery.zip
Type: application/x-zip-compressed
Size: 2887959 bytes
Desc: guides _fiware-iot-discovery.zip
URL: <https://lists.fiware.org/private/fiware-iot/attachments/20151211/2d4f7e6a/attachment.bin>