[Debburn-devel] common maintainer mailing list for low-level burning apps and libs

George Danchev danchev at spnet.net
Sat Feb 27 17:17:47 UTC 2010


Simon Huggins writes:
> [debburn-devel cc'd since readers there probably want to know.  Hence
> whole mail left; please trim]
> 
> On Sat, Jan 30, 2010 at 03:26:43PM +0200, George Danchev wrote:
> > Hereby I would like to propose usage of common mailing list
> > (debburn-devel) for all the packages involved in low-level burning and
> > image manipulation process.
> >
> > As of now all they have their lists on alioth, which is somewhat
> > suboptimal in my opinion and there is room to avoid unnecessary
> > subscriptions or searching through several list archives given as
> > maintainer address.
> >
> > Why common list:
> >
> > * most of the low-level burning apps and libraries tend to have common
> > or similar source of problems, so sharing symptoms and diagnosises
> > would be helpful.
> > * some apps (excluding GUIs) reuse or rely on other apps or libraries.
> > * that would help to discuss more closely and eventually alleviate
> > more efficiently the issues during the 'transfer of authority' from cdr*
> > to alternatives.
> > * that would help external packages like GUI frondends which could use
> > more than one low-level app/lib like versatile brasero to find their way
> > in case of not yet clear source of issues concering the lower level.
> >
> > Why debburn-devel:
> >
> > * most of the cdrkit maintainers are already there, so we get their
> > subscription for free.
> > * most of the other packaging lists seems to be unused.
> > * the name seems to be project neutral.
> > * some upstream authors are already subscribed there too.
> >
> > That being said, I see setting Maintainer field of libburn, libisofs,
> > libisoburn, dvd+rw-tools, libcdio (did I miss any low-level app/lib?) to
> > debburn-devel at lists.alioth.debian.org and have their maintainers
> > subscribed there as a useful optimization, which was my motivation to
> > propose this.
> >
> > Other similar suggestions or eventual rebuttals welcome.
> 
> I don't have a problem with moving maintainer addresses onto a common
> list but I suspect what would happen is that there would be a lot more
> noise on the debburn list and that people may unsubscribe.

Let's start with subscription to debburn-devel list first by all burn 
maintainers, so we can tackle bugs like 567056 more efficiently. Note that 
dvd+rw-tools maintainers agreed to merge burning teams.

-- 
pub 4096R/0E4BD0AB <people.fccf.net/danchev/key pgp.mit.edu>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.alioth.debian.org/pipermail/debburn-devel/attachments/20100227/2241844c/attachment.pgp>


More information about the Debburn-devel mailing list