...
...
...
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
- This should be coordinated with the Component Maintenance Working Group (Phase 1) to help ensure resources for the "master" removal date
- 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?
...
Meeting Times & Communication Channels
...
- First meeting - 2020/07/31 3:00 - 4:00PM EST
- Zoom info - https://princeton.zoom.us/j/94589539731
Meeting ID: 945 8953 9731
One tap mobile
+13017158592,,94589539731# US (Germantown)
+13126266799,,94589539731# US (Chicago)
- Zoom info - https://princeton.zoom.us/j/94589539731
Slack Channel: #branch-renaming-wg
Note that following current best practices within Samvera, interest and working groups should use an existing communication channel unless and until it becomes clear that a dedicated channel is needed. This section should specify which existing channel(s) will be used: e.g., samvera-tech, samvera-partners, samvera-community@googlegroups.com. When using a shared channel, individual working groups should start the subject line with their name in []s, such as [archives] for the Archives Working Group. If and when a dedicated channel is needed, the new channel should be well publicized and open to any interested subscribers/participants in the community.
...
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..
...
- Collin Brittle (Emory)
- Chris Colvard (Deactivated) (Ubiquity Press)
- Alexandra Dunn (UCSB) (2020)
- Jeremy Friesen (University of Notre Dame) (This is Jeremy, I do not need to facilitate this, and for those interested in facilitating a WG, I believe this may be a great opportunity as the scope and time-frame is rather narrow)
- Kate Lynch (Princeton University)
- Alexandra Dunn (UCSB
- James Griffin (Princeton University)
- Facilitator Kate Lynch (Princeton University)
- Lynette Rayle (Cornell University)
- Collin Brittle (Emory)
- Chris Colvard (Deactivated) (Ubiquity Press)