Skip to content

CONTRIBUTING_LADDER.md

Latest commit

 

History

History
136 lines (96 loc) · 2.8 KB

CONTRIBUTING_LADDER.md

File metadata and controls

136 lines (96 loc) · 2.8 KB

Contributing Ladder

This document outlines the different levels of contribution and how contributors can grow within the OpenSourceFramework project.

Level 1: Community Member 👋

Requirements:

  • Star the repository
  • Follow us on social media

Benefits:

  • Access to community discussions
  • Newsletter updates

Level 2: Contributor 📝

Requirements:

  • Have at least 1 PR merged
  • Follow the code of conduct
  • Complete CLA (if required)

Benefits:

  • Mention in CONTRIBUTORS.md
  • Invitation to community Discord

How to Contribute:

  1. Fork the repository
  2. Create a feature branch: git checkout -b feature/amazing-feature
  3. Make your changes following our coding standards
  4. Write tests for new functionality
  5. Submit a PR with a clear description

Level 3: Active Contributor 💪

Requirements:

  • Have 3+ PRs merged
  • Participate in code reviews
  • Help triage issues

Benefits:

  • Write access to branches (via fork)
  • Eligible for project-wide responsibilities

Activities:

  • Review PRs
  • Help new contributors
  • Create documentation
  • Report bugs

Level 4: Maintainer 🔧

Requirements:

  • Have 10+ PRs merged
  • Demonstrated technical expertise
  • Consistent participation for 3+ months

Benefits:

  • GitHub Maintainer role
  • Publish access to npm packages
  • Decision-making power on releases

Responsibilities:

  • Review and merge PRs
  • Release packages
  • Manage security vulnerabilities
  • Mentor contributors

Level 5: Core Team Member ⭐

Requirements:

  • Have 25+ PRs merged
  • Proven leadership
  • Deep understanding of project architecture

Benefits:

  • Full GitHub organization access
  • npm publish access for all packages
  • Conference talk opportunities

Responsibilities:

  • Set technical direction
  • Make architectural decisions
  • Handle security incidents
  • Represent the project externally

Promotion Process

  1. Nomination: Any maintainer can nominate a contributor
  2. Review: Core team reviews the nomination
  3. Approval: Simple majority vote
  4. Announcement: Public announcement of promotion

Recognition

All contributors are recognized in:

  • CONTRIBUTORS.md
  • GitHub profile (via badge)
  • Release notes
  • Annual community spotlight

Code of Conduct Enforcement

All contributors must follow our Code of Conduct. Violations may result in:

  • Warning
  • Temporary suspension
  • Permanent ban

See CODE_OF_CONDUCT.md for details.

Getting Help

Last Updated: February 2026