openstack
/
governance
Code Issues Proposed changes

Remove "meritocracy" from the opens 

The value and meaning of the word "meritocracy" has been a source of
much debate in many communities, open source and otherwise. For many
people it is considered exclusionary and something of a hallmark for
not being in tune with its negative connotations. Rather than
presenting our defenses against those negative connotations and
being more explicit about the local definition of a subjective term,
we can remove it in favor of something that is more direct.

The intent, in the past, has been that "meritocracy" is supposed to
be indicative of a community where the people who get on and do
things and get stuff done are the ones that become become leaders.
The problem with this is "meritocracy" is defined by those who are
already in positions of leadership and thus implicitly excludes
those who may be leading or attempting to lead (or "do") in styles
that are different from existing leaders or who come from
backgrounds different from the norm. These styles may have just as
much "merit" as any other.

The change here simply states what is the case: one of the ways we
achieve openness is by technical governors being elected from
members of the community, rather than being imposed from elsewhere.

Also in this change "technical leads" is adjusted to "team leads" to
reflect the current expansion of "PTL".

Change-Id: Ifdadaad9e616c0ee3ce59f3c1da323ed458c0bc7
This commit is contained in:
Chris Dent 2017-06-12 16:42:52 +01:00
parent 5ad5353753
commit 33c93087e7
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
reference/opens.rst
View File

@ -46,8 +46,8 @@ community. Most decisions are made using a `lazy consensus
<http://www.apache.org/foundation/glossary.html#LazyConsensus>`_ model. All
processes are documented, open and transparent.
The technical governance of the project is a community meritocracy with
contributors electing technical leads and members of the Technical Committee.
The technical governance of the project is provided by the community itself,
with contributors electing team leads and members of the Technical Committee.
All project meetings are held in public IRC channels and recorded. Additional
technical communication is through public mailing lists and is archived.