[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Giving DDs access to perl-team/modules (was: Alioth -> Salsa)



Quoting Dominic Hargreaves (2020-01-28 22:15:00)
> On Tue, Jan 28, 2020 at 09:58:51AM +0100, Jonas Smedegaard wrote:
> > [ re-posted with 7-bit headers to please Debian MTAs ]
> > 
> > Quoting Norbert Preining (2020-01-27 21:38:10)
> > > On Mon, 27 Jan 2020, gregor herrmann wrote:
> > > > Personally I'm in favour of giving DDs commit access, to allow 
> > > > drive-by fixes and also for symbolic reasons; but I also share 
> > > > Dom's point that people who want to become members / add 
> > > > packages/repos should send a short mail to the list.
> > > 
> > > It would be nice to allow all DD to commit to existing packages, 
> > > but starting new packages would need introduction. That would 
> > > allow as you said "drive-by fixes".
> > 
> > I am in favor of granting all DDs full access.
> > 
> > To me it feels like using a technical appreach for a social purpose 
> > if we block access to encourage more introductions: I doubt it will 
> > help.
> 
> What I meant I wrote what I did back then was not that this policy 
> would encourage more contributors, but that it ensured that 
> contributors were known to the team, and we'd had a chance to point 
> out to them the various team policies and practices to help their 
> learning and reduce the instance of having to correct problems later.

Thanks for the clarification - and sorry for misrepresenting your point!

I can see how requiring explicit membership ensures that everyone with 
access has received our introduction.  I just don't recognize a need for 
it to be mandatory, and I do see us missing out on potential good 
contributions.

Do we have any actual bad experiences with people being a burden by 
"messing" with our repositories without proper guidance?

if what we really want is - as Norbert puts it above - that newcomers 
_should_ send a short mail to the list, then I prefer that we try only 
_encourage_ them to do so without _enforce_ it through access control - 
and then if that turns out to cause burdening experiences only then we 
can revisit the option of requiring explicit membership.


> But my opinion alone on this shouldn't count for muchm as my
> contributions at the perl-team level have dropped off considerably
> recently...

Your point (now that I - hopefully - understand it) makes good sense to 
me, and I appreciate it being brought up - even though I happen to 
agree.

I sure hope that whatever is "distracting" you from spending time here 
is joyful.


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

Attachment: signature.asc
Description: signature


Reply to: