Clarify TSC responsibilities/limitations in the TSC Charter

[jasnell]

Alternative to #1754 that represents the text and coverage that I would like to see updated in the charter. The other PR is getting confusing with multiple edits and I want to make sure that the changes I would like to see are clear/distinct.

Obviously, everything here would also need to be reviewed and approved by the CPC/Foundation

Most of this is likely better handled at the CPC level, but there are a few TSC members who are insisting that some governance changes need to be made/clarified so this is my attempt at such clarification.

[rginn]

We share the goal of technical accuracy. While we may not write code commits, technical marketing and communications are also technical disciplines, just applied differently. The OpenJS executive and marketing teams bring over 20 years of experience supporting open source release communications, security disclosures, and a variety of blog content in close collaboration with OSS projects, including the Node.js TSC and maintainers. Our focus is on making sure communications are accurate, clear, and accessible, and we aim to support contributors, not override them.

I like how this is coming together in this PR. I would add “...in collaboration with the OpenJS Foundation” to the charter update to reflect how we’ve worked better together on all things Node.js.

[mcollina]

I really think this should be part of the CPC set of documents for all projects.

[jasnell]

I agree

[jasnell]

@mcollina ... what are the next steps on this one? I assume that a proposal would need to be made to the CPC to include these?

[mcollina]

Yes. I think this change would need to go in https://github.com/openjs-foundation/cross-project-council/blob/main/CPC-CHARTER.md#section-6-non-responsibilities-of-the-cpc.