Skip to content

Code of Conduct requirements under Merged Foundation #663

Description

@mhdawson

The requirements for a Code of Conduct on projects under a merged Foundation are being discussed in this issue: openjs-foundation/cross-project-council#80.

In it's current form it would require that the Node.js project delegate the escalation process to the Foundation level and use a common Code of Conduct. I believe the proposed common Code of Conduct is in alignment with what we already do (or close enough not to be a concern).

A number of TSC members have already chimed into the discussion. Based on discussion in the private section of the last TSC meeting we agreed that wewe want to make sure we have TSC consensus that the proposed approach will be acceptable to use as a group.

I'd ask the following:

Based on the results we'll flow that feedback into the discussion on openjs-foundation/cross-project-council#80

@nodejs/tsc

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    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