Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

...


...

CHARTER

Scope & Objectives

The goal of this working group is to describe (and execute?) a plan to stop using the "master" branch name in samvera and samvera-labs Github projects.

...

Git's default "master" branch derives from "master/slave" jargon which perpetuates systemic racist language and systems (see https://mail.gnome.org/archives/desktop-devel-list/2019-May/msg00066.html). To uphold our Samvera Code of Conduct and Anti-Harassment Policy, we must move away from the term "master" in our technical language (as well as words like blacklist or whitelist).

...

  • A new "default branch" name that will replace "master"
  • A date when the new "default branch" will be available on all projects in samvera and samvera-labs GitHub organizations
  • A date when the "master" branch will no longer be available
  • A document describing what to migrate or be aware of:
    • Remediating developer clones
    • Remediating forks (if necessary)
    • Remediating gem references pointing to branches
  • Should we send a community letter to Github about requests for feature?

...

Note that Working Groups must have participants from three different Partners.  All members of a working group producing software must be licensed Samvera contributors covered by the appropriate CLAs. Other types of contributions such as requirements, design, best practices, documentation, etc. - do not require CLAs but participants should accept that the materials to which they contribute may be released under a Creative Commons Attribution 4.0 International License..

...