Repository navigation
docs(roadmap): record the services considered and declined (#150) - #368
Merged
Merged
Conversation
`roadmap.md` already carries "Decided but not built", on the reasoning that an accepted ADR with nothing tracking it is indistinguishable from a rejected one after six months. This is the mirror of that: a service rejected for good reasons with nothing written down is indistinguishable from one nobody thought of, and gets proposed again, evaluated again, and possibly deployed on the second pass because the first pass left no trace. The shortlist that produced #129-#148 also produced rejections. Five of them are now recorded with what was actually weighed, so a later proposal argues with the reasoning rather than restarting from nothing: * Nextcloud — overlaps Immich, Paperless-ngx and file sync, and its app ecosystem is a second unpinned supply chain outside compose.yaml. Names Syncthing as what to evaluate if the want is sync, not a suite. * the *arr stack — five services with indexer credentials and standing outbound appetite, in the tier ADR-0008 defined as low consequence. * YunoHost-class installers — they own the compose file, the update path and often the proxy, which is the trade this repository exists not to make. * Guacamole — turns a browser session on Hicks into a path to every console, and stores the credentials to do it. There is a KVM in U6. * Authelia / Authentik — already decided by ADR-0008 and given an expiry by ADR-0022; listed only so the next shortlist does not present it as new. They are declines rather than bans, and the section says so: the *arr stack is "for now", Nextcloud names its alternative, and the SSO decline has a known end condition. Documentation only, which is what the issue asked for. Closes #150 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #150. Documentation only — no code changes, which is what the issue asked for.
Why
roadmap.mdalready carries "Decided but not built", on this reasoning:This is the same argument turned around. A service considered and rejected for good reasons, with nothing written down, is indistinguishable from one nobody thought of — and gets proposed again, evaluated again, and possibly deployed on the second pass because the first pass left no trace.
What
A new "Considered and declined" section, placed between "Decided but not built" and "Done", recording the five rejections that came out of the same shortlist as #129–#148:
compose.yaml— the same objection that rules out Home Assistant add-ons in #134Declines, not bans
The section says so explicitly, because the distinction is the whole value of writing them down:
make validatepasses.🤖 Generated with Claude Code