← 2023 | Notion 🔒 | Sheet 1 🔒 | Sheet 2 🔒 | 2025 →

Greetings!

Welcome to Sentry's annual Open Source Fund Fest for 2024! This program takes a lot of work to run and this issue is the central source of truth for coordinating all of the moving parts. This year our budget is $750,000, which is 50% more than last year in terms of dollars per developer and in absolute terms (we have about the same number of developers). We aim to publish the blog post 🔒 announcing this year's funding on October 29 November 12.

The Pledge

The big news this year is that we are launching the Open Source Pledge to spread our funding model to other companies. We soft-launched on August 28 and our major marketing launch kicks off on October 8.

Three Components

There are three key components to this year's edition:

1. Thanks.dev—We were a launch partner for this new platform two years ago, and our pilot project went so well that last year we contracted with Thanks.dev to manage the bulk of our budget. This year we plan to do the same.

2. Open Source Collective—We plan to pilot a new feature with them aimed at scaling distributions based on data from Ecosyste.ms.

3. GitHub Sponsors—We are continuing our partnership with GitHub. Honestly the product is starting to really lag behind for at our scale, but they do have a new bulk recurring sponsorship workflow that we intend to exercise.

Feel free to comment on this issue or reach out on Bluesky with questions. Thank you to all of the maintainers who build the software Sentry depends on. 🙏

To Do

• Disburse $600k through TD.
  • Allocate to foundations.
  • Include .NET Foundation?
  • Include rrweb.
  • Remove bcoe - full audit for current employees.
  • Review TD sheet - make adjustments (boost +/-20, survey 1-10) - pick up 12 stragglers from 2023
  • Grant OC perms to TD crew (sentry fund, not sentry-team account).
• Disburse $75k through OC.
• Set up $75k drips on GHS from three orgs (getsentry, codecov, syntaxfm). #247
• Update hero with more lead time 🔒, should redraw in current style vs. reusing old w/ only year changed
• Publish a post 🔒 - "We Just Gave $750,000 to Open Source Maintainers"
• Run internal survey. 🔒
• Include https://github.com/Zalathar.
• Polar dev budgets? - product canceled
• Email dang ahead of time to avoid getting modded if possible—should we frame our post differently? - not gonna bother, hole is too deep, need to drink beers with the right person
  • e.g. “How we distributed $750k to OSS in 2024”