GitPlanet

Cheap and reliable Node.js hosting starts at $3/month, and $1/month static HTML hosting

Created with love in Canada, visit hostnodejs.com today

Feel like to post an Ad? Learn Details
All Projects → ssb-js → ssb-js

ssb-js / ssb-js

Licence: other
Governance repository for the SSB-JS organization.

Labels

governancessbssb-js

Projects that are alternatives of or similar to ssb-js

gobyte
GoByte Core - GBX
Stars: ✭ 35 (+133.33%)
Mutual labels:  governance
Meta
Discussions around the processes and coordination of the Bitcoin Design Community
Stars: ✭ 120 (+700%)
Mutual labels:  governance
governance-crosschain-bridges
This repo contains the crosschain governance bridges used for the aave markets deployed across different networks
Stars: ✭ 116 (+673.33%)
Mutual labels:  governance
test-infra
Falco workflow & testing infrastructure
Stars: ✭ 18 (+20%)
Mutual labels:  governance
poa-network-consensus-contracts
Main repository for POADAO consensus. Includes contracts for Initial Ceremony, Governance, Management of Validators
Stars: ✭ 68 (+353.33%)
Mutual labels:  governance
opengovernance.dev
opengovernance.dev
Stars: ✭ 29 (+93.33%)
Mutual labels:  governance
compound-governance-examples
Examples for building on Compound Protocol Community Governance.
Stars: ✭ 52 (+246.67%)
Mutual labels:  governance
ssb-graphql
GraphQL server for Scuttlebot
Stars: ✭ 18 (+20%)
Mutual labels:  ssb
poa-dapps-voting
POA Network Governance Dapp
Stars: ✭ 24 (+60%)
Mutual labels:  governance
Community
Istio governance material.
Stars: ✭ 2,228 (+14753.33%)
Mutual labels:  governance
aragon-wiki
The Aragon wiki
Stars: ✭ 76 (+406.67%)
Mutual labels:  governance
foundation
Interactions with the CDF Staff and Board
Stars: ✭ 20 (+33.33%)
Mutual labels:  governance
devops-governance
Example end-to-end Governance Model from CI/CD to Azure Resource Manager. Use this project to deploy example AAD, ARM and Azure DevOps resources to learn about e2e RBAC.
Stars: ✭ 79 (+426.67%)
Mutual labels:  governance
AIPs
Ampleforth Improvement Proposals
Stars: ✭ 20 (+33.33%)
Mutual labels:  governance
ssb-ref
check if a string is a valid ssb-reference
Stars: ✭ 14 (-6.67%)
Mutual labels:  ssb
Governance-Account
基于智能合约开发，提供区块链用户账户注册、私钥重置、冻结、解冻等账户全生命周期管理，支持管理员、阈值投票、多签制等多种治理策略。
Stars: ✭ 17 (+13.33%)
Mutual labels:  governance
about
Home to all of our staff information, decision-making rules and processes. It is our staff manual that can be developed collaboratively with the community and reused by everyone.
Stars: ✭ 26 (+73.33%)
Mutual labels:  governance
productivity-tools
List of popular productivity tools for SharePoint
Stars: ✭ 26 (+73.33%)
Mutual labels:  governance
collective
How the unified collective is governed
Stars: ✭ 41 (+173.33%)
Mutual labels:  governance
Jupiter
Jupiter是斗鱼开源的面向服务治理的Golang微服务框架
Stars: ✭ 3,455 (+22933.33%)
Mutual labels:  governance
View All Similar Projects ➔

SSB-JS

⚠️ 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.

History

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.

Projects

Maintainers

2020

  • @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

Process

  • 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.

Repositories

  • 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

  • Projects SHOULD be written in JavaScript or TypeScript.
  • Projects SHOULD have internally consistent code style.
  • 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

  • '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

  • '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.

Governance

  • 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.
Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].