Code of Conduct

MainNavigation	No

This code was initiated in 2020, in the depths of a pandemic, and is irregularly updated. Last updated: May 2024. Contributors: Loes Bogers, André Fincato, Anja Groten, Juliette Lizotte, Karl Moubarak, Margarita Osipian, Sylvie van Wijk.

Report a violation by writing to karl@hackersanddesigners.nl

About the H&D community

Since 2013 Hackers & Designers (H&D) has grown from an informal meetup series at the intersection of art, technology and design into a large community of international designers, artists, coders, students and practitioners. H&D activities cater towards active participation, mutual exchange and (un)learning. H&D likes to approach the organization of such activities as 'horizontal' as possible. That is, the way our events are organized is up for discussion, and we try to incorporate as many voices in the process of organizing as possible.

About this document

With this Code of Conduct, we want to clarify the values and atmosphere we aim to foster and facilitate. We hope it can serve as a guideline for collaboration, as a point of reference for accepted and unaccepted behavior in the spaces where we encounter each other. If you have suggestions, please let us know. (Find contact details at the bottom of the document)

We believe a Code of Conduct is never finished. Therefore, we approach ours as a living document, (re)written as a collaborative effort, informed by experiences, and in conversation with our visitors, participants and collaborators and the references listed below. Every time we rewrite it and read it out loud, for example at the start of a summer camp, we activate what it stands for and open the floor to additions and edits.

Why a Code of Conduct for H&D?

H&D stimulates collaboration across disciplines, technological literacy, different levels of expertise, international borders, ages, languages. To bridge these differences, learn and unlearn from one another does not always go without misunderstanding, feeling excluded or unsafe.

We are committed to providing an environment of mutual respect that is welcoming to all participants. We therefore propose this document as a way to define a common ground, and answer the question: What do we do when, in spite of all efforts, things go wrong?

We expect...

• Attentiveness to language: We use English as the main language of communication. We are mindful of the fact that English is not the native language for many of us. Therefore, we try to use simple language and avoid jargon to keep things accessible for everyone. If we use jargon, we explain what we mean by it.
• Dedication and commitment: People put a lot of energy and thought into organizing. Therefore: if you say you would like to come, please show up and be present. If you can't come after all, please inform us or the workshop facilitators in advance.  
• Listening to others: There's always an opportunity to learn something new from someone else.
• Shared response-abilty: We expect and encourage everyone (both participants and initiators of workshops) to share the responsibility for enacting and sustaining a safer and inspirational space, to be open to different perspectives and encourage one another to make our voices heard. We understand that no space is ever a safe space for everyone; claiming a space to be safe, and actively creating a space that is welcoming and engaging, are two different things. We try to aim for the latter.
• Individual response-ability: We don't assume. Ask questions, speak out about your needs (nobody can read minds), and accept that your needs might not always be met. If you feel you cannot express yourself in a group, please know you can always reach out to a H&D member.
• Willingness to (un)learn: If someone calls us out on something, we try to listen, pause, perhaps apologize and thank them for sharing their concerns. We take responsibility to educate ourselves if we are not aware and are hearing something new (borrowed from Recurse and Feminist Club Amsterdam)
• Embrace experimentation: We like to nourish a space for experimentation and collaboration, so we manage our expectations accordingly!
• Adoption of an open source, libre, collaborative attitude includes giving credit to original authors and sources. Maybe you could consider publishing the work you create in the context of a Summer Camp or workshop explicitly as part of the open domain, so others can build on it? Free/libre Open Source licensing options are discussed below.
• Respect different rhythms of learning: If things go too fast for someone, they should always be able to address it and feel encouraged to ask for help. We consider helping others (when they are asking for it) core to sustaining an inclusive community.
• Value different practices: We celebrate different skill sets, different disciplinary and educational backgrounds. Learn from each other and embrace the fact that you might learn something else than you expected.
• We don't shame people who do not solely use open source and libre tools. However, we strongly encourage to consider using open source over, often more convenient corporate and proprietary tools. Free, libre and open source software allows us to look inside, learn from, contribute to and critique. The open character of the tools we use is crucial to a self-determined learning experience.
• Ask permission: We sometimes record (online) sessions for the purpose of documentation and further distribution. We announce this beforehand and give people the opportunity to share if they prefer not to appear on a picture or recording and, (if online) are able to turn off their camera. We sometimes document on-site workshops for on and offline publications. Before starting to take pictures, we ask others what they feel comfortable with. Would you prefer your face to be blurred out, or would you prefer not being in the pictures at all? Let us know! Are you hosting or participating in a workshop? Please also announce recordings, taking photographs and screen grabs and give people a chance to opt-out.
• Introductions and pronouns: When introducing yourself, please indicate your preferred pronouns. It's a good idea to add your preferred pronouns after your screen name on Jitsi and other platforms (e.g. "Margarita she/her") for easy reference.
• General video conferencing etiquette: Having our camera on is not a must. But if possible, it is definitely nice for facilitators to see who is in the room, so they don't feel like they're speaking into a void. We keep our mic's muted unless we want to say something to the group. Using the chat is a good option to ask questions and make comments without interrupting the flow of the session. (see also https://etherpad.hackersanddesigners.nl/p/hdsa2020-tool-ecology for more recommendations)

