Update Chair duties file for release tracker etc
- Adding per release tracker in duties - Cleanup on the UC reference as it is merged in TC now - Add TC onboarding guide step Change-Id: I918b601c219383d55f7614a4594522948b72b031
This commit is contained in:
parent
3d37dfba53
commit
4184c7d4d8
29
CHAIR.rst
29
CHAIR.rst
|
@ -28,20 +28,19 @@ General
|
||||||
* maintain the agenda in the wiki
|
* maintain the agenda in the wiki
|
||||||
https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee
|
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)
|
* Review proposals to the openstack/governance repo (see below)
|
||||||
* Coordinate the agenda for joint leadership meetings with the board (see below)
|
* Coordinate the agenda for joint leadership meetings with the board (see below)
|
||||||
* Send weekly update emails to openstack-dev (see below)
|
* Send weekly update emails to openstack-discuss (see below)
|
||||||
|
|
||||||
Each Cycle
|
Each Cycle
|
||||||
==========
|
==========
|
||||||
|
|
||||||
|
* Manage the initiative tracker
|
||||||
|
* Prepare release tracker etherpad (During PTG), Example:
|
||||||
|
https://etherpad.opendev.org/p/tc-xena-tracker
|
||||||
|
* Update the etherpad link in the wiki
|
||||||
|
https://wiki.openstack.org/wiki/Technical_Committee_Tracker
|
||||||
* See "Around TC elections"
|
* See "Around TC elections"
|
||||||
* Ensure that the TC has a representative on the meta SIG team, to
|
|
||||||
work with the UC to manage SIGs.
|
|
||||||
* Ensure that 2 TC members are signed up to manage the goal selection
|
* Ensure that 2 TC members are signed up to manage the goal selection
|
||||||
process for the next cycle.
|
process for the next cycle.
|
||||||
* Ensure the next release naming is started
|
* Ensure the next release naming is started
|
||||||
|
@ -59,7 +58,9 @@ membership changes when the election results are published.
|
||||||
|
|
||||||
When the election results are available, the outgoing chair should:
|
When the election results are available, the outgoing chair should:
|
||||||
|
|
||||||
* welcome new and returning members
|
* welcome new and returning members. Make sure to send the TC onboarding
|
||||||
|
guide to new members:
|
||||||
|
https://governance.openstack.org/tc/reference/tc-guide.html
|
||||||
* update the tech-committee group in gerrit:
|
* update the tech-committee group in gerrit:
|
||||||
https://review.opendev.org/#/admin/groups/205,members to remove
|
https://review.opendev.org/#/admin/groups/205,members to remove
|
||||||
members who should no longer be included and add new members
|
members who should no longer be included and add new members
|
||||||
|
@ -127,9 +128,8 @@ Remind TC members to review patches that are lingering without review.
|
||||||
Joint Leadership Meetings
|
Joint Leadership Meetings
|
||||||
=========================
|
=========================
|
||||||
|
|
||||||
The TC, User Committee, Board of Directors, and leaders of other
|
The TC, Board of Directors, and leaders of other Foundation projects meet
|
||||||
Foundation projects meet at the Summit to discuss topics of interest
|
at the Summit to discuss topics of interest to the entire group.
|
||||||
to the entire group.
|
|
||||||
|
|
||||||
Work with the Chair of the Board to build the agenda for the meeting,
|
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.
|
using input from the TC about topics that we want/need to discuss.
|
||||||
|
@ -153,10 +153,9 @@ Foundation Annual Report
|
||||||
========================
|
========================
|
||||||
|
|
||||||
Near the end of each calendar year the OpenStack Foundation prepares
|
Near the end of each calendar year the OpenStack Foundation prepares
|
||||||
an annual report. The TC and UC are responsible for contributing a
|
an annual report. The TC is responsible for contributing a status update
|
||||||
status update for the OpenStack project and community. The Foundation
|
for the OpenStack project and community. The Foundation staff will contact
|
||||||
staff will contact the TC chair, who should either write the report or
|
the TC chair, who should either write the report or ensure that it is written.
|
||||||
ensure that it is written.
|
|
||||||
|
|
||||||
See
|
See
|
||||||
https://www.openstack.org/assets/reports/OpenStack-AnnualReport2017.pdf
|
https://www.openstack.org/assets/reports/OpenStack-AnnualReport2017.pdf
|
||||||
|
|
Loading…
Reference in New Issue