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. 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
• 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
• Keep the conversation in the PR to not lose information
• Incorporate feedback
• Get quorum for approval