Text to motivate Code of Conduct at workshops

[weaverbel]

@lexnederbragt asked me a while ago about developing wording Instructors can use to introduce the Code of Conduct at workshops (and I didn't get onto it soon enough, sorry Lex!). I think having a set of words people can use might help new Instructors feel more comfortable raising this in workshop introductions - I am sure some people don't 100% know what to say and might worry that they will say the wrong thing. I am raising it as an issue that might need to be included in the Instructor Training @ErinBecker.

I myself always say something like:

"It is really important to us as Instructors that this workshop provide a welcoming environment for everyone. People learn best when they feel comfortable, and when they feel they belong. Software and Data Carpentry both subscribe to a Code of Conduct - you can find a link to it on line x on the workshop etherpad. The Code can probably be summed up in four words: 'Don't be a jerk!' What does that mean? Apart from prohibiting the obviously unacceptable stuff like harassing or vilifying anyone - do something like that and you will be asked to leave at once - it means this:

• Please don't make someone feel stupid because they don't know what you know.
• Please don't try to make anyone feel bad because of the hardware or software tools they use.
• Please don't talk over people - everyone has an equal right to be heard.
• Please don't mock people's questions.

We are all learners here - including your Instructors! We Instructors take the Code of Conduct very seriously, and we have a process for dealing with violations and complaints. Observing the code makes the workshop better for everyone ... so ... what questions or comments do you have for me about that? ... If no-one has any questions or comments, then let's get started!"

[lexnederbragt]

Thanks, Belinda!

[weaverbel]

I'd be keen to hear your thoughts on this @lexnederbragt - feel free to suggest changes etc.

[lexnederbragt]

It's very good as it is. I probably personally would not say the "do something like that and you will be asked to leave at once " part or tone it down a bit as is is rather heavy (albeit true). But instructors need to adjust the tone to their audience anyway.

[karinlag]

I'm with Lex here - very good, but would not mention the leave at once thing 😁

And I love the "Don't be a jerk". I've wanted to use that expression myself, but was uncertain whether "jerk" was really a swear word...?

[ErinBecker]

"Jerk" isn't considered a swear word in any of the parts of the US I've lived. . . I would recommend incorporating this into the workshop introductions episode. Any other ideas about where this might fit?

…

On Wed, Mar 14, 2018 at 1:46 PM, Karin Lagesen ***@***.***> wrote: I'm with Lex here - very good, but would not mention the leave at once thing 😁 And I love the "Don't be a jerk". I've wanted to use that expression myself, but was uncertain whether "jerk" was really a swear word...? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#645 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ASSbf4D5oe70i8yaeSUIqB0mrBDNyZJzks5teYGigaJpZM4Spt4a> .

-- Associate Director, The Carpentries

[weaverbel]

Happy for the "do that and you will be asked to leave ..." bit to be deleted and I agree - people are welcome to adapt or tailor this to their needs but it is probably easier for them to tailor SOMETHING than make something up on the spot when they are probably juggling twenty different other things to get the workshop underway ...

[weaverbel]

Rewording and adding a tiny bit more:

"It is really important to us as Instructors that this workshop provide a welcoming environment for everyone. People learn best when they feel comfortable, when they feel they belong. Software and Data Carpentry both subscribe to a Code of Conduct - you can find a link to it on line x on the workshop etherpad. The Code can probably be summed up in four words: 'Don't be a jerk!'

What does that mean?

Apart from prohibiting the obviously unacceptable stuff like harassing or vilifying anyone, it also means this:

• Please don't make someone feel stupid because they don't know what you know.
• Please don't try to make anyone feel bad because of the hardware or software tools they use.
• Please don't talk over people - everyone has an equal right to be heard.
• Please don't mock people's questions.

This is a workshop for beginners. If you know nothing at all about what we are going to be teaching here today, that means you're in the right place!

We are all learners here - including your Instructors! We Instructors take the Code of Conduct very seriously, and we have a process for dealing with violations and complaints. Observing the code makes the workshop better for everyone ... so ... what questions or comments do you have for me about that? ... If no-one has any questions or comments, then let's get started!"

[ChristinaLK]

When we talked about this in the study group this fall, @smcclatchy had a wording that I really liked which was "the Code of Conduct is our way of saying that this is a place for you -- you belong here and deserve to be treated with respect while you are here."

And also, echoing @ErinBecker, where do we want to put this? The section on introductions?

[weaverbel]

Love @smcclatchy's wording - are you suggesting it as an addition @ChristinaLK or as a replacement?

And I propose it go in Workshop introductions @ErinBecker

[maneesha]

I also like @smcclatchy 's wording a lot! I think "don't be a jerk" sounds accusatory - and can leave even well meaning people wondering what they might do wrong. The approach of saying "you belong here and deserve to be respected" puts the well being of the participant first.

I think it needs to go as early in the two day training session as possible - we want to set the stage that you always begin by introducing the CoC.

[ChristinaLK]

@weaverbel as an addition -- maybe right before the last sentence of the 1st paragraph?
I guess (w/ @maneesha ), I would replace "don't be a jerk" with "treat people with kindness and respect." The positive vs the negative.

I really like the bullet point list that sets out some specifics! I think it's good to have some examples of what we mean.

@maneesha, I think we're assuming that the trainers are doing this themselves at the start of the training; this text is for future instructors to use when they start workshops. At least I think that was @weaverbel's intent. Although obviously the trainers could use it too!

[lexnederbragt]

Even better, if the trainers do it at the beginning they can refer back to it when this is taught...

[weaverbel]

I take the point that 'don't be a jerk' might sound accusatory but when I say it, it is done humorously and people generally have a laugh, but they do listen, and they like to know what 'don't be a jerk' might mean. But I am happy to have it changed.

Also I always do CoC at the start of instructor training because I generally use a talking stick to help people observe the CoC - i.e. letting shy people be heard, facilitating proper turn taking, making sure people are not interrupting or talking over other people. No stick, no speech - until it's your turn. The stick actually helps people realise some of their behaviours might be a bit overbearing or that their voice is being heard too often.

[karinlag]

@weaverbel I find the talking stick a very interesting concept - I'd like to know more about how people respond to this, but that is probably a discussion for a different thread.

I think I would consider doing a combo - the "don't be a jerk" would get their attention, and I would then switch to saying something like "the basic point is that we want everybody to treat eachother with kindness and respect".

But, I guess we all have different ways of performing these things 😀

[weaverbel]

Happy to discuss the talking stick @karinlag - feedback from people is a) that it reassures them to know there are talking rules, and b) it shows that we really want to hear from / include everyone, especially quieter voices who often drop out of competition to be heard in workshops where certain voices tend to dominate. The stick shows its value often deeper into a workshop - this is where the quieter people would otherwise have switched off / stopped trying to talk because they have been talked over / drowned out too often. But knowing they will get a turn and not be interrupted empowers them to continue contributing. I see it as a physical embodiment and reminder of our Code of Conduct in a way.

[ChristinaLK]

Is any of this in the handbook? Should it be?

[mikoontz]

I just made a pull request to modify the first bullet point (carpentries/docs.carpentries.org#289) and then saw this issue was still open so I'm posting here too. It'd be good to drop "stupid" from the text, as it is a slur. I suggested replacing it with "clueless" which I think better captures what we mean.

[raynamharris]

Good catch @mikoontz. I suggest a different approach for updating the coc in carpentries/docs.carpentries.org#290 and modify this whole portion entirely to match what the Carpentries board approved of and publicised recently https://docs.carpentries.org/topic_folders/policies/code-of-conduct.html My PR will conflict with carpentries/docs.carpentries.org#289

[ChristinaLK]

From a different issue:
"I am wondering if some instructors, especially new instructors, might feel uncertain about to what extent they have the authority to enforce the CoC then and there if something happpens in a workshop. Maybe that would be something we should adress in the curriculum somehow?"

[ChristinaLK]

For the instructor training curriculum, I think we should have a dedicated space to talk about what the CoC is, why we have one, and point people to further resources.

Could go in "motivation" or "how we operate."

[brownsarahm]

This could also go in "workshop introductions" and give trainees practice introducing it