getsentry / team-ospo

Open Source Program Office (OSPO)
https://open.sentry.io/
11 stars 1 forks source link

Run Fund Fest 2024 #163

Open chadwhitacre opened 1 year ago

chadwhitacre commented 1 year ago

← 2023 | Notion πŸ”’ | Sheet 1 πŸ”’ | Sheet 2 πŸ”’


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

bruno-garcia commented 11 months ago

Re: .NET Foundation: I have more details on an email thread, feel free to reach out to me getting closer to the date. Thank you!

chadwhitacre commented 1 month ago

I have invoices from TD, OSC, and GHS. I'm waiting for final confirmation from OSC before I approve that one. For GHS there are some wrinkles because we also use the platform to pay for some marketing-based sponsorships (different budget than mine).

chadwhitacre commented 1 month ago

Okay let's ship this.

Invoices are queued to be paid.

I'm putting together a spreadsheet of foundations and employee input for TD.

chadwhitacre commented 1 month ago

I went back and updated the 2023 sheet with foundation numbers (dug out of email).

chadwhitacre commented 1 month ago

Payments on invoices are expected to go out today and clear in 2-3 business days.

chadwhitacre commented 1 month ago

GH is timing out on dependency pages:

https://github.com/orgs/getsentry/sponsoring/dependencies https://github.com/orgs/codecov/sponsoring/dependencies https://github.com/orgs/syntaxfm/sponsoring/dependencies

This blocks me from setting up trickles on GitHub.

chadwhitacre commented 1 month ago

Alright, I've got a foundation spread and employee survey up on a spreadsheet, handing those off to @anehzat @nehzata.

chadwhitacre commented 1 month ago

Here's the draft of foundation allocations:

chadwhitacre commented 1 month ago

This blocks me from setting up trickles on GitHub.

Found a way around it! It's the https://github.com/sponsors/explore endpoint that gives me what I need. πŸ‘

chadwhitacre commented 1 month ago

@anehzat @nehzata A couple items to get going:

nehzata commented 1 month ago

Hi @chadwhitacre, rrweb had a balance donation of $13,916.68 made to their Open Collective on 22nd Nov 2023. Have forwarded you the email chain for reference.

Will update the 2023 spreadsheet asap.

nehzata commented 1 month ago

Re: .NET Foundation: I have more details on an email thread, feel free to reach out to me getting closer to the date. Thank you!

@bruno-garcia could you please share .NET Foundation contact for us to coordinate with? πŸ™

chadwhitacre commented 1 month ago

@nehzataβ€”Replied in email as well, what I have is contact@dotnetfoundation.org.

nehzata commented 1 month ago

Thanks @chadwhitacre & @bruno-garcia. Confirming Armin has made contact.

nehzata commented 1 month ago

@chadwhitacre 2023 final amounts are available here.

chadwhitacre commented 1 month ago

