Open Source

Finding Projects
• GitHub Explore / Trending
• goodfirstissue.dev
• Labels: good first issue, help wanted, beginner

Contribution Workflow ```bash # Fork on GitHub, then: git clone https://github.com/YOUR_USERNAME/project.git git remote add upstream https://github.com/ORIGINAL/project.git git checkout -b fix/issue-123

# Make changes, commit with conventional format git commit -m "fix: handle null pointer in user.getProfile() (#123)"

# Keep up to date git fetch upstream && git rebase upstream/main git push origin fix/issue-123 # Open Pull Request on GitHub ```

PR Best Practices
• One PR per concern
• Reference the issue: "Fixes #123"
• Add tests for your change
• Update docs if needed
• Respond promptly to reviews

Key Distinctions
• Permissive (MIT, Apache, BSD): use in closed-source commercial products
• Copyleft (GPL): derivatives must also be open source
• Weak copyleft (LGPL): libraries can be linked from non-GPL code
• Network copyleft (AGPL): covers SaaS deployments

Always add a LICENSE file GitHub's license picker simplifies selection.

Repository Structure `` project/ ├── .github/ │ ├── ISSUE_TEMPLATE/ │ │ ├── bug_report.md │ │ └── feature_request.md │ ├── PULL_REQUEST_TEMPLATE.md │ └── workflows/ci.yml ├── CHANGELOG.md ├── CONTRIBUTING.md ├── CODE_OF_CONDUCT.md ├── LICENSE └── README.md ``

GitHub Actions CI ``yaml name: CI on: [push, pull_request] jobs: test: runs-on: ubuntu-latest steps: - uses: actions/checkout@v4 - uses: actions/setup-node@v4 with: { node-version: 20 } - run: npm ci - run: npm test - run: npm run lint ``

SemVer MAJOR.MINOR.PATCH
• MAJOR: breaking API changes (1.0.0 → 2.0.0)
• MINOR: backward-compatible new features (1.0.0 → 1.1.0)
• PATCH: bug fixes (1.0.0 → 1.0.1)

Conventional Commits (enables automated changelogs) `` feat: add user authentication (#45) fix: correct null pointer in getUser() docs: update API reference refactor: extract payment logic to service BREAKING CHANGE: rename createUser to registerUser ``

Automated Releases ``bash npx semantic-release # analyzes commits → bumps version → creates GitHub release → publishes to npm ``

npm Publishing ``bash npm login npm version patch # or minor / major npm publish --access public ``

Why Contribute
• Fastest way to level up reading production codebases beats tutorials
• Public commits tell your story living resume
• Networking maintainers often hire contributors
• Reputation that transfers across companies

Starting Points (by difficulty) 1. Fix typos in documentation (lowest friction) 2. Improve error messages to be more actionable 3. Add missing tests to existing functionality 4. Translate documentation to other languages 5. Fix a tagged good first issue

Going Deeper
• Become a regular contributor to 2-3 focused projects
• Propose and implement features that solve your own problems
• Start your own library that solves a real, narrow problem well

Great Projects for Learning
• React (facebook/react) excellent PR process
• VS Code (microsoft/vscode) great issue triaging
• Python (python/cpython) rigorous review culture
• Rust (rust-lang/rust) RFC process for major changes