[pkg-fso-maint] openmoko-panel-plugin v0.5

[Joachim Breitner]

Hi Sebastian,

Debian lists usually don’t modify the Reply-To: header, so I assume you
accidentally sent the mail to me in private. So here it is for all:

Am Mittwoch, den 05.11.2008, 21:23 +0100 schrieb Sebastian Ohl:
> Hi folks,
> 
> i don't find the time to answer last night and now there are so many
> mails... ok let's start to answer some. first thank you for the
> invitation to join the fso team. i would by happy to do so(what do i
> have to do?). to the second part of the discussion: the repository. we
> should agree on using one repository. two are only good to maximize
> confusion(as you can see at the notify discussion). as i only know of
> users on the debian repository, i don't have a problem to switch to
> alioth(at least if chris don't have any problem with this). no one knows
> of the prj.openmoko.org project, so there should not be much confusion.
> and we don't have the problem any more that you can only post bug
> reports by creating a user on prj.openmoko.org. 
> 
> what's your opinion on this case chris?

I’m not too sure if doing upstream work inside pkg-fso is the right
thing to do: E.g. if you want to give commit rights to other people,
they would get commit rights for all of our repositories. But I do think
that we can improve collaboration.

My proposal would be that you, for your upstream development, switch to
git. Your git repository could be hosted on projects.openmoko.org, or
github, or a new alioth project where you are admin, or anywhere else.
This leaves you in full control of your project.

Then we agree on a git scheme that suits both your and our work. We
would have a copy of the git repository inside pkg-fso, so if we need to
do Debian-specific changes, we can do them there (any you can
cherry-pick our patches into your repository again).

All this is independent of whether you want to join us in the sense of
doing package uploads etc. – it’d just be another hat of yours. For
that, you need an alioth account that we can add to the pkg-fso project.
This would give you the chance to do uploads to the pkg-fso repository
yourself. But I’m not sure if that helps a lot: In the short-term, the
package will be in the official Debian repository, so one of us DD would
have to do the upload anyways, and if upstream development happens in a
suitable way, that will simply be a matter of 
# git checkout debian
# git merge upstream/%(version)
# dch -R -v %(version)-1 'New upstream version'
# git commit -m "Tag for release" debian/changelog
# git-buildpackage --git-tag --git-sign-tag
# debrelease


And while I’m at it, here are my ideas for a nice git scheme:

All upstream development is happening in the branch “master”. This
branch does not include the debian/ directory. When you do a release,
you bump the version in setup.py, and tag this as %(version). Then, this
happens (possibly by a script, maybe with help of git-import.orig):
     1. ./setup.py sdist creates the release tarball
     2. The contents of the release tarball (which, in some cases
        differs from the content of the master branch) is put on the
        branch “upstream-dist”
     3. The tarball binary information is saved with “pristine-tar
        commit blubb-1.2.3.tar.gz upstream-dist”
     4. To make the connection,“git checkout upstream-dist; git merge -s
        ours %(version)” is run.
     5. The released data is tagged in a format that suits
        git-buildpackage: “git tag upstream/%(version)”
Now everything is in place to make the Debian packaging a real ease, as
all the tarball handling is already in place. To do an upload to Debian,
one can use the above commands.


Now how does that sound? :-)

Greetings,
Joachim

-- 
Joachim "nomeata" Breitner
Debian Developer
  nomeata at debian.org | ICQ# 74513189 | GPG-Keyid: 4743206C
  JID: nomeata at joachim-breitner.de | http://people.debian.org/~nomeata
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Dies ist ein digital signierter Nachrichtenteil
Url : http://lists.alioth.debian.org/pipermail/pkg-fso-maint/attachments/20081105/6ab20108/attachment.pgp