During discussion in below review, there were thought
to make CHAIR.rst file a official reference doc so that
we can update and refer it our formal polciies
- https://review.opendev.org/c/openstack/governance/+/896150
I think it make sense to make it more official doc so that we
refer and keep it up to date.
Change-Id: I8c582c51af89bb654079d9f2ef8674951a049760
Vice chair historically has been a self-nominated position; update the
documentation to reflect this as a valid option.
Change-Id: Id212a8c163e89b5b768bd91b6206ca73b7ac6ef1
It removes the release naming task which is not handled
by TC members anymore. Also add the task to select the
election liaison at the start of cycle.
Change-Id: I584cd5227723759da5325d8015b4fa2f29912cdc
As discussed in PTG[1], we need to define the process
for the TC chair nomination and election.
This commit adds one of the proposal discussed in the PTG
which is to record the nomination in governance repo.
[1] https://etherpad.opendev.org/p/tc-2023-1-ptg#L486
Change-Id: Ia29b92b41ddd7cccda5d9daa317ac4bb0af907ff
TC is more connected with project teams with the
weekly meeting and PTG TC+Leadership interaction sessions.
Also, TC liaisons did not work the way we expected it. In Zed
PTG, we decided to remove it.
- https://etherpad.opendev.org/p/tc-zed-ptg
Change-Id: I08702b015245df35d40e08fa08a3269cc6bb1cac
- 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
As per TC charter, PTL and TC election needs to be held
in between of R-6 to R-4 of each release. To comply
that we need to make sure election schedule is prepared
well before time otherwise we may end up adding the
exception for the elections
- https://governance.openstack.org/tc/reference/election-exceptions.html
Having this in TC chair duties can help to have election
on time. I think before R-5 is best time to check with election
WG on schedule preapration.
Change-Id: Ib47681d99b5647f0a9eca57fd338d874c7e7ded3
The CHAIR.rst contain the information the chair should ensure are
done each cycle. This list doesn't contain very important steps
for the community like preparing the next release python version or
naming (necessary for the release team).
This should improve the current documentation.
Change-Id: I5054ca7e37d065cfc9e395a585e8225abd2e3b09
The previous 'Help Most Needed' list was presenting information in a way
that focused on the desires of the community rather than the value that
sponsoring organisations can generate - for both themselves and the
commons. Replace the list with a new list of 'Upstream Investment
Opportunities', and a process to keep them current by removing them
after they have been on the list for between 6 months and a year, so
that the submitter is forced to reaffirm their interest and the TC is
forced to re-evaluate the relevancy.
Since the current 'Help Most Needed' entries are generally not written
in a style emphasising the value to a business of investing, the initial
list is empty and will be filled as the TC evaluates business cases
according to its new criteria and understanding of the needs of
potential contributing organisations.
To preserve the existing information, the contents of the current 'Help
Most Needed' list appear as the 2018 upstream investment opportunites.
Links to the old list will temporarily redirect here until such time as
the new entries are in place, at which point we can redirect to the main
page with the latest index.
Change-Id: I65fef701dc2e3d50aa84e7ee79b068c78346c846
If there are multiple candidates for chair, using CIVS like we do for
other community elections gives us a way to have private ballots.
Change-Id: Ifcf3e208f9a01fb4d3b84d05b6d6b8964df3b4de
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Be a little more explicit about whether the outgoing or incoming chair
is responsible for a block of tasks. Move the liaison assignment task
to the list of tasks after the incoming chair is confirmed.
Change-Id: Ie9f7b5786e73cda2a55c3978b2058dbd39864689
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Helping the TC stay up to date with the board's work is just as
important as helping the board stay up to date with the TC's work.
Change-Id: I2326e1e304600350d295c41ff78787d2c83cdd1b
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
I received the request for an update for the annual report this week,
so I am noting it in the list of the chair's duties.
Change-Id: I7a6824e700c035baf9e51e5f65a64ee9968f3872
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
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>
Ghanshyam Mann