GitLab's Non-Profits program is part of the Community Relations team.
On this page, you'll find information about how GitLab works with non-profits, our vision, our initiatives as well as our guidelines.
At this time, the GitLab for Non-Profits program is a work in progress and does not have a formal process for providing free licenses. The primary reason is that we do not have the capacity to process applications and issue licenses. The volume of applications to our current free programs, GitLab for Education, GitLab for Open Source, and GitLab for Startups, takes up all of our bandwidth! We do generally see the value in non-profits and we hope to create a non-profit offering in the future when we have capacity and can employ an automated verification process.
Although we do not have a formal non-profit free licensing program, we do partner and collaborate with non-profits in several capacities outlined on this page.
For the purposes of the GitLab for Non-Profits program, a non-profit organization is a legal entity organized and operated for a collective, public, or social benefit. Non-profits are tax exempt within their applicable local, state, provincial, federal, or national government. Any revenues that exceed expenses are committed back to the organization's purpose.
|#community-programs||Communication regarding the GitLab for Education,GitLab for Open Source, GitLab for Startups, and GitLab for Non-Profits.|
GitLab's mission is to change all creative work from read-only to read-write so that everyone can contribute. GitLab partners with non-profits that align with our mission and values. In particular, GitLab partners with non-profits that extend our company's Diversity, Inclusion, and Belonging Mission in exceptional ways. At this time, we prioritize non-profits that seek to create a diverse workforce and an environment where everyone can be their full selves. As time and capacity allow, we hope to extend our scope.
Our strategy focuses on creating impactful partnerships with a non-profits that extend our values and mission further into communities we may not be able to directly reach on our own.
OKR Epics are located in the Community Relations subgroup. We use the
non-profit and the
OKR label on each OKR epic. Key results are generally crated as issue and linked to each OKR epic. Each KR issue should have a milestone and an assignee at the time of creation. If there is a question about who the DRI is for a KR, assign the Program Manager until a DRI is decided upon.
||General label for all issues related to non-profit partnerships|
We are currently gathering feedback from the non-profit community on their needs, types of non-profits that use GitLab, how the non-profit benefits from GitLab, and how non-profits aligns with GitLab values.
If a non-profit entity wishes to provide feedback, please comment on this issue and answer as many questions as possible. Community members can stay up to date by enabling notification on this issue as we will post any updates here as well as in our handbook. To enable notifications, click the Notifications toggle in the sidebar to on.
At this time, we do not have an open call for non-profit partnerships. We do not have capacity to serve the volume of requests that we anticipate.
GitLab team members frequently encounter non-profits requesting a discounted license. Any inbound request for a discounted or free license by a non-profit organization is handled on a case-by-case basis by the appropriate sales team member for the geographic region of the non-profit and their manager. We cannot guarantee that any non-profit requests will be granted as the decision is at the discretion of the sales team.
Discounted or free licenses for non-profits are only issued in very rare cases. Because GitLab does not currently have a license and end-user license agreement specifically for non-profits, we are not able to issue a license without additional support from our legal team in order to modify our existing agreement and license granting process.
In the event that the GitLab team members feels strongly about the mission and values of the non-profit and the alignment with GitLab values and GitLab's diversity, inclusivity, and belonging mission and initiatives, we encourage the GitLab team member to propose a partnership.
The GitLab team member proposing the partnership will become the
internal champion and
directly responsible individual (DRI) for proposing the partnership and seeking approval. Before committing to being the
internal champion please be sure you have at the bandwidth to pursue the partnership and are comfortable advocating for the non-profit to the sales leadership and the executive group at GitLab. All free licenses and any associated benefits with a dollar value must be directly approved by the executive group.
Please review and complete the relevant steps before proposing the partnership:
internal championsubmit the proposal (in the form of an issue) to the executive group for approval via the #e-group slack channel. Once all approval have been obtained the non-profit partner can be awarded the benefits and activities can begin.
Please file an issue in the non-profit project with the following outline (template coming soon).
There are various ways GitLab extends benefits and collaborates with non-profits. This list contains examples and is not limiting or complete:
Please see the following examples of non-profit partnerships.