Page History

We have RFCs for proposing and recording significant changes to Geode. But those only cover the span of time between the software's open-sourcing we only started writing those in spring of 2019. Geode was open sourced in 2015-2016 and now.The the software on which Geode it is based was already mature by then. mature over a decade before that! On what guiding principles is that this software based?

Well, the agilist would say: read the code. That answer is unsatisfactory if we want our project to be inviting to new contributors. There's just to much code for that answer to be practical.

...

Architecture Decision Records look good: https://adr.github.io

Relationship to RFCs

We have RFCs (see Project Proposals and Specifications) for deliberating on changes to the software. But that process and structure is not appropriate for capturing the corpus of past architectural decisions embodied in the software. As we expose more of these legacy decisions we expect we'll want to change some of them. That should yield new RFCs. In the end though, both RFCs and Guiding Architectural Principles (GAPs?) may be useful to keep around. The former is a vehicle for change. The latter is a description and explanation of the current state.