[Pkg-parrot-devel] New version of parrot package is in mentors
Allison Randal
allison at parrot.org
Sat Apr 9 15:00:49 UTC 2011
On 04/08/2011 12:05 PM, Dominique Dumont wrote:
> No problem. I'd be more comfortable though if I could work with a CVS. This
> would also encourage teamwork.
>
> I wouldn't mind working directly on parrot's CVS, but then you may need to
> give write access to more people than you may want to.
>
> Alioth would probalby be a better place to archive debian package files.
Yes, commit access to Parrot's Git repository requires developer status
in the project. If you'd like to apply, the best way to start is by
subscribing to the mailing list and hanging out on the IRC channel, to
get familiar with the kinds of work Parrot needs help with.
But, it's a good idea to set up source control on the full packages
anyway. I'm happy to grant you access on Alioth to start importing older
packages. I'd prefer Subversion, Bazaar, Mercurial, or Git over CVS,
because of the more modern features. Alioth offers all those options.
Any preferences from anyone here likely to contribute?
While we're at it, we'll need some conventions for how we'll collaborate
on the source control, something like:
http://pkg-perl.alioth.debian.org/subversion.html
If we use Subversion, we could just adopt a simplified version of that
one. Or, if someone wants to draft new conventions, we can talk through
them as a group and decide what works for us.
Allison
More information about the Pkg-parrot-devel
mailing list