Introduction to Open Source for Nonprofits and Social Sector Organizations | GitHub Social Impact
skip to content Skill Level: beginner Prerequisites: none Intended audience: developers and decision-makers within the social sector Introduction Open source (OS) software can be used to improve collaboration, increase efficiency, and reduce costs for an organization. When there are minimal restrictions on how it can be distributed, adapted, and reused, it can also be adopted by other social sector organizations, ultimately accelerating work being done to achieve the Sustainable Development Goals (SDGs) .
Why should social sector organizations open source? Collaboration and knowledge sharing: OS software and platforms allow people to collaborate and share knowledge in real-time. By utilizing OS platforms, individuals and organizations can work together to develop and share resources that aim to create positive change. Cost-effective solutions: OS software can be free or available at a low cost, which can help make sustainable development solutions more affordable and accessible to people and communities around the world.
However, it is important to note that there will still be some financial costs as well as an investment of time and resources. Scalability: OS solutions are often designed with scalability in mind, making it easier for organizations to grow and expand their impact in a way that is measurable through monitoring and evaluation. Transparency and accountability: OS is developed in a transparent and collaborative manner, which means that anyone can review the code and suggest improvements or modifications.
This can increase transparency and accountability in decision-making, which can be especially critical when working with or for governments. Localization: OS software and platforms can be easily localized and adapted to meet the unique needs of different communities and regions. This can help ensure that sustainable development solutions are tailored to the specific context and needs of the people they are intended to serve.
Flexibility and customization: OS software is highly customizable, which means that it can be adapted to meet the specific needs of an organization. This flexibility can also help governments avoid vendor lock-in and maintain control over their IT infrastructure. Interoperability: Open standards and protocols common in OS software can help nonprofits and social sector organizations more easily integrate their solutions with other systems, improving efficiency and collaboration.
Data sharing and analysis: OS platforms and tools can be used to collect, analyze, and share data on sustainable development indicators. This can help track progress towards your impact goals and inform policy decisions and resource allocation. How to open source To get started, you can first identify areas where OS software can be used and evaluate options for procurement or identify projects within your organization.
Once a project or product has been identified, you will begin customizing and configuring it to meet your specific needs. This may involve modifying the software code, adding new features, or integrating it with other software tools. Check out the seven questions to ask before open sourcing reference for more information. It will guide you through questions such as “Is there an approval process to help developers introduce new open source software (OSS) into our organization?" In terms of change management, training of staff and volunteer recruitment are important to ensure continued collaboration and engagement.
This may involve providing online training resources, hosting in-person workshops, or hiring consultants to provide training and support. Workshops to introduce OS can also involve fostering a culture of encouraging staff and volunteers to contribute to the development of other OS software in the social sector. To make the most of OS software, social sector organizations should: Identify specific needs and look for relevant solutions within the OS ecosystem.
Evaluate the quality, reliability, and security of the identified solutions, including the strength and responsiveness of your communities. Invest in capacity building and training to ensure staff can effectively implement, customize, and maintain these solutions. Engage with the developer and user communities of chosen solutions, both to learn from others and to contribute your own experiences and insights. Monitor and evaluate the impact of using OS software and DPGs on their operations and overall mission.
Refer to the MERL (monitoring, evaluation, research and learning) Center — a community creating resources about the intersection of MERL and OS, as well as data science and human-centered design — for more information. Open sourcing your project on GitHub The first step to begin open sourcing your project on GitHub will be to create a repository or "repo". This is where all of your code, files, and revision history will live.
For step-by-step instructions on how to set this up, take a quick look at this guide . Documentation for newcomers Repository section What should live in the section README.md Details and description about the project and community, including how to install and use the project. Links to LICENSE.md and CONTRIBUTING.md should be in this section. CONTRIBUTING.md Contribution guidelines and helpful hints of how developers can get started.
DEVELOPMENT.md Guidelines on setting up the development environment. CODE_OF_CONDUCT.md Behavioral expectations for contributors and members of the community. Contributor Covenant is an example that is used in a number of projects. Project organization: roadmap Like any project, you will need someone (or a group of people) to build out a vision for the project in the short-term and long-term. Some of this will be big picture planning — like creating strategies — and some tasks will be smaller but no less important.
It’s these types of everyday tasks that ensure your project stays on track. This planning doesn’t have to be done by someone with a technical background, it can also be done by someone with project management skills. They can begin with some of the following: Documenting a roadmap and planning sprints Creating issues and keeping projects organized Grooming the backlog by prioritizing issues Creating metrics for monitoring and evaluation as well as for measuring impact Being ok with saying no to some feature requests; only plan what you can realistically achieve Being open and transparent with your community about the roadmap and what requested features have been planned Project organization: project boards, issues & labels It’s key to keep your project board well organized so that things like rotating volunteers, high turnover rates, or periods of low production won’t disrupt the work that’s been put in.
If someone new stepped into the project today, they should be able to understand the way the project was structured and know how to continue working in a cohesive manner. Luckily, issues and labels are here to help with just that. Issues help you track work, manage feedback, and communicate with colleagues. Labels can help you categorize issues, pull requests, and discussions. Here are some commonly used labels: Epic - a large body of work that is then broken down into smaller tasks or user stories Good first issues - a good issue for first-time contributors Bug - an unintended behavior or problem Feature - a piece of software that serves a functionality or capability UX - stands for user experience and describes how someone would interact with the product API - stands for application programming interface which refers to the way two or more programs or applications communicate with each other Pro tip: You can configure automatic workflows , which help keep the status of classic project cards in sync with the associated issues and pull requests.
Automation can decrease the amount of manual work needed when an organization has limited resources. Building and engaging with your
The rest of this page is on the live site.