1# Policies on git repositories 2 3This document explains our current policies around git repositories. Everything 4not covered in this document is most likely a case-by-case decision. In these 5cases please create an issue with the 6[Infrastructure Working Group](https://github.com/llvm/llvm-iwg/issues). 7 8## New GitHub repositories 9 10Requirements for *new* repositories as part of the 11[LLVM organisation on GitHub](https://github.com/llvm): 12 13* The repo will be used for something related to the LLVM ecosystem or community. 14* The repo contains a `README.md` explaining the contents. 15* The repo contains a `CONTRIBUTING.md`, ideally copy this from 16 [llvm-project](https://github.com/llvm/llvm-project/blob/main/CONTRIBUTING.md). 17* The repo contains a `LICENSE.TXT`, preferably copy this from 18 [llvm-project](https://github.com/llvm/llvm-project/blob/main/LICENSE.TXT). 19 Other licences need to be discussed case-by-case. 20 21If you want to integrate your project as part of the Monorepo, please take a 22look at the 23[Developer Policy](project:DeveloperPolicy.rst#Adding an Established Project To the LLVM Monorepo). 24 25To request a new repository, please create an issue with the 26[Infrastructure Working Group](https://github.com/llvm/llvm-iwg/issues). 27 28## Repo access on GitHub 29 30Some 3rd party applications require write access to our GitHub organisation in 31order to work properly. Typical examples are continuous integration services 32reporting build results back to GitHub. We consider granting access to such 33application if they provide benefits to the LLVM community and do not raise 34privacy or security concerns. 35 36To request access please run an RFC on the mailing list and get community 37feedback. 38