|JWT Charter [message #23621]
||Mon, 18 December 2006 13:10
| Marc Dutoo
Registered: July 2009
Here is a more formal description of a minimal organisation for JWT.
Feedback is obviously welcome before it goes on the wiki !
Object of the document
This document (the JWT Charter) describes the organisation of the JWT
* JWT abides by the Eclipse Bylaws and general Eclipse project
* Beyond these, hereafter lays the description of the JWT internal
organisation. It aims to provide JWT with a structure that is as light
as may be ni order to allow it to achieve its mission.
[take excerpt from proposal]
The JWT Board consists in the Project Lead and the Advisory Board. The
JWT Board should meet at least every two months to define the
orientation of the project and take decisions that are critical about it.
The JWT Project Leader is in charge of projet management, including
planning, ressource allocation, and release roadmap. He does so in
agreement with the funding organisation and contributors of any kind,
with the assistance of the Advisory Board. For now JWT has two
co-leaders : Florian Lautenbacher of the University of Augsburg, Germany
and Marc Dutoo of Open Wide, France.
The JWT Advisory Board consists in individuals whose experience,
knowledge and position bring the best possible foresight to JWT, in
order to guide evolutions of the project and important decisions. Their
members have a duty of representing the JWT project and its vision for
the BPM tooling field, providing guidance and insight according to their
specialty, advisor title, and / or Project Leader calls for assistance.
The JWT Advisory Board participates to Board Meetings, where it has a
consulting right. For now there are four advisors : * Fabrice Dewasmes
(Vision Advisor) - Pragma Consult * Alain Boulze (Market Advisor) -
INRIA / Objectweb BEING VALIDATED? * Miguel Valdez (Technology Advisor)
- Bull * Günther Palfinger (Technical Advisor) - eMundo GmbH?, Germany
JWT follows the principles of meritocracy to grant commit rights and
responsibilities within the project, meaning that one should have proven
its involvment and its capabilities.
The JWT Core Development Team is composed of all regular comitters. Its
meeting takes place every two weeks (save for exceptional
circumstances), according to a scheduling unanimously approved by its
members, and should be attended by all its members.
JWT funding organisations ...
JWT Contributors consist in individuals and organisation contributing to
the development of the Toolbox. This includes Initial Contributors, and
JWT Partners consist in other organisation and individuals willing to
commit themselves to JWT. Therefore it encompasses funding
organisations, initial contributors, committers and the Board.
Powered by FUDForum
. Page generated in 0.01760 seconds