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.

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.

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.

Required:

  • The year you're reporting for. You can report for a year at any point during that year.
  • Your total of payments made for that year.
  • Your average number of employed full-time equivalent developers for that year.

Recommended:

  • 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. Let us know you'd like to join,

by creating a GitHub issue.

The issue should include:

  • A link to your blog post.
  • A short (less than 600 character) description of your company, including why you're joining.
  • Your branding materials.

For branding materials, we need at least the following, or your nearest equivalents to them:

  • A glyph/icon in a square area with a non-transparent background (see examples).
  • A glyph/icon in a square area with a transparent background.
  • A full name/wordmark in a wide rectangle with a transparent background.

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 and our other promotional resources 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, every year, you should publish a blog post and submit it in an issue as in step 2 above. It does not matter which date you publish your blog posts on, as long as you're submitting one per year.

Questions?

Feel free to open an issue or schedule a call.