Re: inclusive language

Trevor Woerner

On Wed 2020-07-15 @ 12:25:23 PM, akuster808 wrote:
On 7/15/20 10:45 AM, Trevor Woerner wrote:
On Wed 2020-07-15 @ 08:33:56 PM, Adrian Bunk wrote:
On Wed, Jul 15, 2020 at 01:31:34AM -0400, Trevor Woerner wrote:
4. What will be affected? Branch names, variable names, function names,
fetchers, patch file names, documentation… Given the fact we build code from
upstream projects, if we currently build from an upstream's master branch and
that upstream project never changes the name of their main branch away from
"master", I don't think there's anything we can do in those cases.
If the word "master" alone is considered non-inclusive for people in
the US then CVs are also affected, like speaker bios at conferences.

What replacement term are US universities using for their M-word degrees?
This is a good question.

Some projects are replacing "master" in isolation; such as when used as a branch
name. Other projects are only replacing "master" when paired with "slave".
 "Master" has been used in commit headers, so do we intend on re-writing
git history?
Right now we're in the discussion phase.

As far as I'm concerned, if most people who speak up decide that's what we
should do, then that's what I'll work towards; although (from the feedback so
far) I doubt that's the path we'll take.

Join { to automatically receive all group messages.