⚠️ On May 2022, staltz, arj03 and mixmix (the only active members of ssb-js) decided to disband SSB-JS and move the repos back to SSBC. See a thread on SSB about the decision: %1NtrLWhxeuHr03NRoyriInzLSvPVn7fkiZ6C61PPhVo=.sha256.

The following text reflects the old rules for this GitHub org.

The SSBC is a structureless organization that doesn't adaquately serve the needs of participants in the Scuttlebutt ecosystem. The SSB-JS namespace is an attempt to build a healthy organization with reliably maintained software.

Healthy organizations have healthy governance, which requires decision-making and conflict-resolution practices available to all members. Most decisions should be made organically from the bottom up, but decisions that change the SSB-JS organization require discussion and consent.

• Chloride
• Multiserver
• MuxRPC
• SSB-Keys
• SSB-Ref
• SSB-Validate
• Secret-Stack

• @arj03 -- Multiserver, SSB-Ref, and SSB-Validate
• @christianbundy -- Multiserver, MuxRPC, and SSB-Validate
• @mixmix -- Chloride, SSB-Ref, and Secret-Stack
• @soapdog -- MuxRPC and SSB-Keys
• @staltz -- Chloride, SSB-Keys, and Secret-Stack

• The key words "MUST", "MUST NOT", "REQUIRED", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.

• There MUST be one Git repository for governance and one for each project.
• The 'SSB-JS namespace' refers to the SSB-JS organizations on GitHub and npm.
• The SSB-JS namespace MUST be read-only unless specified otherwise.
• Repositories and build artifacts must be hosted in the SSB-JS namespace.
• Repositories MUST have a 'main' branch.
• Repositories SHOULD NOT have any other branches.
• Repositories MUST allow project discussions via issues.
• Repositories MUST allow patch proposals via pull requests.
• The latest commit on the 'main' branch SHOULD always be versioned and released on npm.

• Projects SHOULD be written in JavaScript or TypeScript.
• Projects SHOULD have internally consistent code style.
  • Projects SHOULD follow the default Prettier rules.
  • Projects SHOULD follow the recommended ESLint rules.
• Projects SHOULD have documentation of all public APIs.
• Projects SHOULD have automated tests for all target platforms.
• Projects SHOULD have internally consistent contribution guidelines.

• 'Contributors' are anyone who participates in a project.
• Contributors MUST read a project's CONTRIBUTING.md before submitting a pull request.
• Contributors interested in seeing their pull requests merged SHOULD update their pull requests when maintainers identify blocking concerns.
• Contributors MUST aim to foster an open, welcoming, and harassment-free space.
• Contributors SHOULD recommend changes in the form of patches.
• Contributors who want to be maintainers SHOULD participate consistently and often.

• 'Maintainers' are contributors trusted to steward a project and vote.
• Maintainers MUST have the 'owner' role on GitHub and NPM.
• Maintainers MUST have 2FA enabled on GitHub and NPM.
• Maintainers SHOULD communicate in a project's CONTRIBUTING.md how contributors can get started and what is expected in a pull request.
• Maintainers SHOULD communicate in the project's CONTRIBUTING.md what types of changes in a project pull request are frequently blocked from merging.
• Maintainers SHOULD review and merge outstanding patches for the project they maintain.
• Maintainers MAY review and merge patches for other projects.
• Maintainers SHOULD NOT merge their own pull requests.
• Maintainers SHOULD aim to make contributing a fun and simple experience.
• Maintainers SHOULD merge project pull requests in a fast and friendly manner.
• Maintainers SHOULD NOT suggest non-blocking changes on project pull requests.
• Maintainers SHOULD close pull requests that are outdated in comparison to the main branch.
• Maintainers SHOULD invite high-quality contributors to become maintainers.
• Maintainers SHOULD remove anyone who fails to apply this process.

• The governance repository MUST be hosted at https://github.com/ssb-js/ssb-js.git.
• Roles and repositories in the SSB-JS namespace MUST match the governance repository.
• Activity in the SSB-JS namespace MUST apply the process from the governance repository.
• Patches to the governance repository MUST NOT be merged unless the latest commit on a pull request is approved by ⅔ of active maintainers.
• If there are no active maintainers because their term expired, the previous cohort should be considered 'active maintainers' for the purposes of voting.
• Maintainers MUST merge governance patches that are approved.
• Maintainers MUST NOT merge governance patches that are not approved.