EFI: Update projects rules

[sheplu]

Motivation

The TC operates in constraints fixed by the OpenJS Foundation and needs to follow some global rules and requirement. A quick check of all documents like charters, bylaws, roles, CoC, Contributing should be verified to see if they need to be updated.

Expectation

Be compliant with all expectations of a large Open Source Project, and be certain that functioning processes are in place if they are needed. To simplify all the update, maybe move all document to an admin repo and update all readme to link to it

Implementation

Check all documents, review wording and scope
Validate that all emails and links are valid
Review with the Foundation and CPC that the guidelines are followed

Status

Part: Organization
Status:

• Review Charter:
• Review CoC:
• Review Contributing:
• Move all global document out of the express repository:
• Expectation "At Large" project from OpenJS Foundation/CPC

Draft

The TC operates in constraints fixed by the OpenJS Foundation and needs to follow some global rules. One of the first actions is to review all charters and bylaws to ensure a full adherence with the Foundation while allowing the TC to move faster.
This would include, but not limited to
Organization charters / bylaws
TC scope and capabilities
Code of Conducts
Branding, naming
Links / relationship with the OpenJS foundation
Security rule

[jonchurch]

The Nativescript Governance doc is really good! If a bit stodgy! Apparently it is based off of Node.js'

https://github.com/NativeScript/management/blob/master/nativescript-governance.md#governance

What I like about it is how it clearly outlines the different roles, their permissions, their expectations, and the process involved in becoming each type of member.

[crandmck]

Move all global document out of the express repository:

Note that the contents of Contributing.md, Collaborator-Guide.md, and Security.md are duplicated into https://github.com/expressjs/expressjs.com/blob/gh-pages/en/resources/contributing.md via the script at
https://github.com/expressjs/expressjs.com/blob/gh-pages/get-contributing.sh... And the page is published to https://expressjs.com/en/resources/contributing.html.

So this script will just need to be updated for the new locations, then re-run, and the updated file committed to the expressjs.com repo.

At some point, it would be better to make this into a GH action (as well as the get-readmes.sh script) but that can come later.

Oops, I just noticed expressjs/admin#2 so I'll note this there as well.

[wesleytodd]

Yeah these were intended as tracking issue initially but I think we should close them in favor of concrete discussion issues once those are made. The tracking issues were just to see the conversations and make sure we didn't loos track of any work in the process.