Introduce RFC as a Technical Standard to Manage Change#4
Draft
LBHSPreston wants to merge 1 commit intomainfrom
Draft
Introduce RFC as a Technical Standard to Manage Change#4LBHSPreston wants to merge 1 commit intomainfrom
LBHSPreston wants to merge 1 commit intomainfrom
Conversation
spikeheap
reviewed
Jan 30, 2025
Comment on lines
+1
to
+4
| --- | ||
| status: proposed | ||
| --- | ||
|
|
Contributor
There was a problem hiding this comment.
Suggested change
| --- | |
| status: proposed | |
| --- |
This was a mistake on my part. Adding the status means it ends up in the repository still saying proposed, or it needs to say accepted in the PR, which doesn't feel like it makes any sense either 🤷 .
I suggest we delete that bit from the template and just say anything in main is accepted, while anything in a branch is proposed.
We can deal with edge cases like revoking decisions if we ever end up with that complexity
stonest
reviewed
Jan 30, 2025
| ## Scope | ||
| - Changes to architecture such as database technologies, encryption methods, etc. | ||
| - Changes to programming patterns such as Event Driven Architecture | ||
| - Changes to a feature or implementation for a serfice that has moved from development to BAU. |
There was a problem hiding this comment.
Suggested change
| - Changes to a feature or implementation for a serfice that has moved from development to BAU. | |
| - Changes to a feature or implementation for a service that has moved from development to BAU. |
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
3 participants
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.
Introducing the RFC Standard
This is an RFC to introduce RFCs. At the moment we do not have a consistent way of recording decisions on Architecture (we previously used ADRs bit it feels limited in scope and doesn't cover all our scenarios), Processes or Technical Operations.
Use of RFCs will aid in recording and auditing decisions on changes to our architecture and technical ways of working including comments and contributions from colleagues.
Below is a preview of what the document currently looks like. This is likely to change a bit before we have the final version.