# Make Team Contributor Pathway > **Career Track**: WordPress Open Source Contribution | **Category**: [[03 - Contributors|Contributors]] ## 🎯 Pathway Overview Make Team Contributors dedicate time to improving WordPress through organized contribution teams (Core, Design, Mobile, Accessibility, Polyglots, Documentation, Themes, Plugins, Community, Meta, CLI, TV, Marketing, Training, Test, Tide, Openverse, Photos, etc.). This pathway is for those passionate about open source and giving back to WordPress, often alongside paid work. **Related Pathways**: [[Developer Pathway]] | [[Designer Pathway]] | [[Open Source Contributor Pathway]] | [[Make Team Lead Pathway]] --- ## 📊 Contribution Progression Snapshot | Level | Contribution Hours/Month | Recognition | Key Milestone | |-------|--------------------------|-------------|----------------| | New Contributor | 2-4 hours | Contributor badge | First accepted contribution | | Regular Contributor | 4-8 hours | Team recognition | Consistent monthly contributions | | Core Contributor | 8-16 hours | Trusted contributor | Reviewing others' work | | Team Rep/Component Lead | 16-24 hours | Leadership role | Guide team initiatives | **Note**: This is volunteer work. Most contributors have day jobs and contribute in spare time. Some work for organizations that sponsor their contribution time. --- ## 🟢 New Contributor ### What You'll Learn **Getting Started** (15 hours) - [[Introduction to WordPress Contribution]] - WordPress open source philosophy and GPL - Finding your fit among Make teams - Contribution tools (Trac, GitHub, Slack, Make P2) - Community etiquette and good first issues - Code of Conduct and inclusive community practices **First Contributions** (20 hours) - Choose team focus: - **Core**: [[Contributing to WordPress Core]] - **Design**: [[Contributing to WordPress Design]] - **Documentation**: [[Contributing to Documentation]] - **Support**: [[Contributing to WordPress Support]] - **Accessibility**: [[Contributing to Accessibility]] - **Polyglots**: [[Contributing to Translation]] - **Community**: [[Contributing to Community Team]] ### You Can Demonstrate **Initial Contributions**: - ✅ Complete Good First Issue (bug report, documentation edit, translation, forum answer) - ✅ Participate in team meetings (attend weekly chat, introduce yourself) - ✅ Follow team processes (use correct tools, follow workflow) - ✅ Communicate effectively (ask questions well, accept feedback graciously) - ✅ Make 3-5 contributions in first 2-3 months **Community Participation**: - Join team Slack channel and introduce yourself - Attend team meetings (weekly/bi-weekly depending on team) - Read team handbook and P2 updates - Ask for mentorship or buddy assignments - Understand team goals and priorities **Professional Behaviors**: - Respond to feedback constructively - Follow through on commitments - Communicate when can't complete something - Respect volunteer nature of community - Credit others' work appropriately ### Career Readiness Indicators **You're ready to become Regular Contributor when you can**: - Make contributions independently without hand-holding - Understand team workflows and tools - Know where to find information (handbooks, P2s) - Participate meaningfully in discussions - Mentor other new contributors **Recognition at This Level**: - WordPress.org profile with Contributor badge - Named on team roster - Mentions in team updates - Community welcome and appreciation ### Learning Resources **Required**: - [[Introduction to WordPress Contribution]] (15h) - One team-specific contribution guide (20h) - Attend 4+ team meetings over 2 months **Recommended**: - [[WordPress Open Source Philosophy]] (5h) - [[Effective Technical Communication]] (8h) - [[Code Review Best Practices]] (10h - if technical team) **Community Engagement**: - Join WordPress Slack (particularly your team channel) - Subscribe to team P2 blog - Attend Contributor Day at WordCamp (in-person or online) - Find a mentor or contribution buddy --- ## 🔵 Regular Contributor ### What You'll Deepen **Expanded Contribution** (40 hours) - [[Advanced Contribution Methods]] - Taking on larger tasks (not just good first issues) - Proposing ideas and improvements - Collaborating across teams - Understanding release cycles - Participating in decision-making **Specialization** (varies by team): - **Core**: [[Core Development Practices]] - Patch writing, testing, security review - **Design**: [[Design Systems & Contribution]] - Figma, design reviews, pattern library - **Docs**: [[Documentation Leadership]] - Content strategy, organization, style guide - **A11y**: [[Accessibility Auditing]] - WCAG testing, remediation proposals - **Polyglots**: [[Translation Leadership]] - GTE role, string management - **Community**: [[Event Organization]] - Meetup/WordCamp planning ### You Can Demonstrate **Consistent Contribution**: - ✅ Contribute 4-8 hours monthly (sustainable long-term) - ✅ Complete 2-4 contributions per month - ✅ Take on medium-complexity tasks independently - ✅ Participate actively in team discussions and decisions - ✅ Help onboard new contributors **Quality & Impact**: - Contributions accepted with minimal revisions - Work affects thousands of users (Core features, widely-used patterns, critical docs) - Thoughtful feedback on others' proposals - Proactive problem identification and solutions - Cross-team collaboration when appropriate **Community Leadership** (Emerging): - Answer questions from new contributors - Attend and participate in team meetings regularly - Help maintain team documentation - Represent team positively in community - Build relationships with other contributors ### Career Readiness Indicators **You're ready for Core Contributor status when you can**: - Work independently on complex contributions - Provide quality reviews of others' work - Understand codebase/systems deeply (team-specific) - Trusted by team for critical work - Mentor new contributors effectively - Demonstrate sustained commitment (6-12 months regular contribution) **Recognition at This Level**: - Regular mentions in team updates and credits - Invited to team leadership discussions - Speak at WordCamps about team work - Props in release notes (for Core/relevant teams) - Community trust and respect ### Learning Resources **Required**: - [[Advanced Contribution Methods]] (40h) - Team-specific specialization path (varies) - Attend 12+ team meetings over 6 months **Recommended**: - [[WordPress Release Process]] (12h) - [[Open Source Project Management]] (15h) - [[Mentoring New Contributors]] (10h) - [[Speaking About WordPress]] (8h) **Community Engagement**: - Speak at local WordPress Meetup about contribution - Write blog post about contribution experience - Help organize Contributor Day at WordCamp - Mentor 1-2 new contributors - Participate in Slack discussions helping others --- ## 🟣 Core Contributor / Trusted Contributor ### What You'll Master **Deep Expertise** (60+ hours) - [[WordPress Core Systems]] (if Core/technical team) - [[WordPress Governance & Decision-Making]] - [[Team Leadership Principles]] - [[Conflict Resolution in Open Source]] - [[Strategic Planning for WordPress]] **Review & Mentorship**: - Reviewing others' contributions (code, design, docs) - Providing constructive feedback effectively - Teaching contribution practices - Identifying and developing future leaders **Cross-Team Leadership**: - Understanding how teams interconnect - Facilitating cross-team initiatives - Representing team in broader community - Contributing to WordPress strategy ### You Can Demonstrate **Technical/Domain Leadership**: - ✅ Deep expertise in team's domain (WordPress Core internals, accessibility standards, design systems, etc.) - ✅ Review contributions from others with quality feedback - ✅ Propose and lead significant initiatives - ✅ Make architectural or strategic decisions - ✅ Represent team in cross-team discussions **Mentorship & Community**: - ✅ Mentor multiple contributors (3-5 people) - ✅ Onboard new contributors systematically - ✅ Improve team processes and documentation - ✅ Build inclusive, welcoming team culture - ✅ Handle conflicts constructively **Sustained Contribution**: - 12-24+ months consistent contribution - Present at team's needs, not just pet projects - Reliable for critical releases and initiatives - Trusted with sensitive work (security, governance) ### Career Readiness Indicators **You're ready for Team Rep/Lead role when you can**: - Understand team strategy and represent it to others - Make decisions aligning with WordPress project goals - Handle team administrative responsibilities - Build and maintain team health - Collaborate effectively with other team reps - Balance contribution with other life responsibilities sustainably **Recognition at This Level**: - Core Contributor badge (Core team) or equivalent - Commit access (for some teams: Core, Meta, Themes, Plugins) - Speaker at WordCamp US/Europe - Interviewed for WordPress.org news/features - Make.WordPress.org author for team blog - Community-wide recognition as expert ### Learning Resources **Required**: - [[WordPress Core Systems]] (60h+ team-specific) - [[WordPress Governance & Decision-Making]] (20h) - [[Team Leadership Principles]] (25h) - 18+ months regular, sustained contribution **Recommended**: - [[Conflict Resolution in Open Source]] (15h) - [[Strategic Planning for WordPress]] (20h) - [[WordPress Project History]] (10h) - [[Speaking at Major Conferences]] (12h) **Community Engagement**: - Speak at WordCamp US or Europe (team topic) - Write for Make.WordPress.org team blog - Represent team at State of the Word - Lead contributor workshops or trainings - Mentor 3-5 contributors actively --- ## 🔴 Team Rep / Component Lead ### What You'll Lead **Team Leadership**: - Guide team strategy and priorities - Facilitate team meetings and decision-making - Represent team to WordPress leadership - Manage team health and culture - Onboard and develop contributors - Communicate team work to broader community **Strategic Contribution**: - Align team work with WordPress roadmap - Propose and drive major initiatives - Collaborate with other team reps - Participate in WordPress project governance - Make decisions affecting millions of users - Balance community needs with project direction **Community Building**: - Grow contributor base - Foster inclusive, welcoming culture - Recognize and celebrate contributors - Resolve conflicts and challenges - Build sustainable contribution models - Connect contribution to WordPress mission ### Recognition & Responsibility **Official Roles** (examples): - **Core Team Rep**: Represent Core team in project leadership - **Component Lead**: Lead specific Core component (REST API, Gutenberg, etc.) - **Team Lead**: Lead entire Make team (Design Lead, Accessibility Lead, etc.) - **Release Lead**: Coordinate major WordPress releases - **Security Team**: Handle WordPress security issues **Privileges**: - Commit access (where appropriate) - Voice in WordPress project direction - Platform at major conferences - Directly shape WordPress for 43% of web **Responsibilities**: - 16-24+ hours/month contribution (often more) - Availability for critical issues - Represent team professionally always - Maintain confidentiality where required - Put WordPress project above personal interests ### Career Advancement Options **WordPress Project Leadership**: - **Release Squad Lead**: Lead WordPress major releases (3-4 releases as component lead typically required) - **Executive Director**: Hired role leading WordPress open source project (appointed by Matt Mullenweg) - **Project Lead**: Matt Mullenweg currently - co-founder of WordPress (theoretical future opening) **Parallel Professional Growth**: - **Principal Engineer at WordPress Company**: Technical leadership leveraging deep WordPress knowledge (Automattic, WP Engine, 10up, Human Made, etc.) - **CTO of WordPress Product Company**: Executive role at WordPress-focused company - **Independent Consultant**: High-value consulting leveraging Core contributor status - **Founder**: Start WordPress product/service company with community credibility **Continued Contribution**: - **Emeritus Status**: Step back from active leadership while maintaining respect and voice - **Mentor Role**: Focus on developing next generation of leaders - **Specialized Focus**: Deep dive single area (security, performance, accessibility) at highest level ### Compensation Models **Volunteer Contribution** (Most Common): - Contribute in spare time alongside day job - Employers may allow some work time for contribution (5-20% time) - Personal fulfillment, learning, networking, resume-building **Sponsored Contribution**: - Work for WordPress-focused company (Automattic, WP Engine, etc.) that sponsors contribution time - Job description includes X hours/week of contribution - Salary ranges from contributor's normal role (Developer, Designer, etc.) **Five for the Future**: - Organizations pledge 5% of company resources to WordPress contribution - Employees dedicate ~2 hours/week to contribution as part of job - Strengthens WordPress while allowing companies to benefit from healthy ecosystem **WordPress Foundation Roles** (Rare, ~10 positions): - Executive Director and small team are paid positions - Competitive tech salaries ($100-200K+ depending on role) - Funded by WordCamps, donations, WordPress trademark ### Time Commitment Reality Check **Entry Contributors**: 2-4 hours/month is valuable and welcome **Regular Contributors**: 4-8 hours/month sustainable long-term **Core Contributors**: 8-16 hours/month requires employer support or reduced other commitments **Team Leads**: 16-24+ hours/month typically requires sponsored time or retirement/sabbatical *Burnout is real. Sustainable contribution serves WordPress better than heroic sprints.* --- ## 🔄 Career Advancement & Lateral Moves ### Transitioning Between Teams **Skills Transfer Well**: - Communication and collaboration skills universal across teams - Understanding of WordPress philosophy and governance - Community relationships and reputation - Contribution workflows and tools **Switching Teams**: - Start as new contributor in new team (reset to learning mode) - Leverage existing credibility (faster trust-building) - Bring cross-team perspective (valuable for collaboration) - Common switches: Design ↔ Core, Documentation ↔ Training, Community ↔ Marketing ### Contribution + Career Synergies **Contribution Accelerates Career**: - **Networking**: Know WordPress who's who, get job opportunities before public - **Learning**: Cutting-edge WordPress knowledge, learn from experts - **Reputation**: Community credibility = client trust = higher rates/salaries - **Speaking**: Conference talks = visibility = opportunities - **Hiring**: Many WordPress companies prefer/require open source contribution **Career Experience Improves Contribution**: - **Developer → Core Team**: Professional dev skills elevate contribution quality - **Designer → Design Team**: Real-world design experience informs WordPress decisions - **Product Manager → Community Team**: PM skills useful for WordPress events/programs - **Teacher → Training Team**: Teaching experience makes training content better - **Marketer → Marketing Team**: Professional marketing elevates WordPress marketing ### Geographic & Cultural Contribution **WordPress is Global**: - Contribution teams span all time zones - Asynchronous work (Slack, P2, Trac) accommodates everyone - Translation teams for 200+ languages - WordCamps on every continent (except Antarctica... yet) **Polyglots Team Essential**: - WordPress available in 200+ languages - Translation contributors enable WordPress globally - GTE (General Translation Editor) leadership role per language - High-impact contribution (enable millions of users) --- ## 📚 Ongoing Contribution Development ### Sustaining Long-Term Contribution **Preventing Burnout** (Critical): - Set boundaries (X hours/month, not available 24/7) - Say no to overcommitment (better to contribute steadily than burn out) - Take breaks (contribution should be joyful, not stressful) - Share responsibilities (team leadership should not be single points of failure) - Celebrate wins (acknowledge progress and impact) **Life Balance**: - Contribution fits around job, family, health (not other way around) - Employers who support contribution (ideal, but not always possible) - Seasons of life (contribute more when possible, less when not - that's OK) - Long-term view (decades-long contribution more valuable than heroic years followed by burnout) ### Building Contribution Skills **Technical Skills** (for Technical Teams): - Stay current with WordPress development practices - Learn new technologies WordPress adopts (React, TypeScript, etc.) - Understand performance, security, accessibility deeply - Follow web standards evolution **Non-Technical Skills** (All Contributors): - Communication (writing clearly, speaking effectively) - Empathy (understanding diverse perspectives) - Conflict resolution (handling disagreements constructively) - Leadership (inspiring and guiding others) - Project management (organizing initiatives) ### Community Connections **Building Relationships**: - Contributor Day at WordCamps (meet people in person) - Team Slack (daily interactions) - Video meetings (put faces to names) - Social events at WordCamps (hallway track matters) - Alumni networks (people move between companies but relationships persist) **Mentorship Circles**: - Find mentors (learn from experienced contributors) - Be a mentor (teach and give back) - Peer learning (contributors at similar levels learn together) - Cross-team connections (broaden perspective) --- ## 🎯 Success Metrics by Level ### New Contributor - **Contributions**: 3-5 in first 2-3 months - **Participation**: Attend 4+ team meetings - **Learning**: Understand team workflow and tools - **Community**: Make connections, ask good questions ### Regular Contributor - **Contributions**: 2-4 per month sustained for 6+ months - **Quality**: Work accepted with minimal revision - **Helping**: Answer questions from new contributors - **Growth**: Take on medium-complexity tasks ### Core Contributor - **Contributions**: Review others' work, not just own contributions - **Leadership**: Mentor 3-5 contributors - **Impact**: Work affects thousands/millions of users - **Sustained**: 12-24+ months consistent contribution ### Team Rep/Lead - **Team Health**: Growing, active, healthy contributor base - **Strategy**: Team aligned with WordPress project goals - **Collaboration**: Effective cross-team work - **Sustainability**: Team functions even when you're unavailable --- ## 🔗 Related Resources ### Getting Started - [Make WordPress](https://make.wordpress.org/) - [Good First Bugs](https://make.wordpress.org/core/handbook/contribute/good-first-bugs/) - [Core Contributor Handbook](https://make.wordpress.org/core/handbook/) - [Five for the Future](https://wordpress.org/five-for-the-future/) ### Team Handbooks - Each Make team has handbook on make.wordpress.org/[team-name]/handbook/ ### Tools - [Trac](https://core.trac.wordpress.org/) - Bug tracking and patches - [GitHub](https://github.com/WordPress/) - Some teams use GitHub - [Slack](https://make.wordpress.org/chat/) - Real-time communication - [P2](https://wordpress.org/news/category/community/) - Team blogs --- *This pathway is part of the [[1. Projects/WP Curriculum/03 - Contributors/README|WordPress Curriculum Project]]* *Last Updated: 2025-11-07 | Next Review: 2026-02-07*