Sustainability

We encourage all participants and organizers to contribute toward reducing our collective ecological footprint through responsible sourcing and reduced consumption of resources with a high environmental cost.

• We encourage us to view every project or process through its full lifecycle, considering not just the materials used at the point of creation, but their sourcing, utilization, and responsible disposal/repurposing. This means actively questioning the flow of resources (both physical supplies and ideas) and designing processes that minimize waste across all inputs and outputs.
• We prioritize stocking plant-forward options in our catering. While individual dietary choice is respected, we encourage reflection on the overall ecological impact of consumption - be it food, travel, or digital resources - aiming always for low-impact practices.

Unacceptable behaviour

The following types of behaviour are unacceptable at H&D, both online and in-person:

• Hatred or violence: There is no space for racism, sexism, queer/transphobia, ageism, ableism or classism.
• Harassment
• Trolling / bullying / making fun of
• Exclusionary social behaviours: In the form of well-actually's, feigned surprise, backseat driving and subtle-isms. We borrow these social rules from Recurse and find them very helpful in communities that engage in technical practices and learning. Feigned surprise, for example: Dan: "What’s the command line?" Carol: "Wait, you’ve never used the command line?". For more examples, see also: https://www.recurse.com/social-rules#no-subtle-ism.

Reporting & Intervening

While we strive for open communication, addressing problems when they arise we are not always able to immediately step in and support with conflict resolution. It's for this reason that we want to list alternatives.

Situation that require immediate aid

In case of harassment, abusive behavior, or if there's something else making you feel uncomfortable/unsafe/excluded, you can contact the people from H&D that might be present with you in the space or contact those specifically tasked with ensuring the code of conduct is respected:

Karl      karl@hackersanddesigners.nl

Juliette     juliette@hackersanddesigners.nl

We are not trained in conflict resolution but are committed to help and mediate where we can.

If we receive a report about abusive behavior we will contact the person(s) involved to have a conversation with them. We may revoke access to workshops, activities and physical or digital collaboration spaces if an individual's unacceptable behavior persists.

Confidentiality

What you share is confidential. If we feel like it would be important to share what you discussed with the H&D team or someone else, we explicitly ask for your consent.

Why reach out?

It's important for us to know how to improve and learn from experiences.

Sharing the responsibility of making the spaces and moments we co-create safe(r) and welcoming.

Situations that require immediate aid beyond our capacity: emergency hazards

The emergency number in the Netherlands is 112

Call 112 in case of fire hazards, floods, immediate medical assistance, acute physical danger, etc.

References

• https://www.recurse.com/code-of-conduct
• https://www.recurse.com/social-rules#no-subtle-isms
• https://en.m.wikipedia.org/wiki/Recurse_Center#Social_environment_and_influence
• https://libregraphicsmeeting.org/lgm/public-documentation/code-of-conduct/
• http://constantvzw.org/w/?u=http://media.constantvzw.org/wefts/123/
• https://varia.zone/en/pages/code-of-conduct.html
• http://bangbangcon.com/conduct.html
• https://us.pycon.org/2013/about/code-of-conduct/
• https://geekfeminism.wikia.org/wiki/Conference_anti-harassment/Policy
• http://www.thefeministclub.nl/coc/
• https://pad.riseup.net/p/A_Call_for_Complaint%2C_for_Sick_Speech-keep
• https://snelting.domainepublic.net/wp-content/uploads/SNELTING-CodesofConduct0505.pdf
• The following statement about safe[r] spaces is part of a 'Manifesto on moderation' written by Amal Alhaag and Margarita Osipian: "Understand that no space is ever a safe space for everyone; claiming a space to be safe, and actively creating a space that is welcoming and engaging are two different things. Try to aim for the latter."