How to Contribute to Open Source  ## Metadata - Author: [[Open Source Guides]] - Full Title: How to Contribute to Open Source - Category: #articles - Document Note: --- tags: - #open_source - #contributing - #community Author: Open Source Guides Source: Website Reference: https://opensource.guide/how-to-contribute/ date created: 2025-08-22 00:00 --- # Title: How to Contribute to Open Source ## Table of Contents: - [📚 References](#-references) - [📝 Summary](#-summary) - [📖 Main Content](#-main-content) - [🗒️ Notes](#️-notes) - [📖 References](#-references-1) - [🗣️ Paraphrase](#-paraphrase) - [📰 Newsletter](#-newsletter) - [✅ Action Items](#-action-items) - [🧪 Hypotheses](#-hypotheses) - [📊 Methodology](#-methodology) - [❓ Questions](#-questions) - [🔮 Future Research](#-future-research) - [💡 Implications](#-implications) - [🧠 Learning Styles Assessment](#-learning-styles-assessment) - [📊 Accessibility Assessment](#-accessibility-assessment) - [🌍 DEIB Assessment](#-deib-diversity-equity-inclusion-and-belonging-assessment) - [✅ Logical validity](#-logical-validity) - [🎯 Conclusion](#-conclusion) ### References: - Open Source Guides. “How to Contribute to Open Source.” https://opensource.guide/how-to-contribute/ - GitHub “/contribute” pages example: https://github.com/facebook/react/contribute - First Contributions practice repo: https://github.com/firstcontributions/first-contributions - Make a Pull Request (Kent C. Dodds): https://www.youtube.com/watch?v=rgbCcBNZcdQ ## 📝 Summary: This guide demystifies contributing to open source by showing that meaningful contributions include far more than code. It explains community roles, key project documents and communication channels, how to find beginner-friendly issues, what to check before contributing, and best practices for opening issues and pull requests. It emphasizes respectful, public, and concise communication; aligning with a project’s vision; and staying resilient when feedback, delays, or rejections happen. The core message: open source is people-powered—small, thoughtful contributions and positive collaboration practices matter. ## 📖 Main Content: The guide begins by motivating contributions: fixing issues you encounter, building community, and experiencing empowerment through even tiny changes like typo fixes. It broadens the definition of contribution to include writing, design, organizing, user research, documentation, and translations. You don’t need to code to be valuable. It outlines “reading the room” before proposing changes, and presents the anatomy of a typical open source project—roles (author, owner, maintainer, contributor, community member), core documents (LICENSE, README, CONTRIBUTING, CODE_OF_CONDUCT), and communication spaces (issues, pull requests, forums/mailing lists, chat). To find projects, start with the software you use, keep an eye out for small fixes, and leverage GitHub’s /contribute pages. A pre-contribution checklist encourages verifying licensing, activity, responsiveness, and a welcoming culture. Communication advice focuses on context, doing homework, brevity, public discussion, patience, respect for decisions, and kindness. It provides concrete steps for opening issues and PRs, guidance on early WIP PRs, referencing issues, including screenshots, writing tests, and matching project style. It also prepares contributors for common outcomes: no response, requested changes, or rejection—and how to handle each with professionalism. The closing note celebrates participation: open source thrives on each issue, PR, and helpful comment. ### 🗒️ Notes - Why contribute - Improve software you rely on (“contributing the patch back is the best way to ensure … benefit”) - Meet like-minded people and build long-term community - Empowerment through small wins (e.g., fixing typos) - What counts as a contribution - Not just code: documentation, translations, examples, tutorials, newsletters, event-organizing, triage - Design: usability, research, style guides, visual identity - Organizing: duplicate issue linking, label suggestions, closing stale issues, clarifying questions - Non-software open content: books, recipes, lists, classes - Read the room - Observe norms, priorities, and communication style before proposing - Avoid derailing ongoing conversations; align proposals to context - Anatomy of a project - Roles: author, owner, maintainers, contributors, community members - Core docs: LICENSE, README, CONTRIBUTING, CODE_OF_CONDUCT, other docs/gov - Channels: issue tracker, PRs, forums/mailing lists, chat - Finding a project - Start with tools you use/admire - Fix what you notice; treat problems as fixable - Use GitHub /contribute to discover beginner-friendly issues - Many casual contribs are docs-related - Pre-contribution checklist - Open source license present - Active commits, responsive issues/PRs, constructive summaries (avoid flame wars) - Welcoming signals: CONTRIBUTING, CODE_OF_CONDUCT, tone - Communication best practices - Provide context, reproducible steps, explain value to project - Do homework first; be concise; keep public; be patient - Respect decisions; maintain civility across cultures/time zones - Issues vs PRs - Issues for problems, proposals, high-level topics - PRs for fixes and work-in-progress on discussed items - Announce intent, confirm stale issues, close with outcomes - PR craft - Fork/clone; keep upstream in sync; reference issues; include screenshots - Test changes; follow project style; start early as WIP - Practice via First Contributions; watch tutorials - Handling outcomes - No response: polite bump after a week; avoid private pings; move on if needed - Requested changes: be responsive; ask for help; hand off if bandwidth changes - Rejection: ask for feedback; respect maintainers; fork if you disagree - Celebratory close - Every contribution counts; thank maintainers; open source is human-first ## 📖 References: - Open Source Guides. “How to Contribute to Open Source.” https://opensource.guide/how-to-contribute/ - GitHub /contribute pattern: https://github.com/facebook/react/contribute - First Contributions practice: https://github.com/firstcontributions/first-contributions - Make a Pull Request video: https://www.youtube.com/watch?v=rgbCcBNZcdQ ## 🗣️ Paraphrase: 1) Original idea: You don’t need to write code to contribute; many neglected areas benefit from help. - Paraphrase: Coding isn’t a prerequisite for making an impact. In fact, projects often need help even more in areas like documentation, translations, and organization—offering support there can be one of the most valuable contributions. 2) Original idea: Respect community decisions and keep communications public, concise, and patient. - Paraphrase: Keep conversations in the open, be brief, and give maintainers time. If your idea isn’t aligned with the project’s direction, accept their decision graciously—or explore a fork if your vision diverges. ## 📰 Newsletter: This week in WordPress and open source: Learn smarter, build faster, and ship joyfully! - Learn web dev: If you’re just starting or leveling up, focus on fundamentals—semantic HTML, modern CSS layout (Flexbox/Grid), and JavaScript modules—then layer in WordPress block development. A quick starter: build a custom block with JSX, register it via block.json, and test in the Site Editor. - Recent updates: Gutenberg continues refining the Site Editor and Interactivity API. Core performance gets steady gains via lazy-loading and script strategy. Keep an eye on the [WordPress Developer Blog](https://developer.wordpress.org/news/) for deep dives. - Community highlights: First-time contributor workshops are booming—consider running one at your local meetup! Open source thrives on documentation, triage, and translation as much as code. - New plugins: Look for plugins adopting the Interactivity API for app-like UX without heavy frameworks. Bonus points for plugins that publish CONTRIBUTING and CODE_OF_CONDUCT files. - Pro tip: Use each repo’s /contribute page (e.g., [React’s contribute view](https://github.com/facebook/react/contribute)) to find beginner-friendly issues. Start small—typo fixes and docs clarifications are gold. - Extra credit: Practice PR flow in the friendly [First Contributions repo](h - Summary: Contributing to open source projects is a rewarding way to learn and build skills. You can contribute in various ways, not just by writing code. Remember to find welcoming projects and communicate effectively when contributing. - URL: https://opensource.guide/how-to-contribute/  #### Why contribute to open source?  Working on [freenode] helped me earn many of the skills I later used for my studies in university and my actual job. I think working on open source projects helps me as much as it helps the project! Contributing to open source can be a rewarding way to learn, teach, and build experience in just about any skill you can imagine. Why do people contribute to open source? Plenty of reasons! ##### Improve software you rely on Lots of open source contributors start by being users of software they contribute to. When you find a bug in an open source software you use, you may want to look at the source to see if you can patch it yourself. If that’s the case, then contributing the patch back is the best way to ensure that your friends (and yourself when you update to the next release) will be able to benefit from it. ##### Improve existing skills Whether it’s coding, user interface design, graphic design, writing, or organizing, if you’re looking for practice, there’s a task for you on an open source project. ##### Meet people who are interested in similar things Open source projects with warm, welcoming communities keep people coming back for years. Many people form lifelong friendships through their participation in open source, whether it’s running into each other at conferences or late night online chats about burritos. ##### Find mentors and teach others Working with others on a shared project means you’ll have to explain how you do things, as well as ask other people for help. The acts of learning and teaching can be a fulfilling activity for everyone involved. ##### Build public artifacts that help you grow a reputation (and a career) By definition, all of your open source work is public, which means you get free examples to take anywhere as a demonstration of what you can do. ##### Learn people skills Open source offers opportunities to practice leadership and management skills, such as resolving conflicts, organizing teams of people, and prioritizing work. ##### It’s empowering to be able to make changes, even small ones You don’t have to become a lifelong contributor to enjoy participating in open source. Have you ever seen a typo on a website, and wished someone would fix it? On an open source project, you can do just that. Open source helps people feel agency over their lives and how they experience the world, and that in itself is gratifying. #### What it means to contribute If you’re a new open source contributor, the process can be intimidating. How do you find the right project? What if you don’t know how to code? What if something goes wrong? Not to worry! There are all sorts of ways to get involved with an open source project, and a few tips will help you get the most out of your experience. ##### You don’t have to contribute code A common misconception about contributing to open source is that you need to contribute code. In fact, it’s often the other parts of a project that are [most neglected or overlooked](https://github.com/blog/2195-the-shape-of-open-source). You’ll do the project a *huge* favor by offering to pitch in with these types of contributions!  I’ve been renowned for my work on CocoaPods, but most people don’t know that I actually don’t do any real work on the CocoaPods tool itself. My time on the project is mostly spent doing things like documentation and working on branding. Even if you like to write code, other types of contributions are a great way to get involved with a project and meet other community members. Building those relationships will give you opportunities to work on other parts of the project.  I first reached out to the Python development team (aka python-dev) when I emailed the mailing list on June 17, 2002 about accepting my patch. I quickly caught the open source bug, and decided to start curating email digests for the group. They gave me a great excuse to ask for clarifications about a topic, but more critically I was able to notice when someone pointed out something that needed fixing. ##### Do you like planning events? * Organize workshops or meetups about the project, [like @fzamperin did for NodeSchool](https://github.com/nodeschool/organizers/issues/406) * Organize the project’s conference (if they have one) * Help community members find the right conferences and submit proposals for speaking ##### Do you like to design? * Restructure layouts to improve the project’s usability * Conduct user research to reorganize and refine the project’s navigation or menus, [like Drupal suggests](https://www.drupal.org/community-initiatives/drupal-core/usability) * Put together a style guide to help the project have a consistent visual design * Create art for t-shirts or a new logo, [like hapi.js’s contributors did](https://github.com/hapijs/contrib/issues/68) ##### Do you like to write? * Write and improve the project’s documentation * Curate a folder of examples showing how the project is used * Start a newsletter for the project, or curate highlights from the mailing list * Write tutorials for the project, [like PyPA’s contributors did](https://github.com/pypa/python-packaging-user-guide/issues/194) * Write a translation for the project’s documentation  Seriously, [documentation] is mega-important. The documentation so far has been great and has been a killer feature of Babel. There are sections that could certainly use some work and even the addition of a paragraph here or there is extremely appreciated. ##### Do you like organizing? * Link to duplicate issues, and suggest new issue labels, to keep things organized * Go through open issues and suggest closing old ones, [like @nzakas did for ESLint](https://github.com/eslint/eslint/issues/6765) * Ask clarifying questions on recently opened issues to move the discussion forward ##### Do you like to code? * Find an open issue to tackle, [like @dianjin did for Leaflet](https://github.com/Leaflet/Leaflet/issues/4528#issuecomment-216520560) * Ask if you can help write a new feature * Automate project setup * Improve tooling and testing ##### Do you like helping people? * Answer questions about the project on e.g., Stack Overflow ([like this Postgres example](https://stackoverflow.com/questions/18664074/getting-error-peer-authentication-failed-for-user-postgres-when-trying-to-ge)) or Reddit * Answer questions for people on open issues * Help moderate the discussion boards or conversation channels ##### Do you like helping others code? * Review code on other people’s submissions * Write tutorials for how a project can be used * Offer to mentor another contributor, [like @ereichert did for @bronzdoc on Rust](https://github.com/rust-lang/book/issues/123#issuecomment-238049666) ##### You don’t just have to work on software projects! While “open source” often refers to software, you can collaborate on just about anything. There are books, recipes, lists, and classes that get developed as open source projects. For example: Even if you’re a software developer, working on a documentation project can help you get started in open source. It’s often less intimidating to work on projects that don’t involve code, and the process of collaboration will build your confidence and experience. #### Orienting yourself to a new project  If you go to an issue tracker and things seem confusing, it’s not just you. These tools require a lot of implicit knowledge, but people can help you navigate it and you can ask them questions. For anything more than a typo fix, contributing to open source is like walking up to a group of strangers at a party. If you start talking about llamas, while they were deep in a discussion about goldfish, they’ll probably look at you a little strangely. Before jumping in blindly with your own suggestions, start by learning how to read the room. Doing so increases the chances that your ideas will be noticed and heard. ##### Anatomy of an open source project Every open source community is different. Spending years on one open source project means you’ve gotten to know one open source project. Move to a different project, and you might find the vocabulary, norms, and communication styles are completely different. That said, many open source projects follow a similar organizational structure. Understanding the different community roles and overall process will help you get quickly oriented to any new project. A typical open source project has the following types of people: * **Author:** The person/s or organization that created the project * **Owner:** The person/s who has administrative ownership over the organization or repository (not always the same as the original author) * **Maintainers:** Contributors who are responsible for driving the vision and managing the organizational aspects of the project (They may also be authors or owners of the project.) * **Contributors:** Everyone who has contributed something back to the project * **Community Members:** People who use the project. They might be active in conversations or express their opinion on the project’s direction Bigger projects may also have subcommittees or working groups focused on different tasks, such as tooling, triage, community moderation, and event organizing. Look on a project’s website for a “team” page, or in the repository for governance documentation, to find this information. A project also has documentation. These files are usually listed in the top level of a repository. * **LICENSE:** By definition, every open source project must have an [open source license](https://choosealicense.com). If the project does not have a license, it is not open source. * **README:** The README is the instruction manual that welcomes new community members to the project. It explains why the project is useful and how to get started. * **CONTRIBUTING:** Whereas READMEs help people *use* the project, contributing docs help people *contribute* to the project. It explains what types of contributions are needed and how the process works. While not every project has a CONTRIBUTING file, its presence signals that this is a welcoming project to contribute to. * **CODE\_OF\_CONDUCT:** The code of conduct sets ground rules for participants’ behavior associated and helps to facilitate a friendly, welcoming environment. While not every project has a CODE\_OF\_CONDUCT file, its presence signals that this is a welcoming project to contribute to. * **Other documentation:** There might be additional documentation, such as tutorials, walkthroughs, or governance policies, especially on bigger projects. Finally, open source projects use the following tools to organize discussion. Reading through the archives will give you a good picture of how the community thinks and works. * **Issue tracker:** Where people discuss issues related to the project. * **Pull requests:** Where people discuss and review changes that are in progress. * **Discussion forums or mailing lists:** Some projects may use these channels for conversational topics (for example, *“How do I…“* or *“What do you think about…“* instead of bug reports or feature requests). Others use the issue tracker for all conversations. * **Synchronous chat channel:** Some projects use chat channels (such as Slack or IRC) for casual conversation, collaboration, and quick exchanges. #### Finding a project to contribute to Now that you’ve figured out how open source projects work, it’s time to find a project to contribute to! If you’ve never contributed to open source before, take some advice from U.S. President John F. Kennedy, who once said, *“Ask not what your country can do for you - ask what you can do for your country.”* Contributing to open source happens at all levels, across projects. You don’t need to overthink what exactly your first contribution will be, or how it will look. Instead, start by thinking about the projects you already use, or want to use. The projects you’ll actively contribute to are the ones you find yourself coming back to. Within those projects, whenever you catch yourself thinking that something could be better or different, act on your instinct. Open source isn’t an exclusive club; it’s made by people just like you. “Open source” is just a fancy term for treating the world’s problems as fixable. You might scan a README and find a broken link or a typo. Or you’re a new user and you noticed something is broken, or an issue that you think should really be in the documentation. Instead of ignoring it and moving on, or asking someone else to fix it, see whether you can help out by pitching in. That’s what open source is all about! > [28% of casual contributions](https://www.igor.pro.br/publica/papers/saner2016.pdf) to open source are documentation, such as a typo fix, reformatting, or writing a translation. > > If you’re looking for existing issues you can fix, every open source project has a `/contribute` page that highlights beginner-friendly issues you can start out with. Navigate to the main page of the repository on GitHub, and add `/contribute` at the end of the URL (for example [`https://github.com/facebook/react/contribute`](https://github.com/facebook/react/contribute)). You can also use one of the following resources to help you discover and contribute to new projects: ##### A checklist before you contribute When you’ve found a project you’d like to contribute to, do a quick scan to make sure that the project is suitable for accepting contributions. Otherwise, your hard work may never get a response. Here’s a handy checklist to evaluate whether a project is good for new contributors. **Meets the definition of open source** **Project actively accepts contributions** Look at the commit activity on the main branch. On GitHub, you can see this information on a repository’s homepage. Next, look at the project’s issues. Now do the same for the project’s pull requests. **Project is welcoming** A project that is friendly and welcoming signals that they will be receptive to new contributors. Whenever you see a long thread, spot check responses from core developers coming late in the thread. Are they summarizing constructively, and taking steps to bring the thread to a decision while remaining polite? If you see a lot of flame wars going on, that’s often a sign that energy is going into argument instead of into development. #### How to submit a contribution You’ve found a project you like, and you’re ready to make a contribution. Finally! Here’s how to get your contribution in the right way. ##### Communicating effectively Whether you’re a one-time contributor or trying to join a community, working with others is one of the most important skills you’ll develop in open source. [As a new contributor,] I quickly realized I had to ask questions if I wanted to be able to close the issue. I skimmed through the code base. Once I had some sense of what was going on, I asked for more direction. And voilà! I was able to solve the issue after getting all the relevant details I needed. Before you open an issue or pull request, or ask a question in chat, keep these points in mind to help your ideas come across effectively. **Give context.** Help others get quickly up to speed. If you’re running into an error, explain what you’re trying to do and how to reproduce it. If you’re suggesting a new idea, explain why you think it’d be useful to the project (not just to you!). > 😇 *“X doesn’t happen when I do Y”* > > 😢 *“X is broken! Please fix it.”* > > **Do your homework beforehand.** It’s OK not to know things, but show that you tried. Before asking for help, be sure to check a project’s README, documentation, issues (open or closed), mailing list, and search the internet for an answer. People will appreciate it when you demonstrate that you’re trying to learn. > 😇 *“I’m not sure how to implement X. I checked the help docs and didn’t find any mentions.”* > > 😢 *“How do I X?”* > > **Keep requests short and direct.** Much like sending an email, every contribution, no matter how simple or helpful, requires someone else’s review. Many projects have more incoming requests than people available to help. Be concise. You will increase the chance that someone will be able to help you. > 😇 *“I’d like to write an API tutorial.”* > > 😢 *“I was driving down the highway the other day and stopped for gas, and then I had this amazing idea for something we should be doing, but before I explain that, let me show you…“* > > **Keep all communication public.** Although it’s tempting, don’t reach out to maintainers privately unless you need to share sensitive information (such as a security issue or serious conduct violation). When you keep the conversation public, more people can learn and benefit from your exchange. Discussions can be, in themselves, contributions. > 😇 *(as a comment) “@-maintainer Hi there! How should we proceed on this PR?”* > > 😢 *(as an email) “Hey there, sorry to bother you over email, but I was wondering if you’ve had a chance to review my PR”* > > **It’s okay to ask questions (but be patient!).** Everybody was new to the project at some point, and even experienced contributors need to get up to speed when they look at a new project. By the same token, even longtime maintainers are not always familiar with every part of the project. Show them the same patience that you’d want them to show to you. > 😇 *“Thanks for looking into this error. I followed your suggestions. Here’s the output.”* > > 😢 *“Why can’t you fix my problem? Isn’t this your project?”* > > **Respect community decisions.** Your ideas may differ from the community’s priorities or vision. They may offer feedback or decide not to pursue your idea. While you should discuss and look for compromise, maintainers have to live with your decision longer than you will. If you disagree with their direction, you can always work on your own fork or start your own project. > 😇 *“I’m disappointed you can’t support my use case, but as you’ve explained it only affects a minor portion of users, I understand why. Thanks for listening.”* > > 😢 *“Why won’t you support my use case? This is unacceptable!”* > > **Above all, keep it classy.** Open source is made up of collaborators from all over the world. Context gets lost across languages, cultures, geographies, and time zones. In addition, written communication makes it harder to convey a tone or mood. Assume good intentions in these conversations. It’s fine to politely push back on an idea, ask for more context, or further clarify your position. Just try to leave the internet a better place than when you found it. ##### Gathering context Before doing anything, do a quick check to make sure your idea hasn’t been discussed elsewhere. Skim the project’s README, issues (open and closed), mailing list, and Stack Overflow. You don’t have to spend hours going through everything, but a quick search for a few key terms goes a long way. If you can’t find your idea elsewhere, you’re ready to make a move. If the project is on GitHub, you’ll likely communicate by opening an issue or pull request: * **Issues** are like starting a conversation or discussion * **Pull requests** are for starting work on a solution * **For lightweight communication,** such as a clarifying or how-to question, try asking on Stack Overflow, IRC, Slack, or other chat channels, if the project has one Before you open an issue or pull request, check the project’s contributing docs (usually a file called CONTRIBUTING, or in the README), to see whether you need to include anything specific. For example, they may ask that you follow a template, or require that you use tests. If you want to make a substantial contribution, open an issue to ask before working on it. It’s helpful to watch the project for a while (on GitHub, [you can click “Watch”](https://help.github.com/articles/watching-repositories/) to be notified of all conversations), and get to know community members, before doing work that might not get accepted. You’ll learn *a lot* from taking a single project you actively use, “watching” it on GitHub and reading every issue and PR. ##### Opening an issue You should usually open an issue in the following situations: * Report an error you can’t solve yourself * Discuss a high-level topic or idea (for example, community, vision or policies) * Propose a new feature or other project idea Tips for communicating on issues: * **If you see an open issue that you want to tackle,** comment on the issue to let people know you’re on it. That way, people are less likely to duplicate your work. * **If an issue was opened a while ago,** it’s possible that it’s being addressed somewhere else, or has already been resolved, so comment to ask for confirmation before starting work. * **If you opened an issue, but figured out the answer later on your own,** comment on the issue to let people know, then close the issue. Even documenting that outcome is a contribution to the project. ##### Opening a pull request You should usually open a pull request in the following situations: * Submit trivial fixes (for example, a typo, a broken link or an obvious error) * Start work on a contribution that was already asked for, or that you’ve already discussed, in an issue A pull request doesn’t have to represent finished work. It’s usually better to open a pull request early on, so others can watch or give feedback on your progress. Just mark it as a “WIP” (Work in Progress) in the subject line. You can always add more commits later. If the project is on GitHub, here’s how to submit a pull request: * **[Fork the repository](https://guides.github.com/activities/forking/)** and clone it locally. Connect your local to the original “upstream” repository by adding it as a remote. Pull in changes from “upstream” often so that you stay up to date so that when you submit your pull request, merge conflicts will be less likely. (See more detailed instructions [here](https://help.github.com/articles/syncing-a-fork/).) * **Reference any relevant issues** or supporting documentation in your PR (for example, “Closes #37.”) * **Include screenshots of the before and after** if your changes include differences in HTML/CSS. Drag and drop the images into the body of your pull request. * **Test your changes!** Run your changes against any existing tests if they exist and create new ones when needed. Whether tests exist or not, make sure your changes don’t break the existing project. * **Contribute in the style of the project** to the best of your abilities. This may mean using indents, semi-colons or comments differently than you would in your own repository, but makes it easier for the maintainer to merge, others to understand and maintain in the future. If this is your first pull request, check out [Make a Pull Request](http://makeapullrequest.com/), which [@kentcdodds](https://github.com/kentcdodds) created as a walkthrough video tutorial. You can also practice making a pull request in the [First Contributions](https://github.com/Roshanjossey/first-contributions) repository, created by [@Roshanjossey](https://github.com/Roshanjossey). #### What happens after you submit a contribution You did it! Congratulations on becoming an open source contributor. We hope it’s the first of many. After you submit a contribution, one of the following will happen: ##### 😭 You don’t get a response. Hopefully you [checked the project for signs of activity](https://opensource.guide/how-to-contribute/#a-checklist-before-you-contribute) before making a contribution. Even on an active project, however, it’s possible that your contribution won’t get a response. If you haven’t gotten a response in over a week, it’s fair to politely respond in that same thread, asking someone for a review. If you know the name of the right person to review your contribution, you can @-mention them in that thread. **Don’t** reach out to that person privately; remember that public communication is vital to open source projects. If you make a polite bump and still nobody responds, it’s possible that nobody will respond, ever. It’s not a great feeling, but don’t let that discourage you. It’s happened to everyone! There are many possible reasons why you didn’t get a response, including personal circumstances that may be out of your control. Try to find another project or way to contribute. If anything, this is a good reason not to invest too much time in making a contribution before other community members are engaged and responsive. ##### 🚧 Someone requests changes to your contribution. It’s common that you’ll be asked to make changes to your contribution, whether that’s feedback on the scope of your idea, or changes to your code. When someone requests changes, be responsive. They’ve taken the time to review your contribution. Opening a PR and walking away is bad form. If you don’t know how to make changes, research the problem, then ask for help if you need it. If you don’t have time to work on the issue anymore (for example, if the conversation has been going on for months, and your circumstances have changed), let the maintainer know so they’re not expecting a response. Someone else may be happy to take over. ##### 👎 Your contribution doesn’t get accepted. Your contribution may or may not be accepted in the end. Hopefully you didn’t put too much work into it already. If you’re not sure why it wasn’t accepted, it’s perfectly reasonable to ask the maintainer for feedback and clarification. Ultimately, however, you’ll need to respect that this is their decision. Don’t argue or get hostile. You’re always welcome to fork and work on your own version if you disagree! ##### 🎉 Your contribution gets accepted. Hooray! You’ve successfully made an open source contribution! #### You did it! Whether you just made your first open source contribution, or you’re looking for new ways to contribute, we hope you’re inspired to take action. Even if your contribution wasn’t accepted, don’t forget to say thanks when a maintainer put effort into helping you. Open source is made by people like you: one issue, pull request, comment, or high-five at a time., How to Contribute to Open Source, Open Source Guides, 01h7wkphjdxyrtgsmv92dpxfjp.