Uh oh!
There was an error while loading. Please reload this page.
Update area-owners to reflect Libraries Area Pod changes - #61642
Conversation
tannergooding
left a comment
There was a problem hiding this comment.
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
commented
Nov 16, 2021
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
commented
Nov 16, 2021
@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:
|
Uh oh!
There was an error while loading. Please reload this page.
ericstj
left a comment
There was a problem hiding this comment.
This adjusts the lead ownership for JSON / Reflection pods
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
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.Runtimepod with @tannergoodingarea-Microsoft.Extensionspod with @maryamariyan and @tarekgh, and is no longer noted as a Consultant forarea-System.Text.RegularExpressionsarea-System.Reflectionpod with @buyaa-n and @joperezr, is noted as a Consultant forarea-System.Text.Json, and is no longer noted a Consultant forarea-System.Linqarea-Extensions-Cachinggains @adamsitnik as a Consultantarea-System.ComponentModel.Compositionandarea-System.Compositionmove to thearea-Microsoft.Extensionspod with @eerhardt, @maryamariyan, and @tarekgharea-Diagnostics.Activitygains @eerhardt and @maryamariyan as co-owners alongside @tarekgharea-System.Drawingremains with @safern, aligning with the Libraries Infrastructure podarea-System.Formats.Cbormoves to thearea-System.Securitypod with @bartonjs and @GrabYourPitchforks; @eiriktsarpalis is noted as a Consultantarea-System.Text.Encodingandarea-System.Text.Encodings.Webmove to thearea-System.Securitypod with @bartonjs and @GrabYourPitchforksarea-System.Resourcesgains @steveharter as a co-owner and @tarekgh as a Consultantarea-System.Text.RegularExpressions,area-System.Threading.Channels, andarea-System.ThreadingTasksmove to thearea-System.Reflectionpod 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.