[One-project-devel] ONE Software Roadmap and milestones

[Pierfranco F. <pfe...@so...>]

Dear partners,

we are approaching two strategic milestones in the short term:

- San Gallen Student Workshop	[due 17th June 2008]
- Coop Service Users I Trial	[due 10th July 2008]

To this extend we have defined another technical meeting:
6th Technical Meeting [due 9th June 2008], the venue might be Girona.
PLEASE HERE UNISG CONFIRM AVAILABILITY and ALL PARTERS PLEASE CONFIRM
ATTENDANCY with all the persons attending![1] In the campus we need to 
have complete access the the resources of our laptops inside the lan: 
please UNIG comfirm this.

We have to commit to our duties because in the 6th technical meeting we
HAVE TO IMPLEMENT the *FULL ROUND* implementation of a negotiation
model! This was the goal of this just past meeting by CS and we failed,
next time we can not miss this goal, users have to execute the entire
platform! In the remaining few weeks, about a month, we will provide FIX 
and stability.

Not mentioning that we have also to startup the testing environment: we 
need a ONE Node in CN with all the components deployed.

The ONE platform will not be terminated by June because we will have
about another 7 months to go for the II Trial [due March 2009], for this
reason we have to decide *now* WHICH features will be available and
WHEN! This is extremely important and key for the success, we have to
sync our efforts.

For this reason I'm asking all the development partners to provide me a
list of the *features* they will support for their components and *when*
in association with a specific *version*: I'm expecting a major version
release each month for each of you. This roadmap is to be continued
'till December 2008 when all the features are to be finished.

This effort was already defined in the wiki in
http://one-project.sourceforge.net/wiki/index.php/Project_Phases since
more then a year ago, but was not considered and left empty and 
"unfortunately" not followed by partners. This time I'm asking to 
provide ME such a features list with milestones. Failing on doing this 
will probably result in jeopardizing the integration of the project and 
the fail in demonstrating the platform and the entire project as a 
consequence.

For each partner I need a list of components' name, version, features 
list and the expected delivery date: delivery means actual deployment in 
the test environment. I'm attaching here a first draft version, the list 
   does not assume to be complete: please integrate as required!

Again, as kindly asked in the past, _*PLEASE*_ do apply the ONE standard 
for versioning and dependency in the first software release. Apply this 
to Maven in SF.

Please make sure each of you (proactively) follow up the content of the 
mail and the associated actions, this letter must not be a dead end by 
any of you,

best
Pierfranco

[1] http://www.doodle.ch/bkma9f5wf6bt7yuy