getsentry / team-ospo

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

FY2023 Q3 #34

Closed chadwhitacre closed 1 year ago

chadwhitacre commented 2 years ago

โ† 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.

charts

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

Build

Ship Self-hosted

Drive Engagement

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

Bonus

No

chadwhitacre commented 2 years ago

Filing these links re: Customer Feedback board:

chadwhitacre commented 2 years ago

Milestones

August

September

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

October

chadwhitacre commented 2 years ago

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 commented 2 years ago

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 commented 2 years ago

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 commented 1 year ago

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

chadwhitacre commented 1 year ago

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 commented 1 year ago

Bi-weekly update:

chadwhitacre commented 1 year ago

Bi-weekly update:

chadwhitacre commented 1 year ago

Bi-weekly update: