Rewrite all github.com/magma/community documents and community-related documents in the magma repository.

[lucasgonze]

Most of the governance documents should live in the magma/community repository, not in the magma/magma repository, which is for code. However the community repo:

1. Has been archived since 2022
2. Hasn't been updated in a long time
3. Needs to host the charter

Tasks:

• [x] Unarchive
• [x] Check each document for stale data
• [ ] Update TSC membership listing
• [x] Migrate charter into this repository
• [ ] Move community-related documents in the magma repo to the community repo

[lucasgonze]

As I get deeper into the project I am rethinking it. The documents in the community repo are years behind the documents in the magma repo. What I should do is

1. review every community-related document in the magma repo
2. update the text of the README in the community repo to explain that the contents are useless
3. unarchive the community repo
4. verify that all files in the community repo also exist in the magma repo

[lucasgonze]

Review each of the following:

• [x] ../community/CODE_OF_CONDUCT.md

Dup of file in magma repo. Out of date. Proposed resolution: possibly this file, then rearchive community repo.

• [x] ../community/CONTRIBUTING.md

Dup of file in magma repo. Out of date. Proposed resolution: possibly this file, then rearchive community repo.

• [x] ../community/Governance.md

This file is missing from the magma repo. Maybe it should be copied over to that repo. (But first verify that this information isn't elsewhere already).

• [x] ../community/Organization_of_Work.md

Good information about project social structures. Should be part of governance documentation. Consolidate with info in community/Governance.md

• [x] ../community/README.md

• Check that this info is all in the magma/README.md file.

• Rewrite to explain that the community repo is no longer where these documents live.

• Rearchive community repo.

• [x] ../community/Reviewing.md

Self-evident information, probably from a very early stage of the project. Delete file before rearchiving.

• [ ] ../magma/CODE_OF_CONDUCT.md

Dup of file in magma repo. Out of date. Proposed resolution: possibly this file, then rearchive community repo.

• [x] ../magma/CONTRIBUTING.md

Badly broken. For some reason TSC governance information is in there. This needs a complete rewrite.

• [ ] ../magma/DCO.md

Merge this information into the README, then delete this file.

• [x] ../magma/README.md
• [ ] ../magma/REWARDS_PROGRAM.md

Rethink these items:

• Weighted Voting

• List Of Reward Eligible GIthub Issues

• [ ] ../magma/SECURITY.md

• Check that this is in sync with https://github.com/magma/magma/security/policy. Consider removing magma/SECURITY.md file to be sure they can't get out sync.

• Read the details to be sure they are still accurate

[lucasgonze]

Resolved: use a monorepo instead of a multirepo.

[lucasgonze]

Code of conduct files have only a trivial syntax difference.

[lucasgonze]

CONTRIBUTING.md:

• big differences between the repos
• the version in the magma repo is much more up to date
• version in the magma repo is badly broken. For some reason TSC governance information is in there. This needs a complete rewrite.

The goop in magma/CONTRIBUTING is the technical charter, as Kendall called it at the time. Need to figure out where that really goes.

Prior art for good CONTRIBUTING files:

• https://github.com/rails/rails/blob/main/CONTRIBUTING.md
• https://github.com/opengovernment/opengovernment/blob/master/CONTRIBUTING.md

[lucasgonze]

WTF: there also exists a repo called https://github.com/magma/Governance

[lucasgonze]

The state of this list is a mess. I need to re-review and document every item.

[lucasgonze]

Archived /magma/community repo

[lucasgonze]

All remaining items have been reviewed and either implemented or I have decided they were defined before I full understood the project structure.