Multimedia Teams in Debian

[Free Ekanayaka]

Hi,

|--==> On Fri, 28 Nov 2008 18:47:54 +0100, Loïc Minier <lool at dooz.org> said:

  LM> On Fri, Nov 28, 2008, Free Ekanayaka wrote:
  >>demudi has already a repo on git.debian.org, and I prefer it over
  >>collab-maint because the latter is writable only by DDs (for non-DDs
  >>you have to ask for write permission on case-by-case basis), while the
  >>former is writable by all the members of the relevant Alioth project,
  >>DDs or not.

  LM>  That doesn't make any sense to me:
  LM>  - demudi:       non-DD have to ask, DD have to ask
  LM>  - collab-maint: non-DD have to ask, DD don't

  LM>  Besides, you ask only once for collab-maint membership, but it's not
  LM>  only about multimedia packages.

But in case of demudi (or whatever alioth project we choose) we have
direct control on the project members, this avoids having to ask every
time, we can do it ourselves. Furthermore we avoid giving write
permission to the whole collab-maint tree to any contributor of our
project.

  >>I would like to have a git branch for these patches as well, but we
  >>might want to make this optional. For very small patches it is
  >>probably overkill.

  LM>  Please, no; you can create the patches from local git branches when you
  LM>  prepare them, but it doesn't make sense if we export branches to
  LM>  patches because what we might receive are ... updated patches.

  >>As said, I would stick to the git-buildpackage standards, that means a
  >>git branch for upstream sources, which can get imported with
  >>git-import-orig

  LM>  Sounds right!

We would still be compliant with the git-buildpackage standards, but
we would simply have more branches than only master and upstream.

In any case if exporting patch branches does not sound good, I can
keep them in my private repository only, that's the beauty of git :)

Ciao!

Free