CONTRIBUTE · Open Dev Societyfree to copy and reuse

Make your first contribution.

From fork to a draft pull request on one of our projects. 26 people have done it before you; every one of them is on the Contributors page.

Start now Not a coder?

Time
30–60 min
Level
beginner
Open issues
17 across 4 projects
You end with
1 draft pull request
From the teamRavi Pratap SinghfounderPriyanshu Bhardwajlead maintainer
01

Why do it

the goal

To change one real thing in a tool people use, have it reviewed in the open, and leave with your name on it.

02

What you need

4 things · tick as you go

0 of 4 ready

No local setup beyond what the project's README asks for. No experience required: review is part of the process, not a gate.

03

Step by step

pick a project, then work down
Pick a project · 4 have open issues

OpenStock · terminal0/5 done

  1. 1
    $ gh repo fork Open-Dev-Society/OpenStock --clone

    Without the GitHub CLI: Fork on github.com, then git clone your copy.

  2. 2
    $ gh issue list --repo Open-Dev-Society/OpenStock

    Comment on the issue so nobody doubles up. Small is good.

  3. 3
    $ cd OpenStock && git switch -c you/first-pr
  4. 4
    $ git add -A && git commit -m "Fix #<issue>: <what changed>"

    Run the project first and check the fix by hand. The README says how.

  5. 5
    $ git push -u origin you/first-pr && gh pr create --draft --fill

    Say what you changed and why, and link the issue.

Rose = yours to fill in. Needs the GitHub CLI: cli.github.com

04

What happens next

after you open the PR
CONTRIBUTORopen to everyone#27youon Contributors
  1. 1

    Draft opened. Push your branch and open a draft PR early. Say what you changed and why.

  2. 2

    Reviewed in public. A maintainer comments on the PR, where anyone can read it.

  3. 3

    You iterate. Push fixes to the same branch and the PR updates itself.

  4. 4

    Merged. Your name is on the commit, and your card is on the Contributors page.

05

Not a coder? Start here

5 ways in · no code needed for B–E
A

Code

Developers and engineers

  • Fix a bug or build a feature.
  • Review open pull requests.
  • Improve performance and security.
Open issues
B

Writing

Writers and editors

  • Write docs and tutorials.
  • Turn a fix into a guide or post.
  • Translate or proofread what's there.
Contributing guide
C

Design

Designers

  • Design logos and graphics.
  • Improve a tool's interface.
  • Make launch and social assets.
This site is open source too
D

Teaching

Educators and mentors

  • Write course material.
  • Lead a workshop or session.
  • Mentor someone through their first PR.
Join the Discord
E

Media

Podcasters and creators

  • Record a podcast or video.
  • Write about a tool you use.
  • Share what ships.
Follow on X
06

Code of conduct

6 values

Be respectful and welcoming. Harassment and discrimination are not tolerated, anywhere we work.

1
Open and transparent.
We build in the open and welcome feedback.
2
Inclusive and welcoming.
Everyone belongs here, whatever their experience.
3
Free and accessible.
We never lock knowledge or tools behind paywalls.
4
Community-driven.
We listen to the people who show up.
5
Quality and impact.
We aim for changes that make a difference.
6
Respectful and collaborative.
We treat each other with kindness.

Report anything to opendevsociety@gmail.com. Read the full code of conduct

07

Questions

5 common ones
1Do I need experience?

No. Pick an open issue, open a draft and ask. Review happens in the open, so you learn as you go.

2Where do I ask a question?

Open a GitHub Discussion on the repo, or ask in the Discord .

3I found a bug. What now?

Open an issue labelled bug on that tool's repository.

4Do I keep the credit?

Yes. Every merged PR carries your GitHub name, and your card goes on the Contributors page.

5Can I bring my own project?

Yes, and it stays yours. Read the manifesto