7c49e952fb
I am in the 2017 KubeCon Berlin. We are talking about contribution and that lead me to this page. I noticed the page does not render in markdown correctly when looking at it in a browser: https://github.com/mbruzek/community/tree/master/sig-contribx |
||
|---|---|---|
| .. | ||
| README.md | ||
README.md
SIG Contributor Experience
We need your help!!!
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.
Meeting:
- Meetings: Wednesdays 9:30AM PST (biweekly and changing soon)
- Zoom Link: https://zoom.us/j/7658488911
- Check out the Agenda and Minutes!
Goals:
- Ensure contributors are happy and productive.
- Owns project PR and issue automation.
- Help people get involved in the Kubernetes Community.
Organizers:
- Garrett Rodrigues grod@google.com, @grodrigues3, Google
- Elsie Phillips elsie.phillips@coreos.com, @Phillels, CoreOS
Issues:
- Detailed backlog
- velocity-improvement issues
- Too many notifications, which are insufficiently targeted and have too little context, as well as missing notifications for important events
- Too-coarse ACLs
- Inadequate PR reviewer assignment and processes, with too small a reviewer pool
- Lack of a sustainable approach to issue management (we have thousands of open issues, with over 100 new ones each week)
- Lack of processes for growing leadership within the community
- Trying to maintain a large monorepo in github, which is intended for small repos and teams
- Insufficient project-wide (cross-SIG) communication and coordination
- Need to make slackarchive more discoverable
- Too many flaky tests
- Excessive PR rebases due to checking in generated files
- Inadequate and out-of-date contributor documentation