[news.eclipse.technology.jwt] Workgroups organisation

[Marc Dutoo <marc.dutoo@xxxxxxxxxxx>]

Hi all

Walking in the steps of Florian's email, and after having both of us put 
some thought on it together, I hereafter present to you the organisation 
of work within JWT. Note that obviously nothing is written in stone.

In the following days people in charge of each workgroup will have to be 
chosen, and each workgroup started with some first inputs.

In a side note, thanks Florian for you updated "Next steps" PDF 
document, now available on top of the Kickoff meeting page ( 
http://wiki.eclipse.org/index.php/Image:JWT_NextSteps.pdf ).


Workgroups organisation
=======================
We've defined below a set of workgroups. The idea of a workgroup is
   * to outline the most important work subjects
   * to help everyone focus on meaningful tasks according to the 
project and their own interests
   * to put people in charge - let's not shy away from it : as some 
Greek goddess said it, it's time to "just do it" ;)

How does it work
   * workgroups have a goal pertaining to the JWT project's completion. 
Workgroups have to work on analysing, laying out and developing 
everything pertaining to the subject so this goal is achieved.
   * workgroups have at their head a person in charge, who has to 
animate, track and manage tasks within the workgroup (actually nothing 
more, nothing less than "pushing things forward")
   * workgroups may have subthemes, allowing to track work on different 
subjects
   * special : almost every workgroup has a metamodel theme, which has 
to gather all metamodel wishes, impacts and desideratas produced by 
other workgroups.

Communication
=============
In order to ease discussions on the differents subject, subjects of 
workgroup messages should be prefixed by [<workgroup>] (ex. "[xpdl] What 
about Bonita code").

We'll set up new mailing lists within eclipse.org for dev, users etc. so 
as to be more consistent as an eclipse project.

The wiki must be used to put anything of value to the development team 
or users, such as technical or user documentation, meeting preparation 
and minutes, roadmap etc.

The JWT eclipse newsgroups (eclipse.technology.jwt on the eclipse 
newsgroup server) should be used along with the right mailing list to 
announce meetings, meeting minutes, releases, administrative news etc.


documentation or training sessions
==================================
Some will be useful at some point. For now those are being thought about :
   * On AgilPro architecture and / or model. A document will soon be 
put on the wiki by Florian. It is in german with diagrams and an english 
summary. It will be followed by more information/
   * On development environment and build + how to use it.

Now the workgroups:
===================
Those are the suggested workgroup definitions based on people's 
interests and knowledge. All positions are open, volunteers are welcome 
& don't hesitate to contact us if we don't contact you ;)

   [metamodel] :
Every workgroup has / may submit their analyses and wishes fo it 
according to their own challenges. Here we'd need people responsible for 
gathering impacts and challenges sent by the other workgroups, as well 
as maintaining consistency in the metamodel.
Some discussion themes : comparison with other metamodels.
people : Florian, Etienne (MDA expert), Koen, Marc

   [architecture] :
The point is to gather all the pieces together, write the detailed 
architecture where there is none (ex. WAM), get inputs where there is a 
starting point.
people : Marc, Pardeep (transverse interests), Gunther, Fabrice, Florian

   [xpdl] :
Works toward an XPDL mapping for JWT.
Discussion themes : how to do it, what piece of code to use or not, what 
extensions or changes would be required to the metamodel.
people : Emmanuel and Miguel (novasuite, bonita), Marc, Tim (double 
mapping experience), Roman (XPDL mapping impl) (Koen ???)

   [we] :
discussion themes : list from description in proposal, including about 
the representation model
people : Florian, Koen (jBPM experience), Tim & Wojcheck (interested & 
own tools), Gunther

   [wam] :
Works on the WAM analysis, design and development.
Some discussion themes could be the subAPIs : 1. start engine 2. deploy 
3. mapping & start process etc.
people : Gunther, Pardeep, François Petitit, Goulven Le Jeune (for 
having some genericity on the deployment side), Fabrice, Gunther 
(because of Adapter Framework), Marc

   [scorware] :
Works on subjects pertaining to the JWT - SCOrWare relationship, 
SCOrWare impacts on JWT as well as desideratas.
people : Alain, Marc, Yann and Daniel (Amadeus), Etienne

   [users] :
Gathers all user-oriented point of views and desideratas.
Fabrice, Alain, Marc, Yann and Daniel, Neville Kroeger, Harlad Schubert 
(SAP)

Feedback is welcome !

Best regards
Marc Dutoo
Open Wide