FY2023 Q3

[chadwhitacre]

← Q2 · Q3 · Q4 →

---

Conclusions

We focused on three big projects this quarter: dogfooding, funding, and engagement.

1. Dogfooding

Success! 👉 https://self-hosted.getsentry.net/ 👍

1. Embarrassment-driven development—it was embarrassing that we were using neither a) Sentry, nor b) self-hosted Sentry. Now we are!
2. Value from (a): We've already fixed two issues discovered from this.
3. Value from (b): We crashed due to low disk space. This is the sort of pain our users feel, we're building empathy which improves our support.
4. Here's the Vanguard post.
5. New team came together! 👏 @ethanhs @hubertdeng123

2. Funding

Success! 👉 "We Just Gave $260,028 to Open Source Maintainers" (preview, publishing today) 👍

1. The main story is continuity: last year we put an industry-leading program in place, this year we ran it again.
2. Grew program by ~70%, in line with our headcount growth.
3. Pilots with two new funding platforms, Thanks.dev and StackAid.

3. Engagement

Progress. 👌

1. Started the quarter thinking we would define and get started building tech to support migration.
2. Went through one big meeting with stakeholders and a number of smaller conversations.
3. Converging on solving with no new tech, only process changes + training.
4. "Open Source Customer Engagement Reset" Vanguard post in the works for ~next week.

Maintain

• Self-hosted
  • 22.8.0
  • 22.9.0
  • 22.10.0
  • backlog
    • SENTRY_URL_PREFIX is the big one
• TTR/TTT
• FOSSA - back burner, waiting for them to make changes, we'll need to make changes, too
• Engagement 🌮s
• Funding (last year)

Build

Ship Self-hosted

• Self-hosted Sentry Sesh (community meetup)
  • № 1 scheduled for August 3 w/ @BYK @aminvakil
  • One additional, open to the public? DEX? Decided on quarterly, scheduled in Discord.
• Dogfood—stand up a self-hosted instance in our GCP, send install.sh errors to it Dogfood self-hosted Sentry #36

Drive Engagement

"Move EPD to GitHub?" scrapped for parts, going after highest-value pieces.

• Work with Customer Support to start doing support on GitHub.
• Work with PM to keep moving Product Requirements to GitHub.
  • win: New Performance Issue Types sentry#37083
  • win: Session Replay Alpha Launch sentry#39460
• Work with EPD/GtM to move Customer Feedback to GitHub.
  • Build a Zendesk integration decided to focus on what we can do with zero engineering effort
  • Build a browser extension 🤑
  • Write/update Notion docs.
  • Retrain CS
  • stretch: Retrain CSM/SE

Bonus

• support - help out with "free support" project.
• marketing - help with DEX
• marketing - laid groundwork for a "Future of Open Source: Licensing" event
• marketing - go to ATO

No

• Move EPD to GitHub.
• Add segments to 401 viz to better target 🌮s.
• Convert GH Actions → GH App.
• Build out an attribution page.

[chadwhitacre]

Filing these links re: Customer Feedback board:

• https://getsentry.atlassian.net/browse/FEEDBACK-4
• Feature request: manually add tags sentry#5572
• https://getsentry.atlassian.net/browse/FEEDBACK-672

[chadwhitacre]

Milestones

August

• August 2 - support - get Support on GitHub
• August 2 - engagement - unconfuse bot
• August 3 - SSS № 1
• August 5 - clean up discussions
• August 3-5 - FOSSA incident - inc-187
• August 5 - engagement - identify stakeholder team
• August 8-12 - vacation for Chad
• August 15 - 22.8.0
• August 16 - support - make sure they're handling GitHub okay
• August 19 - funding - revisit last year, map out this year
• August 17 - funding - finalize general split inc. Foundations plan
• August 19 - dogfood - get a GCP project
• August 19 - dogfood - stand up self-hosted
• August 23 - support - make sure they're handling GitHub okay
• August 23 - engagement - assemble stakeholder team
• August 22-26 - hackweek
• August 29 - funding - survey #team-engineering
• August 30 - support - make sure they're handling GitHub okay

September

