start document with chair's responsibilities

Start a reviewable document with the chair's responsibilities. This
isn't included in the published documentation for now because it is
meant as a set of informal notes rather than a binding document.

Change-Id: I7e4a15aa8d63ef77c60e0b93887e3c2ffe075149
Signed-off-by: Doug Hellmann <doug@doughellmann.com>

CHAIR.rst

@@ -0,0 +1,124 @@
+===========================
+ TC Chair Responsibilities
+===========================
+
+.. note::
+
+   This document is maintained as a simple text file, outside of the
+   published governance document, because it is meant to be used for
+   shared notes rather than as an official "guide to being TC chair".
+
+General
+=======
+
+* Keep the Board informed of important decisions
+
+  * email the board chair and secretary with brief summaries of
+    decisions, linking to the public discussion (e.g., resuming
+    meetings, election outcome, etc.)
+
+* Manage formal TC meetings
+
+  * maintain the agenda in the wiki
+    https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee
+
+* Manage the initiative tracker
+
+  * https://wiki.openstack.org/wiki/Technical_Committee_Tracker
+
+* Review proposals to the openstack/governance repo (see below)
+* Coordinate the agenda for joint leadership meetings with the board (see below)
+* Send weekly update emails to openstack-dev (see below)
+
+Around TC elections
+===================
+
+During the election period all current TC members continue to serve,
+even if their term is up and they are not running again. Committee
+membership changes when the election results are published.
+
+When the election results are available:
+
+* welcome new and returning members
+* update the tech-committee group in gerrit:
+  https://review.openstack.org/#/admin/groups/205,members to remove
+  members who should no longer be included and add new members
+* encourage all TC members to vote on the patch prepared by the
+  election officials with the new roster
+* encourage all TC members to sign up for the openstack-tc mailing
+  list (while it exists)
+* propose a patch to remove current chair and vice chair
+
+After the election results are confirmed:
+
+* propose a patch to restore chair status, if planning to serve again
+* after a chair is selected, ensure they appear in the
+  tech-committee-chair group in gerrit:
+  https://review.openstack.org/#/admin/groups/206,members
+* the outgoing chair should notify the board chair and secretary of
+  the new TC membership and chair
+* start the liaison assignment process (see below)
+
+After the chair status is confirmed:
+
+* propose a patch to appoint a vice chair
+
+Project Team Liaisons
+=====================
+
+Each term of the TC we designate 2 members to be liaisons to each
+project team
+(https://wiki.openstack.org/wiki/OpenStack_health_tracker).
+
+* update the wiki to remove the current list of liaisons, leaving the
+  project team names there
+* encourage TC members to volunteer to act as liaisons for the project
+  teams they want (set a deadline, ~1 week)
+* use tools/assign_liaisons.py to randomly assign the remaining
+  members to fill in any gaps
+
+Governance Repo Patches
+=======================
+
+Different changes to openstack/governance use different voting
+rules. The chair is responsible for setting the topic for each change
+to the right value, and monitoring reviews so we know when it is OK to
+approve them or when they need to be rejected.
+
+https://governance.openstack.org/tc/reference/charter.html#motions and
+https://governance.openstack.org/tc/reference/house-rules.html cover
+the voting rules
+
+Running "tox -e check-review-status" builds a report to show the
+current status of each patch.
+
+Keep in mind that even patches that are technically ready for approval
+may need to be held if there is strong minority dissent or someone key
+to the discussion hasn't had a chance to participate.
+
+Remind TC members to review patches that are lingering without review.
+
+Joint Leadership Meetings
+=========================
+
+The TC, User Committee, Board of Directors, and leaders of other
+Foundation projects meet at the Summit to discuss topics of interest
+to the entire group.
+
+Work with the Chair of the Board to build the agenda for the meeting,
+using input from the TC about topics that we want/need to discuss.
+
+Weekly Update Emails
+====================
+
+We use weekly email summaries of TC activity as a way to communicate
+with the rest of the community more easily. These are especially
+important for folks who do not have time to follow all of the
+discussions directly.
+
+The summary should include:
+
+* updates about ongoing discussions, including links to mailing list
+  threads, IRC logs, and reviews
+* a list of the top 1-2 of things TC members should be focusing on for
+  the next week, such as reviews or mailing list threads