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

Create 2020-10-05-how-to-deversify-your-team.md.md #106

Open
wants to merge 5 commits into
base: master
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
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
33 changes: 33 additions & 0 deletions _posts/2020-10-05-how-to-deversify-your-team.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,33 @@
# OA call for a more diverse team

After Julien Colomb sent a request for a more diverse team members for his [jams open source initiative](https://github.com/jam-schema/jams),
Andre Maia Chagas followed up, expressing similar problems for his [Open Neuroscience project](https://open-neuroscience.com/en/).
The two decided to ask for help to determine what they could do in the hope to attract a more diverse crowd in their project,
that are lead mostly or even exclusively by white male men.

![screenshot of slack messages](/assets/img/posts/slack-screenshot-2020.png)

This blog is gatehring the diverse advice they received from the community.

resources:
https://openlifesci.org/posts/2020/10/01/annual-report-part-1/

from malvika:

>there is a small video tutorial we have created which should be launched at the JupyterCon this Friday on Open Source Community: inclusive practices. A preliminary set of resources can be seen here: https://github.com/jupytercon/2020-OpenSourceCommunities (presentations).
This tutorial asks people to think about why we need diversity, who our community members are, why they would like to work on our project, what value exchange is created between our project and their involvements, what inclusive practices we can develop for them in the projects, and how we can start creating leadership roles for members who we want to see in the community. Would evaluating these aspects be useful?
As Yo suggested, inviting people who are missing from your community will be the first step. Then, allowing them to make decisions around what is needed for them to feel supported in your project will be more important/effective than making decision for them/



actively inviting people who are outside your current representation, both to participate but also to the leadership team.

From https://figshare.com/articles/presentation/Does_Research_Software_Engineering_have_a_diversity_crisis_and_what_can_we_do_/12955094/4:

https://discover-cookbook.numfocus.org/ : cookbook on organising inclusive conferences

https://www.recurse.com/manual :rule of the recurse place, put in particular social rules that are interesting.

https://frameshiftconsulting.com/ally-skills-workshop/ : learn working against biais and exclusion while being part of the priviledged part of the society: become an ally.

https://womeninhpc.org/community/resources : ressource on getting better at being inclusive
Binary file added assets/img/posts/slack-screenshot-2020.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.