diff --git a/reference/tc-guide.rst b/reference/tc-guide.rst index 18d12f125..644751f79 100644 --- a/reference/tc-guide.rst +++ b/reference/tc-guide.rst @@ -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 -`_ -2.`House Rules for openstack/governance repo -`_ -3.`Role of the TC -`_ +#. :doc:`Technical Committee Charter ` + +#. :doc:`House Rules for openstack/governance repo ` + +#. :doc:`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 -`_ 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 + `_ + 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 ` 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 -`_. +of repos that are under the governance of the TC is listed below: + +* `governance/reference/technical-committee-repos.yaml `_. + +* `governance/reference/user-committee-repos.yaml `_. The `TC review dashboard `_ @@ -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. +`_ +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 -`_. -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 -`_. 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