Merge "Update joining-tc.rst to be general tc-guide.rst"
This commit is contained in:
Zuul
Gerrit Code Review
commit
be6751a1f4
|
|
@ -32,5 +32,5 @@ Reference documents which need to be revised over time.
|
|||
Requirements for previously-used incubation/integration process <incubation-integration-requirements>
|
||||
house-rules
|
||||
comparison-of-official-group-structures
|
||||
joining-tc
|
||||
tc-guide
|
||||
OpenStack-name-in-external-services
|
||||
|
|
|
|||
|
|
@ -1,71 +0,0 @@
|
|||
===================================================
|
||||
What's next? After the Technical Committee Election
|
||||
===================================================
|
||||
|
||||
Once the most recent TC election results are in, it is time to
|
||||
start organizing the committee for the next cycle.
|
||||
|
||||
The first step for the pre-existing TC members is to approve the
|
||||
patch prepared by the election officials to update the TC roster.
|
||||
This looks something like this: https://review.opendev.org/#/c/680356/
|
||||
|
||||
After the patch is merged, the TC is officially seated and we need to select
|
||||
a chair. If you are interested in being chair (see also ``CHAIR.rst`` in the
|
||||
governance repository) and propose a patch on ``reference/members.yaml`` to
|
||||
change your ``role:`` to ``chair``.
|
||||
|
||||
After the chair is designated, contact the chair if you're interested at being vice-chair.
|
||||
The chair proposes a patch to add a vice-chair in
|
||||
``reference/members.yaml`` about one week after being selected for chair.
|
||||
|
||||
Tips for new members
|
||||
~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
Joining the TC can seem a little daunting, especially when you may already have
|
||||
responsibilities in a project team, SIG, or group. A large part of being on the TC is
|
||||
active communication to ensure each member is up-to-date on what's being
|
||||
discussed, issues that may have arisen, and what's coming up.
|
||||
|
||||
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 helpful for mentions in other channels if you are the tc-liaison to a
|
||||
specific project.
|
||||
|
||||
Each project under OpenStack governance is assigned two TC members to act as
|
||||
liaisons. These liaisons should act as a bridge between that project and the
|
||||
TC, helping the project with governance concerns. You will be assigned a list
|
||||
of projects based on random selection. It is best to introduce yourself to the
|
||||
project members either in person at a Forum or PTG or at their regular IRC
|
||||
meetings. This mechanical assignment looks something like this:
|
||||
https://review.opendev.org/#/c/680386/
|
||||
|
||||
Once you have been assigned your projects, the first work item for new and recurring
|
||||
members is to talk to the projects you are liaison of. We recommend introducing yourself
|
||||
to the PTL, a greeting to the project team to ensure they know someone to talk to,
|
||||
making sure the TC is an accessible community.
|
||||
|
||||
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>`_. 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
|
||||
<http://eavesdrop.openstack.org/#Technical_Committee_Office_hours>`_. For more
|
||||
information, see our `wiki page
|
||||
<https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee>`_.
|
||||
|
||||
Familiarize yourself with the governance changes currently being discussed in
|
||||
the `openstack/governance project
|
||||
<https://review.opendev.org/#/q/status:open+project:openstack/governance>`_.
|
||||
Make sure you are familiar with the `house rules
|
||||
<https://governance.openstack.org/tc/reference/house-rules.html>`_ that govern
|
||||
voting on governance changes. 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=>`_
|
||||
can help you stay on top of what changes need your vote.
|
||||
|
||||
If you have any questions about getting started with the TC, ping any of the existing
|
||||
team members in the #openstack-tc channel.
|
||||
|
|
@ -0,0 +1,162 @@
|
|||
===================================================
|
||||
It All Starts with a Technical Committee Election
|
||||
===================================================
|
||||
|
||||
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
|
||||
appreciate the interest and your desire to volunteer to help
|
||||
steer this big wonderful project!
|
||||
|
||||
Below is an outline of what you need to know about the duties of a
|
||||
Technical Committee member.
|
||||
|
||||
After the Election
|
||||
-------------------
|
||||
|
||||
Once the most recent TC election results are in, it is time to
|
||||
start organizing the committee for the next cycle.
|
||||
|
||||
The first step for the pre-existing TC members is to approve the
|
||||
patch prepared by the election officials to update the TC roster.
|
||||
This looks something like this: https://review.opendev.org/#/c/680356/
|
||||
|
||||
After the patch is merged, the TC is officially seated and we need to select
|
||||
a chair. If you are interested in being chair (see also ``CHAIR.rst`` in the
|
||||
governance repository) and propose a patch on ``reference/members.yaml`` to
|
||||
change your ``role:`` to ``chair``. These chair nomination patches should be
|
||||
proposed within two weeks of the new members being seated.
|
||||
|
||||
After the chair is designated, candidates for vice chair should propose their
|
||||
candidacies within the week after the chair is seated. The candidate needs to
|
||||
propose a patch to add a vice-chair in ``reference/members.yaml``.
|
||||
|
||||
General Info
|
||||
------------
|
||||
|
||||
Joining the TC can seem a little daunting, especially when you may already have
|
||||
responsibilities in a project team, SIG, or group. A large part of being on the
|
||||
TC is active communication to ensure each member is up-to-date on what's being
|
||||
discussed, issues that may have arisen, and what's coming up.
|
||||
|
||||
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>`_
|
||||
|
||||
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.
|
||||
|
||||
TC Project Liasions
|
||||
~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
Each project under OpenStack governance is assigned two TC members to act as
|
||||
liaisons. These liaisons should act as a bridge between that project and the
|
||||
TC, helping the project with governance concerns. You will be assigned a list
|
||||
of projects based on random selection if you don't set them yourself. You can
|
||||
pick your preferred projects yourself after you are seated by submitting a
|
||||
patch. This mechanical assignment of tc members as liaisons looks something
|
||||
like this: https://review.opendev.org/#/c/680386/.
|
||||
|
||||
Once you have been assigned your projects, the first work item for new and returning
|
||||
members is to talk to the projects for which you are a liaison. We recommend
|
||||
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.
|
||||
|
||||
Meetings & Office Hours
|
||||
~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
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>`_. 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
|
||||
<http://eavesdrop.openstack.org/#Technical_Committee_Office_hours>`_. For more
|
||||
information, see our `wiki page
|
||||
<https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee>`_.
|
||||
|
||||
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>`_.
|
||||
|
||||
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=>`_
|
||||
can help you stay on top of what changes need your vote.
|
||||
|
||||
Duties
|
||||
-------
|
||||
|
||||
In general, being a member of the Technical Committee is as much work as you are
|
||||
willing to dedicate time to it. That said, there are some 'bare-minimums' you
|
||||
should be meeting.
|
||||
|
||||
Be Present on ML and IRC
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
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
|
||||
~~~~~~~~~~~~
|
||||
|
||||
Attend as many office hours as you can. There might be a lot of them where no
|
||||
one outside the TC comes to talk about anything, but on the off chance that
|
||||
there is someone, or another TC member that has something to discuss, it is
|
||||
good to be present wherever possible. When office hours begin, wave or say
|
||||
hello or indicate in some way that you are around to chat. If something does
|
||||
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.
|
||||
|
||||
Governance Core Duties
|
||||
~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
Block time on your calendar at least weekly if you 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.
|
||||
|
||||
Monthly Meeting
|
||||
~~~~~~~~~~~~~~~
|
||||
|
||||
Attend the Technical Committee meetings (assuming your timezone allows) that
|
||||
happen the first Thursday of every month. 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.
|
||||
|
||||
TC Interactions with Other Governing Bodies
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
Its encouraged that you attend Board of Directors meetings wherever possible.
|
||||
There are a variety of topics that often come up that the TC should be weighing
|
||||
in on. Sometimes there are face to face meetings as well where your attendance
|
||||
is encouraged.
|
||||
|
||||
Loading…
Reference in New Issue