Join the Pledge

Feel free to open an issue or schedule a call if you have any questions.

How to Join

1

1. Pay $2,000 per full-time equivalent developer on staff

directly to any Open Source maintainers or foundations of your choice, and commit to doing so in future years. The projects you're paying should meet the Open Source Definition and our guidelines. Of course, this includes any existing payments you've made this year. If you need help figuring out which projects you depend on, you can use a tool like thanks.dev.
2

2. Publish a blog post

or equivalent on your company website, detailing the payments 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.

Note that only cash payments to maintainers of Open Source projects, or to Open Source foundations, count towards the pledge. We understand that companies contribute to the Open Source ecosystem in other ways than cash payments. These contributions are important, and the blog post is the best place to show them off.

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

3. Create a short JSON file with your company and payment info,

and host it at any URL you wish.

Want to do things by hand? Check out an example JSON report or the full schema.

Want us to create your JSON file for you? Fill in this form:

JSON Creation Form

Please make sure this is a valid URL.

Here's your JSON:

 
4

4. Create a pull request to add yourself to the member list

by changing members.csv. The format is company-slug,json-url. There should be no spaces in the company slug.
5

5. Include your branding materials in the PR,

so that we can add your logo to the website, and promote you in future campaigns.

We need at least:

  1. a glyph/icon in a square area with a non-transparent background (see examples),
  2. a glyph/icon in a square area with a transparent background, and
  3. a full name/wordmark in a wide rectangle with a transparent background,
or your nearest equivalents. Try to include vector files (e.g. SVG), or at least high-resolution (> 800px wide) raster files.

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.

Future Annual Reports

To remain a member, you should publish annual reports every year and add them to your JSON file. We'll fetch this file automatically.

Future annual reports should end on the same day of the year as your initial annual report. For example, if your first annual report was for the year ending October 1st 2024, your next annual report should contain data for the year ending October 1st 2025. Of course, you can actually publish this report at any time, for example if you've already made all of your payments earlier in the year.

Questions?

Feel free to open an issue or schedule a call.