Create governance models and structures for open source projects with team-specific templates for small, medium, and large teams, including NASA/government compliance guidance
This skill helps establish clear governance structures for open source projects, particularly those sponsored by government organizations like NASA. A well-defined governance model ensures transparency, encourages contributions, maintains technical standards, and provides clear decision-making processes.
The skill provides three specialized governance templates optimized for different team sizes and organizational complexity, each designed to foster healthy open source communities while meeting institutional requirements.
When to Use This Skill
Starting new open source projects that need governance structure
Converting private projects to open source with proper governance
Establishing team roles and decision-making processes
Meeting compliance requirements for government-sponsored projects
Scaling team governance as projects grow
Related Skills
Clarifying contributor pathways and responsibilities
Setting up transparent development processes
Team Size Assessment Guide
Before selecting a template, assess your team size and organizational needs:
Small Teams (2-5 active contributors)
Characteristics:
Direct communication between all members
Simple decision-making process
Minimal bureaucracy needed
Close collaboration on most decisions
Limited formal roles required
Best for: Early-stage projects, research projects, small utilities, proof-of-concepts
Medium Teams (6-20 active contributors)
Characteristics:
Mix of direct and structured communication
Need for some formal roles and processes
Multiple areas of expertise/ownership
Balance between flexibility and structure
Growing external contributor base
Best for: Established projects, multi-component systems, growing communities
Large Teams (20+ active contributors)
Characteristics:
Formal communication structures required
Complex decision-making processes
Multiple committees or working groups
Diverse stakeholder representation
High volume of contributions and decisions
Best for: Enterprise projects, multi-organization initiatives, mature ecosystems
Template Selection Workflow
Step 1: Assess Your Current State
Ask these key questions:
Team Size: How many active contributors do you have?
Growth Trajectory: How quickly is the team expected to grow?
Organizational Complexity: How many organizations are involved?
Decision Complexity: How complex are typical technical decisions?
Compliance Requirements: Are there government/institutional requirements?
Step 2: Choose Your Template
Choose Small Teams Template when:
≤5 active contributors
Single organization primary
Simple technical decisions
Rapid iteration needed
Minimal bureaucracy preferred
Choose Medium Teams Template when:
6-20 active contributors
Multi-organization involvement
Moderate decision complexity
Balance of speed and process needed
Growing external interest
Choose Large Teams Template when:
20+ active contributors
Complex multi-organization structure
High-stakes technical decisions
Formal process requirements
Established community governance needed
Step 3: Consider Special Requirements
Government/NASA Projects:
Choose template one size larger than assessment suggests
Ensure compliance sections are properly filled
Include institutional copyright requirements
Add security and export control considerations
Government Project Specifics
NASA/JPL Compliance Considerations
When working on NASA or other government-sponsored projects:
Institutional Requirements:
Include appropriate copyright headers
Reference institutional policies
Ensure export control compliance
Follow security guidelines
Role Definitions:
Include government oversight roles
Define contractor vs. civil servant responsibilities
Establish foreign national participation rules
Set up approval workflows for sensitive decisions
Documentation Standards:
Meet federal record-keeping requirements
Ensure transparency in decision-making
Maintain audit trails for key decisions
Follow accessibility standards (Section 508)
Contribution Guidelines:
Implement contributor license agreements (CLAs)
Set up IP clearance processes
Define acceptable contribution sources
Establish security review procedures
Customization Guide
Common Customizations
Project Information:
Replace [INSERT PROJECT NAME] with your project name
Update [INSERT PROJECT DOMAIN] with your domain area
Q: Which template should I choose if I'm between sizes?
A: When in doubt, start with the smaller template. It's easier to add complexity than remove it.
Q: What if my organization has specific governance requirements?
A: Use the closest template as a starting point, then customize roles and processes to meet your organizational needs.
Q: How often should governance be reviewed?
A: Review governance effectiveness quarterly in the first year, then annually or when significant team changes occur.
Q: Can I mix elements from different templates?
A: Yes! The templates are starting points. Customize by mixing and matching elements that work for your specific context.