Back to Templates
CollaborationAny

Open Source Contribution - Seeking Guidance

Purpose: Requesting to contribute to open source project
Target: Open Source Maintainer or Core Contributor

Email Subject

Interested in contributing to [Project Name]

Alternative subjects:

  • • Would love to contribute to [Project Name]
  • • Found your project [Project Name] - seeking contribution guidance
  • • First-time contributor interested in [Project Name]

Email Body

Hi [Name],

I hope you're doing well! My name is [Your Name], and I'm a [Your Role] with experience in [relevant tech stack].

I've been using [Project Name] for [use case - e.g., "my personal projects" or "at work for [purpose]"] and I'm really impressed by [specific feature or aspect of the project].

I'd love to contribute to the project and give back to the community. I've gone through the documentation and:
• Reviewed the CONTRIBUTING.md guidelines
• Set up the development environment locally
• Explored the codebase

I'm particularly interested in:
• [Area 1 - e.g., "improving documentation"]
• [Area 2 - e.g., "working on issues labeled 'good first issue'"]
• [Area 3 - e.g., "adding tests" or "fixing bugs"]

GitHub: [Your GitHub Profile]

Could you point me to some beginner-friendly issues or areas where contributions would be most valuable? I'm eager to learn and contribute meaningfully.

Thank you for maintaining such an amazing project!

Best regards,
[Your Name]
[LinkedIn Profile if relevant]

Tips for Success

  • Show you've actually used the project
  • Demonstrate you've read the contribution guidelines
  • Start with small contributions (docs, tests, bugs)
  • Be patient - maintainers are often volunteers
  • Follow the project's code style and conventions

Do's

  • ✓Start with good first issues
  • ✓Read all contribution guidelines first
  • ✓Set up the project locally before reaching out
  • ✓Be respectful and patient with maintainers
  • ✓Write clean, well-documented code

Don'ts

  • ✗Don't expect immediate responses
  • ✗Don't take on complex issues as first contribution
  • ✗Don't ignore code review feedback
  • ✗Don't spam maintainers with messages
  • ✗Don't submit low-quality PRs

Placeholders Reference

[Name] - Maintainer's first name
[Your Name] - Your full name
[Your Role] - Your current role
[Relevant tech stack] - Technologies relevant to the project
[Project Name] - Open source project name
[Use case] - How you use the project
[Specific feature] - Something you appreciate about the project
[Area] - Areas you want to contribute to
[Your GitHub Profile] - Your GitHub URL
[LinkedIn Profile] - Your LinkedIn URL

Follow-up Email

Subject: Following up - Contributing to [Project Name]

When to send: 7-10 days after initial email

Hi [Name],

I hope you're doing well! I wanted to follow up on my message about contributing to [Project Name].

I understand you might be busy. In the meantime, I'll continue exploring the codebase and look for areas where I can help.

Thank you!

Best regards,
[Your Name]

Success Stories

Arjun B.

Became core contributor to popular React library

Started with docs, now maintains several features

Expected Response Rate:

30-45%

Best Time to Send:

Any day, 2 PM - 6 PM