Coder Social home page Coder Social logo

dei-wg's People

Contributors

danielskatz avatar exoticdft avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

dei-wg's Issues

How do we continue to remind people of inclusive language use?

Some notes from first meeting discussion about this:

  • During last year, the Stanford POC-IT working group had backlash over a list of words
    • Should we mention this in our overview blog post for Black History Month
  • Out-in-tech has community bots that notify users; something we should consider?
    • Ping general community about this concept?
    • Maybe start conversation in DEI-discussions channel, see where this goes, then have steering committee guide further discussion/direction
  • Create a blog post and/or newsletter announcement about this
    • Could we create a single sentence blurb about this for all future, quarterly, etc. newsletters?

DEI Resource Toolkit

DEI Resources Toolkit

  • DEI Resource Toolkit Topics
  • Goal: Series of blog posts (posted on us-rse.org) with common tag,
  • Todo: Poll on Slack with topics to get interest, topics are main categories in list above (one post per topic)
  • One topic idea: Looking for a job as an RSE - academia, industry, government
  • DEI Resources

Draft guideline for invited speakers

We need to complete a draft of guidelines for invited speakers to follow. This will help us pick invited speakers and guide the speakers' presentations towards some topics.

Media Club: June topic, DEI aspects of review processes

We'd like to discuss DEI aspects of review processes

This is related to the US-RSE 2023 conference; it's too late to change any process there but we want to have this discussion now as we document the process we're using to make sure we're prepared for US-RSE 2024 🙂

A starting point for discussion could be the SciPy conference reviewer guidelines, first written in 2017 that include many references I'm pasting in here:

Sources and citations
Prepared by the SciPy 2017 Diversity Committee and Program Chairs. Thanks to Philip B. Stark for useful links.

This document is a compilation from different sources listed below:

https://doughellmann.com/blog/2011/10/18/how-i-review-a-pycon-talk-proposal/

https://nearsoft.com/blog/europython-2016-a-review/

Everyday Bias: Identifying and Navigating Unconscious Judgments in Our Daily Lives. Howard J. Ross.

https://hbr.org/2015/04/3-ways-to-make-less-biased-decisions

https://www.ncbi.nlm.nih.gov/pmc/articles/PMC4238945/#!po=88.4615

[1]http://bmjopen.bmj.com/content/5/9/e008707

[2] http://bjp.rcpsych.org/content/176/1/47/full-text.pdf+html

[3] https://www.ncbi.nlm.nih.gov/pubmed/28580134/

[4] https://www.amazon.com/Everyday-Bias-Identifying-Navigating-Unconscious/dp/1442230835

[5] https://implicit.harvard.edu/implicit/takeatest.html

[6] https://hbr.org/2015/04/3-ways-to-make-less-biased-decisions

[7] Threats to objectivity in peer review: the case of gender

Review DEI webpage and suggest updates

  • Work with Website group to decide on the PR process for WG pages
    • goal is to ping the dei-wg to make sure at least one other person from the dei-wg reviews PRs before they are merged
    • We should choose a specific DEI-WG member as a requester for this update
    • We should also state the PR shouldn’t be merged until it is reviewed by a DEI-WG member
  • Create a PR to update the DEI-WG webpage on us-rse.org, the README here is good place to start
  • Add a “table” of info at the top (email, slack channel, meeting link, co-chairs, etc.)

Collect and share DEI-related metrics

Understanding the demographics of the US-RSE membership will inform our decisions about what DEI goals to focus on as well hold us accountable on our progress in achieving a more diverse membership.

Sample Guidlines: Best Practices for Collecting Demographic Data from Submittable.com

  • #12

  • Determine the purpose and goals

  • Keep it brief

  • Get help from diverse groups when designing questions

  • Explain why you are collecting this information

  • Research best practices

    • Allow multiple selections and always include a blank option for write-in
    • Make questions optional

US-RSE Survey Planning

Adding this presentation [Scipy 2020] Scipy by the Numbers.pdf that @celiacintas very kindly shared with me -- SciPy conference usually reports something like this every year during the Diversity BoF

I think having a visualization like this that we regularly update somewhere (DEI working group page?) could help us hold ourselves accountable

Deciding on Chair/Co-Chair

Chair/Co-chair discussion from 02/14/24:

  • Some groups just have some step down - look for someone to step up, but that can be problematic if no one steps up
  • If people want to step down, try to give ~3 months leadway?
  • Lance and I were concerned about just assuming to stay in the roles
  • We don’t want to have people stay in the position for multiple years without some process that allows them to “easily” throw their hat in the ring
  • How do we get more people to participate in these meetings in general?
    • Emailing agenda on Mondays before the meeting, may help attendance
    • Newsletter “next/upcoming [WG] meetings” section?
  • We should find some better ways to share the Zoom link for the meeting, some have had issues in general finding the Slack link to then get Zoom information
    • “I do think we should capitalize on the bookmarks in Slack for the WGs. We specifically have Zoom link, drive link, our Github initiatives, and other "important links"” - Alex
  • Have a conversation every so often; Every month?
    • Whatever we decide, this would be good to be transparent about for those that are just joining; Maybe have some sort of “bylaws” on the web page

