> You can join the collab-maint group following the procedure at [0]. Basically > you need an account on alioth.debian.org, send a request to join the group and > then tell me so I can support your request.
Alioth account created (thomaslee-guest) & collab-maint request sent. Can I trouble you with the next step below? ---- Ask a DM or DD, with whom you are going to work, to send a *signed* email to n...@debian.org saying "Please accept the request of FIRSTNAME LASTNAME USERNAME-guest to join collab-maint. We are going to work together on project PROJECTNAME".>> ---- > The usual procedure would be to upload those packages somewhere like > mentors.debian.net, but I prefer to work directly from git, so, when you are > done you ping me and I'll review the modifications directly via git, and build > and upload the package if everything is ok. That sounds great. I'm somewhat familiar with git-buildpackage, but I'll take a look at pbuilder too. Thanks again! Cheers, Tom On Sun, Oct 21, 2012 at 8:29 AM, Alessandro Ghedini <al3x...@gmail.com> wrote: > On 10/20, Tom Lee wrote: >> I'll attempt to update this bug to reflect its ITA status, though I'm not >> sure >> if permissions on the bug tracker will prevent me from doing that. I'll nudge >> this ticket again if it seems like I can't. Once that's done, I'll check out >> the code from git & update the control file etc. > > There are no restrictions in using the BTS, so you can go ahead without > problems. > >> I'm assuming I won't have access to push to that repository even after I take >> over as maintainer, correct? Is it typical for somebody in my position to >> continue maintaining the package using third-party infrastructure (e.g. >> github)? If so, I'll update the Vcs-* fields, too. > > You can join the collab-maint group following the procedure at [0]. Basically > you need an account on alioth.debian.org, send a request to join the group and > then tell me so I can support your request. > >> Last of all, you mentioned that you're willing to sponsor uploads. I guess I >> can just build new packages & put them up somewhere, then ping you when >> there's something that needs your attention? > > The usual procedure would be to upload those packages somewhere like > mentors.debian.net, but I prefer to work directly from git, so, when you are > done you ping me and I'll review the modifications directly via git, and build > and upload the package if everything is ok. > > As for the git part, you may want to have a look at the git-buildpackage > package > which provides a few tools to help in the maintainance of packages using git. > There's a nice manual at [1]. > > Another tool you may want to look into is pbuilder [2] which can be used in > conjunction with git-buildpackage. I think they are both covered in the New > Maintainer's Guide somewhere. > > Cheers > > [0] https://lists.debian.org/debian-devel-announce/2012/01/msg00006.html > [1] http://honk.sigxcpu.org/projects/git-buildpackage/manual-html/gbp.html > [2] http://www.netfort.gr.jp/~dancer/software/pbuilder-doc/pbuilder-doc.html > > -- > perl -E '$_=q;$/= @{[@_]};and s;\S+;<inidehG ordnasselA>;eg;say~~reverse' -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
