Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Meta issue: How/where should complaints about working-group members be lodged? #19730

Copy link
Copy link
@mklement0

Description

@mklement0
Issue body actions

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

Reactions are currently unavailable

Metadata

Metadata

Assignees

No one assigned

    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

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      Morty Proxy This is a proxified and sanitized view of the page, visit original site.