For nonprofits
Who can submit a project?
Any verified nonprofit that is part of the GitHub for Nonprofits program. Your organization must be a 501(c)(3) or equivalent nonprofit that is nongovernmental, nonacademic, noncommercial, and nonpolitical in nature. If you haven't joined yet, see Quickstart for GitHub for Nonprofits to apply.
What kinds of projects are a good fit for Project Pods?
Projects that have a clear problem, defined deliverables, and can be completed by a small team in a short timeframe. Examples include building a data dashboard, redesigning a website for accessibility, setting up CI/CD pipelines, creating documentation, or developing a new feature for an existing open source tool. The best projects are ones where a volunteer team can make meaningful progress without needing months of onboarding. The more context you provide, the faster volunteer teams can start contributing. At minimum, include a clear problem statement, specific deliverables, the skills and technologies involved, and an estimated time commitment. Projects with well-labeled issues, a contributing guide, and a descriptive README attract volunteers faster.
What kinds of projects are not a good fit?
Projects that require long-term, ongoing maintenance with no clear end point, projects that involve sensitive or proprietary data that can't be shared in an open source repository, or projects that need a single specialized expert rather than a collaborative team. If your project doesn't fit the Pod model, you can still list individual issues on For Good First Issue for solo contributors.
What happens after we submit?
The GitHub Social Impact team reviews your submission. If accepted, your project is listed on the Project Pods page for volunteer teams to discover. If revisions are needed, you'll receive specific feedback on what to adjust. You can revise and resubmit at any time.
Why would a project submission be sent back for revisions?
Common reasons include unclear goals or deliverables, lack of defined tasks or issues in the repository, or insufficient information about required skills and technology. A revision request means your project needs a few adjustments before it is ready for volunteer teams to pick up. Ensure that project details are specific enough for a team to act on, your repository includes a README and contributing guide, and issues are labeled and scoped for contributors. You are welcome to revise and resubmit at any time.
How long does the review process take?
Reviews are typically completed within two weeks. You'll receive an email notification when your project has been reviewed.
How are volunteers matched to our project?
Once your project is approved, it's listed on the Project Pods page where volunteer teams browse available projects and choose ones that fit their skills and interests. Each listing shows the skills needed, technology stack, and time commitment so teams can self-select. Volunteers join as a group, through a corporate team running a volunteer day, a coding bootcamp cohort, or a community circle looking for a project. Groups then respond to the project issue to be connected for a project kickoff.
Are there any costs for nonprofits?
No. Participation in Project Pods is completely free.
What is our role once volunteers start working?
You are the project owner. Your primary responsibilities are to select the project volunteer team, answer questions in issues and pull requests, review contributions in a timely manner, and provide context about your mission and the mission you serve. Volunteers are donating their time, so responsive communication keeps them engaged and productive.
What if the volunteer team doesn't finish the project?
Project Pods are short-term engagements. If additional work remains, you can extend the project timeline, recruit another Pod, or continue the work internally. All contributions stay in your repository for ongoing use.
Can we submit more than one project?
Yes. You can submit multiple projects. Each one goes through the same review process and is listed independently on the Project Pods page.
What if we don't have a full project yet?
If your organization has individual tasks or issues that could use a contributor but you're not ready to scope a full team-based project, you can list them directly on For Good First Issue. Add your repository and label issues with 'good first issue' or 'help wanted'. Individual developers browsing the site can discover and pick them up on their own. When you're ready to scope a larger project for a team, come back and submit a Project Pod.
For volunteers and teams
Who can join a Project Pod?
Anyone. Corporate volunteer teams, coding bootcamp cohorts, university groups, community circles, or a group of friends. You don't need to be part of a specific organization to participate.
How do we find a project to work on?
Visit the For Good First Issue Project Pods page and browse listed projects. Each listing includes the problem description, skills needed, technology stack, estimated time commitment, and a link to the GitHub repository.
How are volunteers matched to projects?
There's no formal matching process. Volunteer teams browse available projects and choose ones that align with their skills and interests by replying to the Project Pod issue.
What is the typical time commitment?
It varies by project. Some Pods are designed for a single-day sprint, others span a week, and some involve short-term tasks over a few weeks. Each project listing specifies the estimated time commitment.
What if we can't finish the project?
Communicate with the nonprofit project owner. Let them know what you've completed, what remains, and any context that would help the next team pick up where you left off. All contributions are valuable, even partial ones. Open source means someone else can continue the work.
Is there any cost to participate?
No. Project Pods are completely free for volunteers.
Can our company use Project Pods for a corporate volunteer event?
Yes. Project Pods are designed for exactly this use case. A corporate team can browse available projects, select one that fits their team size and skill set, and complete it during a volunteer day, hackathon, or sprint. Each project listing provides all the context your team needs to get started.