Hi All,
As you can read below, the urgent need to provide potential FIWARE users
with coherent and clean documentation that is compliant with released
software has arise.
Basically, the central administration agreed to make procedures more
lightweight in order to provide better results in less time.
Practically speaking, the whole process private wiki ->public wiki has
been revised. It will not be the chapter leader anymore the person who
edits the public wiki with contents taken from the private wiki.
As said below:
Those partners with GEris to be published on the catalogue (those at
https://docs.google.com/spreadsheet/ccc?key=0AqGGeaQGro3fdG83Y0dQVEFKSHFYWmtXdlpEdnVpaXc&usp=sharing#gid=0)
must ensure consistency with the latest release delivered:
* Ensure that the latest version is available in a repository clearly
linked from the catalogue in the Downloads tab(Files, github or
whatever you use)
* Update the Installation and admin manual on the public wiki directly
and make sure that it is referred from the catalogue
* Update the User & Programmer manual on the public wiki directly and
make sure that it is referred from the catalogue
* Update the Unit Testing Plan manual on the public wiki directly and
make sure that it is referred from the catalogue
* Update the FIWARE Lab recipes, images, etc. if needed
* Update the FIWARE Academy courses (http://edu.fi-ware.org/) if needed
From now on, updating the software means updating everything and
keeping it in perfect synchrony. It can be done anytime, at the end of
every Sprint or even in its middle (e.g., due to a hot patch it is
urgent to publish). The manuals and info must correspond to the same
release always. To avoid temporary inconsistencies, we ask you to
prepare everything offline in the most suitable repository in each
case(word, private wiki, etc.) and port it all in one go to the all the
repositories.
I suggest in the Apps chapter we add to the above described procedure
another step, that is:
* Inform the chapter leader and architect (me and Javier) of what has
been updated.
I am considering keeping track of these changes elsewhere than an email,
but let's see how often this happens.
The important point is to remember that consistency of SW and
documentation is now up to each GE owner. I will supervise these actions
but please consider that you know what you are editing.
Thanks in advance for your help!
Best,
alessandra
-------- Messaggio Inoltrato --------
Oggetto: [Fiware] Synchronizing all the GEri related materials
Data: Fri, 3 Oct 2014 07:59:28 +0200
Mittente: Juanjo Hierro <juanjose.hierro at telefonica.com>
A: fiware at lists.fi-ware.eu <fiware at lists.fi-ware.eu>,
fiware-chapter-architects at lists.fi-ware.org,
fiware-chapter-leaders at lists.fi-ware.org
Dear all,
It seems that our repositories are not always well aligned and part
of this is caused by the lack of flexibility in the procedures. We have
decided to give it a push by relaxing the current work procedure.
This was triggered by finding that some partners have new versions of
code (R3.4 , for instance) and the manuals were the old ones for R3.3.
Those partners with GEris to be published on the catalogue (those on
[1]) must ensure consistency with the latest release delivered:
* Ensure that the latest version is available in a repository clearly
linked from the catalogue in the Downloads tab(Files, github or
whatever you use)
* Update the Installation and admin manual on the public wiki directly
and make sure that it is referred from the catalogue
* Update the User & Programmer manual on the public wiki directly and
make sure that it is referred from the catalogue
* Update the Unit Testing Plan manual on the public wiki directly and
make sure that it is referred from the catalogue
* Update the FIWARE Lab recipes, images, etc. if needed
* Update the FIWARE Academy courses (http://edu.fi-ware.org/) if needed
The only step on which we will keep applying supervision is
publication of VM images, deployment recipes, etc. on FIWARE Lab.
The catalogue has a workflow that still implies approvals of edited
entries but Stefano will try to swiftly approve your edits until we
implement a more agile workflow (under definition).
From now on, updating the software means updating everything and
keeping it in perfect synchrony. It can be done anytime, at the end of
every Sprint or even in its middle (e.g., due to a hot patch it is
urgent to publish). The manuals and info must correspond to the same
release always. To avoid temporary inconsistencies, we ask you to
prepare everything offline in the most suitable repository in each
case(word, private wiki, etc.) and port it all in one go to the all the
repositories.
The Security chapter is still backdated (in R2) and R3 will be ported
to the public wiki by Thales shortly. You will have to internally
coordinate in Security to publish all your stuff in an orderly fashion.
Note that with all these measures we are giving you a lot of
empowerment. We will implement a methodology that will mean that such
empowerment will remain for those partners who show they are reliable.
However, a given FIWARE GEri owner or even a complete chapter may loose
this empowerment and it will be put in quarantine (i.e., activities
under close supervision and strict approval procedures) if it is find
out that general rules, templates, etc are not followed or provided
content is not of enough good quality.
Best regards,
Miguel and Juanjo
[1]
https://docs.google.com/spreadsheet/ccc?key=0AqGGeaQGro3fdG83Y0dQVEFKSHFYWmtXdlpEdnVpaXc&usp=sharing#gid=0
------------------------------------------------------------------------
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
--
--
*Alessandra Toninelli*
SpagoBI Consultant
*SpagoBI Labs
Engineering Group*
Via Marconi 10 - 40122 Bologna - Italy
Tel. + 39 051 0435300
Mob. +39 345 7720205
Skype: alessandra.toninelli.eng
www.spagobi.org <http://www.spagobi.org> - www.eng.it
<http://www.eng.it/web/eng_en/home>
Respect the environment. Please don't print this e-mail unless you
really need to.
The information transmitted is intended only for the person or entity to
which it is addressed and may contain confidential and/or privileged
material. Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by persons or
entities other than the intended recipient is prohibited. If you
received this in error, please contact the sender and delete the
material from any computer.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-apps/attachments/20141003/a3fb5e21/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: spagobi.png
Type: image/png
Size: 3639 bytes
Desc: not available
URL: <https://lists.fiware.org/private/fiware-apps/attachments/20141003/a3fb5e21/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image006.jpg
Type: image/jpeg
Size: 1379 bytes
Desc: not available
URL: <https://lists.fiware.org/private/fiware-apps/attachments/20141003/a3fb5e21/attachment.jpg>
-------------- next part --------------
_______________________________________________
Fiware mailing list
Fiware at lists.fi-ware.org
https://lists.fi-ware.org/listinfo/fiware
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy