Add decentralized repo ownership
- Dominant language
- Ruby
- Stars
- 126
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
It would be great if decentralized ownership could be added to this concept.
Approving merges to master using consensus instead of a single man's opinion.
Incentives and rough concept are described in my short paper: [Trust Issues In Open Source and NPM](https://docs.google.com/document/d/1tyJmNzVLVvNzJe1J0unFqawbuDKljYKzLg_H5nOqU7s/edit?usp=sharing)
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue names no files, tests, or entry points. Start by reading the linked paper and the repository's existing ownership and merge workflow documentation, then map the proposed consensus process to the current project design. Done would require an agreed, implementable decentralized ownership design rather than a general proposal.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, ruby
- Domain
- devtools, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100