Establish GitHub Management Subproject

This commit is contained in:
Christoph Blecker 2018-07-18 15:06:08 -07:00
parent a6baaf2018
commit 8adb7c849a
No known key found for this signature in database
GPG Key ID: B34A59A9D39F838B
6 changed files with 59 additions and 9 deletions

7
github-management/OWNERS Normal file
View File

@ -0,0 +1,7 @@
reviewers:
- cblecker
approvers:
- cblecker
labels:
- sig/contributor-experience
- area/github-management

View File

@ -9,6 +9,10 @@ policies to reduce friction and ease administration of our Github repositories
and organizations. We have also created a number of tools to automate setup and
enforcement of these policies.
These polices are overseen by the
[GitHub Management subproject](subproject-responsibilites.md) of the Contributor
Experience Special Interest Group.
## Guides
- [Organization Owners Guide](org-owners-guide.md)
- [Repository Creation Guidelines](kubernetes-repositories.md)

View File

@ -0,0 +1,27 @@
# GitHub Management Subproject Responsibilities
This subproject will be responsible for:
- Establishing policies, standards, and procedures for routine GitHub management
tasks, including but not limited to: org membership, org permissions, repo
creation/administration
- Establishing a policy around "Org Owner" permissions, and grant/limit these
privileges accordingly
- Establishing policies and best practices for bot accounts, service accounts,
webooks, and third-party integrations
- Maintaining documentation related to the above
- Establishing a "GitHub Administration team" that will oversee the execution of
GitHub management tasks (inviting new members to the org, creating repos,
executing moderation decisions, auditing permissions)
- Working with other sigs and interested parties in the project to execute
GitHub tasks where required
This subproject will explicitly not be responsible for:
- Tooling and automation for GitHub (this falls under sig-testing, and the
sig-contributor-experience Contributor Workflow and Automation subproject)
- Determining policies around which repos can get created (this falls under
sig-architecture and the steering committee)
- Moderation policies and escalations on GitHub (this falls under the Moderation
subproject, the Code of Conduct committee, and the steering committee)
- Contributor workflow within Kubernetes repos, e.g. mandated use of labels
(this falls under the guise of the subproject responsible for the repo, and
the Contributor Workflow and Automation subproject)

View File

@ -46,6 +46,9 @@ The following subprojects are owned by sig-contributor-experience:
- **community-management**
- Owners:
- https://raw.githubusercontent.com/kubernetes/community/master/communication/OWNERS https://raw.githubusercontent.com/kubernetes/community/master/events/OWNERS
- **github-management**
- Owners:
- https://raw.githubusercontent.com/kubernetes/community/master/github-management/OWNERS
- **contributors-guide**
- Owners:
- https://raw.githubusercontent.com/kubernetes/community/master/contributors/guide/OWNERS

View File

@ -1,8 +1,8 @@
# Projects and Goals
*note - this is a temporary file until we can figure out a better project management solution.*
*note - this is a temporary file until we can figure out a better project management solution.*
This is a list of the projects and goals currently underway with Contributor Experience. Please submit a PR if you are adding your project to this list. To introduce a new project, attend a weekly meeting or drop a note to us on the mailing list - details can be found on our [README](README.md).
This is a list of the projects and goals currently underway with Contributor Experience. Please submit a PR if you are adding your project to this list. To introduce a new project, attend a weekly meeting or drop a note to us on the mailing list - details can be found on our [README](README.md).
Want to contribute? Take a look at this list and the "future" at the bottom. Thank you to all of our contributors for your hard work!
@ -14,7 +14,7 @@ Project | Owner(s)/Lead(s) | Description | Q1, Q2, Later
Projects and Goals (this doc) | @parispittman | Create projects.md | Q1
de-SPOF Community Management | @castrojo | eg: YouTube management | Ongoing
## Mentoring
## Mentoring
Launch a multi-tier strategy test that promote all levels of the [contributor ladder](/community-membership.md) and diversity throughout the project.
Project | Owner(s)/Lead(s) | Description | Q1, Q2, Later
@ -26,7 +26,7 @@ Project | Owner(s)/Lead(s) | Description | Q1, Q2, Later
["Buddy" Program](https://github.com/kubernetes/community/issues/1803) | @parispittman, @chris-short | 1 hour 1:1 sessions for new and current contributors to have dedicated time; meet our contributors but personal | Q2
## Contributor Documentation
Ensure the contribution process is well documented, discoverable, and consistent across repos to deliver the best contributor experience.
Ensure the contribution process is well documented, discoverable, and consistent across repos to deliver the best contributor experience.
Project | Owner(s)/Lead(s) | Description | Q1, Q2, Later
---|---|---|---
@ -36,7 +36,6 @@ Project | Owner(s)/Lead(s) | Description | Q1, Q2, Later
[Label Documentation](https://gist.github.com/spiffxp/24937d8478853054c088ffc298021214) | @spiffxp | GitHub is rolling out a label description feature in the future; this is to document the label descriptions for contributors | Q1
Issue hygiene | @spzala | Produce clear understanding and documentation of issue hygiene | Q1
## Contributor Workflow and Automation
Ensure contributors have a smooth and similar process across repos to deliver the best contributor experience. Provide sufficient automation so that direct write access to repos is no longer required.
@ -45,6 +44,13 @@ Project | Owner(s)/Lead(s) | Description | Q1, Q2, Later
Cherry Pick Process | @spiffxp | Design and Prototype | Q2
PR Descriptions | @grodrigues3, @spiffxp | Automation allowing people to edit pr descriptions for tldr or correct issue / pr; release notes based (design). Define remaining work to be done. | Q1 - ongoing
## GitHub Management
Set polices and procedures to handle management GitHub settings, permissions, security, and process.
Project | Owner(s)/Lead(s) | Description | Q1, Q2, Later
---|---|---|---
Establish GitHub Management Subproject | @cblecker | | Q3
## Project-wide Communication Channels
Build, curate, moderate, and make project wide communication channels accessible.
@ -74,9 +80,9 @@ KubeCon ContribEx Update and Deep Dive | @parispittman, leads | Run the 30 min u
## FUTURE
These projects do not have an owner and have not started yet; however, we would like to get them on the slate for sometime this year.
These projects do not have an owner and have not started yet; however, we would like to get them on the slate for sometime this year.
Project | Description
---|---
Project | Description
---|---
Automation of new membership | Current process is emailing a googlegroup and an org owner adds person to GH org
Audit schedule | Create an audit schedule to make sure all communication pipelines are up and running smoothly eg: check that google group mailing lists have back up owners/maintainers, make sure meetings are following the calendar process, etc.

View File

@ -811,6 +811,9 @@ sigs:
owners:
- https://raw.githubusercontent.com/kubernetes/community/master/communication/OWNERS
https://raw.githubusercontent.com/kubernetes/community/master/events/OWNERS
- name: github-management
owners:
- https://raw.githubusercontent.com/kubernetes/community/master/github-management/OWNERS
- name: contributors-guide
owners:
- https://raw.githubusercontent.com/kubernetes/community/master/contributors/guide/OWNERS
@ -2029,7 +2032,7 @@ workinggroups:
A Working Group dedicated to discussing, designing and documenting using Kubernetes for developing and deploying IoT and Edge specific applications
leadership:
chairs:
- name: Dejan Bosanac
- name: Dejan Bosanac
github: dejanb
company: Red Hat
meetings: