TC Charter

[jonchurch]

An expectation of expressjs/discussions#169 (Define Technical Committee role) is

Charter for the TC and specific part for processes that could involve the TC, for example nominating new TC members, appointing a Captain or creating a Working Group.
This would also include role of the TC at a more global scope, for example CPC representation

I don't think we've addressed this directly yet, so here is a draft to do so.

With this, I am requesting input or direct pushes to this branch (I am turning on Allow Edits from Maintainers to allow pushing to my fork). The sections in this doc are my opinion of what are required to document the TC process to the satisfaction of the EFI section Define Technical Committee Role. Missing from that EFI doc is language around Working Groups and Project Captains.

Specifically I've left blank:

• Governance Structure
• Decision making process (lifted langauge from Contributing.md, still open for improvement)
• Change Management (removed this as it's vague and covered by Amendments)
• Amendments to the charter (lifted some language from Charter.md, still open for improvement)
• CPC Representation

[wesleytodd]

This is great! One thing I was thinking is that we have too many docs in this repo already for project governence beyond just this repo. I know this is the "central" place but I think to reduce noise and stuff maybe we should keep source documents in the discussions repo and have the ones in here be more like a "hub" and not contain the whole content?

What do you think about that? It would really help reduce the release notes for the main package not contain commits for "add triager" or "add TC member".

[jonchurch]

@wesleytodd

maybe we should keep source documents in the discussions repo and have the ones in here be more like a "hub" and not contain the whole content?

That is captured as a proposed solution in the EFI doc "Update Project Rules" expressjs/discussions#170 and I think it makes sense. Calling it an implementation detail for now though! I want to get feedback/edits on this doc, but don't care what repo it ends up landing in 👍

I agree with the sentiment, we currently have these markdown docs in the repo even before adding another:

• Charter.md
• Code-Of-Conduct.md
• Collaborator-Guide.md
• Contributing.md
• History.md
• Readme-Guide.md
• Readme.md
• Release-Process.md
• Security.md
• TC-Charter.md
• Triager-Guide.md

Thats a lot!

[wesleytodd]

Yeah it is a lot! That is exactly why seeing this triggered me to ask if we could move it over instead. I agree we can have the discussion anywhere but if we are going to land it there in the end it might be nice to start there so we don't have the history in a different repo.

[wesleytodd]

@jonchurch can you redirect this PR at the new expressjs/admin repo?