RFH: Perl

[Niko Tyni]

On Mon, Dec 29, 2008 at 06:27:15PM -0500, Guy Hulbert wrote:

> > so you should have commit access soon. Others: please let me know your
> > Alioth username [1] and I'll add you too.
> 
> gh-guest

OK, you're on the member list now. Welcome! 

> >  Things to do off the top of my mind:
> 
>  - team documentation ?

Sure. There's webspace at http://perl.alioth.debian.org/ , or we could
use the Debian wiki. I don't care very much which one we choose; the
Alioth page could be hooked to a git repository which is nice, but the
wiki is probably quicker to get going.

Maybe we should start with a wiki page, and move it to the alioth webspace
later if needed.

> It took me a while to figure out how to set up an Alioth account and I will
> be a further while messing with building from the git checkout.  I like to
> document *everything* so I'm happy to work exclusively on team
> documentation for a while.

That would obviously be great. I'm happy to answer any questions that
come up.

> What do I need to test builds -- is etch sufficient or do I need a sid box ?

A sid environment would be good, that's the development target anyway.
I suppose it doesn't make much difference with bug triage and the like,
but you're not going to be able to install the packages on an etch box.

Using a sid chroot could be a good compromise. You might want to look at
the schroot package, it manages chroots quite nicely.

> >  - come up with a team policy of coordinating uploads and anything
> >  else we need to agree on

Brendan earlier wrote on this:

> My inclination would be to allow any
> of the volunteers to commit to the repository, but to have one person
> responsible for integrating each of the releases.

I think at least announcing uploads a few days in advance would be good,
but we can discuss this once we actually have something to upload :)
-- 
Niko