Skip to main content
A collaborator of the Node.js website repository is a member of the Node.js Website Team. The Website Team is responsible for the technical development of the Node.js website.
Regular contributors do not need to become collaborators. Any contribution is appreciated, and collaborator status is a formality that comes with obligations. You can make meaningful contributions without ever becoming a collaborator.

Prerequisites

To be considered for collaborator status, you should have:
  • Significant knowledge of modern web technologies
  • Understanding of web standards
  • An active contribution history to the repository

Application process

If you are an active contributor and want to become a team member, contact one of the existing Website Team members for guidance.
1

Get nominated

Nomination must be done by an existing Website Team member via a GitHub Issue. You cannot nominate yourself.To be eligible for nomination:
  • You must be actively contributing to the repository.
  • Your contributions must include significant code reviews or code contributions.
2

Nomination issue is created

The nominating team member opens a GitHub Issue that includes:
  • An explanation of why the nominated person is a good addition to the team
  • Links to relevant contributions, such as:
    • Code reviews
    • Comments on issues and pull requests
    • Pull requests or issues authored
    • Comments or posts in Discussions
3

Approval period

The nomination issue must remain open for at least 72 hours with no objections.For the nomination to be approved:
  • At least three existing Website Team members must agree (via comments or 👍 reactions).
  • All objections must be resolved before proceeding.
  • Objections from TSC members or Core Collaborators are valid and must be resolved.
4

Added to the team

Once the approval conditions are met, you are added to the Website Team and become a collaborator with the associated responsibilities.

Maintaining collaborator status

Once you become a collaborator, you are expected to maintain your status by meeting the following requirements.

Policy adherence

Activity requirements

  • Author at least one commit in the past twelve months.
  • Engage actively in project discussions and code reviews.

Consequences of inactivity

Collaborators who have been inactive for more than twelve months may be removed from the active collaborators list.
  • Removal: Collaborators inactive for more than twelve months may be removed.
  • Reinstatement: Removed collaborators can return through the same nomination and approval process upon resuming active participation.
  • Policy violations: Violations of the moderation policy or Code of Conduct may result in immediate removal, depending on severity and a TSC decision.

Build docs developers (and LLMs) love