Explore Contributors, Trusted Committers, and Core Maintainers
In this three-part series, In continuation of my last article on InnerSource (busting the myths), I am presenting a new article that talks about:
- Various InnerSourcing roles and their responsibilities
So, let’s start.
For simplicity, I am considering an internal developer tooling platform as a central or core offering within an enterprise.
1. Contributors
These are the developers from various business units who use the developer tooling platform and contribute back improvements, fixes, and new features.
Contributors are the end-users and enhancers of the tooling platform. They represent the diverse needs of different business units and bring real-world usage experience back to the core platform through code contributions, bug reports, and feature requests.
Key Characteristics:
- Primary Identity: Business unit developers (mobile App team, Trade Booking team, data insights team, etc.)
- Engagement: Part-time, need-driven participation
- Motivation: Solve specific problems their teams are facing with the core platforms like language-specific SDKs or CI-CD template providers
Responsibilities:
- Tool Usage & Feedback: Use developer tools in their daily work and provide feedback on usability and functionality
- Bug Reporting: Identify and report issues encountered while using the platform tools
- Feature Contributions: Develop new features or improvements that benefit their business unit and potentially others (reusability)
- Documentation: Document use cases, create tutorials, and share best practices specific to their domain
- Testing: Validate new tool releases against their specific business unit’s requirements
- Community Participation: Share best practices and common use cases and assist others in the development community.
Examples of Contributions:
- Adding support for a new programming language to the CI/CD pipeline
- Contributors can spot and fix bugs in shared libraries, CLIs, or APIs they use
- Share native customisation with others having a similar use case (by contributing to the core tooling platform)
- Building monitoring dashboards specific to their service requirements.
- Developing IDE plugins that integrate with the core tooling platform
- Act as alpha testers for new tools or releases
- Add missing unit or integration tests for critical components
2. Trusted Committers
In InnerSourcing, decentralisation increases the pace of innovation. However, without quality gates or guardrails, that speed can compromise platform integrity. Trusted committers act as the glue, balancing openness with accountability. Their dual role as both contributors and gatekeepers makes them essential to the safe scaling process.
Trusted Committers are the technical mentors and quality guardians of the development tooling platform. They ensure that contributions from business units integrate seamlessly with the overall platform architecture while maintaining high standards and ensuring cross-team compatibility.
Key Characteristics:
- Primary Identity: Senior developers with platform expertise and cross-business unit perspective
- Engagement: Regular, sustained involvement with both the core platform and business unit contributors
- Motivation: Ensure platform quality remains intact while enabling business unit productivity at the same time
Responsibilities:
- Code Review & Integration: Review and approve merge requests from business unit contributors, ensuring code quality and platform compatibility
- Cross-Team Mentoring: Guide developers from different business units on how to effectively contribute to and use the platform
- Platform Evangelism: Promote adoption of tooling platform across business units and gather requirements from different teams
- Quality Assurance: Ensure that new features and changes don’t break existing functionality used by other business units
- Knowledge Translation: Bridge technical gaps between business unit-specific needs and platform architecture
- Release Management: Coordinate releases and communicate changes across business units
Examples of Activities:
- Reviewing a mobile team’s contribution to adding iOS-specific testing capabilities
- Helping define or update CI/CD workflows if needed (e.g., for new modules or components)
- Ensuring that the web team’s authentication integration doesn’t impact other teams’ deployments
- Organising cross-team workshops on new platform features
- Validating that a new CI/CD feature works across different technology stacks
- Create and update clear contribution guidelines, templates, and documents
3. Core Maintainers
If trusted committers are the gatekeepers of quality, core maintainers are the long-term stewards of direction, architecture, and evolution. They sit at the intersection of product strategy, developer experience, and technical governance (picture below).
In an InnerSourced ecosystem, where many teams may contribute to shared tooling, core maintainers provide the continuity and technical backbone that keeps things scalable. In other words, they balance the diverse needs of all business units while maintaining platform coherence and long-term sustainability.
Key Characteristics:
- Primary Identity: Platform architects and strategic technical leaders that have a historical and holistic context of the overall platform
- Engagement: Full-time focus on platform strategy, architecture, and governance
- Motivation: Create a unified, scalable tooling ecosystem that serves the entire organisation
Responsibilities:
- Platform Strategy: Define the long-term roadmap and architectural vision for the development tooling platform
- Architecture Governance: Make decisions about technology choices, integration patterns, and platform boundaries
- Cross-Business Unit Coordination: Work with business unit leaders to understand strategic requirements and align platform capabilities
- Scalability & Performance: Ensure the platform can handle growth in users, workloads, and complexity across all business units
- Security & Compliance: Maintain platform security standards and ensure compliance requirements are met organisation-wide
- Vendor & Technology Management: Evaluate and integrate third-party tools, manage licenses, and make build-vs-buy decisions.
- Platform Operations: Oversee platform reliability, monitoring, and incident response
Examples of Activities:
- Choosing between Kubernetes and alternative container orchestration platforms
- Defining API standards for how business unit tools integrate with the platform
- Establishing security protocols for cross-business unit data access
- Planning migration strategies when updating core platform components
- Deciding whether to build custom solutions or adopt enterprise vendor tools
- Setting platform SLAs and defining support models for business units
- Identify and grow new trusted committers from the contributor base
- Participate in incident reviews when platform failures trace back to tooling issues
Summarising the three InnerSorcing roles visually:
Other Posts about InnerSourcing: Busting myths about InnerSourcing
Leave a Reply