-
Notifications
You must be signed in to change notification settings - Fork 8.1k
Closed
Labels
Issue-Enhancementthe issue is more of a feature request than a bugthe issue is more of a feature request than a bugResolution-FixedThe issue is fixed.The issue is fixed.WG-Cmdletsgeneral cmdlet issuesgeneral cmdlet issuesWG-DevEx-SDKhosting PowerShell as a runtime, PowerShell's APIs, PowerShell Standard, or development of moduleshosting PowerShell as a runtime, PowerShell's APIs, PowerShell Standard, or development of modulesWG-Enginecore PowerShell engine, interpreter, and runtimecore PowerShell engine, interpreter, and runtimeWG-Interactive-Consolethe console experiencethe console experienceWG-Languageparser, language semanticsparser, language semanticsWG-RemotingPSRP issues with any transport layerPSRP issues with any transport layerWG-Securitysecurity related areas such as JEAsecurity related areas such as JEA
Description
Summary of the new feature / enhancement
The Code of Conduct (understandably) only broadly defines unacceptable behaviors; e.g., "Disruptive behavior".
It also states:
We encourage all communities to resolve issues on their own whenever possible.
In that vein:
The responsibilities of working groups are laid out here and here.
Resolving complaints in the context of PowerShell's working groups seems like something that should be handled on a community (repository) level, yet the linked documents do not define a process for that - all there is are DOs and DON'Ts, and the following admonishment:
It's worth noting that Working Group members who repeatedly speak on behalf of the Working Group without consensus, they may be censured or removed from the team.
Therefore:
- If a community member perceives inappropriate behavior on the part of a working-group member, how can a complaint be lodged?
- Raise a separate issue here?
- @-mention a specific user designated as an arbiter / point of first contact in the context of the issue at hand?
- Send an email to a yet-to-be-announced working-group/community-specific email address?
Proposed technical implementation details (optional)
No response
Metadata
Metadata
Assignees
Labels
Issue-Enhancementthe issue is more of a feature request than a bugthe issue is more of a feature request than a bugResolution-FixedThe issue is fixed.The issue is fixed.WG-Cmdletsgeneral cmdlet issuesgeneral cmdlet issuesWG-DevEx-SDKhosting PowerShell as a runtime, PowerShell's APIs, PowerShell Standard, or development of moduleshosting PowerShell as a runtime, PowerShell's APIs, PowerShell Standard, or development of modulesWG-Enginecore PowerShell engine, interpreter, and runtimecore PowerShell engine, interpreter, and runtimeWG-Interactive-Consolethe console experiencethe console experienceWG-Languageparser, language semanticsparser, language semanticsWG-RemotingPSRP issues with any transport layerPSRP issues with any transport layerWG-Securitysecurity related areas such as JEAsecurity related areas such as JEA