Architecture "Principles"

[Adam Kaplan]

I want to take a moment to discuss my thought process behind my "Architecture Principles" PR [1]. I plan to share similar ideas verbally during the community call tomorrow.

The current published architecture goals list [2] for Konflux is challenging to use. There are too many items for a single person to retain at any given moment, and their order is a bit haphazard. Moreover, "goals" does not adequately describe their purpose today. What may have been aspirations when the project began are now implemented solutions. The ideas within the top level goals are now the ground truth we use to evaluate future ideas and initiatives. In short, principles.

The PR addresses these concerns by structuring the current goals within six high-level principles. These high-level principles are deliberately short and memorable; any Konflux contributor should be able to recognize and reference them when evaluating an ADR, pull request, or other work within the community. The lower level "principles" provide specific examples or implementations.

As with anything else in life, principles are not meant to be static and sometimes conflict in specific situations. I hope that by structuring the architecture goals this way, we can have a more informed debate and discussion about Konflux's future direction.

Regards,

Adam

[1] https://github.com/konflux-ci/architecture/pull/333

[2] https://konflux-ci.dev/architecture/#architecture-goals

--

Adam Kaplan

He/Him

Senior Principal Software Engineer

Red Hat

100 E. Davie Street

adam....@redhat.com