[PATCH] D111723: first draft of a written policy around git repos

[Christian Kühnel via Phabricator via llvm-commits]

kuhnel created this revision.
kuhnel requested review of this revision.
Herald added a project: LLVM.
Herald added a subscriber: llvm-commits.

This is a frist draft of a set of policies around new git repos and how we grant write access to our GitHub organisation.

This proposal is based on the discussions in:
https://github.com/llvm/llvm-iwg/issues/40
https://github.com/llvm/llvm-iwg/issues/51


Repository:
  rG LLVM Github Monorepo

https://reviews.llvm.org/D111723

Files:
  llvm/docs/GettingInvolved.rst
  llvm/docs/RepoPolicy.md


Index: llvm/docs/RepoPolicy.md
===================================================================
--- /dev/null
+++ llvm/docs/RepoPolicy.md
@@ -0,0 +1,36 @@
+# Policies on git repositories
+
+This document explains our current policies around git repositires. Everything
+not covered in this documents is most likely a case-by-case decision. In these
+cases please create an issue with the
+[Infrastructure Working Group](https://github.com/llvm/llvm-iwg/issues).
+
+## New GitHub repositories
+
+Requirements for *new* repositories as part of the
+[LLVM organisation on GitHub](https://github.com/llvm):
+
+* The repo is used from something related to the LLVM ecosystem or community.
+* The repo contains a `README.md` explaining the contents.
+* The repo contains a `CONTRIBUTING.md`, ideally copy this from
+  [llvm-project](https://github.com/llvm/llvm-project/blob/main/CONTRIBUTING.md).
+* The repo contains a copy of the `LICENSE.TXT` from
+  [llvm-project](https://github.com/llvm/llvm-project/blob/main/CONTRIBUTING.md).
+
+If you want to integrate your project as part of the Monorepo, please take a
+look at the
+[Developer Policy](DeveloperPolicy.html#adding-an-established-project-to-the-llvm-monorepo>).
+
+To request a new repository, please create an issue with the
+[Infrastructure Working Group](https://github.com/llvm/llvm-iwg/issues).
+
+## Repo access on GitHub
+
+Some 3rd party applications require write access to our GitHub organisation in
+order to work properly. Typical examples are continuous integration provides
+that report build results back to GitHub. We consider granting access to such
+application if they provide benefits to the LLVM community and do not raise
+privacy or security concerns.
+
+To request access please run an RFC on the mailing list and get community
+feedback.
Index: llvm/docs/GettingInvolved.rst
===================================================================
--- llvm/docs/GettingInvolved.rst
+++ llvm/docs/GettingInvolved.rst
@@ -19,6 +19,7 @@
    BugLifeCycle
    CodingStandards
    GitBisecting
+   RepoPolicy
 
 :doc:`Contributing`
    An overview on how to contribute to LLVM.
@@ -54,6 +55,9 @@
 :doc:`GitBisecting`
   Describes how to use ``git bisect`` on LLVM's repository.
 
+:doc:`RepoPolicy`
+   Collection of policies around the git repositories.
+
 .. _development-process:
 
 Development Process


-------------- next part --------------
A non-text attachment was scrubbed...
Name: D111723.379401.patch
Type: text/x-patch
Size: 2394 bytes
Desc: not available
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20211013/2cb4fe0e/attachment.bin>