---
title: consent concerns
language: en
---

__PUBLISH__
__VARIA__

consent concerns script

Introduction: To be read out loud by the group, one at a time whenever someone feels like reading and speaking (10 mins) 

	Archival practices, dissemination of information and knowledge sharing are crucial actions for intersectional feminist groups. Thinking about this we quickly come to questions of access, are the materials available to those who need and want them? There is also the question of consent. If you share knowledge, do you let it be shared forever? Do you agree to share it with people you may not know? Is your identity intertwined with what you shared, your body with your data, the traces of your online actions with the shared space around and its community, and... What does that mean? How to take care of yourself and each other? When trying to give our attention to consent while building Rosa, we noticed that we didn't notice(!) many moments when we gave consent to both the hardware and software. We are curious to learn with you, to consider how the processes of setting up a server could be different. We also want to think through how consent appears in the ATNOFS project. As Rosa travels and material accumulates in the storage from many different people, how are participants able to make choices in what materials they share, and how they share them? This is a polyvocal project, do we consent to share across our differences? And how can we build trust and communicate our boundaries?

Exercise 1: Hello, consent calling (15 mins)

In a circle we think out loud about how consent is relational and can be re-negotiated
	
		Intro (read to the group): "The origin of the word consent comes from latin and means “con” (together) + “sentire” (feel), therefore, by itself, ideally, it expresses a mutual feeling" (Peña, Varon 2019). We like to think of consent as a relational process. And as a process, it can and should be re-negotiated. We are asking to think over and about the power dynamics within these infrastructures and relationships, how information, knowledge and its comprehension plays out in these scenarios, who's being affected and how can we care for aligned collective attitudes.
	
	We will ask, listen, repeat
	Someone begins by asking a question to the person next to them that requires consent
	
	If the answer is yes then this person (who responded with the yes) poses a new question to the person on their other side
	If the answer is no then the question moves around but we try a modification, what conditions would be needed for consent?
	We can also maintain our response of no. If we would never consent to this request then we can change the question completely and continue the circle around
	We can also choose not to speak if we don't want to, at any time

...

Now we can choose if we would like to do exercise 2 or 3

Exercise 2: Consent related to the server and our relationships around it (20 mins) 

	In pairs or groups of three pick out one scenario of consent from below and talk about it.
	
	Scenarios:
	- You want to use, create or store files in the server but don't want them public or seen by others. How do we keep things private or only available for some in a shared environment? How do we ask for consent?
	- One service or tool is taking too much space and slowing everything down making it difficult for others to continue their work. How could we deal with this? How do we negotiate server space? Do we have permission to stop or delete processes or files?
	
	How and when does consent appear in this scenario? In which moment?
	What does trust feel like here?
	Can you change your mind?

	When you are ready change your scenario, you are also welcome to make a new one.
	Come together as a whole group to share, discuss and take notes.
	
Exercise 3: Begin to edit a consensual Code of Conduct (CoC) for the server (20 mins) 

	(If you went through the languages within languages script already)
	In the terminal on your computer you can display the running processes of Rosa, you can stop them or manage them in other ways. 
	For example, in the terminal you can type commands such as:
			ps aux
	ps aux is a listing of all the processes active in Rosa.
	
	Starting from these practices of listening and reading the server, via commands such as px aux, or practices of log reading, how could we write a CoC for the Rosa server?
	You are welcome to take as a basis the Varia Code of Conduct (https://varia.zone/en/pages/code-of-conduct.html), or any other one, or to create your own.
	You can make a new pad here: https://hub.vvvvvvaria.org/rosa/pad/ for the CoC and if you would like to have it indexed, add the magic word "__PUBLISH__".
	
Wrap up: share and discussion moment (10 mins)

..........
	
References: welcome to add!
https://hub.vvvvvvaria.org/rosa/chapters/varia/consent%20concerns/ConsentToOurDataBodies.pdf
https://hub.vvvvvvaria.org/rosa/chapters/varia/consent-concerns/Kovacs-and-Jain-Informed-Consent-Said-Who-Final.pdf