Skip to content

Add new members to Engine and Cmdlet Working Groups (and typo fix) #15560

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 5 commits into from
Jun 15, 2021
Merged

Add new members to Engine and Cmdlet Working Groups (and typo fix) #15560

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
549bcd1
add Engine and cmdlet WG members (and typo fix)
Jun 10, 2021
d188817
Address Rob's comment
daxian-dbw Jun 15, 2021
5bfe7db
fix spelling mistakes
Jun 15, 2021
8796c5d
fix alphabetization of updated WGs
Jun 15, 2021
5d56351
Update .spelling to actually fix the spelling error
daxian-dbw Jun 15, 2021
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
4 changes: 3 additions & 1 deletion .spelling
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1330,7 +1330,6 @@ adamsitnik
msixbundle
PowerShell-Native#70
AppxManifest.xml

- CHANGELOG/7.0.md
codesign
release-BuildJson
Expand All @@ -1339,3 +1338,6 @@ centos-7
- test/perf/benchmarks/README.md
benchmarked
BenchmarkDotNet
- docs/community/working-group-definitions.md
TobiasPSP
jdhitsolutions
31 changes: 14 additions & 17 deletions docs/community/working-group-definitions.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -58,9 +58,12 @@ However, it's expected that many issues will require input from both WGs.

### Members

* @BrucePay
* @daxian-dbw
* @JamesWTruher
* @rjmholt
* @BrucePay
* @rkeithhill
* @vexx32

## Interactive UX

Expand Down Expand Up @@ -111,11 +114,12 @@ Given the commonality of serialization boundaries, the Remoting WG should also f
* @TravisEz13
* @anmenaga

## Modules
## Cmdlets and Modules

For those core/inbox modules whose source code lives within the `PowerShell/PowerShell` repository,
we may have some set of WGs responsible for their cmdlet design guidelines and enforcement,
as well as to manage the proposal of new cmdlets or breaking changes.
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
cmdlets/parameters, and breaking changes.

However, some modules that ship as part of the PowerShell package are managed in other source repositories.
These modules are owned by the maintainers of those individual repositories.
Expand All @@ -130,18 +134,11 @@ These modules include:
* [`PSReadLine`](https://github.com/PowerShell/PSReadLine)
* [`ThreadJob`](https://github.com/PowerShell/Modules/tree/master/Modules/Microsoft.PowerShell.ThreadJob)

Until it is determined how best to handle the remainder of modules that ship as part of PowerShell,
the following modules will be owned by the Committee and Maintainers:

* CimCmdlets
* Microsoft.PowerShell.Diagnostics
* Microsoft.PowerShell.Host
* Microsoft.PowerShell.Management
* Microsoft.PowerShell.Security
* Microsoft.PowerShell.Utility
* Microsoft.WSMan.Management
* PSDiagnostics
* Web/JSON Cmdlets
### Members

* PowerShell Committee as interim members
* @jdhitsolutions
Comment thread
SteveL-MSFT marked this conversation as resolved.
* @TobiasPSP

## Security

Expand Down
2 changes: 1 addition & 1 deletion docs/community/working-group.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# Working Groups

[Working Groups (WGs)][wg] are collections of contributors with knowledge of specific components or
Working Groups (WGs) are collections of contributors with knowledge of specific components or
technologies in the PowerShell domain.
They are responsible for issue triage/acceptance, code reviews, and providing their expertise to
others in issues, PRs, and RFC discussions.
Expand Down