From 0cccb00adc3e6ef04eb6f112a1366de412494102 Mon Sep 17 00:00:00 2001 From: Nikhita Raghunath Date: Mon, 25 Feb 2019 01:21:02 +0530 Subject: [PATCH] github-management: add project board guidance --- github-management/org-owners-guide.md | 22 ++++++++++++++++++++++ 1 file changed, 22 insertions(+) diff --git a/github-management/org-owners-guide.md b/github-management/org-owners-guide.md index c626d5c40..09df20ada 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