commit-policy

Jorge Uriarte Aretxaga  wrote.
> I'm crossposting to dev, because the voting should be public :-)

I agree with that.
I just wanted to respect the policy of Scarab - which I thought was voting about new committers in the committers-list.

Because we are right now talking about this topic, how about relaxing the commit-policy:

We could grant commit-access to everyone who requests it.
Interested newcomers would get their own branch, they can immediately commit to.
First a newcomer would only commit into his own branch and a core-committer would decide when to merge into the trunk.
After some of his contributions have made it into the trunk the newcomer himself would become a core-committer.

With this policy the contributions of  newcomers would immediately be under version control.
This is much more convenient for the newcomers as well as the core-committers who are reviewing the contributions.

I don't think that there is a great danger of abuse and even then we have svn for rescue.

As someone stated, Scarab is a low-profile project. That's why the bigger challenge is to attract contributors, instead of preventing them from polluting the product with their personal pet-features (as it may be the case in high-profile projects like the Linux-kernel).

Ronny