Hi Matthew, >> Your rationale does not explain how the normal policy process has failed >> to deliver the outcomes required by the project. I think the project >> should > > Sorry about that; I rather thought that the TC failing to rule on the > issue was failing to provide clarity on this important issue.
Quite the contrary. The TC was never actually asked to rule on this issue. It is standard that the TC rules on issues when the normal processes have broken down in some way. As described in detail in #727708, the TC chose not to rule on it because the normal policy process was not broken -- in fact the normal policy process had barely even started. The TC is not the project's normal policy process any more than a GR is the project's normal policy process. I would add that picking at a sore like this *will* end up breaking the normal policy process; we're dealing with self-fulfilling prophecies here. Stuart -- Stuart Prescott http://www.nanonanonano.net/ stu...@nanonanonano.net Debian Developer http://www.debian.org/ stu...@debian.org GPG fingerprint 90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7 -- To UNSUBSCRIBE, email to debian-project-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/lfkabg$fse$1...@ger.gmane.org