Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "JWT Kickoff Meeting"
| Line 1: | Line 1: | ||
| − | + | == Meeting agenda == | |
| − | == Meeting | + | |
feb the 5th 2007 - TO BE CONFIRMED | feb the 5th 2007 - TO BE CONFIRMED | ||
| − | |||
| Line 14: | Line 12: | ||
* Registered presentations and subjects : Actions / Next step / Dissemination | * Registered presentations and subjects : Actions / Next step / Dissemination | ||
| + | |||
| + | |||
| + | == Meeting announcement == | ||
| + | |||
| + | |||
| + | In this perspective, a telco / Webex (thanks to Tibco) kickoff meeting will be scheduled at the beginning of february. The proposed date is feb. the 5th, and alternate dates would be the 7th and 8th. | ||
| + | |||
| + | Its goals are to help interested parties know each other and discover their respective interests in JWT, be it expertise or solutions in the BPM tooling or BPM standardisation tooling fields, experience of BPM standardisation or genericity problematics on the representation or grammar mapping levels, BPM engines knowledge... | ||
| + | |||
| + | It will consists in three parts : | ||
| + | |||
| + | * general interested parties presentation (including every board member - anybody interested will have talk time). The point is to help foster further collaboration between actors but also fields. 15 minutes max each including questions. | ||
| + | |||
| + | * architecture : anyone having experience in tackling the BPM tooling standardisation and genericity problematics is invited to present & showcase their architecture. The point is to have a starting point for the architectural analysis leading to the specifications. At least 30-40 minutes each. | ||
| + | |||
| + | * actions to be taken : administrative ones, next steps on all levels & dissemination. This last part is very important since JWT is an open source project gathering very different partners. | ||
| + | |||
| + | |||
| + | Kickoff meeting preparation | ||
| + | |||
| + | In order to be as efficient as possible, and since a physical meeting is not possible, the kickoff meeting should be well prepared. That includes : | ||
| + | * anyone interested to attend, please register by answering this email or directly contacting a project lead | ||
| + | |||
| + | * anyone interested to do a presentation, please register by answering this email or directly contacting a project lead | ||
| + | * specify the wanted alloted time, subject and which part of the kickoff meeting it goes in | ||
| + | * please provide the slides in advance so they may be exposed on the wiki for everyone else to read. | ||
| + | |||
| + | Look for new information, upcoming presentations agenda and contributions to the meeting on http://wiki.eclipse.org/index.php/JWT_Kickoff_Meeting . | ||
| + | |||
| + | |||
| + | Best regards, | ||
| + | Marc Dutoo | ||
| + | JWT Project Lead | ||
| + | Open Wide | ||
Revision as of 14:24, 18 January 2007
Meeting agenda
feb the 5th 2007 - TO BE CONFIRMED
Meeting preparation
- Registered people
- Registered presentations : Interested parties
- Registered presentations : Architecture
- Registered presentations and subjects : Actions / Next step / Dissemination
Meeting announcement
In this perspective, a telco / Webex (thanks to Tibco) kickoff meeting will be scheduled at the beginning of february. The proposed date is feb. the 5th, and alternate dates would be the 7th and 8th.
Its goals are to help interested parties know each other and discover their respective interests in JWT, be it expertise or solutions in the BPM tooling or BPM standardisation tooling fields, experience of BPM standardisation or genericity problematics on the representation or grammar mapping levels, BPM engines knowledge...
It will consists in three parts :
* general interested parties presentation (including every board member - anybody interested will have talk time). The point is to help foster further collaboration between actors but also fields. 15 minutes max each including questions.
* architecture : anyone having experience in tackling the BPM tooling standardisation and genericity problematics is invited to present & showcase their architecture. The point is to have a starting point for the architectural analysis leading to the specifications. At least 30-40 minutes each.
* actions to be taken : administrative ones, next steps on all levels & dissemination. This last part is very important since JWT is an open source project gathering very different partners.
Kickoff meeting preparation
In order to be as efficient as possible, and since a physical meeting is not possible, the kickoff meeting should be well prepared. That includes :
* anyone interested to attend, please register by answering this email or directly contacting a project lead
* anyone interested to do a presentation, please register by answering this email or directly contacting a project lead
* specify the wanted alloted time, subject and which part of the kickoff meeting it goes in
* please provide the slides in advance so they may be exposed on the wiki for everyone else to read.
Look for new information, upcoming presentations agenda and contributions to the meeting on http://wiki.eclipse.org/index.php/JWT_Kickoff_Meeting .
Best regards,
Marc Dutoo
JWT Project Lead
Open Wide