Document the requirements and expectations of a repo under the `haskell` organisation

[mpickering]

It seems that this discussion has already taken place in haskell/core-libraries-committee#43 but isn't documented yet. Can someone take a lead in writing the documentation for this or delegating? According to #1 it is the Haskell Foundation who owns this namespace so can @jmct take responsibility for delegating this task?

---

I was wondering about what the process of adding a new repo to the haskell organisation was.

• How does a repo get added to the haskell organisation?
• Who do you ask to get a repo added to the organisation?
• What are any requirements or expectations of maintainership of repos in the organisation?
• What are the expectations of communication (for example, https://haskell.foundation/guidelines-for-respectful-communication/)?

It would also be good to clarify in the README what the difference between this repo and

• Haskell Foundation repo: https://github.com/haskellfoundation/
• Haskell Github Trust: https://github.com/haskell-github-trust

---

My personal opinion:

• haskell organisation should be only for actively maintained and vibrant projects, I agree with Richard about it being a showcase.
• Packages on life support should be placed in haskell-github-trust (which is like rust-unofficial)