Individual Roles

The content of this page is a work in progress.

Chairman

The Technology Council Chair is a member of the TC. He/she is elected by the TC participants for an undefined time (until he/she resigns).

An important figure at OW2, the TC Chair represents the community of project leaders. In that capacity, the TC Chair: 

  • leads technical discussion aimed at evolving the OW2 code base and maintaining it up-to-date and consistant,
  • ensures the TC provides guidance to the CTO and the OW2 Management Office with regard to the technical infrastructure and the quality program,
  • drives the project lifecycle management process including incubation to mature upgrades and project archiving,
  • if necessary, helps settle conflicts between projects or resolve discussions that may arise from new project proposals. 

The TC Chair supports the OW2 CTO in:

  • the organization of TC meetings,
  • the technical representation of OW2,
  • technical outreach to other communities.

Election

Being the TC Chairman does not take too much time as the operational work is mainly driven by the MO.

We need you as a candidate:

  • if you are one of the enthusiastic members of the TC
  • if you like the OW2 consortium and want to contribute to its success
  • if you want to help the projects by pushing new tools in the OW2 Forge
  • if you want to help define and promote a common architecture vision

CTO

The OW2 CTO is appointed by the Management Office:

  • Defines the Consortium's general strategy for its technology infrastructure.
  • Organizes the Technology Council meetings.
  • Drives the Project selection process.
  • Monitors Projects' lifecycle.
  • Works with the Technology Council on the drafting and implementation of required policies to guarantee code base consistency.
  • Helps improve developer resources.
  • Helps solve conflicts between projects when necessary.
  • Provides technology guidance to Initiatives when necessary.
  • Helps foster community activity on the forums.
  • Is the MO interface with the developer community.

Member

Any project leader has the right to (and should) be part of the Technology Council.

However, not only project leaders are authorized in this group: the Technology Council may invite OW2 individuals for special occasions (particular skills for example, or community involvement). See the current list of Technology Council Participants.

Involvement Evolution

In the event where project leadership changes, or a project leader has no more time to give to the TC, it is the responsibility of the project leader to nominate their successor and advertise the nomination (either with a public mail on the list or by contacting TC Chairman or OW2 CTO).

Mentor

Mentors are Technology Council members willing to help bootstrap incubated projects beginning their life as OW2 projects.
Their help includes technical and community advice.

Please see the list of OW2 Mentors.

Volunteering

Each incubated project is required to have a mentor. The mentor must be a Technology Council participant, as they know the OW2 community. Ideally, the mentor also knows the applicative domain of the incubated project. Mentoring is a volunteer move (nobody assigns a particular TC participant to this task).

Duties

A mentor's duty to the incubated project are multiple.

On the technical side, the mentor should be able to help the project setup its infrastructure (OW2 forge, SCM, lists, jabber, ...) as well as providing some architectural/quality guidance (if needed). If the mentor is unable to do these things himself, he should at least know who can effectively help. Some examples (not exhaustive):

  • Explain multiple accounts of the OW2 jungle infrastructure
  • Describe available services (trackers, SCM, Wikis, ...)
  • Help setup services usage
  • Use knowledge of OW2 community to ask the right question to the right person

On a community oriented side, the mentor should be able to provide a bridge between the incubated project and other existing OW2 projects. This will help to foster collaboration between projects, augment the re-use of code inside OW2, and connect people together for innovations. Some examples (not exhaustive):

  • Connect people from incubated project to OW2 project with whom they may have synergy
  • Improve code sharing, do not re-invent the wheel (because the mentor knows of the existence of re-usable code)