Join the Pledge
Our companies feast at the Open Source table year after year. Through the Open Source Pledge, we pay the maintainers of the software we consume. This prevents the maintainer burnout that flares up in high-profile security incidents such as XZ, Log4j, and Heartbleed.
How to Join
1. Donate $2,000 per full-time equivalent developer on staff
to Open Source maintainers or foundations of your choice, and commit to doing so in future years. The projects you're donating to should meet the Open Source Definition. Of course, this includes any existing donations you've made this year. You can donate to any projects you like, but if you need help figuring out which projects you depend on, you can use a tool like Thanks.dev.2. Publish a blog post
or equivalent on your company website, detailing the contributions your company has made to the Open Source ecosystem the past year. This post does not need to be long or exhaustive. If in doubt, check out sample posts by Sentry or Astral. Ideally, this post would include an itemized list of how much was paid to each maintainer/foundation. When this is undesirable or unrealistic, we ask that you make a best effort. To more conveniently get an itemized list, consider using the Open Source Pledge GitHub Reporter, or Thanks.dev.3. Create a short JSON file with your company and donation info,
and host it at any URL you wish. You can check out an example JSON report or the full schema. You should update this JSON file at least once per calendar year — we'll fetch it regularly. All amounts are in USD so that different reports can be compared to each other. If you're using a different currency, you should convert all amounts to the USD equivalents, using the most appropriate exchange rate.-
name
: The name of your company. -
description
: Will be shown on your member page and ideally includes a general description of your company and some notes on your company's relationship with Open Source software. -
urlLearnMore
: The URL to a page that describes your relationship to Open Source and/or your commitment to supporting Open Source. This page need not be exhaustive, and if you don't have such a page, you can just link to one of the report blog posts. This shouldn't be a link to your homepage. -
urlSquareLogoWithBackground
: Your logo, which should be square and have a non-transparent background. This image should be between 400x400px and 800x800px, and should be appropriately compressed.
annualReport
should contain:
-
dateYearEnding
: The end date of the year you are reporting on. -
url
: The URL to the blog post for the year in question, as detailed above. -
averageNumberOfDevs
: The average number of full-time equivalent developers employed by your company during the year. -
payments
: The total US dollar amount of cash contributions you have made towards Open Source maintainers and foundations during the year. -
monetaryValueofTime
,monetaryValueOfMaterials
: You may also optionally specify, in approximate US dollar equivalents, your contributions to the Open Source ecosystem in sponsored developer time (inmonetaryValueOfTime
) or gifts in kind (inmonetaryValueOfMaterials
). While we acknowledge that contributions in time and in kind are important, they are not included in the cash pledge amount. They will still be displayed on your member page.
4. Create a pull request to add yourself to the member list
by changing members.csv. The format iscompany-slug,json-url
. Please note that there should be no space in the company
slug.
5. Include links to your high-resolution logo,
and optionally any other branding materials, in the pull request so that we can promote you! For those pledging before September 15, this means you'll be included in our major outdoor advertising campaign.Once that's all done, you'll officially be a member. This means that your company and reports will show up on our website, and you'll be entitled to use the Open Source Pledge Member logo on your website and marketing materials if you wish. Thank you so much for joining us in contributing to a healthy Open Source ecosystem that supports maintainers.
If you have any questions, feel free to open an issue, and the relevant member of our team will get back to you.