This article is one of four dedicated to providing information about the Commons Program:
- Innovate with the Open Source Commons
- Contribute to the Open Source Commons
- Understand the Requirements for Joining the Program
- Salesforce.org Open Source Commons Terms of Participation
Table of Contents:
The Open Source Commons program exists to activate leaders in the Salesforce.org community and to give a platform to those that want to solve problems so they can create and share solutions. Others can then benefit from their work, making it easier for nonprofits and schools to maximize their investment in Salesforce.
Collaborating, creating, and sharing solutions for the purpose of helping others use technology comes as second nature to our community. One project, the Salesforce for Nonprofits How-To Videos team, has over 200,000 views on the 70+ Salesforce for Nonprofits how-to videos they’ve shared on their YouTube channel. These videos were created to help under-resourced Nonprofit Admins understand how to use Salesforce.org tools to support their cause.
Another project, the Salesforce for Nonprofits product Outbound Funds Module, was built and maintained within the program and released as an open source package helping Nonprofit track out-bound grants before being contributed to Salesforce.org in 2019. OFM is now a major part of the Grants Management solution.
These are only two examples of how our amazing community is creating impact via the Open Source Commons program.
The concept of Open Source contribution is simple, but assuring quality solutions that can be trusted year over year requires extensive cooperation from our entire community. By joining the OSC, teams are given the opportunity to learn from expert pro bono volunteers from Salesforce.org, access the Salesforce AppExchange and Security Review process, and much more.
Learn how Salesforce supports pro bono volunteers by coordinating events and providing technical expertise and tools.
Collaboration Spaces: Community Sprint events are the heart and most visible part of the Commons program. They are the main working days for many projects, but also serve as touchpoints for teams to connect with new volunteers and as marketing opportunities to bring awareness to the program. In fact, 95% of participants say they feel better connected to other members of the Salesforce community!
Enablement: To promote success, we help our community upskill on tools and best practices, especially when they are building custom packages and other technical solutions.
Tools for Sustainable Solutions: We help our community members keep their projects thriving, helping to build trust and prevent neglect.
In the Commons, working teams use best in class release engineering tools like CumulusCI, developed by Salesforce.org, making it easier to keep pipelines moving.
Join the Open Source Commons group in the Trailblazer Community to find upcoming events and learning opportunities.
Members of our community should feel confident that any open source solution they install will solve their needs—now, and into the future. Salesforce.org's Open Source Commons program supports our open source community's efforts to solve and address concerns around trust, continuity, and stability. Some of these concerns might sound familiar to you:
Admins don't know which open source solutions to trust.
People may be initially super excited to work on an idea, but later abandon it when their priorities change.
If there are problems with an open source application, it's unclear where to report issues.
The Open Source Commons program strives to alleviate these common challenges and provide sustainable solutions for our community.
Projects accepted into the Salesforce.org Open Source Commons program must show a commitment to open source principles, including transparency and accessibility to all.
Adhere to a minimum set of requirements such as including volunteers from at least three different organizations to participate in the program.
All Salesforce packages must pass Security Review, and installable via either the AppExchange or Salesforce.org’s custom installer.
Trust is our most important value and each project must maintain a high quality standard to ensure its success. Curious about the qualification process? Read more about the Open Source Commons program requirements.
Through our Open Source Commons program, we help support your ideas and help you share them with the broader community. We focus on responsible stewardship of open source projects, rather than becoming the product owner.
Open Source Commons community projects are created and supported by members of the community, not by Salesforce.org. Not all solutions are Salesforce packages, but when considering installing one, it's important you understand how they are built and supported.
Find Open Source Commons Salesforce solutions
Before you install any application in your Salesforce instance, whether it be an Open Source Commons project (or another from the AppExchange) you should review its features, documentation, and customer reviews on the app’s online community group page.
Some things to consider:
Community Project apps are required to be managed packages. With a managed package, there are some elements of the app that you can't change once you've installed it in your org. Requiring the use of a managed package means the project team can create new versions, so you'll always be able to stay on top of changes the project team makes.
New versions of a Community Project app are not automatically upgraded in your Production or Sandbox org. Unlike traditional managed packages, Community Project apps need to be manually upgraded by your Salesforce Administrator. This helps to protect your org, and ensures you have time to fully understand all changes or new features and test in your Sandbox before upgrading. Be sure to follow group posts so you are informed when a new version is available to install.
The next related knowledge article, Contribute to the Open Source Commons, can be found here.
000371729

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.