Skip to content

Update WG members #21091

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.

Sign up for GitHub

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
daxian-dbw merged 3 commits into from
Feb 1, 2024
Merged

Update WG members #21091

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
51d4832
Update WG members
StevenBucher98 Jan 17, 2024
9d8fbd8
Added bergmeister
StevenBucher98 Jan 18, 2024
7113097
fix linting problems
StevenBucher98 Jan 31, 2024
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
32 changes: 16 additions & 16 deletions docs/community/working-group-definitions.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -38,6 +38,7 @@ Special consideration should be given to topics like **backwards compatibility**
* @adityapatwardhan (SDK)
* @michaeltlombardi
* @SeeminglyScience
* @bergmeister

## Engine

Expand All @@ -49,8 +50,8 @@ This includes (but is not limited to):
* The language parser
* The command and parameter binders
* The module and provider systems
* `*-Item` cmdlets
* Providers
* `*-Item` cmdlets
* Providers
* Performance
* Componentization
* AssemblyLoadContext
Expand All @@ -61,7 +62,6 @@ However, it's expected that many issues will require input from both WGs.

### Members

* @BrucePay
* @daxian-dbw
* @JamesWTruher
* @rkeithhill
Expand Down Expand Up @@ -104,7 +104,6 @@ particularly given the long-lasting effects of language decisions.

* @JamesWTruher
* @daxian-dbw
* @BrucePay
* @SeeminglyScience

## Remoting
Expand All @@ -118,14 +117,13 @@ Given the commonality of serialization boundaries, the Remoting WG should also f
### Members

* @anmenaga
* @PaulHigin
* @TravisEz13

## Cmdlets and Modules

The Cmdlet WG should focus on core/inbox modules whose source code lives within the
`PowerShell/PowerShell` repository,
including the proposal of new cmdlets and parameters, improvements and bug fixes to existing
including the proposal of new cmdlets and parameters, improvements and bugfixes to existing
cmdlets/parameters, and breaking changes.

However, some modules that ship as part of the PowerShell package are managed in other source repositories.
Expand All @@ -147,6 +145,7 @@ These modules include:
* @SteveL-MSFT
* @jdhitsolutions
* @TobiasPSP
* @doctordns

## Security

Expand All @@ -156,7 +155,8 @@ in order to provide their expertise, concerns, and guidance.
### Members

* @TravisEz13
* @PaulHigin
* @SydneySmithReal
* @anamnavi

## Explicitly not Working Groups

Expand All @@ -170,12 +170,12 @@ This bucket is also not oriented a customer-facing deliverable and is already so
so we don't need to address it as part of the WGs.

* Build
* `build.psm1`
* `install-powershell.ps1`
* Build infrastructure and automation
* `build.psm1`
* `install-powershell.ps1`
* Build infrastructure and automation
* Packaging
* Scripts
* Infrastructure
* Scripts
* Infrastructure

### Quality

Expand All @@ -184,10 +184,10 @@ Similar to the topic of building PowerShell, quality
should be managed by the PowerShell Maintainers.

* Test code
* Pester unit tests
* xUnit unit tests
* Pester unit tests
* xUnit unit tests
* Test infrastructure
* Nightlies
* CI
* Nightlies
* CI
* Code coverage
* Pester