On Sun, Mar 13, 2011 at 11:11:05AM +0100, Raphael Hertzog wrote: > Hi Bill, > > On Sun, 13 Mar 2011, Bill Allombert wrote: > > As the name imply, this a reference document, not a prescriptive document. > > It should > > provide technical answer to technical question. Fundamentally it only > > provides advices. > > Patronizing would be bad form. > > Please be specific, can you tell me where in the latest patch there's > "patronizing" in action?
Please be specific: where did I claim that ? But in anycase, I do not think that statement like << As a package maintainer, you're supposed to fulfill the Debian Social Contract by providing high-quality packages that are well integrated in the system and that adhere to the Debian Policy. >> belong to devref. > Note that the whole "developer duties" chapter is not new. I'm not > introducing it. And the purpose of the developers-reference has always > been broader than "technical answer to technical question". We have always > had explanations of procedures of how to interact with various teams and > the associated expectations put on the maintainer. People always have been free to ignore the devref and always have done so, which was a good thing given it used to be outdated. Cheers, -- Bill. <ballo...@debian.org> Imagine a large red swirl here. -- To UNSUBSCRIBE, email to debian-policy-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110313111803.GH29043@yellowpig
