Skip to content

Add newly joined members to their respective Working Groups #16849

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

Merged
merged 2 commits into from
Feb 8, 2022
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions docs/community/working-group-definitions.md
Original file line number Diff line number Diff line change
Expand Up @@ -20,6 +20,8 @@ Today, DSC is integrated into the PowerShell language, and we need to manage it
* @TravisEz13
* @theJasonHelmick
* @anmenaga
* @gaelcolas
* @michaeltlombardi

## Developer Experience

Expand All @@ -33,6 +35,8 @@ Special consideration should be given to topics like **backwards compatibility**

* @JamesWTruher (PS Standard, module authoring)
* @adityapatwardhan (SDK)
* @michaeltlombardi
* @SeeminglyScience

## Engine

Expand Down Expand Up @@ -81,6 +85,8 @@ These topics include (but are not limited to):
* @daxian-dbw (PSReadline / IntelliSense)
* @adityapatwardhan (Markdown / help system)
* @JamesWTruher (cmdlet design)
* @SeeminglyScience
* @kilasuit

## Language

Expand All @@ -95,6 +101,7 @@ particularly given the long-lasting effects of language decisions.
* @JamesWTruher
* @daxian-dbw
* @BrucePay
* @SeeminglyScience

## Remoting

Expand Down Expand Up @@ -136,6 +143,8 @@ These modules include:
* PowerShell Committee as interim members
* @jdhitsolutions
* @TobiasPSP
* @doctordns
* @jhoneill

## Security

Expand Down