Invitation to join the Debian Multimedia Maintainers team

[Alessio Treglia]

On Tue, Jun 21, 2011 at 10:36 AM, Jeremy Salwen <jeremysalwen at gmail.com> wrote:
> Alessio, in the workflow you described, the upstream.trunk branch is what I
> was referring to as "intermediate packaging work"
>
> I have an account on alioth (jeremysalwen-guest) and I requested to join the
> team a little while ago, but I haven't been accepted yet.

I've added you, so... welcome aboard! :)

I've already set up both lv2file and so-synth-lv2 repos:
   http://anonscm.debian.org/gitweb/?p=pkg-multimedia/lv2file.git
   http://anonscm.debian.org/gitweb/?p=pkg-multimedia/so-synth-lv2.git

Your "upstream" branches on github have been merged into the
respective UPSTREAM.trunk branches.
To retrieve the code and set up your local copy:

   gbp-clone git+ssh://git.debian.org/git/pkg-multimedia/$PACKAGE.git
   cd $PACKAGE && git fetch origin UPSTREAM.trunk:UPSTREAM.trunk

So now you are able to work as upstream by directly committing your
changes to the UPSTREAM.trunk branches.
When you feel comfortable with a certain state of things, please keep
in mind what follows:

 * Use the capitalized form "UPSTREAM/%(version)s" to mark commits
   in your "trunk" branches in order to avoid conflicts with the
   "upstream/%(version)s" used when importing the new release into
   the upstream branches.
 * After tagging a new release, please create a tarball and follow the
   procedure described in our wiki:

     git-import-orig --pristine-tar ../$(PACKAGE)_$(RELEASE).orig.tar.gz

Please don't forget the --pristine-tar option (which is set by default
in the debian/gbp.conf config file, though), it is needed to avoid
downloading stuff from the Debian archive at build time.
For any question or if you don't like this way, let me know!

Cheers,

-- 
Alessio Treglia          | www.alessiotreglia.com
Debian Developer         | alessio at debian.org
Ubuntu Core Developer    | quadrispro at ubuntu.com
0FEC 59A5 E18E E04F 6D40 593B 45D4 8C7C DCFC 3FD0