first draft of a written policy around git repos

[kuhnel]

Summary

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

[tonic]

This is just general comment as I want to read this and think a bit on it, but I think that any criteria about adding a repo should only be in the developer policy. The rest about what to do after, can remain in a separate document.

Tagging @lattner

[mehdi_amini]

llvm/docs/RepoPolicy.md

3 ↗

(On Diff #379401)

4 ↗

(On Diff #379401)

[kristof.beyls]

llvm/docs/RepoPolicy.md

17–18 ↗

(On Diff #379401)

is the URL ending in CONTRIBUTING.md the right URL for LICENSE.TXT here?
I guess that in special circumstances, there could be an exception for a repo to use a different license? E.g. it seems the existing https://github.com/llvm/bugzilla2gitlab and https://github.com/llvm/phabricator repos have different licenses?
I do agree that we should require a LICENSE.TXT or alternative mechanism to clearly document the license covering the repo.

30 ↗

(On Diff #379401)

s/provides/providers/?

[lattner]

This doc looks like a nice clarification, thank you for driving this!

llvm/docs/GettingInvolved.rst

22

Would it be problematic to expand this to GitRepositoryPolicy.md ?

[kuhnel]

addressed review feedback

[kuhnel]

Thx everyone for the reviews, I updated the proposal accordingly.

@tonic
Let me know if you want to see (parts of) this change moved to DeveloperPolicy.rst.
My rationale was: Keep info we only need a handful of times per year out of DeveloperPolicy.

llvm/docs/RepoPolicy.md

17–18 ↗

(On Diff #379401)

is the URL ending in CONTRIBUTING.md the right URL for LICENSE.TXT here?

Thx, was a copy-and-paste error

I guess that in special circumstances, there could be an exception for a repo to use a different license? E.g. it seems the existing https://github.com/llvm/bugzilla2gitlab and https://github.com/llvm/phabricator repos have different licenses?

Good point. I reworded to prefer the LLVM license but others are possible.

[tonic]

In D111723#3066546, @kuhnel wrote:

Thx everyone for the reviews, I updated the proposal accordingly.

@tonic
Let me know if you want to see (parts of) this change moved to DeveloperPolicy.rst.
My rationale was: Keep info we only need a handful of times per year out of DeveloperPolicy.

Sounds like Chris is fine with it, so I am too. I just wanted to make sure he saw the patch and had a chance to review.

llvm/docs/GettingInvolved.rst

.. toctree::
    CodeReview
    SupportPolicy
    SphinxQuickstartTemplate
    Phabricator
    HowToSubmitABug
    BugLifeCycle
    CodingStandards
    GitBisecting
+   GitRepositoryPolicy
 
 :doc:`Contributing`
    An overview on how to contribute to LLVM.
 
 :doc:`DeveloperPolicy`
    The LLVM project's policy towards developers and their contributions.
 
 :doc:`CodeReview`

 
 :doc:`CodingStandards`
   Details the LLVM coding standards and provides useful information on writing
   efficient C++ code.
 
 :doc:`GitBisecting`
   Describes how to use ``git bisect`` on LLVM's repository.
 
+:doc:`GitRepositoryPolicy`
+   Collection of policies around the git repositories.
+
 .. _development-process:
 
 Development Process
 -------------------
 
 Information about LLVM's development process.
 
 .. toctree::

llvm/docs/GitRepositoryPolicy.md

+# Policies on git repositories
+
+This document explains our current policies around git repositories. Everything
+not covered in this document 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 will be used for 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 `LICENSE.TXT`, preferably copy this from
+  [llvm-project](https://github.com/llvm/llvm-project/blob/main/LICENSE.TXT).
+  Other licences need to be discussed case-by-case.
+
+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 services
+reporting 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.