Track potential change to OpenJSF Code of Conduct

Open
#27 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Domain
documentation

Research direction

Start by reading the linked OpenJS Foundation issues 852 and 786 and pull request 851 to determine whether the proposed Code of Conduct changes were decided. Done means updating the repository's Code of Conduct to match an agreed OpenJS Foundation change, but this issue names no target file or settled wording.

Written by the indexing model from the issue text.

Description

openjsf

There has been some discussion on the CoC in the OpenJSF with regards to a silent change in Contributor Covenant v2.1 and some wording.

There's also discussion surrounding changing the CoC handling requirements for OpenJSF projects.

This issue is to track this potential change so that we can update our CoC to match OpenJSF's changes.

see: https://github.com/openjs-foundation/cross-project-council/issues/852
see: https://github.com/openjs-foundation/cross-project-council/pull/851
see: https://github.com/openjs-foundation/cross-project-council/issues/786

Dominant language
No language data
Stars
0
Forks
0
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from loopbackio/loopback-governance

All issues in loopbackio/loopback-governance

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.