Establish GitHub Management Subproject

github-management/OWNERS

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

github-management/README.md

@@ -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)

github-management/subproject-responsibilites.md

@@ -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)

sig-contributor-experience/README.md

@@ -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

sig-contributor-experience/projects.md

@@ -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.
 

sigs.yaml

@@ -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