Having a repo for the wider community

[vmx]

This repository contains valuable information for the whole ecosystem. Things like the Coding Guidelines of the Code of Conduct or information about licensing applies to other projects like IPLD and libp2p as well.

When I add some information for IPLD, I just link to the documents in this repository. I don't want to duplicate all those documents, just for the sake of having them in the IPLD namespace. Though I think it's confusing to always have references to IPFS.

Hence I propose creating a separate umbrella org that contains all that great information, so that it can be used by others as well.

[raulk]

Can that umbrella org be https://github.com/protocol?

Edit: while there are fairly common denominators that we could factor out, I specifically disagree that coding guidelines are in that category.

[mikeal]

While I am normally all for the idea of consolidating information, I think the best thing to do here is to have each project copy and modify these in the their own org and to stop applying the IPFS guidelines to other projects until they are copied over.

If we want these projects to have independent identities then we can't consolidate information in a company specific location.

We also want to give the entire contributorship of a project ownership over these policies and the best way to make that clear is to have each org own their own policies.

[DonaldTsang]

@mikeal I would add that cultures and customs differ from place to place, such that there is no one-size-fits-all solution to everything. Not just from an autonomy sense but a practical one.