Remember than anybody can be contributor. Becoming a committer, specifically, means having privileges to move the project forward according to the agreed-upon roadmap. I personally think there's a lot more to that than just being a Python coder, which is why I personally don't necessarily value code contributions over others. AriaTosca has implications regarding standards bodies and industry reach of TOSCA that go beyond the project's mere technical value. I'm in favor of keeping the various aspects of the list equally important.
In the end the list is just a set of guidelines. Current committers get to vote for accepting new committers, and there can be discussion (on the private@ mailing list) regarding individual candidates. On Wed, Nov 22, 2017 at 1:23 PM, DeWayne Filppi <[email protected]> wrote: > Looks good. I'd only say that it's item 1 and/or item 2, plus bonus points > for things in the rest of the list. If all you provide is amazing code > contributions, that should be sufficient. Also, if it's an election that > should be mentioned. > > On Wed, Nov 22, 2017 at 8:45 AM, Tal Liron <[email protected]> wrote: > > > I've written up a list of requirements: > > > > https://cwiki.apache.org/confluence/display/ARIATOSCA/ > Becoming+a+Committer > > > > It's up to the committers to define this list, but would be happy to get > > feedback from non-committers, too! > > >
