What does it take to become a committer on ActiveMQ?

classic Classic list List threaded Threaded
8 messages Options
Reply | Threaded
Open this post in threaded view
|

What does it take to become a committer on ActiveMQ?

Bruce Snyder
What do you feel it takes to become a committer on ActiveMQ?

In an effort to identify what is required to become a committer on
ActiveMQ, I have created a wiki page so that we can all collaborate to
create some guidelines:

https://cwiki.apache.org/confluence/display/ACTIVEMQ/How+to+Become+a+Committer+on+the+ActiveMQ+Project

Please contribute your thoughts on this page and let's discuss the matter
on this thread.

Bruce

--
perl -e 'print
unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*" );'

ActiveMQ in Action: http://bit.ly/2je6cQ
Blog: http://bruceblog.org/
Twitter: http://twitter.com/brucesnyder
Reply | Threaded
Open this post in threaded view
|

Re: What does it take to become a committer on ActiveMQ?

chirino
Would participation in issue tracker discussions count toward
'participation in discussions on the ActiveMQ mailing lists'?

On Wed, May 20, 2015 at 11:32 AM, Bruce Snyder <[hidden email]> wrote:

> What do you feel it takes to become a committer on ActiveMQ?
>
> In an effort to identify what is required to become a committer on
> ActiveMQ, I have created a wiki page so that we can all collaborate to
> create some guidelines:
>
> https://cwiki.apache.org/confluence/display/ACTIVEMQ/How+to+Become+a+Committer+on+the+ActiveMQ+Project
>
> Please contribute your thoughts on this page and let's discuss the matter
> on this thread.
>
> Bruce
>
> --
> perl -e 'print
> unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*" );'
>
> ActiveMQ in Action: http://bit.ly/2je6cQ
> Blog: http://bruceblog.org/
> Twitter: http://twitter.com/brucesnyder



--
Hiram Chirino
Engineering | Red Hat, Inc.
[hidden email] | fusesource.com | redhat.com
skype: hiramchirino | twitter: @hiramchirino
Reply | Threaded
Open this post in threaded view
|

Re: What does it take to become a committer on ActiveMQ?

Thiago Kronig
I think it counts. Issue triage and bug reporting should count as
"participating in discussions".

Also, great timing! I want to become a ActiveMQ commiter and a guide truly
helps.

I'm mostly reading the code and proposing some fixes for potential thread
safety issues. Some PRs already were merged, and some I think will land
after 1.0 is released.

Please, tell me how can I be of help.

On Thu, May 21, 2015, 11:30 Hiram Chirino <[hidden email]> wrote:

> Would participation in issue tracker discussions count toward
> 'participation in discussions on the ActiveMQ mailing lists'?
>
> On Wed, May 20, 2015 at 11:32 AM, Bruce Snyder <[hidden email]>
> wrote:
> > What do you feel it takes to become a committer on ActiveMQ?
> >
> > In an effort to identify what is required to become a committer on
> > ActiveMQ, I have created a wiki page so that we can all collaborate to
> > create some guidelines:
> >
> >
> https://cwiki.apache.org/confluence/display/ACTIVEMQ/How+to+Become+a+Committer+on+the+ActiveMQ+Project
> >
> > Please contribute your thoughts on this page and let's discuss the matter
> > on this thread.
> >
> > Bruce
> >
> > --
> > perl -e 'print
> > unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*" );'
> >
> > ActiveMQ in Action: http://bit.ly/2je6cQ
> > Blog: http://bruceblog.org/
> > Twitter: http://twitter.com/brucesnyder
>
>
>
> --
> Hiram Chirino
> Engineering | Red Hat, Inc.
> [hidden email] | fusesource.com | redhat.com
> skype: hiramchirino | twitter: @hiramchirino
>
Reply | Threaded
Open this post in threaded view
|

Re: What does it take to become a committer on ActiveMQ?

gtully
In reply to this post by Bruce Snyder
added willingness to document to the list in the wiki.
discussion on issues or the lists could maybe be pulled into separate points.

I think if you hit any or all of the points you could be a committer.

On 20 May 2015 at 16:32, Bruce Snyder <[hidden email]> wrote:

> What do you feel it takes to become a committer on ActiveMQ?
>
> In an effort to identify what is required to become a committer on
> ActiveMQ, I have created a wiki page so that we can all collaborate to
> create some guidelines:
>
> https://cwiki.apache.org/confluence/display/ACTIVEMQ/How+to+Become+a+Committer+on+the+ActiveMQ+Project
>
> Please contribute your thoughts on this page and let's discuss the matter
> on this thread.
>
> Bruce
>
> --
> perl -e 'print
> unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*" );'
>
> ActiveMQ in Action: http://bit.ly/2je6cQ
> Blog: http://bruceblog.org/
> Twitter: http://twitter.com/brucesnyder
Reply | Threaded
Open this post in threaded view
|

Re: What does it take to become a committer on ActiveMQ?

Bruce Snyder
Agreed, I think what we are circling around here is basically effective
communication (using the available tools).

