chapter

WP1 Prep

You can edit this pad by visiting: https://etherport.org/w/rsr::Connecting_Otherwise::WP1:_Collecting_and_Connecting::Notes.md

Note: changes may not show up directly in the site

Notes 2 April

Introduction
- Talking about documentation and checkin in between the workshop leaders
- Etherport onboarding -> getting input for the session
- Alix and Gijs created a work in progress version of the website
- Already have an idea how to document the project but good to have a discussion
- Structure of the website
  - static elements and working tools
  - different categories of pads with different looks: notes, articles
  - Different typeface for notes and articles
  - Alix is working on a typeface, based on the title to use aas identity
  - Public and private pads
  - Rules for making new pads and for consistency
Structure of publication
- Rewriting introductions for the project, thinking more about the audience and to reflect changes that happened in the wps
- Introductions are accesible by clicking on WP titles
- Format for documentation
  - Etherport was developed as an event report tool, back then it had a rigid structure
  - Proposed structure below in notes in agenda meeting 2nd april
  - Public notes pad for each workshop
  - A pad preapred before the workshops that can be shared with participants behorehand
  - Pads are used during workshops as well for documentation, participants can simultaneously edit it
  - Coversations recoded after the workshops
  - Articles from WP members
- Annotation system of Etherport can be used to reflect changes in the text on the margins instead of deleting text
- Wheb you press print it automatically generates a pdf of the publication but it doesnt include the notes
- We could include some of the workshop outputs in the publication, essays etc from the students
Buglist for features and improvements
- Agenda/calendar functionality using th eannotation system > annotated segments are collected based on the date of the activity
Planning for next week
- We will learn more about to learn with etherpad
- Ideas form imporovements and collecting bugs -> system to priopritize them
General discussion
- Anja will leave -> recurring WP leader meetings
- Connecting with students to join the workshops
- Mark is direct contact at GRA so sometimes its easier for them to just contact people there rather then emailing to save time
- Next meeting 4 April 12-13:00

Agenda for the meeting WP leaders, 2nd April

Structure preliminary website:

General content
- Introduction (Lilian, Anja)
- Bibliography / Further reading
- Colophon
WP specific
- Introduction (Lilian, Dorine, Margarita, Anja)
- Workshop script
- Workshop outcomes
- Reflections in different formats
- Note pads
- References / resources
Possible structuring elements
- chapters (WPs)
- tags (relating content)
- annotations / reacties on the text / comments
- footnotes / references
- MO: materials (thought this could be nice since we are thinking about materiality)

Documentation workflow:

Before and during the workshop (by workshop facilitators) and during workshop (with participants)
- Documentation strategies
  - To discuss:
    - Task/role division in documentation during workshop
    - Developing a structure that can accommodate documentation during workshops
    - How to activate and include participants in the documentation, use the pad during the workshops
  - Proposed structure of a pad for a workshop (prepared by workshop facilitators in collab with WP leaders):
    - Workshop title
    - Date, time, duration
    - Location
    - Names facilitators
    - Participants (to be filled during introduction round, + what is their interest in the topic)
    - Workshop description/announcement
      - Can include learning goals / what to expect and what participants get out of the workshop
    - Time table / workshop structure
      - Participants add through eg. writing prompts / ideation space / gathering of process
    - Manual / instructions / eg. code documentations / worksheets
    - Workshop outcomes (pictures or scans of materials, situations, texts written, works produced… )
    - Resources / links / further readings
    - Particpant quotes during the workshop
    - Closing reflections
After the workshop
- Recorded conversations
  - group conversation (based on quotes, more dynamic)
  - interview-style (more structured)
  - …
- Reflective articles
- Postscripts
- Annotations on the workshop script
- Articles
- (Visual) essays

To dos:

Before 2 April: Move existing WP Etherpads to etherport structure
Rewriting WP introductions (by WP leaders)
In the session of 9 April discuss the “in retrospect” section of the publication. Do participants have specific articles they are working on that can be part of the publication?
With Margarita and Dorine:
- how to use etherport/pads during workshop and outside of the workshops
- what is content wise interesting to add:
  - media and formats
- documentation internal sessions vs workshops with participants
- what functions of etherport would be useful for this publication? **12 March meeting with Alix on identity **

Planning poster

Moment to check in and give comments
Content ready for Alix by 1 April (delivered by Dorine)
6 April Design ready for feedback
7 April Moment to check in and give comments
Final design ready by April 10
Print in week of April 13
Poster done by April 20

26 February

Meeting with Alix

Would be good to create an public bug list + keep track of hacks and work arounds + what would be nice adjustments to etherport
Part of wish list: TOC now generates title and page number, but it would be nice if you can structurally add more to the TOC if you want (author name, small abstracts,… )
Alix thinks its valuable to work more closely with a developer on the publication. Heerko can help Alix with this. Maybe a session sitting together would be great. For preliminary website: Heerko can help build up the structure, Alix styles it.
Lilian: reach out to Gijs about preliminary website. Afterwards: create group and discuss schedule.
Design principles: main goal project awareness about different access needs, screen readers,
Gijs: is Etherport accessible for screen readers?
Preliminary one: maybe Heerko and Alix can work on the website without Gijs having the website finished.
12 March 12h c
Ask Márk to book a moment to print the posters mid april / costs (week of 13th of April) / final design done by 10th of April –brent
- A2 sourcing of paper at printers?
- Alix goes by the silkscreen workshop in March / developing the identity together
- Lilian connects heerko and alix

Meeting Anja + Lilian

Results survey so far?
Approaching counter mapping
- plan session with partners?
- BB colophoning approach / Constant example ecosystem / orbit of practices https://observatory.constantvzw.org/tgsoguide_1803211855.pdf
Reconnecting to the topic of commoning / how to involve gijs more in this quesiton of commoning
Guidelines for documentation for different groups
- When to plan this session, optimally before WP2 is starting / so every WP can think about best strategies to document their research / work so that it is usable for others, maybe we need a framework for documentation somehow eg. toolbox or workshop manual (gabriel fontana, workshop scripts publication), collect good and bad references how to share this knowledge (MU platform)
  - https://etherpad.hackersanddesigners.nl/p/WP2-Earthbound_Hardware
- Plan Etherport session
Reviewing budget distribution for different participants in WP1?
Agenda and prep meeting on Monday

Internal work sessions:

** End of March – 2.5 hrs **

Internal session #1 (project management):

   * Etherport introduction + documentation strategies (WP) / development documentation framework for Connecting Otherwise  
   * Sharing of possible learning formats, how documentation can be integral to the workshop rather than an add-on 
   * Where/how can the learning formats live on? 
   * Participants: Gijs, Lilian, Dorine, Heerko, Margarita, Radek, Michele, Anja, BB  
   * Notes / documentation: Márk

** End of April – 1.5 hrs**

Internal Session #2: Counter mapping

   *         
   * Participants: Gijs, Lilian, Heerko, Margarita, Radek, Anja

End of September – 1.5 hrs Internal Session #3: Commoning / Collective ownership
- Where can the learning formats live on? Be activated in other contexts?
- Participants: Sepp, Lilian, Gijs, (BB), Anja, Radek, Heerko
  Mid / End October – 2.5 hrs
Internal Session #4: Documentation Etherport / Preparing student workshop
- Hacks and workarounds
- Bugs or not? November
Student workshop(s) / Practicum Generale:
- Colophoning / Web-to-print / Reusing knowledge and materials
- Simultaneous development of publication (writing, editing, designing)
  **November - December **
Planning final event with WP leaders: Lilian, Margarita, Dorine, Anja, Márk **To do **
Márk actuals budget material costs, create (move some budget from workshop materials to travel costs)
Copyediting costs (from workshop materials)
WP 2 (for lunch and materials, check with Heerko) for material costs
Heerko’s uren (web development – materieele kosten)
- Alix: 4500,00 Publication, visual identity (3000,00 + 1500,00)
- Heerko: 1000-2000,00 (web development)
Gijs reiskosten? **Heerko hours **
From material costs
- Web development fee: 2000,00
From WP1
- Initial hours
  - Research & development 12 hrs
  - Development counter mapping 12 hrs
  - Sending out processing survey data 3 hrs
  - Research studio, internal work sessions 8 hrs
  - **Total: 35 hrs **
- Remapping of hours
  - From material costs
    - Web development fee: 2000,00 (divided between preliminiary and final website/publication, working closely with Alix on implementation of design and interacting with Gijs on technical implementations)
- Role in WP1: Familiarising and teaching with Etherport, documentation from user and teacher perspective, developing learning formats about web2print with 2 outputs in mind (material/printed + website) * Research & development: Developing learning formats / student workshop(s) about web2print with BB (hrs outside of internal work sessions): 12 hrs ** * Preparing internal work sessions 4 hrs * Internal work sessions 8 hrs ** * Documentation Etherport – user perspective (in collab with Alix): 5 hrs * Documentation learning format / workshop for publication (in collab with BB): 6 hrs

**Radek hours **

From WP1
- Initial hours
  - Research & development 8 hrs
  - Sending out processing survey data 3 hrs
  - Research studio, internal work sessions 8 hrs
  - **Total: 19 hrs **
- Remapping of hours
- Role in WP1: Familiarising with Etherport, and using it in other context in the future (Small file media festival, university in dublin and vancouver), contributing to publication, informing Etherport development from ‘small file’ perspective
  - Research studio, internal work sessions (doesnt need to join the last session which is focussed on preparing student workshop) 6 hrs
  - Documentation Small File Media tools / methods WP3: **5 hrs **
  - Contribution to publication (written article): **8 hrs **

16 February

**Design brief for Alix **

About the project:

Connecting Otherwise

Developing artistic/design research methodologies and workshop formats for regenerative digital practices

Commissioner:

Rietveld Sandberg Research

The Hmm

Connecting Otherwise is an artistic/design research project that focuses on the development of interdisciplinary workshop formats exploring regenerative aesthetics and the materiality of digital technologies through hands-on and collective research approaches.

Brief

Development of a coherent visual identity that reflects the essence of the research project and can be applied to various digital and material deliverables.
Identity should convey following principles inherent to the project:

make tangible and reimagine digital materiality
hands-on and collaborative research methods
learning / researching through making
The “material lens” / digital materiality
breaking the dichotomy of digital vs material
process-driven
open-source / commons-based approach to reuse and dissemination of existing knowledge
reuse / regeneration / frugatlity (low band-width, low res, slow connectivity) as aspirational for digital design and art making
feminist / decolonial hacking principles
should be appealing to both art school population as well as wider audience of creative practitioners and cultural producers Deliverables
Concept and design for the overall project “Connecting Otherwise”
- including typographic concept, color-scheme, concept for image treatment
Posters for workshop announcements (for digital use: portrait and horizontal) as well as printed in small edition (at Rietveld)
Preliminary website and process tool, in Etherport (general project description, wp descriptions, index and embed of pads)
Hybrid publication produced in Etherport (ref. https://expandedpublishing.net/), output should be a website that can display rich media content as well as a pdf that can fullfils print requirements
Some give-away? sticker? Requirements
Accessible, low impact design (light weight, screen reader accessible)
Open source fonts

Deadlines

Initial website (end of March?)
Announcement poster WP2 (ask Dorine when she needs)

19 January 2026

Meeting WP1: Collecting and Connecting

Gijs Open Source Publishing - Etherport publishing platform
Sepp - “Etherport” through Going Hybrid research project, Institute For Network Cultures (deinstitutionalizing)
Heerko - Part of Hackers & Designers, Concerned with the publishing part, worked on Octomode a lot, Markdown integration
Alix - Worked with Etherport with Xpub, graphic designer, Designed the publication Going Hybrid (??)
Miquel, Gersande, (Ott) - BookBinding / BB Workshop
Mark - research coordinator, and artist
Anja - Project leader, uplfting workshops, addressing structural issues in how workshops are recognized vs curricular education, How Material Comes to Matter
Lilian - The Hmm, hands on way of learning, practice what you preach, red line in their programme about energy consumption in our digital life and that’s where this project fits in. Worked with Etherport
- Leader of WP1 Collecting and Connecting
- Overarching WP, digital tools in use and their alternatives, mapping and countermapping
- WP also takes care of the reporting of what has been delivered in the project and delivers a publication made with Etherport
- Etherport is not only the publishing tool but also addressed within the project
WP4 Ancestral Connections
- Michele Boulogne - Gleb from TXT
- Process driven addressing digital technologies through material lens, developing workshop methodologies ultimately
WP2 Earthbound Hardware
- Looking at sand and clay that we find in computation
- Looking at computation mor egenerative and less wasteful way
- Dorine van Meel is the workpackage leader
- Researchers from the ceramic department and the garden department
- Herko is taking a part in this WP
- Field trip, study trip to NXP, company designing computer chips
WP3 Small File Publishing
- moving image
- compression techniques
- working together with Media Lab, XLab or Video editing workshop
Publication and reporting develops from the get go
The first workshop will take place in April, WP2
There is an emphasis on what is already there and acknowledging that rather than inventing new things
BB Workshop - think about how to develop a workshop or learning format, using Etherport and publishing tools, making tools to be distributed and reused
Sepp: economic, social organization of Etherport
- initially was developed in collab with framer framed who does not use it at all now
- getting requests from all over the world
- disseminiating but not making it commercial
- organically growing co-cohort using the tool
- sepp wants to do organizing work, think about tool ecologies, building community around the tools
  - wants to organize an assembly, involving more of the osp team
  - discuss governance of the tool
  - and also economic question 1000.00-1500,00 / year, how to organize that, setting these things into motion
  - what are other natural partners to involve, PhDArts, there interest, are also deinstitutionalizing
  - project timeline / technical development roadmap aligning them
Gijs
- Making it more robust, nu,ber of users expanding
- Separate access
- Different layers of documentation,
  - end user
  - potential implementor or manitainer for another group of users
  - docuentation in the code for programmers
- How to receive feedback?
- Hot to support and maintain a community around the tool? What kind of insrastruture is necessary there?
- How to document feedback? Bug tracking? Issues that evolve, trouble shooting, future technical features, but are there other ways of addressing bugs and issues To Do’s
make etherport more rbist, more accessible, importance of documentation
make user accounts for all people involved
documentation
- end user
- maintainer
- documentation in the code
feedback from users
Printing practices?
Alix
- Documenting Etherport for designers
- Needs some investigative hacking attitude
- Working with tomasso on a standard template for publishing
- for event reporting there is a template structure incl. tagging system
- Tactical Media publication -> makle a template that could serve as a basis for this series and maybe for others
- https://expandedpublishing.net/
Subject of reuse in relation to design explore as a condition
Look into how others are documenting?
More freedom for designer-focussed documentation (Alix could be involved in this part)
- Manual video, illustration of processes