"... the study of intersections between forms or systems of oppression, domination or discrimination. An example is ... that the experience of being a [rainbow] [unicorn] cannot be understood in terms of being [rainbow], and of being [a unicorn], considered independently, but must include the interactions, which frequently reinforce each other." -- Wikipedia
Scientific python seems to reside in a technological space where the combined diversity issues of both science and computing compound one other to ill-effect.
The old developers aren't diverse. So, we need new developers to join in.
“The feedback giver explained that he 'used high standards' in evaluating the essays for publication in the teaching magazine. Still, he said, having read the student’s essay, he believed the student could meet those standards. His criticism, this form of feedback implies, was offered to help the student meet the publication’s high standards. Black students trusted this feedback as much as white students, and trusting it powerfully motivated them to improve their essay.”
-- Claude Steele, Whistling Vivaldi
New Developer Instructions
Comprehensive Documentation
Accessible Listhost
Define Expectations Clearly
Curate Low Hanging Fruit
Give Permissions Generously
Strict Issue Assignment Workflow
Targeted Sprints
Appoint an Ambassador
Mentor Users Directly
Consider Users Conferences
A lot of this material came from my personal experience. However, much of it was annealed from conversations with colleagues throughout the scientific and computing communities (too many of you to name). I got some specific ideas for this particular talk from here and here.