> 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.
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.