[Fwd: Re: [LAD] [LAU] Join the Debian Multimedia Team! (to improve the state of Linux audio)]

[Fabian Greffrath]

> A thought to consider - when I embarked upon creating debian and
> ubuntu packages of my own software, I found very little in the way
> of guides to assist a developer, the guides are focused on
> maintaining someone else's software (often already packaged).
> 
> It can't hurt to educate developers on how to assemble packages for
> their own software, just making them aware of what's required will
> lead to reduced effort to package and the ones who chose to include
> the debian build files in the source shift the maintainer effort to
> quality control type role (hopefully fed back to the developer to
> include).

I don't see a difference between adding a (well maintained) debian/ 
directory to someone else's software or to my own, i.e. if you know 
how to make Debian packages out of sources for package foobar, you are 
also able to prepare the packaging for the softeware you wrote 
yourself. Why should this be documented separately?

Do I miss the point?