Skip to content

Clarify TSC responsibilities/limitations in the TSC Charter #1756

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
+37 −1
Open

Clarify TSC responsibilities/limitations in the TSC Charter #1756

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
c7e32df
Clarify TSC responsibilities/limitations in the TSC Charter
jasnell Jun 30, 2025
0954e39
fixup! Update TSC-Charter.md
jasnell Jul 2, 2025
748ffc9
Update TSC-Charter.md
jasnell Jul 2, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
38 changes: 37 additions & 1 deletion TSC-Charter.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,8 @@
## Section 1. Guiding Principle

The Node.js project is part of the OpenJS Foundation. The project
operates transparently, openly, collaboratively, and ethically.
operates transparently, openly, collaboratively, and ethically, and in
close partnership with the OpenJS Foundation and the broader ecosystem.
Project proposals, timelines, and status must not merely be
open, but also easily visible to outsiders.

Expand Down Expand Up @@ -39,6 +40,7 @@ a voting TSC member to a regular TSC member.
In order to ensure adequate representation of the interests of diverse stakeholders,
no more than one-fourth of the TSC voting membership may be affiliated with the same
company/entity.

If a change in TSC voting membership or a change of affiliation by a TSC voting member
creates a situation where more than one-fourth of the TSC voting membership are
affiliated with the same company/entity, then the situation must be immediately remedied
Expand Down Expand Up @@ -74,9 +76,43 @@ including:
* Development process and any coding standards.
* Mediating technical conflicts between Collaborators or Foundation
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.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you please add "the project website and download server".

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Within this bullet point or a separate one? Also, "the project website" is fairly broad. Should we define that scope a bit more?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This reasonate with me:

* All infrastructure needed to support the development and distribution of the project, including the Website, CI infrastructure, Download service, etc.


The TSC will define Node.js project’s release vehicles.

### Exclusions and limitations of TSC responsibilities
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree


The Foundation handles all matters related to fundraising and financial
sponsorship on behalf of the project. The Foundation shall, on the project's
behalf, solicit funding and financial sponsorship for the Node.js project.

The TSC may not enter into any legal agreements.

Specific exclusions from the communication oversight responsibilities include:

* Brand marketing
* Fundraising and financial sponsorship of the project (including, but not
limited to, the OpenJS Foundation's own financial sponsorship of the project)
* Legal matters

All communication from the project touching on these topics must be reviewed
and approved by the Foundation.

All uses of OpenJS Foundation-owned trademarks and intellectual property by the
project are subject to the [OpenJS Foundation Trademark Policy](https://trademark-policy.openjsf.org/).
This includes use of any marks -- in full or in part -- in domain names, social
media account handles, event names and other similar identifiers.

The TSC may establish and administer project-specific communication channels,
such as social media accounts and discussion forums, administered under the
oversight of the TSC, subject to the above requirements. Should such channels
make any use of OpenJS Foundation-owned trademarks or intellectual property, the
channels must be capable of being administered jointly by both the TSC and the
Foundation.

## Section 5. Node.js Project Operations

The TSC will establish and maintain a development process for the
Expand Down