This is a follow-up to our previous analysis of the user
survey results. This includes comparisons between the
2022 and 2021 date.
Change-Id: Iab768aef3712616bc1fbccefe8491521722c4e61
We have agreed to use term Active Contrubitor rather then
Active Technical Contributor, which means it's high time we've aligned
naming in our tools and releases documentation to align on
term to use. Moreover, it makes even more sense with Extra ACs, since
these are designed for ones, who do not contribute in gerrit but with
other means, which are usually non-technical.
Needed-By: https://review.opendev.org/c/openstack/releases/+/893833
Needed-By: https://review.opendev.org/c/openstack/election/+/893810
Change-Id: Id9f2d182d93a9fbe1357e9ecd4814d49d6eb962f
This is a follow-up to our 2019 analysis of the user
survey results. This includes comparisons between the
2019 and 2021 date.
Change-Id: I1161093d2d728e5d4c875f6db65b0bbdcb79201b
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
As we meet every week, we do not need separate office hour as such.
And with the office hour mostly inactive, in TC meeting[1], we decided
to remove it for now. If meeting time change to monthly or so then
we can re-add the weekly office hour.
[1] https://meetings.opendev.org/meetings/tc/2021/tc.2021-11-04-15.02.log.html#l-24
Change-Id: I283eace0e1805c567082017af1ce8b68c5b8d88e
As discussed in PTG[1], we will move towards
one office hours (Asia TZ centric) per week.
[1] https://etherpad.opendev.org/p/tc-xena-ptg
Change-Id: I35b5b1bb4341045fe15e29ac2f1cce92f71d1dfb
We have resolution merged for distributed leadership[1] and
there are few projects want to adopt this model in Wallaby cycle,
first one is oslo[2].
This commit add the support of new model in governance tooling,
doc and, schema. Basically making changes to fill the distributed
leadership liaisons and displaing those in projects rst.
Below are the changes done:
- Removed 'PTL' field to be mandatory instead making either 'PTL' or
'leadership_type: distributed' field as mandatory.
- To avoid confustion with existing liasion field, changed TC
liaison field name from 'liaisons' to sub field named 'tc_members'
- Extended the existing liaison field for distributed leadersip
liaisons.
It will looks like below:
liaisons:
tc_members:
- zaneb
- ttx
release:
- name: Hervé Beraud
irc: hberaud
email: hberaud@redhat.com
- name: Daniel Bengtsson
irc: damani
email: dbengt@redhat.com
tact-sig:
- name: Hervé Beraud
irc: hberaud
email: hberaud@redhat.com
security:
- name: Daniel Bengtsson
irc: damani
email: dbengt@redhat.com
and on site:
TC Members Liaisons
ricolin, belmoreira
Release Liaisons
Hervé Beraud (hberaud) <hraud@redhat.com>, Daniel Bengtsson (damani) <dbengt@redhat.com>
[1] https://governance.openstack.org/tc/resolutions/20200803-distributed-project-leadership.html
[2] https://review.opendev.org/#/c/757906
Change-Id: If96915a16a8746aed6f0cb844c53ad61a300c234
As per the definition of this tag
"The “OpenStack TC Approved Release” is used as the superset
of projects used by the OpenStack Foundation when creating
commercial trademark programs." (read full definition in [1])
this tag was used to know if project under OpenStack is mature
so that it can be considered as possible candidate for
trademark programs. This situation was in early stage of OpenStack
hen we used to have incubated vs integrated project status but now
everything in project.yaml file is consider as mature, following
release, active etc.
Bylaw requirements are (section 4.1, 4.13[2])
"The Technical Committee shall designate a subset of the OpenStack
Project an “OpenStack Technical Committee Approved Release” from time
to time. The Board of Directors may determine "Trademark Designated
OpenStack Software" from time to time, which will be a subset of the
"OpenStack Technical Committee Approved Release" as provided in
Section 4.1(b)(ii) and (iii)" (read full text in bylaw link[2])
We do not need any changes in bylaw as all projects listed in projects.yaml
file are applicable as "OpenStack Technical Committee Approved Release" and if
any of the current trademarked software is going to be deleted from the
projects.yaml then it need to be done with Coordination Procedures listed
in bylaw.
This commit proposes to remove this tag and add section in place of this
tag defintion to consider all the projects listed
in projects.yaml as "OpenStack Technical Committee Approved Release".
[1] https://governance.openstack.org/tc/reference/tags/tc_approved-release.html#rationale
[2] https://www.openstack.org/legal/bylaws-of-the-openstack-foundation
Change-Id: I0955c20a74eea8cac5f920bba60be1a334d50754
This proposal is to have two office hour but covering with
different TZ.
Poll dta summary for these two office hour time[1]
01:00 UTC on Tuesdays: 5 votes
15:00 UTC on Wednesdays: 10 votes
[1] https://doodle.com/poll/q27t8pucq7b8xbme
Change-Id: I4c05793c3d99d8ddefe22367975af4acc9c4817c
Create a single governance body to represent all contributors
to OpenStack (developers, operators and end users of the software).
The User Committee is defined in the OpenStack Foundation
bylaws, and amending those is very costly (in time, money and
effort). Luckily, the bylaws defer most of the UC details to a
User Committee charter, which contents are modifiable by the
User Committee itself.
This change adds a minimal User Committee charter that implements
the User Committee as a subcommittee of the Technical Committee.
This allows to operate as a single group without requiring costly
bylaws changes to be implemented first.
Change-Id: I8614f650bbc4176929caf15304cdefaed070c3f6
Switch to openstackdocstheme 2.2.1 version. Using
this version will allow especially:
* Linking from HTML to PDF document
* Allow parallel building of documents
* Fix some rendering problems
Update Sphinx version as well.
Disable openstackdocs_auto_name to use 'project' variable as name.
Change pygments_style to 'native' since old theme version always used
'native' and the theme now respects the setting and using 'sphinx' can
lead to some strange rendering.
openstackdocstheme renames some variables, so follow the renames
before the next release removes them. A couple of variables are also
not needed anymore, remove them.
See also
http://lists.openstack.org/pipermail/openstack-discuss/2020-May/014971.html
Change-Id: I611663fd224ddbd8a315732966c60ca67a5ffc40
This repo is now testing only with Python 3, so let's make
a few cleanups:
- Remove obsolete sections from setup.cfg
- Use newer openstackdocstheme and Sphinx versions for Python3
- Cleanup */source/conf.py to remove now obsolete content.
- Remove install_command from tox.ini, the default is fine
- Move python3 to testenv in tox.ini
- Switch to hacking 3, fix problems found.
Change-Id: I26fcab3b288b5ed64c74f7a6725b43036f195d44
As the end date of a term is fluctuating, it's probably easier
to mention the elected date of each of the TC members, and users
can do the math.
This should clarify things.
Change-Id: I102296a986a1800c809ad875443f8a924dd0b30b
The 2019 OpenStack User Survey was the first time
that the OpenStack Technical Committee submitted
questions. After some review at the Ussuri PTG
in Shanghai the TC has come up with the following
analysis.
Change-Id: Ia72323805e4eb8c2407bf8d9dfdfe066f860b2a3
To make sure it is reachable through the sidebar, like on the
rest of the governance website.
Depends-On: https://review.opendev.org/#/c/706240/
Change-Id: I82280e00a1ee53bf56687bdb19bba84d32ac2312
Take the opportunity to show an OpenStack logo in front of the
badges, since this is displayed on the rendered README for every
OpenStack repository.
Change-Id: I63da32c79e7738f2ae777ef5772d8ab7a1fc317f
Rather than sorting badges by size, sort them alphabetically.
Since we can no longer rely on the last line having the largest badge,
change the column width calculation logic to actually look at all badges
in a column, rather than look at it from the bottom.
Change-Id: Ia116a46236ba2e8d8757d0191f0cf6432c81c600
Instead of displaying a "project official" badge which does not mean
much when you browse the project on opendev or GitHub, display an
"openstack community project" badge pointing to the project team list,
and a "cii best practices passing" badge pointing to our CII results.
Fix a bug that prevented badges with spaces from being properly
displayed.
Change-Id: I0be1fcc9c5553cc06891a593b253e3aee4e8ebb8
The "project:official" badge is currently placed first because it
happens to be the smallest one. Separate base badges from tag badges
and always place them first.
Change-Id: I4a0e4ac277c3dfef52a7949c7143f16f4e08e48b
Before making deeper changes, clean up existing code by:
- introducing variables controlling number of columns, and spacing
between badges
- renaming confusing function names and variables
- adding a few comments
- wrapping long lines
Change-Id: I79fccd1221274bf6aa96f6c4c7404ebe10545660
Project team pages (like [1]) display "Liaisons", but it can be unclear
to the reader that those are TC liaisons. Add "TC" to make it clearer.
[1] https://governance.openstack.org/tc/reference/projects/solum.html
Change-Id: I4ef520b2dfdc272f0217014a61624949ce1a8a0f
As discussed at the PTG in Denver, one issue of the current
goal selection process is that it conflates definition of the
goal (which is ideally an iterative process) with selection of
a specific goal for a series, in a single review.
This has made it hard to process goal reviews in the past,
especially considering we need to select the set of goals
(as collectively feasibale together in a single cycle), and
not select them individually.
This change proposed to set up a three phase process. Wishlist
goals that do not have a champion ready to drive them yet should
live in the backlog etherpad. Once goals have a champion, those can
iterate through goal definition in a specific "proposed" directory.
Finally, when time comes for us to select goals for a specific
series, we can propose a set of goals in a single review (by
proposing a set of moves from the proposed repository to the
selected/series repository).
This should hopefully address the review issues that have been
plaguing the goal definition and selection process in the past, as
well as let us vote on a selection of goals using Gerrit, rather
than try (and fail) to rely on out-of-band mechanisms.
Change-Id: I9e00a0d9c3eb91ec6b1048c773d84032d3ce9f0e
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
Following the discussion at the Forum in Denver and the TC meeting
at the PTG (also in Denver) one of the outcomes[1] of those discussions
was to propose a lightweight framework for popup teams.
To avoid repeating past failures in cross-project work, this proposal
pushes forward a relatively low barrier to entry, with the TC making an
early decision on whether the team objective sounds like a good idea
for OpenStack, rather than approving detailed implementation specs. It
focuses on supporting the popup teams rather than "blessing" them.
[1] http://lists.openstack.org/pipermail/openstack-discuss/2019-May/006225.html
Change-Id: I39a4c3814ec3442c60c91055b41b0876976aaeab
openstackdocstheme now gets the last modified timestamp for files by
default. This makes most of our sphinx extension for this redundant. We
do have a few generated files that we perform special handling that
openstackdocstheme does not know about, so this updates our extension to
optimize for only checking the files that will not be covered by the
theme.
This also adds a bindep file to fix a doc build issue with a font
missing. Gate jobs used to use a common bindep-failback.txt file if
there wasn't a local one present. That mechanism was recently removed,
and it appears now the docs build will not pass unless a needed fonts
package is installed that is not there by default.
Change-Id: I454f4d92e397d6410cb869498f348b86ae26ca0a
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
Slawek Kaplonski