Add resolution to define election officilas' roles

This change adds a new folder to store TSC resolutions to address
matters that are not listed in the TSC charter onwards. This change
defines the role and responsibilities of election officials in greater
details than what the charter contains.

Change-Id: Ia43740c506ab2fab9fc1be9095e96f2e489c1ad3

doc/source/index.rst

@@ -35,6 +35,7 @@ sets the overall project priorities in collaboration with the community.
     :maxdepth: 1
 
     reference/tsc/*
+    resolutions/*
 
 Indices and Tables
 ==================

doc/source/resolutions

@@ -0,0 +1 @@
+../../resolutions

resolutions/20190520_election_activities.rst

@@ -0,0 +1,75 @@
+===============================
+ 2019-05-20 Election Activities
+===============================
+
+We expect all members of our community to adhere to the highest
+standards of behavior during Technical Steering Committee and Program
+Leader elections. Everyone should respect the election process, as set
+out in the `Community Code of Conduct`_.
+
+We trust the instincts, good faith, maturity, and sound judgement of
+our community members. Talking about governance issues in person at
+official StarlingX events or privately with co-workers or friends is
+expected. However, we are a diverse, world-wide community, and we
+encourage everyone to discuss community issues publicly using
+inclusive forums where we can all learn from and contribute to the
+conversation. Using the `discuss mailing list`_ for those
+discussions ensures that everyone has an opportunity to participate,
+unlike exclusionary forums such as private mailings and in-person
+events that overlook community members who cannot travel to the event,
+even if no invitation is required to gain entrance.
+
+Administering Elections
+=======================
+
+Prior to each election, the TSC names community members to administer
+the election. As described in the `Technical Steering Committee Charter`_,
+these election officials identify the appropriate electorate, verify
+all candidates' qualifications, configure the voting software, and
+ensure that votes are collected and counted properly.
+
+Although we hope that everyone will follow our community ideals, we
+recognize that, whether through mistakes or bad intent, that will not
+always be the case. In addition to the logistical operation of the
+election, the election officials are also responsible for receiving
+reports of potential abuse.
+
+During the election, the officials report to the active members of the
+TSC (defined as those members whose terms have not expired and have not
+stepped down for other reasons). Of course, any active TSC member
+involved in the election (such as for a PL/TL position) would not be
+involved in resolving any issues. This ensures that TSC members
+running in the election do not have undue influence over its outcome,
+while also maintaining oversight by the elected representatives still
+serving on the TSC.
+
+Reporting Problems
+==================
+
+If you observe a problem with the election or campaigning activities,
+you should bring the details to the election officials privately for
+an impartial review.
+
+The officials will report privately to the active TSC members, who will
+work with the election officials to talk to all of the parties
+affected and determine how to resolve the situation. The resolution
+may include private apologies and reprimands, or, in extreme cases,
+voiding and re-running the election.
+
+After the matter is resolved, the active TSC members and election
+officials will prepare and publish an official summary of the
+incident. In most cases, the names of people and companies involved
+will be redacted because the goal of the incident report is to
+emphasize our community culture and values through education, rather
+than to publicly punish the parties involved.
+
+In an especially extreme case, the active TSC members may decide to
+refer the issue to the OpenStack Foundation Executive Director and
+Secretary for further action related to the Code of Conduct or other
+Foundation rules. Community members always retain the right to report
+issues to the Foundation staff directly, following the processes
+described in the Code of Conduct.
+
+.. _Technical Steering Committee Charter: https://docs.starlingx.io/governance/reference/tsc/stx_charter.html
+.. _Community Code of Conduct: http://www.openstack.org/legal/community-code-of-conduct
+.. _discuss mailing list: http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss

resolutions/index.rst

@@ -0,0 +1,18 @@
+.. _resolutions:
+
+=============
+ Resolutions
+=============
+
+When a motion does not result in a change in a reference doc, it can
+be expressed as a resolution.
+
+2019
+====
+
+.. toctree::
+   :maxdepth: 1
+   :glob:
+   :reversed:
+
+   2019*