On Sat, Feb 23, 2013 at 10:25 AM, Sebastien Goasguen <run...@gmail.com>wrote:
> > On Feb 22, 2013, at 11:30 PM, Jessica Tomechak <jessica.tomec...@gmail.com> > wrote: > > > On Fri, Feb 22, 2013 at 2:45 AM, Joe Brockmeier <j...@zonker.net> wrote: > > > >> On Fri, Feb 22, 2013, at 01:01 AM, Rohit Yadav wrote: > >> > >>> While this is the first time a proposal was made public, I had to > >>> rant, the toughest email I had to write, but anyway you should ignore > >>> it: > >> > >> I'd also point out, this isn't something that we dreamed up specifically > >> for CloudStack - we're following Apache practices here. It's worth > >> researching whether something is CloudStack-specific or an Apache > >> process before holding other folks feet to the fire about the way > >> they're doing things. > >> > >> These are the Apache guidelines for voting on committers: > >> http://community.apache.org/newcommitter.html > >> > >> AFAIK, individual projects (and certainly not incubating projects) are > >> not free to disregard these practices. > >> > >> Best, > >> > >> jzb > >> -- > >> Joe Brockmeier > >> j...@zonker.net > >> Twitter: @jzb > >> http://www.dissociatedpress.net/ > >> > > > > > > Totally agreed about all Animesh's awesome contributions. But I have a > > "this is my first open-source project" question. > > > > I searched Reviewboard and don't see any patches from Animesh. Why would > > someone who doesn't write code need to be a committer? > > > > I read the Apache "committers" docs [1][2] and they mention a few > > "back-office" things committers can do, but they pretty much assume that > > writing code is the main reason to be a committer. > > > > Again: totally agreed about Animesh's awesome contributions. Maybe > Animesh > > has written tons of code for the project which I've overlooked, in which > > case I apologize. I'm still curious about what else committers can do. > > We have voted and posted bylaws for the community: > > https://cwiki.apache.org/CLOUDSTACK/apache-cloudstack-project-bylaws.html > > They define a contributor as: > > "Contributors are all of the volunteers who are contributing time, code, > documentation, or resources to the CloudStack Project. Contributions are > not > just code, but can be any combination of documentation, testing, user > support, > code, code reviews, bug reporting, community organizing, project > marketing, or > numerous other activities that help promote and improve the Apache > CloudStack > project and community." > > And explain that: > > "A Contributor that makes sustained, welcome contributions to the project > may be > invited to become a Committer by the PMC. The invitation will be at the > discretion of a supporting PMC member." > > To summarize, it's not just code. > > -Sebastien > > > > > > [1] http://community.apache.org/committers/index.html > > [2] http://www.apache.org/dev/new-committers-guide.html > > > > Jessica T. > > OK, thanks for the replies. This clarifies that Committer may be more of a vote-of-confidence than anything related to committing code. Still wondering: aside from gaining direct commit permissions on the code repo, what other permissions does an Apache Committer have, if any? This was more the point of my question, "curious about what else committers can do." For example, maybe only Committers can edit certain blogs, or do certain types of configuration on other infrastructure. As I mentioned, the Apache docs refer to some "back-office" tasks that committers can do that non-committers can't, but they do not go into much detail about this. That's the point on which I'm still curious. Maybe, for example, it takes a Committer to update those Apache docs about being a Committer? If this is a question for a different Apache list, please let me know. Jessica T.
