wrte access to debian documentation project (ddp) etc. (Bug#612011)
Hi, (switching to debian-doc)
On Sat, Feb 05, 2011 at 10:58:56PM +0100, Javier Fernández-Sanguino Peña wrote:
> On Fri, Feb 04, 2011 at 09:45:44AM -0800, Steve Langasek wrote:
> > > I am not sure if I can directly commit as DD or if someone needs to add
> > > needed priviledges.
> > You must be a member of the ddp group on alioth to commit. I'm not sure if
> > the admins have a general policy for granting commit access; I know that
> > most translations are submitted as patches.
> We have a general policy to grant commit access to translators if they are
> going to actively contribute. Actually, most of the translations (fr, de, es, cs, ro,
> ru..) are updated by the translators themselves and only a few (da comes to
> mind) are being submitted as patches to the BTS.
As I said in another post, I have granted write access to Hector.
> Since I believe Hector wants to commit himself to his work it would be best
> if he had direct write access at least to the 'ca' subdir.
Partial write access is not supported. Whoever get write access as a
member of "ddp" on alioth shall have full write acess to all DDP pages.
De facto policy:
* request write acesss in anyway
* private mail to me
* debian-doc mailing list post I happen to notice
* alioth web interface to request access
* I gnerally grant write acesss
* He needs to present me:
* explicit reasons to have write access
* track record or substance of contents
* If translation already have previous commiter, verify and cordinate with him.
* Ask him to use alioth web interface to request access after making
Alioth web interface is at:
Currently, 93 people there.
The admin access are for the following who can add accounts.
| Wolfgang Borgert debacle
| Raphaël Hertzog hertzog
| Javier Fernandez-Sanguino Pen~a jfs
| Josip Rodin joy
| Lucas Nussbaum lucas
| Osamu Aoki osamu
| Pierre Machard pmachard
| Simon Paillard spaillard
I think we need to make account clean up of unused ones (especially
non-DD) after squeeze release.
Also, http://www.debian.org/doc/cvs#obtaining needs to be updated in
line with the practive. I think something about presentation of "track
record" and "explicit rationale" are missing there.
As for some odd activity of copying sources between upstream VCS to DDP,
we need to update build script to make it pull from other VCS too. I
think d-i is good example in which submodules may be pulled from git
repo while main VCS is kept in svn repo. They do this using "mr". That
is for wheezy :-)
Another thing to consider is to make build environment in some kind of
chroot using testing distributon snapshot so we will not suffer issues
such as po4a transition and source will be compatible between package
and web building.