openstack
/
governance
Code Issues Proposed changes

Update TC onboarding guide 

This commit updates the TC onboarding guide for
various fixes and formatting, like weekly meeting info
etc.

Change-Id: I33da1288d03781487ba5f1e1ae7254a89fe862a7
This commit is contained in:
Ghanshyam Mann 2021-04-19 13:24:05 -05:00 committed by Ghanshyam
parent 53d5e75908
commit 399e81836c
1 changed files with 49 additions and 40 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

89
reference/tc-guide.rst
View File

@ -1,9 +1,9 @@
===================================================
It All Starts with a Technical Committee Election
===================================================
====================================
Technical Committee Onboarding Guide
====================================
You're either here because you are interested in being on the TC one
day or because you are recently elected, either way: Thank You! We
day or because you were recently elected, either way: Thank You! We
appreciate the interest and your desire to volunteer to help
steer this big wonderful project!
@ -44,25 +44,29 @@ Other Documents
In addition to this document, there are three others you should read as a new
TC member and reference throughout your term on the TC.
1.`Technical Committee Charter
<https://governance.openstack.org/tc/reference/charter.html>`_
2.`House Rules for openstack/governance repo
<https://governance.openstack.org/tc/reference/house-rules.html>`_
3.`Role of the TC
<https://governance.openstack.org/tc/reference/role-of-the-tc.html>`_
#. :doc:`Technical Committee Charter </reference/charter>`
#. :doc:`House Rules for openstack/governance repo </reference/house-rules>`
#. :doc:`Role of the TC </reference/role-of-the-tc>`
Communication
~~~~~~~~~~~~~
As a TC member, we have two primary ways of communicating. Take a moment to
ensure that your email filters are configured to ensure you see any messages on
the `mailing list
<http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss>`_ with
the '[tc]' topic tag. Please also join the '#openstack-tc' channel on IRC, and
set a notification for the string 'tc-members'. There is no requirement to do
this, but we recommend also setting a notification for a string with your name.
This is also helpful for mentions in other channels if you are the tc-liaison
to a specific project.
As a TC member, we have two primary ways of communicating.
#. Email:
Take a moment to ensure that your email filters are configured
to ensure you see any messages on the `mailing list
<http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-discuss>`_
with the '[tc]' topic tag.
#. IRC channel:
Please also join the ``#openstack-tc`` channel on IRC, and set a notification
for the string ``tc-members``. There is no requirement to do this, but we
recommend also setting a notification for a string with your name. This
is also helpful for mentions in other channels if you are the ``tc-liaison``
to a specific project.
TC Project Liasions
~~~~~~~~~~~~~~~~~~~~
@ -81,14 +85,18 @@ introducing yourself to the PTL in an email or during a team meeting if you're
able to attend them, a greeting to the project team to ensure they know someone
to talk to, making sure the TC is an accessible community.
You can see the assigned list of projects per TC member in
:doc:`TC Liaisons </reference/tc-liaisons>`
TC Repos
~~~~~~~~~
While your main focus as a TC member is the governance repo, the complete list
of repos that are under the governance of the TC is listed in
`governance/reference/technical-committee-repos.yaml
<https://opendev.org/openstack/governance/raw/branch/master/reference/technical-committee-repos.yaml>`_.
of repos that are under the governance of the TC is listed below:
* `governance/reference/technical-committee-repos.yaml <https://opendev.org/openstack/governance/raw/branch/master/reference/technical-committee-repos.yaml>`_.
* `governance/reference/user-committee-repos.yaml <https://opendev.org/openstack/governance/raw/branch/master/reference/user-committee-repos.yaml>`_.
The `TC review dashboard
<https://review.opendev.org/#/dashboard/?title=Technical+Committee+Inbox&foreach=project%3Aopenstack%2Fgovernance+is%3Aopen&My+proposals=owner%3Aself&Formal+Vote+Items+I+have+not+voted+on+yet=topic%3Aformal-vote+NOT+(+label%3ARollCall-Vote%2B1%2Cself+OR+label%3ARollCall-Vote-1%2Cself+)&Has+at+Least+One+Objection=(+label%3ARollCall-Vote%3C%3D-1+OR+label%3ACode-Review%3C%3D-1+)&Quickies=(+topic%3Atypo-fix+OR+topic%3Acode-change+OR+topic%3Adocumentation-change+OR+topic%3Aproject-update+)&Formal+Vote+Items=topic%3Aformal-vote&Goal+Items+I+Haven't+Voted+On=path%3A^goals%2F.*+NOT+(+label%3ARollCall-Vote%2B1%2Cself+OR+label%3ARollCall-Vote-1%2Cself+)&I+Haven't+Voted+on+this+Draft=NOT+(+label%3ARollCall-Vote%2B1%2Cself+OR+label%3ARollCall-Vote-1%2Cself+)&Everything=>`_
@ -108,9 +116,19 @@ As discussed above, communication is incredibly important. As a team, you want
to make sure questions from the community in IRC and on the ML don't go
unanswered.
Office Hours & Meetings
Meetings & Office Hours
~~~~~~~~~~~~~~~~~~~~~~~
Attend the Technical Committee meetings (assuming your timezone allows). The
TC has meetings every Thursday in #openstack-tc; `check
Eavesdrop.
<http://eavesdrop.openstack.org/#Technical_Committee_Meeting>`_
To hold the meeting we must meet quorum, so it's important that you attend
as many as possible. If you have topics that should be discussed at the
meeting, they should be sent to the chair or vice-chair to be included
in the agenda. The agenda should also be publicized to the openstack-discuss
list to encourage community involvement.
We hold office hours at various times during the week on the #openstack-tc
IRC channel, `see
Eavesdrop for the schedule of those as well
@ -126,26 +144,17 @@ get discussed during office hours, make sure that someone has the action item
to summarize the discussion to the ML so that members not present, and the
greater community have insight into what is being discussed.
Attend the Technical Committee meetings (assuming your timezone allows). The
TC has meetings on the first Thursday of each month in #openstack-tc; `check
Eavesdrop for the current schedule
<http://eavesdrop.openstack.org/#Technical_Committee_Meeting>`_.
To hold the meeting we must meet quorum, so it's important that you attend
as many as possible. If you have topics that should be discussed at the
meeting, they should be sent to the chair or vice-chair to be included
in the agenda. The agenda should also be publicized to the openstack-discuss
list to encourage community involvement.
Governance Core Duties
~~~~~~~~~~~~~~~~~~~~~~
Block time on your calendar at least weekly for reviewing open
patches in the repos listed in `technical-committee-repos.yaml
<https://opendev.org/openstack/governance/raw/branch/master/reference/technical-committee-repos.yaml>`_. Even if you
have already done a review of the patch, there might have been other progress
that you should familiarize yourself with and stay up to date on. If you are
interested, there are other repositories it might be good to keep an eye on
as well that are related to TC duties like openstack/elections.
Book time on your calendar for reviewing open patches in the TC Repos.
As a TC member, you are a primary maintainer (a core member in OpenStack terms)
of all the TC repos. Even if you have already done a review of the patch,
there might have been other progress that you should familiarize yourself
with and stay up to date on.
If you are interested, there are other repositories it might be good to keep
an eye on as well that are related to TC duties, like openstack/elections.
TC Interactions with Other Governing Bodies