RE: [cdt-dev] Re: [cdt-core-dev] CVS Write access to Hoda

[Sebastien Marineau <sebastien@xxxxxxx>]

> > until we get a clear policy from our fearless leader on who 
> should have
> > commit/not commit.
> >
> 
> The grand pooba will probably say that eclipse is a meritocracy 8-).

We have indeed discussed this a few times in the past. For starters,
here's an extract from the Eclipse tools project charter:

"
Developers who give frequent and valuable contributions to a subproject, 
or component of a subproject (in the case of large subprojects), can have
their status promoted to that of a "Committer" for that subproject 
or component respectively. A Committer has write access to the source code
repository for the associated subproject (or component), and gains 
voting rights allowing them to affect the future of the subproject (or
component).

In order for a Developer to become a Committer, another Committer 
for the subproject (or component) can nominate that Developer or the
Developer can ask for it. Once a Developer is nominated, the 
Committers for the subproject (or component) will vote. If there 
are at least 3 positive votes and no negative votes, the Developer 
is recommended to the PMC for commit privileges. If the PMC approves, 
the Developer is converted into a Committer and given write access 
to the source code repository for that subproject (or component). Becoming 
a Committer is a privilege that is earned by contributing and showing 
discipline and good judgement. It is a responsibility that should be 
neither given nor taken lightly.
"

At CDT project start, we seeded the commiter list with the original set of
people from QNX (along with Doug and John P. from Rational) who were the
leads
in the components. We have adjusted the commiter list slightly since then; 
from now on, however, I'd rather we follow the eclipse philosophy, 
which is to have other contributors submit their patches 
(and have the commiters review/integrate/approve them), and eventually, 
after people have shown good contributions and judgement, nominate 
them for commit access. This is the "eclipse way".

One of the things we have to balance is short-term efficiency in the
acceptance
of contributions (e.g. direct commit access) while maintaining a strong
"unity of design" in the CDT, which can only occur if a small team of 
people get to scrutinize and integrate contributions. I'm particularly 
sensitive to "unity of design" for the CDT core, as it will be the central 
integration point for tools integration.

In any case, my recommendation for now would be to have people send
contributions
and have them earn commit access. One thing which is important is for 
people to send their changes/diffs to the mailing list, so that everyone
can get visibility into the contributions (e.g. it's better for Hoda to
submit diffs to cdt-patch, and then have Doug or Alain integrate them).

My 0.02$ :-)

Sebastien