[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[tools-leads] Guidelines for nominating a committer in a Tools sub-project
- From: ERIC CLONINGER <dcp874@xxxxxxxxxxxx>
- Date: Wed, 27 Apr 2011 13:25:55 -0500
- Delivered-to: firstname.lastname@example.org
Sequoyah has recently moved over from the defunct DSDP, so there will
be some learning how things are done "over here".
In DSDP, we had a guideline that we tried to follow before accepting a
new committer. We usually wanted to see at least 3 "quality
contributions" and some assurance that contributions would continue
before nominating someone as a committer. I think the intentions were
good in that we wanted to know someone was willing to support their
contributions and was interested in the future of the project. It
worked differently for sponsoring companies as those entities had a
monetary interest in seeing various Eclipse projects succeed. But
still, we wanted to see that anyone who is adding code into a project
could maintain the expected quality level.
Is there a similar guideline within Tools? Either as an individual or
as an employee of a sponsoring company?
Eric Cloninger (ericc@xxxxxxxxxxxx)
Product Line Manager, MOTODEV Tools
Eclipse Sequoyah Project Lead