Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Concrete Action / #BLM Post #110

Merged
merged 32 commits into from
Jun 29, 2020
Merged
Show file tree
Hide file tree
Changes from 23 commits
Commits
Show all changes
32 commits
Select commit Hold shift + click to select a range
03a05e7
Concrete Action: Initial edited draft
ywwg Jun 19, 2020
7682172
concrete action: one sentence per line
ywwg Jun 20, 2020
014e0d8
Update pages/news/2020-XX-XX-concrete-action.html
ywwg Jun 20, 2020
cbf93c2
Update pages/news/2020-XX-XX-concrete-action.html
ywwg Jun 20, 2020
07d0c7e
Update pages/news/2020-XX-XX-concrete-action.html
ywwg Jun 20, 2020
c82268c
reword
ywwg Jun 20, 2020
f8d6467
Merge branch 'terminology-post' of https://github.com/ywwg/website in…
ywwg Jun 20, 2020
6e72636
Update for multiple authors
ywwg Jun 20, 2020
c484d61
notes addressed
ywwg Jun 20, 2020
e3610a2
opening graf
ywwg Jun 20, 2020
141f3de
Apply suggestions from code review
ywwg Jun 21, 2020
0cba9be
rewordings
ywwg Jun 21, 2020
1d231b5
Merge branch 'terminology-post' of https://github.com/ywwg/website in…
ywwg Jun 21, 2020
721d633
Apply suggestions from code review
ywwg Jun 21, 2020
5fecff3
irony!
ywwg Jun 21, 2020
b5e37e4
Merge branch 'terminology-post' of https://github.com/ywwg/website in…
ywwg Jun 21, 2020
321ae7d
trying to nail down the wording of this important graf
ywwg Jun 22, 2020
6b15008
make it more clear that we can't eliminate "master" everywhere
ywwg Jun 22, 2020
ce171d2
more links for background on the movement
ywwg Jun 22, 2020
4c8ec1b
Update pages/news/2020-XX-XX-concrete-action.html
ywwg Jun 22, 2020
d7a0369
fill in the placeholders
ywwg Jun 22, 2020
2145f2e
more realistic number of cycles
ywwg Jun 22, 2020
91b7fd6
more optimistic
ywwg Jun 22, 2020
90cda94
Update pages/news/2020-XX-XX-concrete-action.html
ywwg Jun 23, 2020
1ce566e
restore link to dance music history
ywwg Jun 23, 2020
75d47ab
reword -> foundational
ywwg Jun 25, 2020
1d0b511
outreachy committment
ywwg Jun 28, 2020
5d6f1f4
Apply suggestions from code review
ywwg Jun 29, 2020
7dbcf08
tweak title
ywwg Jun 29, 2020
d12ac59
Merge branch 'terminology-post' of https://github.com/ywwg/website in…
ywwg Jun 29, 2020
4dd567e
change filename
ywwg Jun 29, 2020
882a538
notes
ywwg Jun 29, 2020
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
65 changes: 65 additions & 0 deletions pages/news/2020-XX-XX-concrete-action.html
Original file line number Diff line number Diff line change
@@ -0,0 +1,65 @@
title: Concrete Action: Taking a Stand with Terminology and Recruitment
ywwg marked this conversation as resolved.
Show resolved Hide resolved
author: Mixxx, April
date: 2020-06-08 01:00:00

{% extends "post.html" %}

{% block post %}

{% load markup %}
{% filter markdown:"extra" %}

# #BlackLivesMatter

Alongside the protesters in the US and around the world, the Mixxx team unequivocally condemns police brutality.
The systemic racism that burdens people of color every day is the responsibility of white people around the world to address.
Mixxx' core development team feels it necessary not to remain silent on this issue, for ["silence in the face of injustice is complicity with the oppressor."](https://www.theguardian.com/news/2000/sep/14/guardianobituaries)