Also, when offering pull requests, have they created a JIRA issue? Have
they discussed their issue on the mailing list? Etc.

Bruce

On Thu, May 21, 2015 at 9:28 AM, Gary Tully <[hidden email]> wrote:

> added willingness to document to the list in the wiki.
> discussion on issues or the lists could maybe be pulled into separate
> points.
>
> I think if you hit any or all of the points you could be a committer.
>
> On 20 May 2015 at 16:32, Bruce Snyder <[hidden email]> wrote:
> > What do you feel it takes to become a committer on ActiveMQ?
> >
> > In an effort to identify what is required to become a committer on
> > ActiveMQ, I have created a wiki page so that we can all collaborate to
> > create some guidelines:
> >
> >
> https://cwiki.apache.org/confluence/display/ACTIVEMQ/How+to+Become+a+Committer+on+the+ActiveMQ+Project
> >
> > Please contribute your thoughts on this page and let's discuss the matter
> > on this thread.
> >
> > Bruce
> >
> > --
> > perl -e 'print
> > unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*" );'
> >
> > ActiveMQ in Action: http://bit.ly/2je6cQ
> > Blog: http://bruceblog.org/
> > Twitter: http://twitter.com/brucesnyder
>



--
perl -e 'print
unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*" );'

ActiveMQ in Action: http://bit.ly/2je6cQ
Blog: http://bruceblog.org/
Twitter: http://twitter.com/brucesnyder
Reply | Threaded
Open this post in threaded view
|

Re: What does it take to become a committer on ActiveMQ?

clebertsuconic
> Also, when offering pull requests, have they created a JIRA issue? Have
> they discussed their issue on the mailing list? Etc.

Pull requests comments are sent to the dev-list. I don't think we
should enforce discussion on the list before a Pull Request. It's nice
in some cases but that's a case by case I think
Reply | Threaded
Open this post in threaded view
|

Re: What does it take to become a committer on ActiveMQ?

christopher.l.shannon
I usually like to create Jira tickets and submit pull requests for them
without first bringing it up on the dev list. I find it's easier to discuss
the issue directly on Jira after I have a patch already created.  I think
it gives the reviewer a better idea of what I'm trying to accomplish and
they can provide more useful feedback if I've submitted something to
review.  Plus the issue on Jira gets linked automatically with the commit
so it is easy to view later.

I agree with Thiago that having a guide is welcome because I've also been
wondering what is required to become a committer on ActiveMQ.

On Thu, May 21, 2015 at 11:59 AM, Clebert Suconic <[hidden email]
> wrote:

> > Also, when offering pull requests, have they created a JIRA issue? Have
> > they discussed their issue on the mailing list? Etc.
>
> Pull requests comments are sent to the dev-list. I don't think we
> should enforce discussion on the list before a Pull Request. It's nice
> in some cases but that's a case by case I think
>
Reply | Threaded
Open this post in threaded view
|

Re: What does it take to become a committer on ActiveMQ?

jgomes
This is a great discussion for our community to have. I wonder if other
Apache communities have a similar document detailing their guidelines.
Something to keep in mind as we form our guidelines is the overall Apache
view of committers (from https://community.apache.org/contributors/):

Becoming a Committer

There is nothing at The Apache Software Foundation that says you must write
code in order to be a committer. Anyone who is supportive of the community
and works in any of the CoPDoC areas (*Co*mmunity, *P*roject, *Do*cumentation,
*C*ode) is a likely candidate for committership.

Apache is a meritocracy. That is, once someone has contributed sufficiently
to any area of CoPDoC they can be voted in as a committer. *Being a
committer does not mean you commit code, it means you are committed to the
project. (emphasis added)*

One of the key contributions people can make to the community is through
the support of a wide user base by assisting users on the user list,
writing user oriented docs and ensuring the user viewpoint is understood by
all developers. A main idea behind being a committer is the ability to be a
mentor and to work cooperatively with your peers.

Some of those users become committers in their own right. Some will test
code, some will write documentation, some will do bug triage and some will
write code.



On Thu, May 21, 2015 at 9:56 AM Christopher Shannon <
[hidden email]> wrote:

> I usually like to create Jira tickets and submit pull requests for them
> without first bringing it up on the dev list. I find it's easier to discuss
> the issue directly on Jira after I have a patch already created.  I think
> it gives the reviewer a better idea of what I'm trying to accomplish and
> they can provide more useful feedback if I've submitted something to
> review.  Plus the issue on Jira gets linked automatically with the commit
> so it is easy to view later.
>
> I agree with Thiago that having a guide is welcome because I've also been
> wondering what is required to become a committer on ActiveMQ.
>
> On Thu, May 21, 2015 at 11:59 AM, Clebert Suconic <
> [hidden email]
> > wrote:
>
> > > Also, when offering pull requests, have they created a JIRA issue? Have
> > > they discussed their issue on the mailing list? Etc.
> >
> > Pull requests comments are sent to the dev-list. I don't think we
> > should enforce discussion on the list before a Pull Request. It's nice
> > in some cases but that's a case by case I think
> >
>