Varia's CoC
What: Presentation at Sandberg
When: 27 January 2021
Time: 10am-12pm
Their pad:
Their annotation on CoC:
Who: Luke and Cristina

Trajectory of our CoC
- Professionalisation grant
- Relearn 2019
- Collective Conditions 2019
- Displayed at  |

Perhaps to mention
> Moderator tasks
> How we wanted to ask Eleanor Greenhalgh to give us a workshop but this never happened (CORONA)
> How we wanted to organise field trip days to relax and spend onspanning time with each other but this never happened (CORONA)
> How do we take care of each other online these days?

Our CoC

Abridged Version (in the space)

Pad used by Varias for the preparation

- Discussion on codes of conduct
- Femke Snelting on CoC in Free Software communities
- Geek Feminism's evaluations of CoC
- Collective Conditions Reader

Some Codes of Conduct
- Collective Conditions
- Free BSD
- Hackers & Designers
- Relearn Paris CoC
- Community Agreement
- Geek Feminism

45 min
5 min - what is varia: what we do (events, work groups, infrastructure)
- member run organisation (16), started in 2017 by 5 people, who then invited others in, takes time to establish how you want to run the space
- everyday technology
- examples of events
- run and maintain our own our own infrastructure

10 min - admin model of varia
- very brief intro to what we have now
- before prof / after prof
- proffessionalisation: 3 docs - roles of board, CoC, aims
  - conversations -> points that are important | who feels comfortable with whom
  - we met again to review and edit the documents
  - ginger coons helped with the CoC, Femke Snelting helped with aims of the space
  - we got paid

30 min - varia's CoC
5 min - intro
- make-up of varia: mainly PZI graduates + Luke 
- motivations for CoC
    - what is a CoC : A code of conduct is a document which sets out expectations for members of a community, with regard to how they will behave toward each other. (Geek Feminism)
  - a number of incidents here and there...
  - constant rra/mb invite NOOO1, zeitgeist
  - CoC as part of formalising our organisation
  - CoC popping up in technology communities
  - goals of CoC: 
      -- to affirm the inclusivity and diversity of communities, 
      -- to facilitate the mediation of disagreements, 
      -- and to prevent and respond to cases of harassment. 
  - CoC comes from corporate background (from Femke Snelting's piece): 
      1. Historically, the term ‘Code of Conduct’ appears in relation to changing international business practice in the early 1990s. In the aftermath of state de-regulation and the globalisation of capital, transnational companies were pressured by NGOs and trade unions to adopt voluntary Codes of Conduct. In the absence of state control and international legal frameworks, this would, at least in theory, regulate their impact on social and environmental conditions. It is no surprise that the depoliticised mix of managerial and motivational language of these business codes rings through in documents adopted by projects such as Ubuntu and Python. Both projects operate in a US-based entrepreneurial environment.
      2. A second influence is the informal tradition of ‘netiquette’ which circulated in the early days of the Internet. Reiterating the way etiquette functions as a framework to govern social interactions through behavioral norms, netiquette established a loose set of conventions that facilitated friction- free interaction over networks.5 Common-sensical advice such as “Remember that the recipient (of your e-mail) is a human being whose culture, language, and humor have different points of reference from your own,” has found its way into many Codes of Conduct.
      3. Codes of Conduct are influenced by feminist and LGBTQ activism for Safe Spaces and also by anti-oppressive practices that try to address racism, sexism, homophobia and trans-phobia head on.6 These intersectional approaches to privileges and power can be found back in the language and methods of certain Codes of Conduct, such as the one adopted by FreeBSD. 


- Relearn 2019
- Collective Conditions 2019, standing on shoulders of peers, remixing, adaptations

5 min - other examples of CoC
- LibreHosters
- CoTech and online moderation (
- Examples from other initiatives

10 min
- technical & social relation, how one influences the other; convivial tools ( ); consent is key to privacy: 
    - XMPP Archive Incident (you can literally talk to or be your own sysadmin)
    - feminist servers? The Sudo Incident + 
    - Etherpad welcome message (from opt-out to opt-in)
    - Varia as unintentional service provider
    - XMPP logbot and what can be archived (consent)
    - Convivial Tools 
    - taking photos in the space

5 min Corona situation
- post-COVID situation > we applied for Stimu; 
- pre-stimfonds introspective problem modelling; post-stimfonds meetings where we tried to find ways to support ppl who didn't get funded
- doubled down on infra work
- came up with 4 ppl in the space
- chat overload > move to email for important things
- solidarity financial model: use the donation we received from Alina Lupu to fund the contrib of ppl in case they couldn't pay it due to financial circumstances
- fighting the landlords - rent stop, rent payment ruling, self-organised mess

5 min future
- future
  - review and adapt going forward
  - what would happen in case of violations / transformative justice
  - "no silver bullet": the facilitating we do in meetings builds our skills, the strategies we use (check in at the start of the meeting, messaging a member privately if they feel , holding meetings to figure out how to support ) building capacity to do self-organising; day to day things that bring us into a position we can handle the nazi poster
  - do you need this document? luke: it's the most effective as a backdrop, a place to refer to when things happen; it's an enabling tool; 

place holder on wiki:
Code_of_Conduct page on wiki:

= Questions =

* Why did we start this process (motivating factors for CoC, aims etc.)
* What was the budget and how was the split out (roughly)
* Timeline and how meetings were organised
* before prof / after prof check-list kinda thingy