varia ATNOFS chapter facilitation

to do:

• devise way to read CoC
• make welcoming pad (on rosa) for list of supermarkets, restaurants, bars, our contact info, schedule, etc...
• print CoC for buddy time / tuesday (julia)
• write out info for buddys / should it be printed and hand on along with the CoC?
• make a question pad --> questions are added to the rosa pad https://hub.vvvvvvaria.org/rosa/pad/p/rosa
• access statement - https://pad.vvvvvvaria.org/access
• collect extension cables
• put spideralex recording through speech to text
• add a moment for capturing/recording/logging; starting from the middle of those who are here? how can we facilitate this?

Saturday 26 & Sunday 27 March
10:00 - 18:00

Wednesday 23. March
18:00 - 20:00 online presentations, using Narrowcast, broadcast from Varia

prep for the day:

• set the beamer
• coffee and stuff
• breakfast

Saturday 26. March
9:30 -  10:00 breakfast
10:00 - 11:00 

• • amy says. House Info.
    • Thank you for coming
    • no photo - wear a sticker - you can make the legend
    • toilet is there
    • CoC - Julia & Artemis
    • covid
      • - state of restrictions in the NL (basically none)
      • - uncertain times, we are still trying to understand how to navigate them
      • - open to the different needs in the room
      • - if you would like us to wear masks, please do not hesitate to let the coc person know, at any point, can be anonymous
      • - please try to take a self test
      • - RIB as part of the attempt to spread out and have more space + we can also be outside
    • RIB, where is?
    • Introduce the script.
  • Everyone says. (scripted introduction to the project (pass script around the room and everyone reads one line))

• • • General Intro to Varia, ATNOFS and the Varia chapter <script: one person reads a word/sentence/paragraph/none>https://hub.vvvvvvaria.org/rosa/pad/p/begin.atnofs

• • cristina says. introduction to making a chapter in this weekend
    • - resonant publishing
    • - soft structure
    • - license
    • - moment on sunday to review
    • - __PUBLISH__
    • - rosa urls, please only share with groups that you trust
  • manetta and alice say. Infrastructure / Rosa
    • - pads
    • - octomode
    • - folds
    • - files
    • - server access
  • alice says. Round of introductions 
    • 5 min to talk to the person on your left
    • introduce the other person: their name, find out one anothers pronouns, and converse the question: what was the last thing you made public? (interpret that as you like)
  • julia says. Activities for the day (3 simultaneous to rotate through)
  • amy says. Starting with buddy time

11:00 - 11:30

• (beamer) introduce publishing infrastructure, tour of rosa
• share proposed varia activities / proposal of roles / invitation to transform and make variations of activities and roles
  • - alias workshop/voices of rosa - languages within languages
  • - octomode/soft structure workshop / resonant tentacular publishing
  • - consent*? making public/citation practices/open licenses

11:30 - 12:00 + coffee + peepee

• introduce buddy system and get buddy's to go over CoC together (https://www.youtube.com/watch?v=VhTa1q0mqdg)
• share Code of Conduct (https://varia.zone/en/pages/code-of-conduct.html)
• chat w/ buddy

12:00 - 13:00

• 1 x 1 hour activities/roles - rest when you want

13:00 - 14:00 LUNCH
14:00 - 16:00

• 2 x 1 hour activities/roles - rest when you want

16:30 - 17:00

• Buddy time

17:00 - 18:00 Sharing: summary, imagination

• 3 min: 1 to 1
• 5 min: 4 people
• 10 min: 8 people
• 20 min: all together
• total: 38 min + 10mins explanation and moving around + 10mins closing
  • (remind people to meet their buddy at breakfast)

18:00 - 19:00 drinks & conversation

Sunday 27. March
9:30 - 10:00 breakfast w/ Buddy
10:00 - 11:30 shorter intro & listening workshop
11:30 - 11:45

• !!!!

11:45 - 13:00

• activities continue in freeflow

13:00 - 14:00 LUNCH
14:00 - 17:00 w/coffee

• people share propositions if they have an activity to propose
• and / or people continue with what they already started
• and / or gather materials for documentation, how can your work be shared?

17:00 - 18:00 print party w/booze

notes from chat w/ marloes
multiple small exercises
on the server but also outside of it, what does it mean to have a feminist server?
thinking about consent and the small interaction with the server, thinking about consent within feminism, how can we change the language with the server in order to think about consent and your interaction with the server. How a shared space as a server can be safe, how they can be private, how we can trust each other. What is private and what is in between, how language can highlight this conversation

the server is not the central point
it is the space for sharing
we are going to be working on a soft structure, a way to imagine what can be documented and in what form. it gives a framework. it gives styling. using the octomode we go from pads to pdf to print. Michael used the term soft structure to talk about the sponge.
we have some more ideas, on Saturday we want to do 3 short workshops in a rotation manner.

marloes will steal people away for interview

finger protocol
challenging ideas of availability - requires a lot of energy and labour
if a feminist server goes into a pocket to travel then this connects
oooo does maps of the labour

questions about rosa

How is Rosa a feminist server?
How does Rosa operate?
what does operate mean?
Does operate mean work?
Does work mean labour?
Is this labour paid?
Is this work around Rosa elitist or niche? Is it available for all?
Is niche the same as elitist?
Does getting to know Rosa involve commitment?
What barriers are there in making that commitment?
What makes us feel like we can trust each other?
Can we think of Rosa in plural?
How is Rosa different if it runs on the same software as other servers (who don't say their feminist)?
What is the difference between a feminist server and a server maintained with feminist principles?
What is the difference between a community server and a feminist server?
will rosa have time to go to rest/sleep?
What does it mean to personify Rosa?
Why is Rosa given the label of feminist?
How is Rosa intersectional?
How is personifying Rosa with a female name affecting our relationship with it?
Is Rosa only a female name?
Does Rosa have pronouns?
Could Rosa choose their own pronouns?
Can Rosa have characteristics without personification?
Can complex systems do stuff without personification?
What's the problem with personification?
What is the urgency to make Rosa?
How could one argue that Rosa is not a feminist server?
Is Rosa only software or hardware?
Is this division (software / hardware) binary?
What happens if you think otherwise?
How does Rosa relate to their environment?
Are there more extension cables?
Can I unplug something?
How can we relate/connect to a technical device as a server in different ways, with different knowledges?
How to make space for technical and other ways of shaping a server?
How to get away from that hierarchy?
How to intertwine different knowledges?
How to make sure there is still space for conversation about Rosa without splitting up?
How to respect and appreciate different skills?
How to do break away from the fear of technical work, while not overloading yourself in the meantime?
Is it a question of time?
How to not dismiss things as simply technical?
How to formulate this into a question?
Can publishing play a role that?
Can dinners play a role in that?
What do you want for lunch?
Where are we having dinner this week?
Can I have breakfast now?
How to acknowledge the extractivist processes that have allowed Rosa to come to be?
...

• • • • • • • • • • • • • • • • We wonder about these things.

How can we make feminist server practices public?
How can we share our practices, through publishing?
How do we learn?
How can we develop feminist methods?
How can we make feminist technologies?
What is publishing?
What are feminist technologies?
Is feminism intrinsically about sharing?