Awesome! I've updated the spreadsheet linked from last year's post. I put a comment in there about rrweb (here's the transaction, btw).

chadwhitacre commented 1 month ago

We are pushing back our blog post target from October 29 to November 12, so that we have more time to distribute funds before announcing.

bruno-garcia commented 3 weeks ago

Sorry I didn't keep up with notifications but glad things got figured out! I talked to Chad on slack πŸ™

chadwhitacre commented 3 weeks ago

@nehzata I think there might be something goofy with the sheet. Even if I drop the inclusion percentage to 0%, payees that are showing $0 for auto (meaning they are not detected in our deps, yes?) are still coming out quite high in the 2024 column. Am I reading this right that I should expect $0 in 2024 in this case?

Image

nehzata commented 3 weeks ago

@chadwhitacre columns D & G are overrides. I've setting G237 to 0 to set the inclusion percentage to 0 and got the following. Image

Please let me know if I misunderstood the problem.

chadwhitacre commented 3 weeks ago

Ah, sorry to have been unclear: I was fiddling with the B7 knob on the vars tab. I guess I'm doing it wrong?

Intent

Thinking in terms of dollars, my intention is this:

  1. Start by allocating everyone the same dollar amount as they received last year.
  2. Review removals this year. Cut their allocation by half and drop entirely if below a certain threshold.
  3. Review new additions this year. Allocate to them based on a comparison with other projects in terms of prevalence in our codebase and employee interest.
  4. Adjust the whole up or down based on overall budget.
  5. Keep an eye on ecosystem ratio and adjust as needed.
chadwhitacre commented 2 weeks ago

I'm setting up GitHub drips on the three orgs. Process:

  1. cancel all previous sponsorships
  2. export a CSV
  3. run a script to split into multiple 100-row files
  4. upload the files, copy/paste minimum errors into minimums.csv
  5. rerun the script to split files with minimums taken into account
  6. fiddle around to hit budget targets
  7. checkout - "Pay later" - "Set sponsorship end date" of Oct 2025 (to prevent step 1 in future)
chadwhitacre commented 2 weeks ago

syntaxfm done (didn't need cancelations, working up a script for that)

nehzata commented 2 weeks ago

@chadwhitacre spreadsheet vars!B7 calculations should be fixed now.

nehzata commented 2 weeks ago

@chadwhitacre did you want us to automate the existing sponsorships cancelations?

chadwhitacre commented 2 weeks ago

did you want us to automate the existing sponsorships cancelations?

@nehzata Thanks for the offer. As far as I can tell, cancellation is not immediate. It takes effect on the next payment cycle date (Nov 11 in our case). An account in pending cancellation state cannot be updated using bulk sponsor.

chadwhitacre commented 2 weeks ago

@nehzata We're out of time. Let's go ahead and issue the payouts based on the current state of the spreadsheet (I switched the inclusion % back to 20 where you had it). Thanks.

nehzata commented 2 weeks ago

Sure thing @chadwhitacre. Will ping you once done.

nehzata commented 2 weeks ago

@chadwhitacre receipt url for the sentry "enterprise" :)

Have sent an invite for your afternoon – final sync prior to distributing funds. Please feel free to adjust if required. We're available from 8am AEDT. Thanks Chad!

chadwhitacre commented 2 weeks ago

Nice! Invite accepted. Excited to bring this in for a landing! πŸ‘

chadwhitacre commented 2 weeks ago

I'm noticing a big discrepancy between the sponsorables discovered by GitHub and those listed on the TD sheet πŸ”’. What explains that, I wonder? πŸ€”

chadwhitacre commented 2 weeks ago

punchlist/notes from TD phonecall:

chadwhitacre commented 2 weeks ago

My punchlist:

nehzata commented 2 weeks ago

@chadwhitacre How do we add funds to the Sentry Fund on OC? Is it really hidden or do we have to email OC to send an invoice for payment? These are the only options we see. Image

nehzata commented 2 weeks ago

@chadwhitacre rrweb has been paid from existing funds in the account. Just need to figure out how to add funds back in pls.

chadwhitacre commented 2 weeks ago

Is it really hidden or do we have to email OC to send an invoice for payment?

I've always emailed them for an invoice dance.

nehzata commented 2 weeks ago
chadwhitacre commented 6 days ago

Tying up some loose ends ... I think we're all set with Python, yes?

Also, Zalathar is in the spreadsheet but not showing up in the receipt. Am I reading that right?

nehzata commented 4 days ago

We haven't received an invoice from Python/Loren yet. Maybe it has been sent to an @sentry email / receivables inbox? Armin sent a follow up email last week I think... We haven't heard back yet.

Got to the bottom of why Zalathar not visible btw – should be visible now. Did not impact distributions.

chadwhitacre commented 3 days ago

We haven't received an invoice from Python/Loren yet.

Gotcha, seeing the email thread now. Let's top it up next week (Thanksgiving holiday this week in the US).

Got to the bottom of why Zalathar not visible btw – should be visible now. Did not impact distributions.

Thanks! πŸ‘ Were there others affected?

nehzata commented 3 days ago

Gotcha, seeing the email thread now. Let's top it up next week (Thanksgiving holiday this week in the US).

Enjoy the break!

Thanks! πŸ‘ Were there others affected?

Yes – there was a handful of recent manual inclusions that got affected. All received funds – just weren't showing up on the receipt page. avaloniaui, christianchiarulli, franky47, game-ci, giskard-ai, kamijin-fanta, mattleibow, tamasfe, wslulciuc, xmonad & zalathar.

chadwhitacre commented 3 days ago

Awesome, thanks for confirming.