Going beyond the hashtag, we have been discussing concrete actions we can take as a community and today we announce two efforts: first, to fully **[eliminate master/slave terminology](https://www.washingtonpost.com/opinions/2020/06/12/tech-industry-has-an-ugly-master-slave-problem/) from our code base** and second, to **recruit paid interns from underrepresented communities** to join our contributor base.
ywwg marked this conversation as resolved.
Show resolved Hide resolved

## Terminology Changes

Major projects like [Python](https://www.vice.com/en_us/article/8x7akv/masterslave-terminology-was-removed-from-python-programming-language), [Go](https://www.reddit.com/r/golang/comments/gy9ylr/go_has_removed_all_uses_of_blacklistwhitelist_and/fte1zk0/), and now [Github](https://www.cnet.com/news/microsofts-github-is-removing-coding-terms-like-master-and-slave/) have all worked to eliminate the use of the [problematic](https://blog.carbonfive.com/problematic-terminology-in-open-source/) terms, "master" and "slave," and today Mixxx joins them.
The issue of nomenclature and terminology in software is one example of how deeply embedded white privilege is around the globe and we hope changing these terms is one small step towards a more inclusive and diverse coding community.

Although we eliminated the use of the word "slave" back in [2016](https://github.com/mixxxdj/mixxx/commit/e59916caf72a256bb28b1722759a629c5cc9cf81), "master" still appears in a number of places.
We have a "master" code branch, a "Master Sync" feature, an "EngineMaster" object, and more.
We are working to migrate our code away from these words, even in many cases where the particular meaning of "master" was never explicitly associated with a problematic context.

It’s important to note that there will be some cases where the word will remain.
Many DJ controllers have buttons marked "master" on them, and we need to refer to those buttons by name.
There are also the audio engineering concepts of a "master tape" or "audio mastering", so there may be areas of our documentation or code that would be less understandable if we tried to use synonyms.
But in situations where "master" is used in code, we commit to changing the language we use by the end of the year.

But changing language is not enough.

## Building A More Diverse Community

As an entirely online community that allows anyone to participate with a pseudonym, we don't know the exact demographic makeup of our contributors.
Our impression, however, is that the Mixxx contributor base is largely white, male, and either from the US or Western Europe.
Employers have a tacit (and sometimes explicit) expectation that prospective employees "prove themselves" by contributing to open source projects. Companies also often value referrals, which increase the likelihood that new hires will be similar to previous hires, thus perpetuating homogeneity.
ywwg marked this conversation as resolved.
Show resolved Hide resolved
We want to break this cycle and ensure that the door to our open source network is open to everyone.
It is our goal to make both the Mixxx community and the software we make as inclusive, accessible and welcoming as possible.
As such, it is our responsibility to actively seek out and promote the participation of groups who are underrepresented in our community.

Research shows that blind admission and hiring tends to result in less diverse outcomes.
To that end, we plan to participate in the [Outreachy](https://www.outreachy.org/) program and have a paid internship position by December 2020, the next available cycle.
Outreachy’s stated goal is to provide "internships to work in open source and free software, for women (both cis and trans), trans men, and genderqueer people" and "residents and nationals of the United States of any gender who are Black/African American, Hispanic/Latin@, Native American/American Indian, Alaska Native, Native Hawaiian, or Pacific Islander."
They encourage "anyone who faces under-representation, systemic bias, or discrimination in the technology industry of their country" to apply.

Our goal is that this Outreachy intern will be one of an increasing number of valued contributors from more diverse backgrounds that will help us be a healthier, more sustainable open source project.
With your help, we intend to continue the internship process semiannually for at least 2 cycles, or how ever many we are able to raise funding for, and at that time assess if we should continue with the program or if our diversification efforts would be better served with a new approach.
Copy link
Member

@Holzhaus Holzhaus Jun 23, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How do we fund the second cycle if we don't get enough donations?

And it's also possible that we stop after 2 cycles if our assessment determined we should rather do something else right? But it also says we participate how every many cycles we are able to raise funding for. That's a contradiction.


An Outreachy intern will cost Mixxx $6,500 to sponsor.
As a project that is entirely community-driven, we are looking to you, our collaborators and users, to secure the funding for this effort. There is no company behind Mixxx.
All Mixxx developers are volunteers that work on Mixxx in their free time.
We [have never and will never charge for Mixxx](/news/2020-05-22-you-dont-need-to-pay-for-mixxx/), so this is a chance for you to contribute money that will go directly to a person working on the project.

We are currently working out the details of our fundraiser and we hope to have it launched in the next couple weeks.

We're aware that replacing some terms and participating in Outreachy might seem insignificant in light of the discrimination and violence that people of color and Black people in particular face every day.
As a project that depends on donations and volunteer work, we invite all our collaborators and users to discuss further community action on [Zulip](https://mixxx.zulipchat.com) as we continue to stand against racism and discrimination.
Keep protesting!

ywwg marked this conversation as resolved.
Show resolved Hide resolved
{% endfilter %}
{% endblock %}
15 changes: 13 additions & 2 deletions plugins/news.py
Original file line number Diff line number Diff line change
Expand Up @@ -12,8 +12,14 @@
POSTS = []
AUTHOR_METADATA = {
'': {
"name": "Mixxx Team",
"url": "https://github.com/orgs/mixxxdj/people",
'name': 'Mixxx Team',
'url': 'https://github.com/orgs/mixxxdj/people',
'email': 'core-team@mixxx.org',
},
'Mixxx': {
'name': 'Mixxx Team',
'url': 'https://github.com/orgs/mixxxdj/people',
'email': 'core-team@mixxx.org',
},
'Be.': {
'github': 'Be-ing',
Expand All @@ -34,6 +40,11 @@
'Pegasus': {
'github': 'Pegasus-RPG',
},
'April': {
'name': 'April M. Crehan',
'github': 'ThisGrrrlFriday',
'email': 'amcrehan@gmail.com',
},
}


Expand Down