Merge "Required Updates for TC and UC merge"
This commit is contained in:
commit
de93da90d3
|
@ -89,6 +89,9 @@ The responsibilities of the Project Policy Board were split between two bodies:
|
||||||
|
|
||||||
The Foundation bylaws also established a third body, the `User Committee`_,
|
The Foundation bylaws also established a third body, the `User Committee`_,
|
||||||
to more accurately reflect the views and needs of the users of OpenStack.
|
to more accurately reflect the views and needs of the users of OpenStack.
|
||||||
|
Since June, 2020 `User Committee`_ has been `merged
|
||||||
|
<https://review.opendev.org/c/openstack/governance/+/734074>`_
|
||||||
|
into the `Technical Committee`_ and is not a separate body anymore.
|
||||||
|
|
||||||
The Technical Committee was originally formed by all the PTLs + five members
|
The Technical Committee was originally formed by all the PTLs + five members
|
||||||
directly elected by all the contributors. In June 2013, to accommodate the
|
directly elected by all the contributors. In June 2013, to accommodate the
|
||||||
|
|
|
@ -94,7 +94,6 @@ are relevant):
|
||||||
* ``[release]`` Affects the upcoming release, all PTLs or release liaisons
|
* ``[release]`` Affects the upcoming release, all PTLs or release liaisons
|
||||||
should read
|
should read
|
||||||
* ``[tc]`` Discussion around Technical Committee activities
|
* ``[tc]`` Discussion around Technical Committee activities
|
||||||
* ``[uc]`` Discussion around User Committee activities
|
|
||||||
|
|
||||||
There are many mailing lists in the OpenStack ecosystem. Projects should ensure
|
There are many mailing lists in the OpenStack ecosystem. Projects should ensure
|
||||||
they have subscribers on all of the lists relevant to their project.
|
they have subscribers on all of the lists relevant to their project.
|
||||||
|
|
|
@ -47,9 +47,9 @@ audience.
|
||||||
Pre-summit organization
|
Pre-summit organization
|
||||||
-----------------------
|
-----------------------
|
||||||
|
|
||||||
The list of topics being discussed is selected by a selection committee
|
The list of topics being discussed is finalized by a selection committee
|
||||||
including User Committee members, Technical Committee members and Foundation
|
including Technical Committee members and Foundation staff, based on
|
||||||
staff, based on input from the community.
|
input from the community.
|
||||||
|
|
||||||
Topics are first brainstormed by each group on separate etherpads, then
|
Topics are first brainstormed by each group on separate etherpads, then
|
||||||
formally submitted for committee review.
|
formally submitted for committee review.
|
||||||
|
|
|
@ -304,15 +304,6 @@ status of what the team is doing. If you're not sure what's being asked in the
|
||||||
survey or want to update the project-specific survey questions, reach out to
|
survey or want to update the project-specific survey questions, reach out to
|
||||||
someone from the Foundation.
|
someone from the Foundation.
|
||||||
|
|
||||||
User committee
|
|
||||||
--------------
|
|
||||||
|
|
||||||
The User Committee is an elected body within the community that helps
|
|
||||||
facilitate communication between users and developers. If there are specific
|
|
||||||
things your project wants feedback on, but you're not sure how or where to
|
|
||||||
start, the User Committee can help. They hold `weekly meetings`_ on IRC, and
|
|
||||||
they can help you come up with a plan for collecting feedback.
|
|
||||||
|
|
||||||
PTG sessions
|
PTG sessions
|
||||||
------------
|
------------
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue