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

Prepare Q2 2023 Engineering goals #2269

Closed
damianavila opened this issue Feb 27, 2023 · 4 comments
Closed

Prepare Q2 2023 Engineering goals #2269

damianavila opened this issue Feb 27, 2023 · 4 comments
Assignees

Comments

@damianavila
Copy link
Contributor

damianavila commented Feb 27, 2023

Context

Let's agree and prepare/refine the goals we want to pursue in Q2.
And let's make that plan happen before Q2 starts!!

Proposal

I have signaled a few proto-Q2 goals in #2122 (and previous goal issues).

That is essentially a mix of making our infra more robust (1), recovering back some money (2), and building something new (3).

I am open to discussing and bringing up other things, but I think we need to collectively focus on more concrete goals. These topics are already big ones, so I am proposing to aim for small improvements on each of those topics! And those concrete small steps should be well specified before we enter the next quarter.

cc @2i2c-org/engineering so we start dropping ideas!!

Updates and actions

For the Q2 goals definition, we followed the process outlined in 2i2c-org/team-compass#697.

Our notes about this process live in the Prod and Eng meeting notes:

@damianavila
Copy link
Contributor Author

Monitoring and alert

Non-paging ticket alerts (idea from @pnasrat): #2288 (comment) and slack discussion: https://2i2c.slack.com/archives/C01GLCC1VCN/p1677759173803229?thread_ts=1677746693.014559&cid=C01GLCC1VCN.

@consideRatio
Copy link
Contributor

@damianavila I opened #2293 as a goal proposal for Q2.

I also think it would be very valuable if we could make node sharing a default and help hubs transition towards it, but I'd like to not outline that in more detail right now, but its represented by #2121.

@choldgraf
Copy link
Member

@damianavila I believe that this process is now complete, so I'm going to close the issue. Let me know if you wanted to keep it open throughout the sprint or something, but I believe that these goals are now incorporated into the strategic objectives board: https://github.com/orgs/2i2c-org/projects/34/views/7

@github-project-automation github-project-automation bot moved this from In Progress ⚡ to Done 🎉 in Sprint Board Apr 24, 2023
@github-project-automation github-project-automation bot moved this from Needs Shaping / Refinement to Complete in DEPRECATED Engineering and Product Backlog Apr 24, 2023
@damianavila
Copy link
Contributor Author

I also have captured our Eng goals in the Eng board: https://github.com/orgs/2i2c-org/projects/22/views/50.
And for the record, all the planning around Q2 goals lives in the following document: https://docs.google.com/document/d/1dUO2USQlRbcjOEkjlCu1gyTaPBZmGZSRF4L-_9xecmA/edit#heading=h.ycnyhh6g1ri6

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
No open projects
Archived in project
Development

No branches or pull requests

3 participants