Clarify TSC responsibilities/limitations in the TSC Charter #1756
Conversation
|
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. |
jasnell
force-pushed
the
jasnell/clarifying-tsc-responsibilities
branch
from
bdbdb89 to
0954e39
Compare
|
|
||
| The TSC will define Node.js project’s release vehicles. | ||
|
|
||
| ### Exclusions and limitations of TSC responsibilities |
There was a problem hiding this comment.
I really think this should be part of the CPC set of documents for all projects.
| * Establishing guidelines for communication by project contributors about the | ||
| technical development processes of the project, releases and release announcements, | ||
| technical documentation, contributor onboarding and conduct, project governance, | ||
| and technical direction. |
There was a problem hiding this comment.
Can you please add "the project website and download server".
There was a problem hiding this comment.
Within this bullet point or a separate one? Also, "the project website" is fairly broad. Should we define that scope a bit more?
There was a problem hiding this comment.
This reasonate with me:
* All infrastructure needed to support the development and distribution of the project, including the Website, CI infrastructure, Download service, etc.
Co-authored-by: Nick Schonning <nschonni@gmail.com>
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.