It means you have commitment to the project. :)
Being a committer is not just about rights to push code, but also provides
other admin rights on resources as well as voting rights (you need to be a
committer to join the PMC, or Project Management Committee) for releases
and for accepting other com
Yes, but the topic was being a committer. If you aren't producing code or
docs, what exactly are you "committing"?
On Wed, Nov 22, 2017 at 12:33 PM, Tal Liron wrote:
> Remember than anybody can be contributor. Becoming a committer,
> specifically, means having privileges to move the project for
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 cod
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 wrote:
> I
Tal,
Thanks for the write up.
-Vish
Sent from my iPhone
On Nov 22, 2017, at 10:45 AM, Tal Liron
mailto:t...@cloudify.co>> 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, bu
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!
Less cumbersome, sure. But it also breaks the object-oriented contract.
Imagine this situation: a third party develops a powerful node type (let's
say: a virtual router) with many well-defined and polished operations on
custom interfaces (with their own types), custom workflows for various
advance
I think keeping the ability to accept ad-hoc inputs (at least for now) is a
good idea =). This will (among other thing) make the job of writing custom
service template less cumbersome. Just mentioning again that this is the
place I see a possible justification for ad-hoc 'additions', as we don't
ha