[Fiware-wpa] Submission of chapters for the first complete integration of FI-WARE High-level description deliverable

[Juanjo Hierro]

Hi all,

  I would kindly ask you to follow the conventions I explained in my email on June 13 ...


 *   Don't create additional entries to the one that already exist ... you should locate your entry navigating across the Admin pages of the docman system.   When you are at your entry, you should find something like:

[cid:part1.08080305.05030602 at tid.es]


Then, you should upload the new version of your file (which should follow the naming conventions defined) by filling the field "OPTIONAL: Upload new file".    PLEASE, DON'T CHANGE THE OTHER FIELDS.   The field name convention should not be used to change the fields in the "Document Title" and the "Description" fields of the form.


 *   I will delete those entries that I believe are out of date.

  Thanks and best regards,

-- Juanjo


3. Some administrative/management details.

  We will keep the docman system as the way to share versions of the different contributions as well as consolidated releases of the final deliverable at least until June 22.   I want to let you know that we already have SVN (Subversion) available in FusionForge, but I guess it doesn't make sense to migrate right now but keep going until we get this first deliverable finished.    Later, we may migrate to SVN.

  We will keep sharing the contributions in the contribs folder linked to deliverable D.2.2 in the docman system under the FI-WARE project in FusionForge.   However, I will today change the name of the entries in that folder to get something harmonized.    From then on, I expect that all new releases of a given contrib will be uploaded under the assigned entry.  This should be done by going to the Admin interface, then navigating to the entry in question and updating the file assigned to the entry.   You should then assign a name to your contributed file which follows the following name convention:

  "FI-WARE High-level Desc <chapter-name> v<major>.<minor> <date in US format when doc is released> valid until <date in US format when doc will again be blocked for editing a new version>.doc"

 where:

 *   <chapter-name> is a name from the following list:
    *   "Apps" (WP3)
    *   "Cloud" (WP4)
    *   "IoT" (WP5)
    *   "Data" (WP6)
    *   "I2ND" (WP7)
    *   "Security" (WP8)
 *   v<major>.<minor> is the numbering of the version you assign to your contribution (e.g., v1.0 or v5.3)
 *   <date in US format when doc is relased> is the date in which you have closed the edition of the file: (e.g., June 20, 2011 would be "11-06-20").
 *   <date in US format when doc will again be blocked for editing a new version> is the date at which you plan to download the document again and you plan to start editing it again.   If not specified, we will assume you expect to download a new release for editing "the next day (tomorrow) at 09:00am".

  (note: major and minor numbers are not reset when you change the date of a release.   They should be absolute.)

  As an example, you may upload "FI-WARE High-level Desc Cloud v3.2 11-06-18 valid until 11-06-20.doc"

  That file would mean that it is v3.2 of your chapter, released on June 18, 2011.  It will also mean that you don't plan to resume editing of it until June 20, 2011.

  As explained in a previous mail, you should upload new releases of the document (if you have some) no later than 19:00 and, PLEASE, if you have introduced some change in the document, no matter how minor they are, you should update the document in the server at 19:00 and do not touch it until 09:00am the following day.    Besides, you should always download the version that is on the server whenever you plan to start editing your chapter.   Please declare a <date in US format when doc will again be blocked for editing a new version> if you rather don't plan to edit the document the day after.   This would allow Thomas and me to have more time to review it, not just during nights :-)





________________________________
Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo.
This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at.
http://www.tid.es/ES/PAGINAS/disclaimer.aspx
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-wpa/attachments/20110622/b0f3b734/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 74761 bytes
Desc: not available
URL: <https://lists.fiware.org/private/fiware-wpa/attachments/20110622/b0f3b734/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jhierro.vcf
Type: text/x-vcard
Size: 429 bytes
Desc: not available
URL: <https://lists.fiware.org/private/fiware-wpa/attachments/20110622/b0f3b734/attachment.vcf>