Run Fund Fest 2022

[chadwhitacre]

Notion🔒 | Sheet🔒 | 2023 →

---

• kick-off call with Marketing
• EPD Bi-weekly - warm up EMs/PMs
• check in with AP, see where bi-weekly payment runs are hitting
• finalize foundation splits
• email all vendors to get the ball rolling
• settle on foundation allocations
• get invoices from foundations
  • Apache
  • Django - GHS
  • OpenJS
  • OSI
  • Postgres
  • Python
  • Rust
• get invoice from Outreachy
• update deps
  • run through deps once, make sure it works as it stands
  • add php
  • add ruby
  • add java?
  • add dotnet?
  • add cocoa?
  • add unity?
• run internal voting
  • kick-off survey via [email protected] -
  • last-call email to [email protected]
  • #team-engineering haranguing and #announcements
• finalize allocations across platforms (GHS, OSC, TD, SA)
  • pay special attention to any projects we're paying less or dropping, ensure it's desired
  • think through if we want to support frameworks (cf.)
• pay invoices
• distribute funds or otherwise configure platforms
  • GHS
  • OSC
  • TD
  • SA
• publish blog post
  • get on calendar
  • new artwork?
  • include Postgres quote
  • mention Huntr.dev dropping due to sensitivity around Sullivan verdict 😞
  • notify all partners
• Go through vendor intake with TD/SA #66
• Move TD/SA apps to low privilege account #65

[chadwhitacre]

I had a call with Outreachy today, invoice incoming.

I think I'll get an invoice from PSF because it's more book-keeping for them if we go through PSF.

[chadwhitacre]

I requested an order form for GitHub so I can get the invoice going. If I get an invoice dated by September 7 then I should get that paid the week of September 26 so funds are available by Oct 11 when we need them (our balance is used up on Sept 11).

[chadwhitacre]

I won't have final platform amounts determined before late September because voting runs through Sept 15. As long as I have enough in GitHub to cover the estimated first month (or two) then it should be fine to do a second invoice to top up the final balance for the year.

[chadwhitacre]

For OC it is a simple one-time payment so no need to overworry about having the balance topped up in time for a monthly distribution as on GitHub.

[chadwhitacre]

I'd like to think about frameworks, like what Chrome does. I want to get a list of the top language/frameworks we support in our SDKs and see if we can include them as a group.

https://dotnetfoundation.org/assets/documents/FY23-Sponsorship-Levels.pdf

[chadwhitacre]

TIL https://stackaid.us/, invite requested

[chadwhitacre]

to get to distribution:

• process submissions into usable list w/ counts
• finalize SDK upstreams (Go?)
• bring in dependencies (compare w/ TD/SA?)
• start fitting together

[chadwhitacre]

Hrm, grouping projects into ecosystems is not going smoothly.

• I've got one-offs for Flutter, .NET, Swift, ...
• I've got projects like swc that are written in Rust but are tooling for JS/TS

🤔

[chadwhitacre]

I guess the point of grouping is to line up with the ecosystems we depend on the most, which is Python, JS, and Rust. Anything else can get lumped into "other" (last year called this "open source"), would be nice to list the specifics though to demonstrate breadth of diversity. Also since we are users of these tools then something like swc would count for js from our perspective.

[chadwhitacre]

New classification for this year: project vs. individual.

[chadwhitacre]

What I don't have from the fund fest survey is something like:

• ecosystem or major component - py rs js etc.
• downstream ecosystem, SDK related
• project we rely on to ship Sentry
• project individual dev relies on daily to be productive on Sentry
• project individual is interested in but doesn't use for Sentry

🤔

[chadwhitacre]

First draft done. Sheet. Doc.

[chadwhitacre]

Distribution finalized. Invoices obtained for OC, TD, SA. Expecting GHS next week. (Still struggling with OpenJS 🤷).

SA uses a GitHub App.

TD uses API access, I'm considering a separate user account for that. Setup Jira.

[chadwhitacre]

OpenJS is in the chute. 👍 That's all of them!

GitHub distributions are done! Scored a quote tweet! 😁 💃

Next week:

• Distribute on OC, TD, SA.
• Draft blog post.

[chadwhitacre]

GitHub distributions are done!

Okay that's a lie. I have $1,188 left over due to some people setting minimums. I'm considering sending it to OWASP, I had them on the list at a much lower level but I think that'd be a good choice.

[chadwhitacre]

Other platforms:

• OC - working through a bug on their side
• TD - had a call with Ali, should be all set to start payouts on Wednesday!
• SA - call with Wes in 10 minutes ...

[chadwhitacre]

OC done, TD I think I'm done, hearing from Ali seems like he's on it. SA I need to make PRs and do a bunch of config.

Blog post is in draft needs a couple hours work.

[chadwhitacre]

Oh and I did go for OWASP.

[chadwhitacre]

Punchlist for blog post:

• add shout-outs for TD and SA
• write conclusion
• settle down first pass through
• make quote images
• dig up and link header from DAM
• produce external sheet with summary and details
• go through review cycle with Janet and Sarah (others?)

[chadwhitacre]

Blog is live: https://twitter.com/getsentry/status/1585743508031565824

Leaving this open, app review scheduled for tomorrow.

[chadwhitacre]

Should've timed it better, bulk of traffic was into the US evening, went on HN overnight and got dropped in the morning. 😞

[chadwhitacre]

P.S. Confirmed we got modded:

It was flagged by users and a moderator downweighted it. Funding/foundation stuff usually isn't that interesting (in HN's sense of the word) because there isn't that much to discuss about it other than "yay" and something generic about either the funder or the category being funded. That of course does not mean it isn't worthwhile—it just doesn't usually lead to engaging discussion.

[chadwhitacre]

TD and SA accounts finally moved to a low-privilege account (#65). Done-done-done!