Open Source Contribution Pattern
In the open source contribution pattern, teams are given responsibility for developing specific architectural components but are not expected to be the only contributing developers. When this pattern works well, a team will act as a benevolent dictator over their components, reviewing submitted changes to a component for quality and conceptual integrity. This pattern allows for limited centralized control across the architecture. Use this pattern when there are experts available from multiple development teams or when there is a common dependency on specific components.
For this pattern to be successful, teams must know they are responsible for specific components and have a firm understanding of where their ...
Get Design It! now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
