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

- removes peter from code owners #1630

Merged
merged 1 commit into from
Apr 17, 2024
Merged

- removes peter from code owners #1630

merged 1 commit into from
Apr 17, 2024

Conversation

baywet
Copy link
Member

@baywet baywet commented Apr 17, 2024

  • replaces baywet by coseguera since he is now the crew leader

- replaces baywet by coseguera since he is now the crew leader
@MaggieKimani1
Copy link
Contributor

@baywet you're leaving us? 😢

Copy link

Quality Gate Passed Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarCloud

@baywet baywet merged commit e308430 into vnext Apr 17, 2024
8 of 10 checks passed
@baywet baywet deleted the baywet-patch-1 branch April 17, 2024 12:59
@baywet
Copy link
Member Author

baywet commented Apr 17, 2024

@MaggieKimani1 not leaving the broader team no. But I'm at a place where my workload is just not manageable anymore. I've been struggling for months, and coming back from vacations, the backlog is growing faster than I can process items.
Now that @coseguera is in charge of "OpenAPI libs" with a "crew", and he is a principal level person, I think it makes sense he takes one the responsibility to review code changes in this area moving forward.

@MaggieKimani1
Copy link
Contributor

@MaggieKimani1 not leaving the broader team no. But I'm at a place where my workload is just not manageable anymore. I've been struggling for months, and coming back from vacations, the backlog is growing faster than I can process items. Now that @coseguera is in charge of "OpenAPI libs" with a "crew", and he is a principal level person, I think it makes sense he takes one the responsibility to review code changes in this area moving forward.

Ok that's completely understandable. It's been great working with you! 😁

@baywet
Copy link
Member Author

baywet commented Apr 17, 2024

thanks! likewise! don't hesitate to send a perspective if you feel like so.

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

Successfully merging this pull request may close these issues.

3 participants