golem-architecture

Abstract

We are introducing a Golem Amendment Proposal process to establish governance over changes proposed, considered and implemented in Golem ecosystem.

Motivation

The GAP process responds to a number of needs:

Establish governance over features, specification/standards amendments and process improvements managed by Golem Factory.
Ensure visibility of features in the Golem pipeline - this is especially valuable for interested parties outside of Golem Factory.
Open the path to provide ability for Golem community to submit proposals for features in a controlled, systematic manner.

Specification

GAP content & format

A GAP shall be raised as a pull request in golem-architecture repo titled along the lines of GAP-draft Title, including all the relevant artifacts (eg. GAP summary).
A GAP summary gap-draft_title.md shall be provided (following a template) in ./gaps/gap-draft_title/.
The GAP pull request shall be included in GAP project.

GAP workflow

gap workflow

Rationale

The GAP process template has been designed on the basis of Ethereum’s EIP template - as we feel that template ensures the right level of proposal specification details relevant for Golem ecosystem.

Backwards Compatibility

As currently there is no (semi)formal process for governance of Golem feature and change proposals - no backward incompatibilities are introduced.

Test Cases

N/A

Security Considerations

All GAPs must contain a section that discusses the security implications/considerations relevant to the proposed change. Include information that might be important for security discussions, surfaces risks and can be used throughout the life cycle of the proposal. E.g. include security-relevant design decisions, concerns, important discussions, implementation-specific guidance and pitfalls, an outline of threats and risks and how they are being addressed.