Scope & Objectives
Narrative text that should result in a common understanding of:
...
The overall domain into which the discussion falls
...
The shared needs and requirements within that domain
...
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). In looking to live up to our Code of Conduct, we need to move away from the term "master" in our technical language (as well as words like blacklist or whitelist).
On the Samvera Tech Call 2020-07-01, the call members acknowledged that there could be technical repercussions for changing a branch name that many of us have assumed as "ever present." As part of the working group's effort, they will gather known use cases and layout a plan to transition from "master" to a yet to be named default branch. At present, a current working understanding is that we would need to deprecate the use of "master" branch and allow downstream adopters a chance to adjust their implementations.
Deliverables & Timeframe
Narrative or bulleted text describing the tangible outcomes of the working group.
...
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..
- facilitator's name here, facilitator (facilitator's institution here)
- your name here (your institution here)
Resources
- helpful links
Meeting Notes
- list of links
- or table of meeting notes