trigger
trigger
Posted Oct 25, 2012 9:19 UTC (Thu) by zack (subscriber, #7062)Parent article: Debian Python followup
> It is not clear what precipitated the restart of the technical committee vote
> process, though a thread on hijacking packages in debian-devel at the same
> time may have been a partial trigger.
> process, though a thread on hijacking packages in debian-devel at the same
> time may have been a partial trigger.
Not really. At the time of last LWN article on this matter, the main remaining blocker to vote was a re-assessment of the available alternative teams. I've recently done that on the -python list, as documented in the link included in tech-ctte resolution.
After that, it was just a matter of writing the resolution with the various options and voting on it. This matter has been periodically reviewed during tech-ctte meetings (see http://meetbot.debian.net/debian-ctte/2012/ and the archives of the https://lists.debian.org/debian-ctte/ mailing list), until Don managed to sit down and do that.