Skip to content

GOVERNANCE.md

Latest commit

 

History

History
144 lines (84 loc) · 8.72 KB

GOVERNANCE.md

File metadata and controls

144 lines (84 loc) · 8.72 KB

Node.js Web Team Governance

The Node.js Web Team (@nodejs/web) is a team in the Node.js Project that is composed by a set of subteams. Each containing specific responsibilities and goals.

Relationship with the TSC

The Website Team operates with significant autonomy for most website decisions, but must recognize the TSC's ultimate authority on matters affecting Node.js project representation, branding, and strategic partnerships.

Decision Authority Hierarchy

  1. Website Team Authority

    • Technical implementation details
    • User interface and experience design
    • Content organization and information architecture
    • Day-to-day maintenance and updates

  2. TSC Authority

    • Project-wide policies and governance
    • Strategic partnerships and representation
    • Major structural or navigational changes
    • Content that affects Node.js project positioning

Content Requiring TSC Approval

  • Statements on Sociopolitical Issues: Any content expressing positions on political, social, cultural, or humanitarian matters
  • Commercial Relationships and Endorsements: Any content establishing or promoting commercial partnerships, vendor preferences, or paid services related to Node.js

Website changes falling under these categories require formal TSC endorsement as outlined in the TSC Charter. Valid approval consists of at least one TSC member's explicit approval with no objections from any TSC members. This endorsement may be secured through either:

Handling TSC Feedback and Concerns

When TSC members express concerns about proposed changes:

  1. Documentation Requirement: Document all TSC feedback in the relevant issue or PR
  2. Hold Period: Pause implementation until concerns are addressed
  3. Resolution Process:
    • Seek clarification on specific concerns
    • Propose compromise solutions
    • Document resolution attempts and outcomes

Dispute Resolution Process

If disagreements arise between the Website Team and TSC regarding website changes:

  1. Escalation Path:

    • First attempt: Direct discussion on the PR/issue
    • Second attempt: Scheduled discussion in TSC meeting
    • Final resolution: Formal TSC vote if needed

  2. Implementation Requirements:

    • Changes with unresolved TSC objections must not proceed without formal TSC approval
    • When in doubt about approval status, seek explicit confirmation
    • Document the resolution and approval in the PR before merging

  3. Documentation Standard:

    • All significant disagreements and their resolutions must be documented
    • TSC approvals should be explicit and documented in writing
    • Approval pathways should be clear to all current and future contributors

Node.js Website Team (@nodejs/nodejs-website)

The Node.js Website Team is responsible for the day-to-day technical development of the Node.js Website. This is primarily the development of the website itself, adding new features, pages and components, but also fixing any security issues in the website code, handling operational maintenance, and so on.

The maintainers on the Node.js Website Team are responsible for steering the technical direction of the Node.js Website, and reserve the right to make final decisions on any issues or pull requests, in line with the Contribution Guidelines, Collaborator Guidelines, the Code of Conduct and the overall Governance premises of the Node.js project.

Members of this team are nominated through the guidelines provided in the Contributing Guidelines within this repository. After a passed nomination, members should submit a PR to add themselves to the list of current members, shown below.

Current Members

Node.js Web Infra Team (@nodejs/web-infra)

The Node.js Web Infra Team is responsible for maintaining the Infrastructure relating to Node.js's Web Presence. The Node.js Web Infra team has the responsibilities of:

  • Maintaining CI/CD pipelines related to Web Infrastructure
  • Maintaining our Infrastructure Providers*
  • Have technical ownership on best-standards and best-practices for our Web Infrastructure (such as Web Frameworks that we use)

Web Infra Team members should have access to be able to maintain the services mentioned above.

Members of this team are nominated either by the Node.js Technical Steering Committee (TSC) or the Node.js Build WG and follow the guidelines provided in the Collaborator Guidelines of the Node.js Build WG. Note that members of the Node.js Web Team might also recommend people for nomination.

* This team has access to infrastructure providers directly related to the Website only, such as Vercel. Other providers that are shared beyond the Website may be controlled by other teams (for example, the Node.js Build WG owns Cloudflare).

Node.js Web Standards Team (@nodejs/web-standards)

The Node.js Web Standards Team is composed of Node.js Collaborators and External Collaborators that have extensive experience or expertisè on Web Standards, such as Ecma262. The Standards Team is responsible for guiding and serving as points of contact when either Node.js Collaborators, the Node.js Technical Steering Committee (TSC), or the Web Team, requires assistance or guidance regarding Web Standards.

Members of this team are nominated by the Node.js Technical Steering Committee (TSC). Note that members of the Node.js Web Team might also recommend people for nomination.

Node.js UX & Design Team (@nodejs/ux-and-design)

The Node.js UX & Design Team is composed of Node.js Collaborators and External Collaborators that have experience or expertisè with UX & Design. The UX & Design Team is responsible for guiding and serving as points of contact when members of the Node.js Web Team require assistance or guidance regarding UX & Design.

Often members of this team will collaborate on providing best practices and guidelines for the Node.js Website, on matters of UX & Design. Members of this team are also responsible for providing feedback on the Node.js Website, and providing feedback on the Node.js Website's design. (For example, when a discussion arises regarding best practices on topics such as CSS, accessibility, UX flows and intent, or component design, the UX & Design Team has a say on the matter).

Members of this team are nominated by the Node.js Technical Steering Committee (TSC). Note that members of the Node.js Web Team might also recommend people for nomination.

The Interoperability of the Node.js Web Team

As seen above, the different teams under the Node.js Web Team umbrella are responsible for having the oversight on different aspects of Node.js's Web-related projects. However, it is important to note that the Node.js Web Team is not a set of siloed teams, but rather a set of teams that work together to achieve the same goal: Providing the best Web Experience for Node.js.

Following this line of thought, the Web Infra Team is responsible for the technical aspects of the Node.js Website (Infrastructure, Framework, CI/CD, etc); The Website Team is responsible for the day-to-day development of the Node.js Website; The UX and Design Team advise on Design Matters and the Web Standards Team advise on best-practices for Web APIs and Web Technologies/Standards.

But above all, the Web Team should work together to better the Web Experience for Node.js, aiming to provide the best experience for Node.js users.