-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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
Conversation
There was a problem hiding this 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?
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? |
@jeffhandley we should also update FabricBot automation for both runtime and dotnet-api-docs whenever these adjustments are meant to take effect. |
Thanks for calling that out, @eiriktsarpalis. These assignments will go into effect Nov. 22. Follow-up items at that time:
|
There was a problem hiding this 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
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
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.
area-System.Runtime
pod with @tannergoodingarea-Microsoft.Extensions
pod with @maryamariyan and @tarekgh, and is no longer noted as a Consultant forarea-System.Text.RegularExpressions
area-System.Reflection
pod with @buyaa-n and @joperezr, is noted as a Consultant forarea-System.Text.Json
, and is no longer noted a Consultant forarea-System.Linq
area-Extensions-Caching
gains @adamsitnik as a Consultantarea-System.ComponentModel.Composition
andarea-System.Composition
move to thearea-Microsoft.Extensions
pod with @eerhardt, @maryamariyan, and @tarekgharea-Diagnostics.Activity
gains @eerhardt and @maryamariyan as co-owners alongside @tarekgharea-System.Drawing
remains with @safern, aligning with the Libraries Infrastructure podarea-System.Formats.Cbor
moves to thearea-System.Security
pod with @bartonjs and @GrabYourPitchforks; @eiriktsarpalis is noted as a Consultantarea-System.Text.Encoding
andarea-System.Text.Encodings.Web
move to thearea-System.Security
pod with @bartonjs and @GrabYourPitchforksarea-System.Resources
gains @steveharter as a co-owner and @tarekgh as a Consultantarea-System.Text.RegularExpressions
,area-System.Threading.Channels
, andarea-System.ThreadingTasks
move to thearea-System.Reflection
pod with @buyaa-n, @joperezr, and @steveharterarea-Infrastructure
; the Libraries team members are removedarea-Meta
, with @ericstj and @jeffhandley as the ownersBoth here and in the document, libraries area pod members are listed alphabetically within their pods; that was updated where needed.