Individual Roles

Last modified by Guillaume Sauthier on 2011/02/23 11:15

Disclaimer
The content of this page is a Work in Progress.

Chairman

The Technology Council Chairman is a member of the TC.
He/she is elected by the TC participant for an undefined time (until he/she resign).

His/hers list of duties includes:

  • Lead the discussions about technology vision
  • Make sure that the TC fulfills its role
  • Co-organize meetings with the CTO and the Management Office (MO)
  • Run discussions about the architecture and the adoption of new projects
  • Take care of OW2 code base consistency

The work is typically done in duo with the OW2 CTO.

Election Propaganda emoticon_smile

Be the Chairman of the TC does not take so much time as the operational work can be 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

OW2 CTO

To be completed ...

TC Participant

To be completed ...

See the current list of Technology Council Participants.

Mentor

Work in Progress ...

Mentors are people willing to help to bootstrap incubated projects for beginning their lifes as OW2 projects.
Their help includes technical and community advices.

Volunteering

Each incubated project has to have a mentor.
The mentor is a Technology Council participant, he knows the OW2 community.
Ideally he also knows the applicative domain of the incubated project.

Mentoring is a volunteer move (nobody assign a TC participant to this task).

We need you to volunteer for mentoring new projects.
Please step XXX (need english speaker here emoticon_smile )

Duties

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

On a technical side, he should be able to help the project to setup its infrastructure (OW2 forge, SCM, lists, jabber, ...) as well as providing some architectural/quality guidance (if needed). If he's not able to do things himslef, he should at least know who can effectively help.

Some examples (not exhaustive):

  • Explains multiple accounts of the OW2 jungle infrastructure
  • Describe available services (trackers, SCM, Wikis, ...)
  • Help setup theses services usage
  • Use knowledge of OW2 peoples 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, may augment re-use of code inside of OW2, 

Get Involved

Share technical know how with other users, and help to promote OW2

TC Live

 

 

Powered by XWiki Hosted by Xsalto Free PageRank Checker Creative Commons 2.0 license Legal Notice