PEP 8002: Add template questions as an annex

pep-8002.rst

@@ -1,6 +1,7 @@
 PEP: 8002
 Title: Open Source Governance Survey
-Author: Barry Warsaw <barry@python.org>, Łukasz Langa <lukasz@python.org>
+Author: Barry Warsaw <barry@python.org>, Łukasz Langa <lukasz@python.org>,
+   Antoine Pitrou <solipsis@pitrou.net>
 Status: Active
 Type: Informational
 Content-Type: text/x-rst
@@ -127,6 +128,48 @@ Thank you to Alex Crichton from the Rust team for an extensive explanation of ho
 core team governs the project.
 
 
+Annex 1: Template questions
+===========================
+
+The following set of questions was used as a template to guide evaluation and
+interaction with the surveyed projects:
+
+1. Do you have any open documentation on how the governance model is set up?
+
+2. How does the process look like in practice?
+
+   * Who are the key people?
+   * What "special statuses" can contributors have?
+   * How are they elected/how are the statuses assigned?
+   * How are regular decisions made?
+   * How are controversial decisions made?
+   * Is there a voting mechanism? how does it work? how often do votes actually happen?
+   * Is there a veto mechanism? how often was it actually used?
+
+3. How do you like the process?
+
+   * Which parts work well?
+   * Which parts could work better?
+   * When it doesn't work well, how does it look like?
+   * What would you change if it were only up to you?
+
+4. Related project work:
+
+   * How do you decide when a release happens and what goes into it?
+   * How do you decide who gets commit access?
+   * Where do you hold discussions? (GitHub, mailing lists, face-to-face meetings, and so on)
+   * Do you have a RFC/PEP-like process?
+   * Who has access to those discussion channels?
+   * How is this access granted/revoked?
+   * Who moderates those discussions?
+   * Do you (and how) censure participants and how?
+
+5. Process evolution
+
+   * How did this process evolve historically?
+   * How can it be changed in the future?
+
+
 Copyright
 =========