librelist archives

« back to archive

Another policy - commit bit

Another policy - commit bit

From:
Carol Nichols
Date:
2012-08-19 @ 16:12
Another policy question, wheee!! Is this what being a Real Open Source
Maintainer is all about???

Who should get commit bit access to the rstat.us repo? I haven't been
adding anyone to the push & pull access team (that only applies to the
hotsh/rstat.us repo), but that hasn't been a conscious decision of mine,
and since we're getting more interest, I'd like to be able to add more
people.

I like rubinius' policy-- once you have one commit accepted, you get your
commit bit [1]. We have travis running, and only Steve, Dom and I have
access to heroku (deploying & database), so I don't really see much damage
that anyone could do.

If we go with this, there are a bunch of people that contributed a long
time ago, but I'm more inclined to start with anyone who has had commits
accepted in the last month and then go forward from there-- that would be
thomaslee, mathias, colindean, valarissa.

[1] - Best explanation I could find is Commit Access section here

http://www.programblings.com/2008/04/15/rubinius-for-the-layman-part-2-how-rubinius-is-friendly/
-Carol

Re: [rstatus] Another policy - commit bit

From:
Stephen Paul Weber
Date:
2012-08-20 @ 14:23
Somebody claiming to be Carol Nichols wrote:
>Who should get commit bit access to the rstat.us repo? I haven't been
>adding anyone to the push & pull access team (that only applies to the
>hotsh/rstat.us repo), but that hasn't been a conscious decision of mine,
>and since we're getting more interest, I'd like to be able to add more
>people.

I always say, with git, only one person should have push access to any repo.  
However, some projects don't like to work that way, and that's fine.  
I would certainly reccomend keeping the number low.  Pull requests are 
awesome.

-- 
Stephen Paul Weber, @singpolyma
See <http://singpolyma.net> for how I prefer to be contacted
edition right joseph

Re: [rstatus] Another policy - commit bit

From:
Steve Klabnik
Date:
2012-08-19 @ 18:09
I personally do the rbx thing for all my repos now. People have commented
that they feel like a true part of a team.

On Sunday, August 19, 2012, Carol Nichols wrote:

> Another policy question, wheee!! Is this what being a Real Open Source
> Maintainer is all about???
>
> Who should get commit bit access to the rstat.us repo? I haven't been
> adding anyone to the push & pull access team (that only applies to the
> hotsh/rstat.us repo), but that hasn't been a conscious decision of mine,
> and since we're getting more interest, I'd like to be able to add more
> people.
>
> I like rubinius' policy-- once you have one commit accepted, you get your
> commit bit [1]. We have travis running, and only Steve, Dom and I have
> access to heroku (deploying & database), so I don't really see much damage
> that anyone could do.
>
> If we go with this, there are a bunch of people that contributed a long
> time ago, but I'm more inclined to start with anyone who has had commits
> accepted in the last month and then go forward from there-- that would be
> thomaslee, mathias, colindean, valarissa.
>
> [1] - Best explanation I could find is Commit Access section here
> 
http://www.programblings.com/2008/04/15/rubinius-for-the-layman-part-2-how-rubinius-is-friendly/
> -Carol
>

Re: [rstatus] Another policy - commit bit

From:
Steve Klabnik
Date:
2012-08-19 @ 17:48
I personally do the rbx thing for all my repos now. People have commented
that they feel like a true part of a team.

On Sunday, August 19, 2012, Carol Nichols wrote:

> Another policy question, wheee!! Is this what being a Real Open Source
> Maintainer is all about???
>
> Who should get commit bit access to the rstat.us repo? I haven't been
> adding anyone to the push & pull access team (that only applies to the
> hotsh/rstat.us repo), but that hasn't been a conscious decision of mine,
> and since we're getting more interest, I'd like to be able to add more
> people.
>
> I like rubinius' policy-- once you have one commit accepted, you get your
> commit bit [1]. We have travis running, and only Steve, Dom and I have
> access to heroku (deploying & database), so I don't really see much damage
> that anyone could do.
>
> If we go with this, there are a bunch of people that contributed a long
> time ago, but I'm more inclined to start with anyone who has had commits
> accepted in the last month and then go forward from there-- that would be
> thomaslee, mathias, colindean, valarissa.
>
> [1] - Best explanation I could find is Commit Access section here
> 
http://www.programblings.com/2008/04/15/rubinius-for-the-layman-part-2-how-rubinius-is-friendly/
> -Carol
>

Re: [rstatus] Another policy - commit bit

From:
Colin Dean
Date:
2012-08-19 @ 18:08
I think it's a good policy.

In the interest of code reviews, I'll probably not yet merge things into 
master unless they are inconsequential (docs, typos, etc.) or translations
(having commit access for that will make me a whole lot less annoying once
the i18n/l10n stuff is in). 

-- 
Colin Dean
cad@cad.cx


On Sunday, August 19, 2012 at 1:48 PM, Steve Klabnik wrote:

> I personally do the rbx thing for all my repos now. People have 
commented that they feel like a true part of a team.
> 
> On Sunday, August 19, 2012, Carol Nichols wrote:
> > Another policy question, wheee!! Is this what being a Real Open Source
Maintainer is all about??? 
> > 
> > Who should get commit bit access to the rstat.us (http://rstat.us) 
repo? I haven't been adding anyone to the push & pull access team (that 
only applies to the hotsh/rstat.us (http://rstat.us) repo), but that 
hasn't been a conscious decision of mine, and since we're getting more 
interest, I'd like to be able to add more people.
> > 
> > I like rubinius' policy-- once you have one commit accepted, you get 
your commit bit [1]. We have travis running, and only Steve, Dom and I 
have access to heroku (deploying & database), so I don't really see much 
damage that anyone could do.
> > 
> > If we go with this, there are a bunch of people that contributed a 
long time ago, but I'm more inclined to start with anyone who has had 
commits accepted in the last month and then go forward from there-- that 
would be thomaslee, mathias, colindean, valarissa.
> > 
> > [1] - Best explanation I could find is Commit Access section here 
http://www.programblings.com/2008/04/15/rubinius-for-the-layman-part-2-how-rubinius-is-friendly/
> > -Carol