Replace Chinese quotes with English quotes
Change-Id: I411468d6787fa4de7db4d309150ce8fb897f2b20
This commit is contained in:
parent
42eca16ca4
commit
c7d55c958b
|
@ -4,7 +4,7 @@
|
|||
|
||||
Mission
|
||||
=======
|
||||
The User Committee’s (UC) mission is to serve the user community of
|
||||
The User Committee's (UC) mission is to serve the user community of
|
||||
OpenStack, representing them to the broader community (including the Technical
|
||||
Committee, Board of Directors, Projects and PTLs, and projects outside
|
||||
OpenStack). The UC recognizes competence and contribution, and when necessary
|
||||
|
@ -59,7 +59,7 @@ Foundation bylaws.
|
|||
Meetings
|
||||
========
|
||||
UC meetings happen publicly, bi-weekly on IRC. The meeting times should be
|
||||
decided among UC members. If there isn’t consensus on a meeting time, the
|
||||
decided among UC members. If there isn't consensus on a meeting time, the
|
||||
option of rotating the time weekly should be explored. The UC maintains an
|
||||
open agenda on the wiki. The UC meeting is automatically called if anything
|
||||
is posted to that wiki by one of its members at least one day before the
|
||||
|
@ -118,7 +118,7 @@ Committee Election
|
|||
The allotted number of UC seats are partially renewed every 6 months using
|
||||
staggered elections: the minority number of seats are renewed every (Northern
|
||||
hemisphere) Spring, and the majority number of seats are renewed every Fall.
|
||||
Seats are valid for one-year terms. For this election we’ll use a single-winner
|
||||
Seats are valid for one-year terms. For this election we'll use a single-winner
|
||||
election system. The election is held no later than 3 weeks prior to each
|
||||
OpenStack Summit, with elections held open for no less than four business days.
|
||||
|
||||
|
|
|
@ -35,7 +35,7 @@ When considering new working groups/teams for addition, the UC will check that:
|
|||
|
||||
* **The working group/team aligns with the User Committee mission**
|
||||
* **The group must have a clear and defined scope and duration of the effort**
|
||||
* **The group follows the OpenStack way (“the 4 opens”):**
|
||||
* **The group follows the OpenStack way ("the 4 opens"):**
|
||||
|
||||
* **Open Source:**
|
||||
|
||||
|
@ -48,14 +48,14 @@ When considering new working groups/teams for addition, the UC will check that:
|
|||
once a month during those months in which the group is actively
|
||||
working on items) and those meetings are logged, published in the
|
||||
OpenStack meeting calendar via Eavesdrop, and held in an official
|
||||
official OpenStack meeting channels once the project’s
|
||||
application is accepted, if they’re not held there already.
|
||||
official OpenStack meeting channels once the project's
|
||||
application is accepted, if they're not held there already.
|
||||
* If the team uses alternative methods of communication to augment
|
||||
public meetings on IRC then they should provide a summary of
|
||||
their meetings on the User Committee mailing list.
|
||||
* The group shall provide a level and open collaboration playing field
|
||||
for all contributors. The group shall not benefit a single vendor, or
|
||||
a single vendor’s product offerings; nor advantage contributors
|
||||
a single vendor's product offerings; nor advantage contributors
|
||||
from a single vendor organization due to access to information,
|
||||
resources or other proprietary resources available only to those
|
||||
contributors.
|
||||
|
|
Loading…
Reference in New Issue