Contributor
Anyone who helps a project grow, through code, docs, testing, ideas, or community support.
How to contribute
Contribute to open source,
your way.
You don’t need to be an expert. 450+ Eclipse Foundation projects need more than code. Pick what you’d like to do and see where to start.
Getting started
What would you like to do?
Follow, support, and amplify
Helping a project reach more people is a real contribution.
Tip: Don’t just repost. Say why it matters to you.
- Follow its repos, mailing lists, and social accounts.
- Join a community call, webinar, or meetup.
- Share release news and calls for participation.
Contribute as a user or adopter
Maintainers can’t see who uses their project. Tell them.
Tip: Remove sensitive info from logs and screenshots first.
- Report bugs with clear steps to reproduce.
- Add your organisation to the adopters page.
- Share your story in a blog post or talk.
- Sponsor a project or explore membership.
Make non-code contributions
Docs, design, events, and triage are skilled work, not extras.
Tip: Small fixes can go straight in. For bigger changes, talk to the team first.
→ Read why projects need triage (opens an external site in a new tab)
- Fix unclear docs or translate them.
- Write a tutorial or blog post.
- Organise a meetup or propose a community webinar.
- Help triage: reproduce bugs and spot duplicates.
Make technical contributions
Learn a real codebase and build a public portfolio.
Tip: No beginner label? Ask the team for a newcomer task.
- Look for “good first issue” labels.
- Read the README and CONTRIBUTING.md.
- Create an Eclipse Foundation account and sign the ECA.
- Comment on the issue before you start.
Your first technical contribution in five steps.
Give back, learn something new, build a public portfolio. All good reasons.
Read the README and CONTRIBUTING.md
Every project explains how to set up, build, and submit changes.
Sign the Eclipse Foundation Contributor Agreement
Use the same email as your Git commits. Contributing at work? Make sure you’re allowed.
Get started
Questions? Ask the team right on the issue. When your change is ready, open a pull request.
Find a project to join
Search 450+ Eclipse Foundation projects by name or technology.
Popular: Java IoT Automotive Cloud AI
Guides
Learn from great onboarding
These projects make it easy for newcomers to get started.
From contributor to committer
Every committer contributes. Not every contributor needs to become a committer. Learn the difference and how you can grow your role at your own pace.
Committer
A trusted contributor who can commit code, review contributions, and help steer the project. Two ways in:
- Get elected after sustained, high-quality contributions.
- Start a project as an initial committer.
Committer Training
Watch on YouTube (opens in a new tab)Six things to know before you dive in.
Tap any row for details.
Talk to the team before investing heavily.
Learn the project’s goals and current focus so your work fits the team’s plans.
Your first contribution can be tiny.
A “docs fix” or “clear bug” report teaches you the workflow and builds trust.
Don’t overcommit.
Be honest about what you can offer and speak up if that changes.
Build a portfolio and help others.
Write about what you’ve worked on and learned, on your own or through Open Source Global Voices.
Every question matters when you’re learning.
Say what you tried, what happened, and where you got stuck. Then share the answer for the next newcomer: reply in the thread, or better yet, add it to the docs.
You remain responsible for everything you submit.
Check the project’s AI policy first. Review and test everything, and only submit what you can explain.
Using AI to contribute? Do it right.
Use AI to contribute better, but you remain responsible for what you submit.
Do
- Use AI to learn
Understand code, tests, and documentation. - Review and test everything
Understand every change before submitting. - Be transparent
Disclose AI assistance when required by the project. - Check licences and security
Verify provenance, dependencies, and avoid sharing sensitive data.
Don’t
- Submit code you don’t understand
AI-generated code can contain subtle errors or security issues. - Flood projects with AI-generated PRs
Quality matters more than quantity. - Share secrets or private code
Respect confidentiality and project policies. Don’t paste sensitive data into AI tools. - Ignore maintainer feedback
AI assistance doesn’t replace collaboration. Be ready to discuss and iterate.
Most people never start because of a myth.
Myth: “I need to be an expert first.”
Myth: “Real contributions are code.”
Myth: “I don’t have enough time.”
Reality: Fresh eyes spot what experts miss.
Reality: Docs, testing, and events matter just as much.
Reality: Small and finished beats big and stressful.
Pick one project. Find one need. Take the first step.
Share a post, fix a typo, test a release, or open your first pull request. Useful beats big.
Browse 450+ projects Read the contributor guidance