Project submission


Submitting a new project

New projects can be submitted from the project submission page.

The proposal is then debated on the Technology Council mailing list and/or on the issue created in technology council project on GitLab.
The technology council evaluates its relevance for OW2 according to the evaluation criteria. The Technology Council must reach a consensus to adopt the project.

Criteria

The fully executed Individual membership of the project leader is the minimum membership requirement for a project to be accepted in incubation. For projects which are developed commercially by a company, the company is expected to get at least the OW2 Corporate Membership.

in terms of complementarities, synergies, license, support, etc

Criteria for rejection are :

  • No Website
  • No mailing list or communication channel
  • No visible community
  • No licence
  • No case studies
  • VCS repository with low activity (can mean a dead project or not very used)
  • or other that happen during the discussion with the future applicant

Project acceptance discussion

When a new project is submitted, the CTO starts a new thread ([discuss] Project Proposal: XXX) that links to the proposal page on the projects site. This thread and the GitLab issue should be used to discuss and comment on the proposal (before any vote).
This thread should also be used for potential mentors to volunteer. The TC should try and discuss the project proposal within 2 weeks.

When the discussion runs out, the vote for the project acceptance can start.

Vote

Vote period

The vote is open for a pre-defined amount of time - currently one week - that has to be clearly written in the vote thread.

The vote options are +1, 0 or -1.

  • +1 means I'm OK with the proposal
  •  0 means I don't care
  • -1 means I'm opposed to the proposal (veto)

Veto

The veto vote must be argued based on criteria defined above: we must know what is wrong and why we should stop the vote (any -1 without proper explanations will be ignored).

As soon a a veto has been given, the vote is stopped up to a week starting from the moment the objection is raised, and the applicant has to answer the objections before the vote is started again.

All the objections are raised and send to the vote mailing list, the applicant has one week to answer them.

If they are not answered satisfyingly the vote is stopped and the project is rejected.

Result

An option that obtains the majority+1 of casted votes will be chosen.
Ex: if there are 10 participants, the elected option must have at least 6 casted votes ( (10/2) + 1 ).

The results will be announced on the TC list as soon as possible.

Rejections templates

Possibility of asking again for inclusion

The project is rejected for the following reasons {}
What we have evaluated {}
What you can do about it {}

Rejected definitively

The project is rejected for the following reasons {}
What we have evaluated {}

Thanks for submitting to OW2

Examples

The vote manager (usually CTO or TC Chairman) should start a new thread on TC list with an explicit subject: [vote] <topic>.

Examples of VOTE subjects
[VOTE] Maturation Lifecycle Criteria
[VOTE] Accept New Project : CONTRAIL
[VOTE] Archive Project : Funambol

Example of vote mail content:

The vote is to decide if we accept the project in the OW2 code base.
The proposal is available at ...
[ ] +1 Use this set of criteria
[ ]  0 Don't care
[ ] -1 Veto, do not change anything (must be argued)

Example of result mail:

  • subject [VOTE][RESULT] <topic>
  • content example
We've got 21 +1 and no other votes casted.
The project is accepted in the code base.

+1 Florent Benoit, Christophe Hamerling, Guillaume Sauthier,
   Jacques Cayuela, Marc Dutoo, Junfeng ZHAO (Anne), Petr Tuma,
   Benoit Pelletier, Stefano Scamuzzo

0  No votes

-1 No votes

Thank you all for your involvement.