Create a "Guidelines" List for contributing to the Slack Workspace

@sk8forether suggested this idea. This idea was prompted by a Slack discussion about when and where is it appropriate to use things like @channel and such, and the inherent difficulties for neurodiverse folks when trying to navigate social norms. The suggestion would be that having a list of guidelines for expected behavior in this Slack workspace may empower people to contribute without accidentally being perceived as rude or inconsiderate (i.e. by pinging too many people). The guidelines could also include links to "how tos" on controlling notifications.

This would likely fit well on the Get Involved page on the website, so it may also be worth discussing with Outreach WG folks.

@exoticDFT also suggested that - in conjunction with adding this resource - we could limit the chat features (such as @channel) to only maintainers of the Slack workspace or channel to make it easier to not make mistakes. He also noted:

Of course, this is limiting/restricting people from doing certain things, so that might be counter-productive in another way. But worth adding to the discussion...

Make recommendations on how to improve diversity in US-RSE Leadership

Increasing diversity in leadership is an excellent way to ensure the organization has a diverse perspective. It is also a good way to attract more diverse members since they have a better chance of seeing themselves as belonging.

Folder with other notes

Pride Month 2024

Ideas for next year:

  • T-shirt for month of June
  • Pins for Pride and other celebrations
  • Virtual meetups for the different celebrations
  • Short movies (more focused media club activities)
  • Speakers focused on the different celebrations

Black History Month - Feb 2024

Form to ask for ideas

Options

SC'22 Inclusivity

Brainstorming - Miranda Mundt

  • Jay Lofstead is the chair for inclusivity committee at SC’22
  • Miranda is DEI outreach member for SC22 (Chair was given to a person who could not get free registration / travel otherwise)
  • Send her ideas for activities, bofs, etc.
    • LGBTQ+ Community: https://www.nature.com/articles/d41586-020-02325-1 - The event needs to be a welcoming/safe event. Ex: Dallas is a kind of scary place for LGBTQ community members. Location is a big factor.
    • Ongoing Safe Supported Spaces: it would be great to have an on-going affinity group that was specific to a career path (extended throughout the year)
    • RSE-specific get-together: Share backgrounds. Everyone’s background in RSE is so very different (and everyone has imposter syndrome).
    • Peter will send a list of discussion items / problems / solutions from SC’21 last year

Transcribe our videos/records for better accessibility

We'd like to transcribe our current records to provide better, more accurate closed caption.

  1. Currently using YouTube's automation of this
  2. We'd like to update some current ones
  3. We would like to develop a process for doing this when releasing a new recording
  4. Automate this process

Draft Survey Plan

We need to complete a draft survey plan for the entire survey as a first priority. This will enable us to align objectives with questions and data collection. Previous Survey Planning efforts and the first Survey Draft can be used as a starting point.

Streamline new member workflow

Reducing the friction of getting members involved will hopefully make it easier for anyone, including those who identify with under represented group, to find a way that they can contribute to the US-RSE. The general goal is to reduce friction for people to get involved and make it easier for them to find things they may be interested in within the organization.

When people first join US-RSE they may be just "testing the waters" and not immediately join Slack, esp. if they aren't already using the platform. If they don't accept the initial invite right away, they will be missing a lot of the content, discussion, etc. Periodic reminders and ways to reduce the friction of joining Slack afterwards could help.

Similarly, the "Get Involved" page could be updated to include more options at varying levels of commitment.

  • Review message we send when people join US-RSE

  • Determine how to join Slack if you missed the initial invite

    • Currently we advise to email
    • There is a Direct Slack Invite link https://join.slack.com/t/usrse/shared_invite/zt-91yezh46-ZjDvMAA1k3rFcAnpwt_KIg but we can point people to, but we don't want people who aren't on the mailing list using it.
  • Update the "How to Get Involved" web page

    • Include a few options with specific steps at varying levels of commitment
    • Link to get started on Slack - Information on how to join/rejoin Slack if they missed the initial invite
    • Add some “Working Group” instructions
    • A couple of specific, low-barrier things people can do
    • Join a Slack channel based on where they work
    • Attend a community call
  • Link this on every newsletter, mention at meetings, send in welcome email

  • Craft a short message reminding people about Slack and Get Involved that could be added to newsletter, talk slides, etc.

Speaker series/media club webpage

Basically a list for each (recurring) "work product" on the main https://us-rse.org/wg/dei/ page

i.e.

  • one for speaker series, that will include links to talks on YouTube when available
  • one for media club, that will include links to the media: podcasts, books, YouTube links, etc.

@exoticDFT suggests YAML file with data for events that we can update and then have a template using liquid to generate the actual page

Landing page for DEI Celebration Events

The idea is to create a single webpage in the DEI section of the US-RSE website containing all the key information about DEI Celebration Events, with the goal of making it simpler for people who might be interested in getting involved to see what we've done already, and possibly get in touch if they want to be involved.

Some ideas for the content:

  • Collect past initiatives/events
  • Add some kind of "Get involved" contact info (e.g. simple web form)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.