Skip to end of banner
Go to start of banner

2024-08-07 Architectural Decision-Making Processes

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Translator


Date

Attendees 

Discussion items

TimeItemWhoNotes
1 minScribeAll

Jakub Skoczen is next, followed by Taras Spashchenko

Reminder:  Please copy/paste the Zoom chat into the notes.  If you miss it, this is saved along with the meeting recording, but having it here has benefits.

*Making architectural decisions of various scopesAllWe know that a project of this size is faced with architectural decisions of various sizes, ranging from things scoped very narrowly, which impact only one or a few modules/teams, to platform-wide decisions impacting almost everyone.  A one-size-fits all approach to making these decisions is unlikely to work well, and we've seen this already with the RFC process.  Let's enumerate the types/sizes of decisions we make, then try to identify the applicable processes for each.  If there are gaps, do we need to define additional processes or guidance for dev teams, and architects?
NAZoom Chat





  • No labels