Skip to main content
diff options
authorWayne Beaton2020-05-29 03:22:53 +0000
committerWayne Beaton2020-05-29 03:22:53 +0000
commit6ebc349743da39fcdb2016f51dd2ca43dd7ada78 (patch)
parent8b1262128ed30a400481ea08ace0dd290abde7a8 (diff)
Add description of GitHub project access.
1 files changed, 17 insertions, 0 deletions
diff --git a/source/chapters/resources.adoc b/source/chapters/resources.adoc
index ae3ef58..40d2f23 100644
--- a/source/chapters/resources.adoc
+++ b/source/chapters/resources.adoc
@@ -155,6 +155,23 @@ Click on the _Details_ link for more information. Committers must not merge comm
The Eclipse Webmaster creates and maintains a mirror of all GitHub-hosted repositories on Eclipse Foundation hardware.
+==== Access to GitHub Repositories
+All project committers have write access to their project's repositories on GitHub.
+To gain write access to a project's GitHub repositories a developer must:
+* Be <<elections-committer, elected>> as a project committer; and
+* Provide their Github Id in their <<contributing-account,Eclipse Foundation Account>>.
+To gain `admin` level access to their project's GitHub repositories, a project lead must {gitHubRequestUrl}[open a bug] against Community/GitHub. To be eligible to such permission level, the project must be in the mature phase and the request must be motivated; the project lead must explain why (on the bug) they need that access.
+Granting `admin` level access is a relatively new feature. By providing an explanation why the access isr required, it will help the Eclipse Foundation's Webmaster team better understand requirements and guide the evolution of this feature.
=== Issue Trackers

Back to the top