Add project-wide communication
This commit is contained in:
parent
8e581ca730
commit
e759e0ed59
|
@ -29,6 +29,7 @@ This is a backlog of items that the steering committee needs to either handle or
|
||||||
- Committee decision-making process (e.g., modified lazy consensus seeking) and quorum requirement
|
- Committee decision-making process (e.g., modified lazy consensus seeking) and quorum requirement
|
||||||
- Improve/expand definition of members of standing
|
- Improve/expand definition of members of standing
|
||||||
- Identify who is responsible for evolving the governance going forward and how changes will be approved
|
- Identify who is responsible for evolving the governance going forward and how changes will be approved
|
||||||
|
- Project-wide communication requirements, processes, and mechanisms
|
||||||
- Do we need user groups?
|
- Do we need user groups?
|
||||||
- Do we need insurance?
|
- Do we need insurance?
|
||||||
- Do we need a policy similar to [Apache's release policy](http://www.apache.org/legal/release-policy.html)?
|
- Do we need a policy similar to [Apache's release policy](http://www.apache.org/legal/release-policy.html)?
|
||||||
|
@ -36,4 +37,4 @@ This is a backlog of items that the steering committee needs to either handle or
|
||||||
- Do we need a Conflict of Interest policy?
|
- Do we need a Conflict of Interest policy?
|
||||||
- Develop processes to address staffing gaps (engineering, docs, test, release, ...), effort gaps
|
- Develop processes to address staffing gaps (engineering, docs, test, release, ...), effort gaps
|
||||||
(tragedy of the commons), expertise mismatches, priority conflicts, personnel conflicts
|
(tragedy of the commons), expertise mismatches, priority conflicts, personnel conflicts
|
||||||
-
|
|
||||||
|
|
Loading…
Reference in New Issue