Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FY2024 Q1 #64

Closed
36 tasks done
chadwhitacre opened this issue Nov 4, 2022 · 7 comments
Closed
36 tasks done

FY2024 Q1 #64

chadwhitacre opened this issue Nov 4, 2022 · 7 comments

Comments

@chadwhitacre
Copy link
Member

chadwhitacre commented Nov 4, 2022

← Q4 · Q1 · Q2 →


Why We Exist

These conversations playing out in public are so helpful as a user so that I can keep the pulse on how you guys are managing things I'm especially interested in[.] Stuff like this is much of what makes me a rabid fan of Sentry.

getsentry/self-hosted#1873 (comment)

Build

Bonus

Maintain

No


Notion checklist

@chadwhitacre
Copy link
Member Author

@ethanhs to write up new team-ospo ticket to take over backup/restore (likely larger in scope than just getsentry/sentry#36868).

@hubertdeng123 to create an epic and cannibalize #73 for parts.

@chadwhitacre to write up three epics as well

@chadwhitacre
Copy link
Member Author

chadwhitacre commented Feb 6, 2023

We had a departure from the team last Friday. Adjustments to our quarterly plan as a result:

  1. Dropping "Tighten up process for managing impact on self-hosted." We'll handle immediate concerns ad hoc (e.g., Replay, Hybrid Cloud), and we'll aim to revisit a wider program once "First Class Single-Tenant🔒" lands, as it is conceptually parallel.
  2. Dropping "Reach our final time to respond targets consistently across teams." Q4's changes helped a lot, we still want to improve further but it is not as high of a priority as the things we're keeping.
  3. Keeping "Make self-hosted backup/restore work excellently."
  4. Keeping "Install a process for managing team changes."
  5. Keeping "Solve license compliance (again)."
  6. Adding hiring backfill.

@chadwhitacre
Copy link
Member Author

chadwhitacre commented Feb 16, 2023

Biweekly Update

  1. 🟢 Make self-hosted backup/restore work excellently #104

    1. Identified three bugs to focus on.
    2. Fixed the first bug.
  2. 🟢 Install a process for managing team changes #90

    1. Produced a first rough draft of process docs🔒.
    2. Synced with IT/devinfra, sketched process for security-as-code ⇒ Google Groups ⇒ GitHub.
  3. ⚠️ Solve license compliance (again) #92

    1. Depends on FOSSA shipping features. Should know more next week.

I tried squeezing in a bonus project and got burned. Still cleaning that up. 😞

(Notion🔒, email🔒)

@chadwhitacre chadwhitacre mentioned this issue Feb 22, 2023
21 tasks
@chadwhitacre
Copy link
Member Author

chadwhitacre commented Mar 1, 2023

Biweekly Update

  1. 🟢 Make self-hosted backup/restore work excellently #104
    1. Fixed second of three bugs.
    2. Working on third bug.
    3. Defined some additional scope.
  2. 🟢 Install a process for managing team changes #90
    1. Looks like Okta might work for Google ⇒ GitHub after all. 👍
    2. Synced with Vlad to understand top-down workflow.
    3. Got a weight off my chest about product vision🔒.
      • Got here because team structure relates to product structure.
      • Tangent: helped define Our Mission & Products🔒.
        • Sentry's mission is to help developers ship high-quality software! 💃
  3. ⚠️ Solve license compliance (again) #92
    1. Waiting for FOSSA to ship.

Bonus project cleanup is done. 🙄

(Notion🔒, email🔒)

@chadwhitacre
Copy link
Member Author

chadwhitacre commented Apr 24, 2023

Biweekly (🤫) Update

  1. 🟢 Make self-hosted backup/restore work excellently #104Shipped!
  2. 🟢 Install a process for managing team changes #90
    1. Wrote How to Answer People Questions🔒
    2. Wrote Parts of Sentry and Their Owners🔒
    3. Aiming to cut over to product-area-based routing this week.
    4. RBAC team aiming to land GitHub teams in code this week.
  3. 🟢 Solve license compliance (again) #92
    1. FOSSA shipped their features.
    2. We implemented more resilient CI integration.
    3. Shipped to most repos, sentry and getsentry any minute now.

@chadwhitacre chadwhitacre unpinned this issue May 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant