[Pkg-javascript-devel] about granting scm commit access to the alioth project

[Emilien Klein]

Hi team,


2014-01-27 Jonas Smedegaard <dr at jones.dk>

> Greetings, fellow Javascript hackers,
>
> Quoting Jonas Smedegaard (2014-01-02 16:29:30)
> > Quoting Jérémy Lal (2014-01-02 13:01:12)
> >> I wonder if there is a minimum official requirement for granting SCM
> >> commit access to newcomers.
> >
> > At most there is "common practice" and of that there is several:
> > Alioth is provided by Debian and has the requirement that its use
> > should be related to Debian, but apart from that we decide on our own
> > how we want to work internally in our team.
> >
> > I like to avoid taking or giving orders from others, and since we use
> > Alioth only as central "hub" for distributed resources (git and
> > mailinglists) I see no need for hierarchy and routinely appoint "super
> > cow powers" to any newcomer to our team.
> >
> > If others insist that we should have hierarchy and distrust newcomers
> > until they somehow prove themselves worthy of higher power, then I
> > will demote myself to the lowest power (and consider leaving the
> > group).
>

That would be very sad, and a big loss to this team. Please don't do that ;)


>
> Noone commented on this part.
>
> Last call: If noone argues to the contrary, I will promote all team
> members to admin status one week from now.
>

I have no issues with this. Benefit of SCM is that you could always revert
to a previous version, if bad stuff were to happen.
The question is what would happen if folks with admin rights would delete
entire repositories. Are they backed up somewhere, to be able to revert the
bad action?

Committing to the SCN doesn't equate being able to upload packages. (see
[0] for an example)


>
>
> > Speaking of which:
> >
> > I have till now mostly used collab-maint instead of our own git area
> > to ease contributions from other Debian members.  Alioth now (since
> > some time) allows any team to grant write access to all official
> > Debian members, similar to the access rights of collab-maint.  Do
> > anyone in this team disagree with enabling that additional right to
> > our git, or is it ok that I enable it (and start move packages from
> > collab-maint to our own git)?
>
> I have now granted all DDs write access to our team git repository.
>
> I will start move packages there that I have previously maintained at
> collab-maint, and suggest others to do the same.
>

If I understand this correctly, we're talking about moving away from doing
our SCM work in collab-maint, but I guess I've missed to where we would be
moving?

Cheers,
   +Emilien

[0]
http://lists.alioth.debian.org/pipermail/pkg-javascript-devel/2013-February/004907.html
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-javascript-devel/attachments/20140129/879a8416/attachment.html>