• September 9 - dogfood - add Sentry to install.sh
• September 9 - dogfood - document PII policy
• September 15 - 22.9.0 - dogfooding Round 1
• September 16 - funding - pay some projects
• September 30 - funding - pay more projects
• bonus - submit ATO blog post

Lots of heads down work on dogfooding and prepping with platforms (TD, SA).

October

• October 4 - feedback - switch Customer Support over to GitHub(!)
• October 5 - feedback - add PM org to open source onboarding process (future + backfill recent)
• October 6 - dogfooding - vanguard post
• October 11 - funding - distribute funds on GitHub Sponsors
• October 11 - feedback - meet with full PM org
• October 14 - funding - pay more projects
• October 15 - 22.10.0 - dogfooding Round 2
• October 19 - backlog - resolve SENTRY_URL_PREFIX warning (top self-hosted ask)
• October 19 - feedback - grant Discussion perms to PM org
• October 20 - funding - distribute on OC, TD, SA
• October 20 - feedback - document GitHub channels and owners
• October 28 - funding - pay any remaining projects
• October 31 - funding - publish blog post
• November 1 - funding - talk at ATO
• November 1 - bonus - talk at ATO on mypy

[chadwhitacre]

Bi-weekly EPD update:

1. funding – had a call with GitHub Sponsors about current state of their offering, goals for this week are to produce a draft allocation and send an email out to engineering to invite input
2. dogfooding – we have a GCP project set up, goal for end of week is to have self-hosted Sentry installed in it
3. engagement – kick-off meeting scheduled for next week, some final prep this week for that

[chadwhitacre]

send an email out to engineering to invite input

Too late. Hack week is next week and we don't want conflict with that. For next time I've made a note in Notion that we need to have the vote before hack week. For this year we'll have to run it after and do our best.

[chadwhitacre]

Bi-weekly EPD update:

1. funding – set back by Hack Week on internal voting => platform spend (learning for next time) - first two of seven foundation invoices are in the hopper
2. dogfooding – we have self-hosted Sentry installed in GCP, next milestone is to land the install.sh integration, now aiming for end of next week
3. engagement – kick-off meeting went well, galvanized a cross-functional set of owners for this initiative and agreed on division of labor, next step is to follow up post-hackweek and make progress - ETA for cutover is early/mid Q4

[chadwhitacre]

I made a Notion page to keep track of historical engagement tacos. I also have Quick Wins on the Bump, Set, Spike doc.

[chadwhitacre]

Bi-weekly EPD update:

1. funding—Employee submissions are open for two more days, vote! On track to be ready to publish a blog post at the end of October, will be speaking at Red Hat's conference Oct 31—Nov 2.
2. dogfooding—PR landed today! In time for the monthly calver release day after tomorrow.
3. engagement—Seem to be settling into three tiers for this roll-out: Customer Support, Corporate CSM, Enterprise CSM/SE. Customer Support decided yesterday to make the switch to GitHub ASAP, will work with them and build from there.

[chadwhitacre]

Bi-weekly update:

• We shipped a first iteration on dogfooding in 22.9.0 and are tweaking based on what we're seeing so far, on track to wrap up with 22.10.0.
• I've arrived at a final funding distribution and am working through invoices, on track for late October blog post.
• Customer feedback has taken a back seat due esp. to funding. Support is on board, aiming to focus on that the rest of the quarter.

[chadwhitacre]

Bi-weekly update:

• dogfooding - Done! Moving into maintenance mode.
• funding - All invoices are in, doing platform payouts this week and next, on track to publicize at the end of the month (blog post, ATO talk)
• feedback - Customer Support has shifted from Jira to GitHub, will work with them the rest of the month/quarter and regroup for next quarter on expanding further

[chadwhitacre]

Bi-weekly update:

• dogfooding - Working through some nice-to-haves post-shipped, end of quarter.
• funding - Platform payouts are done on GHS and OC, in the hopper for TD and almost in the hopper for SA. Blog post is in rough draft, publish date is Thursday.
• feedback - Lots of activity last week with David and CDV, draft vanguard post is circulating with Ian and a few others. Seems to be coming to a head, aiming for a Nov 1 publish date. tl;dr use public GitHub for customer feedback ;)