contribx: add more friendly sig intro

It's been noted that the SIG Contributor Experience readme is a bit
unfriendly and focused on some past negatives.  I've updated the wording
to more positively align with the forward charter and goals of the SIG
instead of being overly focused on past hurdles.

Signed-off-by: Tim Pepper <tpepper@vmware.com>
This commit is contained in:
Tim Pepper 2018-06-05 18:06:09 -07:00
parent a7572ca5ba
commit a7777c563b
2 changed files with 8 additions and 6 deletions

View File

@ -8,7 +8,7 @@ To understand how this file is generated, see https://git.k8s.io/community/gener
---> --->
# Contributor Experience Special Interest Group # Contributor Experience Special Interest Group
Developing and sustaining a healthy community of contributors is critical to scaling the project and growing the ecosystem. We need to ensure our contributors are happy and productive, we need to break the commit-rate ceiling we hit in July 2015, and we need to get the monotonically growing PR merge latency and numbers of open PRs and issues under control. Developing and sustaining a healthy community of contributors is critical to scaling the project and growing the ecosystem. We need to ensure our contributors are happy and productive, and that there are not bottlenecks hindering the project in, for example: feature velocity, community scaling, pull request latency, and absolute numbers of open pull requests and open issues.
The [charter](charter.md) defines the scope and governance of the Contributor Experience Special Interest Group. The [charter](charter.md) defines the scope and governance of the Contributor Experience Special Interest Group.

View File

@ -746,11 +746,13 @@ sigs:
- name: Contributor Experience - name: Contributor Experience
dir: sig-contributor-experience dir: sig-contributor-experience
mission_statement: > mission_statement: >
Developing and sustaining a healthy community of contributors is critical Developing and sustaining a healthy community of contributors
to scaling the project and growing the ecosystem. We need to ensure our is critical to scaling the project and growing the ecosystem.
contributors are happy and productive, we need to break the commit-rate We need to ensure our contributors are happy and productive,
ceiling we hit in July 2015, and we need to get the monotonically growing and that there are not bottlenecks hindering the project in,
PR merge latency and numbers of open PRs and issues under control. for example: feature velocity, community scaling, pull request
latency, and absolute numbers of open pull requests and open
issues.
charter_link: charter.md charter_link: charter.md
label: contributor-experience label: contributor-experience
leadership: leadership: