|--==> Junichi Uekawa writes:

  >>
  >>The demudi  repository on svn.debian.org is  quite outdated.. Anyway I
  >>usually  import  source packages  with svn-inject   along with the  -o
  >>option, so that we don't keep the whole upstream into SVN. As you say,
  >>working watch files are enough to get the tarball.

  JU> Okay, updating it to be up-to-speed and moving over to it as the
  JU> main development environment might be a way forward.

Then I'll clean up the repository and start injecting all the packages
I handle, both in Debian or not. Packages not in Debian will have "-0"
as a revision number.

  >>>>My original plan   when I've applied  for the  Alioth  project was  to
  >>
  >>Yes, that mailing list  is  quite silent and  needs  a bit of  revamp!
  >>Maybe  we could forward the  commits to it? BTW  I always dreamt about
  >>forming a:h
  >>
  >>Debian Multimedia Team <debian-multimedia <at> lists.debian.org>
  >>
  >>which  would be the  Maintainer of  all (or  most  of) the  multimedia
  >>packages in Debian,  and care about  quality assurance. Bug reports to
  >>shall be reported to the lists and  developers who directly care about
  >>the package  listed  in the Uploaders  field, like   what happens with
  >>debian-boot <at> lists.debian.org does for the d-i packages.

  JU> That would be good. Real names of maintainers should be in the
  JU> Uploaders: field, but using debian-multimedia as a collective place to
  JU> discuss bugs would be cool.

Let's start this  with the packages in  the SVN repository, then we'll
advertise this on the debian-multimedia list.. is it acceptable or are
we trampling toes?

  >>We have    a  registered #demudi  channel   on FreeNode,    but not  a
  >>#debian-multimedia AFAIK, I think someone should register it..
  >>
  >>The #demudi channel is listed in the CIA bot too.

  JU> Okay, I'm not too happy about freenode since it rejects my bot, but we
  JU> can probably work with it.

Ok, anyway feel free to suggest or open a channel on another server.

Cheers,

Free