diff options
| author | Kubernetes Prow Robot <k8s-ci-robot@users.noreply.github.com> | 2019-02-25 20:32:27 -0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2019-02-25 20:32:27 -0800 |
| commit | 3b96213964bed1e41a502e86af1d6e83f9d2f920 (patch) | |
| tree | dc8acbd42890ff8ac13812000dcfb90725f33735 /github-management | |
| parent | 2826f1dfe5d1087a9a9d3292e83a6f3f82cf9ac7 (diff) | |
| parent | 0f3f51b1bc588ea205cbe8b40cdc0445ce6a5937 (diff) | |
Merge pull request #3300 from nikhita/github-management-project-boards
github-management: add project board guidance
Diffstat (limited to 'github-management')
| -rw-r--r-- | github-management/opening-a-request.md | 1 | ||||
| -rw-r--r-- | github-management/org-owners-guide.md | 22 |
2 files changed, 23 insertions, 0 deletions
diff --git a/github-management/opening-a-request.md b/github-management/opening-a-request.md index b0088647..dd7724cb 100644 --- a/github-management/opening-a-request.md +++ b/github-management/opening-a-request.md @@ -9,6 +9,7 @@ If you need help with the following: - Webhooks - Repository creation/migration - Repository archival +- Project Board creation - Other repository and configuration issues Please open an issue against the [kubernetes/org] repository describing your diff --git a/github-management/org-owners-guide.md b/github-management/org-owners-guide.md index c626d5c4..09df20ad 100644 --- a/github-management/org-owners-guide.md +++ b/github-management/org-owners-guide.md @@ -76,6 +76,28 @@ for all orgs going forward. Notable discrepancies at the moment: org. This was a mistake that swapped the usual convention, and we would like to rename the team +## Project Board Guidance + +Guidelines for project boards in the Kubernetes GitHub orgs are described below: + +- All project boards should be organization-level project boards instead of +repository-level even if the project board is intended to be scoped to a single +repository. It is easier to distribute permissions via org-level project boards +since write access to a repo-level project board requires full write access +to the repo. + +- Project Boards *must* have `Public` visibility. + +- The default _Organization Member Permission_ is suggested to be `Write` so +that contributors can move cards themselves as they take on work items. +However if the project board needs to be only scoped to a set of people, +the access *must* be granted through a GitHub team, instead of direct +collaborator access. + +**NB**: Not all project boards in use today currently follow this guidance. +We are looking to coalesce existing project boards towards this model, and use +this model for all orgs going forward. + ## Repository Guidance Repositories have additional guidelines and requirements, such as the use of CLA |