[ I'm not Cc:-ing debian-policy because you didn't and hence, a priori, your mail might be meant to remain private. But I strongly encourage you to ask your questions there. ] On Wed, May 02, 2012 at 01:00:15PM -0500, Jonathan Nieder wrote: > > In that case, please clarify what you expect from me :-), especially > > taking in account the fact that DPL's leadership cannot rule on > > technical matters. > > I think there has been some uncertainty about procedure. For example: In all these examples you, once more, don't need a DPL, although this time you need the Policy editors. Policy editors are official DPL delegates. As such they have the last word on policy and its interpretations (and they can even fix the policy if there is a need to!). The Constitution has more to say on the subject of the relationships among the DPL and his delegates, once the delegation has been made. Don't get me wrong on the above. I'd love to help, but to do so I should stay in the limits of my role. Besides, it is already socially awkward enough to escalate to authority in a project like Debian, let alone escalating to the *wrong* authority. Finally, as already pointed out on -devel, this seems to be a very "by the book" case for the tech-ctte. If the maintainers can't reach an agreement (which it would be unfortunate but might of course happen), just go for the tech-ctte. Other side procedural discussions are likely to be just wastes of time; time that we could put into better use this close to the Wheezy freeze. Hope this explains, Cheers. -- Stefano Zacchiroli zack@{upsilon.cc,pps.jussieu.fr,debian.org} . o . Maître de conférences ...... http://upsilon.cc/zack ...... . . o Debian Project Leader ....... @zack on identi.ca ....... o o o « the first rule of tautology club is the first rule of tautology club »
Attachment:
signature.asc
Description: Digital signature