Mike Bird writes ("Re: git bikeshedding (Re: triggers in dpkg, and dpkg maintenance)"): > On Tue March 4 2008 10:44:22 Ian Jackson wrote: > > Of course this triggers feature has a proper specification. It was > > discussed and agreed on debian-dpkg and now resides in the doc/ > > subdirectory of my dpkg triggers tree, which is what Raphael is > > refusing to allow me to merge. > > Raphael seems to have the power to block your packages but he has > no rational excuse. Can the tech committee overrule Raphael or > does Debian need to fork a dpkg under more sensible maintainers?
Well, I'm hoping to be able to persuade Raphael without completely destroying any chance of us working constructively together. Raphael has been doing much useful work which I want to see continue. I could appeal to the TC but sadly I think (with some shame, as a TC member) that this would be unlikely to yield an answer in time to deploy triggers in lenny, if at all. Also there is of course a conflict of interest for me personally which would make the whole thing look rather like self-dealing. I have considered mediation but I think really the answer that a decision is needed, not a helping hand to allow us to communicate. Our problems are not that Raphael and I are being rude to each other. The main problem is that we have an irreconcilable difference of opinion about workflow. Also, Raphael doesn't seem to trust my code. There are a couple of `nuclear buttons' that I could push: I could announce an intention to hijack dpkg, or I could declare myself upstream (or, very similarly, declare myself `master' in git terminology). These would be very unfriendly and I don't think they would lead to very good outcomes. Ian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]