https://github.com/radicle-dev/radicle-decisions
Radicle Developers of All Countries, Unite!
https://github.com/radicle-dev/radicle-decisions
Last synced: 11 months ago
JSON representation
Radicle Developers of All Countries, Unite!
- Host: GitHub
- URL: https://github.com/radicle-dev/radicle-decisions
- Owner: radicle-dev
- Created: 2020-01-31T15:20:55.000Z (over 6 years ago)
- Default Branch: master
- Last Pushed: 2021-04-06T14:40:10.000Z (about 5 years ago)
- Last Synced: 2023-06-12T01:25:58.617Z (about 3 years ago)
- Language: Shell
- Size: 31.3 KB
- Stars: 17
- Watchers: 13
- Forks: 2
- Open Issues: 2
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# radicle-decisions
**Radicle Developers of All Countries, Unite!**
## What is this?
`radicle-decisions` is the home for our proposed decisions that have been
scrutinised by our team of developers.
_Accepted decisions_ are expected to be adhered to and practiced throughout the
`radicle-dev` organisation.
_Rejected decisions_ will be be left as a trace to what we have proposed and why
it was ultimately rejected.
## Proposals
### Requirements
The proposal process is meant to drive cross-cutting engineering improvements
across Radicle. We want the bar for a proposal to be as low as possible - to
encourage positive change and alignment among engineers. Therefore we see any
proposal as valid as long as an engineer inside of Radicle sees the need to
formalise or decide on a certain aspect of development. It can, but doesn't
need to originate from a discussion on
[radicle.community](https://radicle.community). A discussion should be lifted
into a proposal when enough added benefit has surfaced.
### Common decision to capture
* programming techniques
* architecture changes/patterns
* tools and dependency recommendations
* ecosystem
### Process
* Open a PR with a new proposal copied from the [template](https://github.com/radicle-dev/radicle-decisions/blob/master/proposals/0000-template.md)
* Assign yourself - as the assignee is in charge to see the proposal through
* Request `radicle-dev/engineering` as reviewers
* Announce new proposal in the [development
section](https://radicle.community/c/development-discussion/9)
* Keep the conversation in the PR to not lose information
* Incorporate feedback
* Get quorum for approval