search

MozillaFestival / mozfest-program-2018

Mozilla Festival proposals for 2018
https://mozillafestival.org
100 stars 21 forks source link

Lab CoC: Why we need Code of Conducts, and how to get them in every research laboratory #575

Open mozfest-bot opened 6 years ago

mozfest-bot commented 6 years ago

[ UUID ] f38b43f7-273a-4faf-92f3-fd87814d7bd3

[ Session Name ] Lab CoC: Why we need Code of Conducts, and how to get them in every research laboratory [ Primary Space ] Openness

[ Submitter's Name ] Daniela Saderi [ Submitter's Affiliated Organisation ] Oregon Health & Science University [ Submitter's GitHub ] @dasaderi

[ Other Facilitator 1's Name ] Robin Champieux [ Other Facilitator 1's GitHub ] @rchampieux

What will happen in your session?

Common sense is enough until it isn't. A Code of Conduct outlines expectations for community members, and sometimes that community is an academic lab. CoCs are not only good for establishing productive collaborations between lab members and helping build trust between mentor and mentees. A good one will welcome new members, inspire the team, and make clear the kinds of behavior that won't be tolerated. Ultimately, a good CoC is a tool for fostering a safe, transparent, inclusive, and successful lab. Here, we will discuss why CoCs should be mandatory in academic laboratories and share open templates that can be adopted and adapted. We will invite participants to share experiences and contribute directly to CoC templates on our GitHub repository.

What is the goal or outcome of your session?

The goal of this session is to spark a conversation around why scientific leaders and institutions should encourage (or even mandate) the implementation and enforcement of CoCs in research laboratories to help guide the relationships and expectations of lab members. Our goal is for participants to contribute their knowledge and experience to producing open templates that can be adapted to different circumstances, but are based on the shared objective of wanting to make the academic experience safe, healthy, respectful, equal, and inclusive. We will also share tips on how to engage PIs, department chairs, and program directors in such conversations.

Time needed

60 mins

daniellecrobinson commented 6 years ago

Into it!

dasaderi commented 6 years ago

Thank you for selecting this session! We are really excited to bring this project to Mozfest!

daniellecrobinson commented 6 years ago

If robin can’t go, Kirstie will be there and can talk on this topic!

Sent from my iPhone

On Sep 14, 2018, at 9:56 AM, Daniela Saderi notifications@github.com wrote:

Thank you for selecting this session! We are really excited to bring this project to Mozfest!

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

rchampieux commented 6 years ago

I'm still hoping to attend virtually, but it would be fantastic to tap Kristie's experience. @dasaderi and I have a project meeting tomorrow and are excited to dig into our session plans.

mekline commented 6 years ago

Do you already have enough existing examples to work with? A few people in my corner of 'science twitter' have been sharing lab manuals/expectations for their students recently, and I think at least a few of them explicitly cover codes of conduct...

dasaderi commented 6 years ago

Thank you @mekline. Yes, we do have some example, but the more the merrier.

Here is the repo where we started to gather some info and drafted a template. I look forward to gather more input at Mozfest.

dasaderi commented 6 years ago

Session Plan

Title: Lab CoC: Why we need Code of Conducts, and how to get them in every research laboratory

Goals: a) Discuss the need of Code of Conducts to state clear expectations in a research laboratory environment b) Engage the group in an active design thinking exercise to help develop content as well as a dissemination plan for Lab Code of Conducts

Materials:

Session Outline 1) Introduction (8 minutes) a) Invite participants to introduce themselves with their name, preferred pronouns, and one thing they are passionate about (3 minutes) b) Brief presentation to frame the problem and the structure of the session + ground rules for the session (5 minutes)

2) System mapping – all (10 minutes) The group will be invited to write down on post it notes why they think a CoC is needed in laboratories (or not needed) and name the stakeholders that are involved with the adoption of Lab Cocs. What's the problem being addressed? Who are the players?

3) Understanding users / Empathy maps – breakout groups (10 minutes) Depending on the number of people attending the session, we will split the group in smaller group, designating a note taker to each group. Each group will be working on developing personas and empathy maps (materials for this will be provided) for a previously identified player (e.g., graduate student, lab PI, graduate program director).

4) Ideation / Exploring Lab CoC content – breakout groups (10 minutes) Eeach group will be working on content for the Lab CoC that is related to the persona/player they have been defining in previous section. Some starting point can be found in this GitHub repository where we will then add content to after the session.

5) Engagement and Marketing – breakout groups (10 minutes) The group will be asked to think about how do engage the given group of players they have been working on and have them buy in the idea of a CoC, balancing what needs to be standardized in a core Lab CoC and what can be adapted to each lab/community need. What tools can we give "ambassadors" to help with dissemination and adoption?

6) Final group discussion to bring it all together – all