Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • M mozfest-program-2018
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 295
    • Issues 295
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • MozFest (Mozilla Festival)
  • mozfest-program-2018
  • Issues
  • #575
Closed
Open
Issue created Aug 01, 2018 by mozfest-bot@mozfest-bot

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

[ 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

Assignee
Assign to
Time tracking