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

Update area-owners to reflect Libraries Area Pod changes #61642

Merged
merged 3 commits into from Nov 19, 2021
Merged

Update area-owners to reflect Libraries Area Pod changes #61642

merged 3 commits into from Nov 19, 2021

Conversation

jeffhandley
Copy link
Member

@jeffhandley jeffhandley commented Nov 16, 2021

As we transition from .NET 6 to .NET 7, we're making some changes to the Libraries Area Pods. These changes grant new assignments for folks where desired, incorporate feedback, and make some small load balancing adjustments.

  1. @safern moves to the Libraries Infrastructure pod, with @ViktorHofer and @Anipik removed from the areas
  2. @michaelgsharp moves to the area-System.Runtime pod with @tannergooding
  3. @eerhardt joins the area-Microsoft.Extensions pod with @maryamariyan and @tarekgh, and is no longer noted as a Consultant for area-System.Text.RegularExpressions
  4. @steveharter moves to the area-System.Reflection pod with @buyaa-n and @joperezr, is noted as a Consultant for area-System.Text.Json, and is no longer noted a Consultant for area-System.Linq
  5. area-Extensions-Caching gains @adamsitnik as a Consultant
  6. area-System.ComponentModel.Composition and area-System.Composition move to the area-Microsoft.Extensions pod with @eerhardt, @maryamariyan, and @tarekgh
  7. area-Diagnostics.Activity gains @eerhardt and @maryamariyan as co-owners alongside @tarekgh
  8. area-System.Drawing remains with @safern, aligning with the Libraries Infrastructure pod
  9. area-System.Formats.Cbor moves to the area-System.Security pod with @bartonjs and @GrabYourPitchforks; @eiriktsarpalis is noted as a Consultant
  10. area-System.Text.Encoding and area-System.Text.Encodings.Web move to the area-System.Security pod with @bartonjs and @GrabYourPitchforks
  11. area-System.Resources gains @steveharter as a co-owner and @tarekgh as a Consultant
  12. area-System.Text.RegularExpressions, area-System.Threading.Channels, and area-System.ThreadingTasks move to the area-System.Reflection pod with @buyaa-n, @joperezr, and @steveharter
  13. @ericstj becomes the lead for the pod with @buyaa-n, @joperezr, and @steveharter
  14. @jeffhandley becomes the lead for the pod with @eiriktsarpalis, @krwq, and @layomia
  15. @agocke becomes the lead for area-Infrastructure; the Libraries team members are removed
  16. @danmoseley becomes the lead for area-Meta, with @ericstj and @jeffhandley as the owners

Both here and in the document, libraries area pod members are listed alphabetically within their pods; that was updated where needed.

@jeffhandley jeffhandley added this to the 7.0.0 milestone Nov 16, 2021
@jeffhandley jeffhandley self-assigned this Nov 16, 2021
@ghost ghost added this to Needs triage in Triage POD for Meta, Reflection, etc Nov 16, 2021
Copy link
Member

@tannergooding tannergooding left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.

Is it worth tracking other area ownerships, like ML.NET, in this file as well? That way we have a single central place people can lookup owners, particularly for cross cutting changes?

@jeffhandley
Copy link
Member Author

Thanks, @danmoseley, @agocke, and @tannergooding. Note: I'd like to wait for @ericstj to review before merge. There's no rush.

As far as tracking supplemental repos like dotnet/machinelearning and dotnet/iot, I'd support having another table under the Architectures section. @terrajobst, would that break any of your tooling if we added another table in here for that purpose?

@eiriktsarpalis
Copy link
Member

@jeffhandley we should also update FabricBot automation for both runtime and dotnet-api-docs whenever these adjustments are meant to take effect.

@jeffhandley
Copy link
Member Author

jeffhandley commented Nov 16, 2021

Thanks for calling that out, @eiriktsarpalis. These assignments will go into effect Nov. 22. Follow-up items at that time:

  1. Update the GitHub area teams to reflect new memberships
  2. Update the FabricBot rules for notifications

docs/area-owners.md Outdated Show resolved Hide resolved
Copy link
Member

@ericstj ericstj left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This adjusts the lead ownership for JSON / Reflection pods

docs/area-owners.md Outdated Show resolved Hide resolved
docs/area-owners.md Outdated Show resolved Hide resolved
docs/area-owners.md Outdated Show resolved Hide resolved
docs/area-owners.md Outdated Show resolved Hide resolved
docs/area-owners.md Outdated Show resolved Hide resolved
docs/area-owners.md Outdated Show resolved Hide resolved
docs/area-owners.md Outdated Show resolved Hide resolved
docs/area-owners.md Outdated Show resolved Hide resolved
docs/area-owners.md Outdated Show resolved Hide resolved
docs/area-owners.md Outdated Show resolved Hide resolved
Copy link
Member

@ericstj ericstj left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@joperezr joperezr moved this from Needs triage to Jose's triage backlog in Triage POD for Meta, Reflection, etc Nov 17, 2021
@jeffhandley jeffhandley modified the milestones: 7.0.0, Future Nov 19, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

7 participants