User:Riviera/Draft project proposal/v3: Difference between revisions

From XPUB & Lens-Based wiki
 
(6 intermediate revisions by the same user not shown)
Line 2: Line 2:
= What do you want to make? =
= What do you want to make? =


It’s a newsletter, keeping people up to date with goings-on. On one level, this is a story about a project drawing to a close. In a race against time, the exit strategy is the plot. On a different level, it’s a record of what’s going on at Klankschool.
It’s a newsletter, keeping people up to date with goings-on. On one level, the project addresses the topic of how people aiming to setup servers ought to proceed. Hoping to set up a community infrastructure project? Then seriously consider what is offered by others and do so responsibly. In terms of content, the newsletter may include pieces of text, sounds, algorithms or git repositories. That is to say, it refers to various services running on the klankschool server which I set up in October 2024. It aims to offer coverage of what has taken place at Klankschool since the previous newsletter. On a different level, it’s a record of what’s going on at Klankschool.


It’s release date follows a lunar calendar. It will be published every Last Quarter Moon between December and June. It is circumspect in tone.
By the time the end arrives I hope to:<br />
1. Publish several newsletters<br />
2. Handover everything relating to the server<br />
3. Meet other reasonable requests brought forward by others based on this proposal. For example, saving passwords in a password manager database file.


<span id="how-do-you-plan-to-make-it"></span>
The release date of the newsletter follows a lunar calendar. It will be published every Last Quarter Moon between December and June. It is circumspect in tone.
 
<span id="how_do_you_plan_to_make_it"></span>
= How do you plan to make it? =
= How do you plan to make it? =


I plan to collaborate with Rosa on this project. She and I have a generative back-and-forth in conversations with one another. We have agreed to use markdown as a document format for writing together. We are also planning to use openproject as a way of documenting contributions, project planning, keeping track of tasks. As I will discuss later, ensuring the stability of these systems is important. There is more than one server at play. I set up a containerised mail server and deployed it on a VPS with 2GB of RAM for 15EUR/month. I want to ensure that Klankschool reaches a broad collection of people by building a community around it. I hope to demonstrate the value of an email server to Klankschool through co-curating, attending and writing about a programme of events.
I plan to collaborate with Rosa on this project. The newsletter is thus an effort to document a time-limited collaboration. Rosa and I have discussed putting things on at Klankschool, such as a series of classes about combining live coding with disused hardware. The newsletter may include columns documenting the outcomes of these endeavours. In general, I want to prune the branches of the server over the span of six months, preferring to keep it simple, rather than complex and expansive. I aim to document this practice with a view to extricating myself from the responsibilities I have taken on in relation to the server. Openproject may facilitate with documenting contributions, project planning and keeping track of tasks. Ensuring the stability of the latter system is important to the extent that it is considered a key infrastructural component. Rosa and I agree to use markdown as a document format when writing the newsletter. Initially, I considered using a VPS to run a small mail server. It is likely content will be transcluded and turned into HTML using a static site generator.


<span id="what-is-your-timetable"></span>
<span id="what-is-your-timetable"></span>
= What is your timetable? =
= What is your timetable? =


Line 17: Line 23:


'''November - December:'''<br />
'''November - December:'''<br />
- Warm up the mail server.<br />
- Drum up enthusiasm about programme amongst community members.<br />
- Drum up enthusiasm about amongst community members.<br />
- Advertise the Performances<br />
- Advertise the Performances;<br />
- Organise a workshop<br />
- DONE Speak with Stephen Kerr about these matters<br />
- Organise a workshop.<br />
- Thursday evenings are for repairing.
 
'''Sunday, December 22, 2024: 11:23pm (CET)'''<br />
publish newsletter zero<br />
Topic: Terms of Service
 
'''Tuesday, January 21, 2025: 9:35pm (CET)'''<br />
publish newsletter one<br />
Topic: Privacy Policy


'''Thursday, February 20, 2025: 6:38pm (CET)'''<br />
publish newsletter two:<br />
Topic: Code of Conduct


'''Saturday, March 22, 2025: 12:36pm (CET)'''<br />
{| class="wikitable"
publish newsletter three:<br />
|-
Topic: Counter-cloud action special - DNS Providers
! style="text-align: left;"| Month \ Type
! style="text-align: left;"| Meet
! style="text-align: left;"| Publish Newsletter
! style="text-align: left;"| Topic
|-
| style="text-align: left;"| December
| style="text-align: left;"| Sunday 8th
| style="text-align: left;"| Sunday 22nd
| style="text-align: left;"| Passwords
|-
| style="text-align: left;"| January
| style="text-align: left;"| Tuesday 7th
| style="text-align: left;"| Tuesday 21st
| style="text-align: left;"| Terms of Service
|-
| style="text-align: left;"| February
| style="text-align: left;"| Wednesday 5th
| style="text-align: left;"| Thursday 20th
| style="text-align: left;"| Privacy Policy
|-
| style="text-align: left;"| March
| style="text-align: left;"| Thursday 6th
| style="text-align: left;"| Saturday 22nd
| style="text-align: left;"| Counter Cloud Theme: DNS Providers
|-
| style="text-align: left;"| April
| style="text-align: left;"| Saturday 5th
| style="text-align: left;"| Monday 21st
| style="text-align: left;"| Code of Conduct on Funkwhale
|-
| style="text-align: left;"| May
| style="text-align: left;"| Sunday 4th
| style="text-align: left;"| Tuesday 20th
| style="text-align: left;"| The Future of the calendar
|-
| style="text-align: left;"| June
| style="text-align: left;"| Tuesday 3rd
| style="text-align: left;"| Wednesday 18th
| style="text-align: left;"| Handover
|}


'''Monday, April 21, 2025: 3:42am (CEST)'''<br />
<span id="why-do-you-want-to-make-it"></span>
Publish newsletter four:<br />
= Why do you want to make it? =
Topic: Email Servers


'''Tuesday, May 20, 2025: 2:05pm (CEST)'''<br />
I would like to help create a community space through digital infrastructure. However, it makes limited sense for me to do this in the context of Klankschool as it stands at the moment. To that end, I would like to offer food for thought to others in similar positions attempting to setup their own infrastructure. I want to argue for a rethinking of how to maintain connections across contemporary border regimes.
Topic: Emacs as an instrument
 
'''Wednesday, June 18, 2025: 9:26pm (CEST)'''<br />
The end
 
It’s still to be decided exactly what the content of the newsletter will be. It could range from pieces of text to sounds to algorithms to git repositories. That is to say, it takes advantage of various services running on the klankschool server which I set up in October 2024. It aims to offer coverage of what has taken place at Klankschool since the previous newsletter.
 
By the time the end arrives I hope to:<br />
1. Publish several newsletters<br />
2. Handover everything<br />
3. Unify the database containers; is a database vps needed?<br />
4. Change the DNS provider (I.E. Registrar?)<br />
5. Record all the passwords in a .kdbx file for use with a password manager<br />
6. Raise some funds for klankschool
 
the newsletter, which should be as open to contributions as possible, will be edited by Rosa and I.


<span id="who-can-help-you-and-how"></span>
<span id="who-can-help-you-and-how"></span>
Line 70: Line 84:


decentral1se - Boosting Klankschool events on the Fediverse
decentral1se - Boosting Klankschool events on the Fediverse
Manetta Berends - offering very useful references


knoflook - Sharing events on radar
knoflook - Sharing events on radar


log - Co-sysadmin
log - Co-sysadmin
Manetta Berends - offering very useful references


<span id="relation-to-previous-practice"></span>
<span id="relation-to-previous-practice"></span>
= Relation to previous practice =
= Relation to previous practice =


'''Previous experience with servers'''<br />
'''Concurrent servers'''<br />
Besides maintaining the klankschool server, I am running Nextcloud on a raspberry pi. The computer is temporarily connected to the XPUB HUB. The nextcloud instance is for personal use. It enables me to keep my files backed-up, contacts in order and calendar appointments synchronised with my phone. The parasitic connection relates to this project through the layout of the local area network at my flat. For now, both the Klankschool server and the Pi are physically located at my flat. On the one hand, I need to return the Mac Pro “Trashbin” computer to the department in the near future. That informs the exit strategy I referred to earlier, and thus the narrative of my columns in the newsletter. Focusing on this strand misses a different element that also requires consideration. Thus, on the other hand, what can be saved from the trashbin? What if this machine were to change location? How much needs to go in a VPS? What about the calendar? To what extent can the machines run themselves? It’s necessary to make preparations in view of these questions and the fact that I don’t plan on staying in the Netherlands.
Besides maintaining the klankschool server, I am also running Nextcloud on a raspberry pi. The computer is temporarily connected to the XPUB HUB. The nextcloud instance is for personal and research use. It enables me to keep my files backed-up, contacts in order and calendar appointments synchronised with my phone. On the one hand, there is a parasitic relation between this infrastructure and HUB. Consequently, the connection between the Pi and the HUB is temporary. The HUB infrastructure relates to this project by rippling through the layout of the local area network at my flat. For now, both the Klankschool server and the Pi are physically located at my flat. On the one hand, I need to return the Mac Pro “Trashbin” computer to the department in the near future. On the other hand, I need to stop leeching off the HUB. These necessities, end-goals, structure the narrative of the project.


'''Previous Collaboration with Rosa'''<br />
'''Previous Collaboration with Rosa'''<br />
Line 87: Line 101:


<span id="relation-to-wider-context"></span>
<span id="relation-to-wider-context"></span>
= Relation to wider context =
= Relation to wider context =


'''Terms of Service'''
'''Terms of Service'''<br />
 
Hosts make clear what constitutes permitted uses of the services. Abiding by these terms is significant in relation to a practice of general adherence which I am inclined towards.
The hosting provider makes clear what constitutes permitted uses of the services.
 
'''Collaborative software practices'''


'''Sever maintenance informed by feminism'''
'''Sever maintenance informed by feminism'''<br />
Feminist servers, such as Systerserver and Anarchaserver, are operated by feminist collectives who prefer feminist modes of collaboration. Such servers often provide services for like minded groups or projects. Feminist servers are conceptually distinct from and contextually adjacent to the way in which the Klankschool server has been set up and maintained. I plan to write such that my personal responsibilities in relation to maintaining this server gradually decrease. I am keen to draw upon feminist methods, practice and research in the process of doing so. As such, the newsletter addresses attempting single-handed attempts to maintain infrastructure. It does so through it’s collaborative mode of production, optimistic attitude, and reflexive planning.


<span id="references"></span>
<span id="references"></span>
Line 103: Line 114:
Berends, M., Diakrousi, A. and Gryllaki, A. (2022) ‘Hosting With’, Debug, Linz, Varia [Online]. Available at https://varia.zone/archive/2023-03-Hosting-with-others/hosting-with-zine-booklet.pdf (Accessed 16 October 2024).
Berends, M., Diakrousi, A. and Gryllaki, A. (2022) ‘Hosting With’, Debug, Linz, Varia [Online]. Available at https://varia.zone/archive/2023-03-Hosting-with-others/hosting-with-zine-booklet.pdf (Accessed 16 October 2024).


<!-- Berlant, L. (2016) 'The commons: Infrastructures for troubling times\*', -->
<!-- Environment and Planning D: Society and Space, vol. 34, no. 3, -->
<!-- pp. 393--419 \[Online\]. DOI: 10.1177/0263775816645989. -->
Engelhardt, L., Billie, P. and Reinthal, A. (2023) Self-Hosting Guide [Online]. Available at https://self-hosting.guide/dokuwiki/about_this_site (Accessed 16 October 2024).
Engelhardt, L., Billie, P. and Reinthal, A. (2023) Self-Hosting Guide [Online]. Available at https://self-hosting.guide/dokuwiki/about_this_site (Accessed 16 October 2024).


Strete, A., Cochior C and Mugrefya e (Eds.) (2022) A Traversal Network Of Feminist Servers. Fractalia, Bucharest.
Strete, A., Cochior C and Mugrefya e (Eds.) (2022) A Traversal Network Of Feminist Servers. Fractalia, Bucharest.

Latest revision as of 17:01, 14 November 2024

What do you want to make?

It’s a newsletter, keeping people up to date with goings-on. On one level, the project addresses the topic of how people aiming to setup servers ought to proceed. Hoping to set up a community infrastructure project? Then seriously consider what is offered by others and do so responsibly. In terms of content, the newsletter may include pieces of text, sounds, algorithms or git repositories. That is to say, it refers to various services running on the klankschool server which I set up in October 2024. It aims to offer coverage of what has taken place at Klankschool since the previous newsletter. On a different level, it’s a record of what’s going on at Klankschool.

By the time the end arrives I hope to:
1. Publish several newsletters
2. Handover everything relating to the server
3. Meet other reasonable requests brought forward by others based on this proposal. For example, saving passwords in a password manager database file.

The release date of the newsletter follows a lunar calendar. It will be published every Last Quarter Moon between December and June. It is circumspect in tone.

How do you plan to make it?

I plan to collaborate with Rosa on this project. The newsletter is thus an effort to document a time-limited collaboration. Rosa and I have discussed putting things on at Klankschool, such as a series of classes about combining live coding with disused hardware. The newsletter may include columns documenting the outcomes of these endeavours. In general, I want to prune the branches of the server over the span of six months, preferring to keep it simple, rather than complex and expansive. I aim to document this practice with a view to extricating myself from the responsibilities I have taken on in relation to the server. Openproject may facilitate with documenting contributions, project planning and keeping track of tasks. Ensuring the stability of the latter system is important to the extent that it is considered a key infrastructural component. Rosa and I agree to use markdown as a document format when writing the newsletter. Initially, I considered using a VPS to run a small mail server. It is likely content will be transcluded and turned into HTML using a static site generator.

What is your timetable?

The timetable itself is a living document which will be publicly available at openproject.klank.school for the duration of the project. Here is an overview:

November - December:
- Drum up enthusiasm about programme amongst community members.
- Advertise the Performances
- Organise a workshop


Month \ Type Meet Publish Newsletter Topic
December Sunday 8th Sunday 22nd Passwords
January Tuesday 7th Tuesday 21st Terms of Service
February Wednesday 5th Thursday 20th Privacy Policy
March Thursday 6th Saturday 22nd Counter Cloud Theme: DNS Providers
April Saturday 5th Monday 21st Code of Conduct on Funkwhale
May Sunday 4th Tuesday 20th The Future of the calendar
June Tuesday 3rd Wednesday 18th Handover

Why do you want to make it?

I would like to help create a community space through digital infrastructure. However, it makes limited sense for me to do this in the context of Klankschool as it stands at the moment. To that end, I would like to offer food for thought to others in similar positions attempting to setup their own infrastructure. I want to argue for a rethinking of how to maintain connections across contemporary border regimes.

Who can help you and how?

In alphabetical order:

Alex Olloman - Wants to organise events

decentral1se - Boosting Klankschool events on the Fediverse

knoflook - Sharing events on radar

log - Co-sysadmin

Manetta Berends - offering very useful references

Relation to previous practice

Concurrent servers
Besides maintaining the klankschool server, I am also running Nextcloud on a raspberry pi. The computer is temporarily connected to the XPUB HUB. The nextcloud instance is for personal and research use. It enables me to keep my files backed-up, contacts in order and calendar appointments synchronised with my phone. On the one hand, there is a parasitic relation between this infrastructure and HUB. Consequently, the connection between the Pi and the HUB is temporary. The HUB infrastructure relates to this project by rippling through the layout of the local area network at my flat. For now, both the Klankschool server and the Pi are physically located at my flat. On the one hand, I need to return the Mac Pro “Trashbin” computer to the department in the near future. On the other hand, I need to stop leeching off the HUB. These necessities, end-goals, structure the narrative of the project.

Previous Collaboration with Rosa
In mid 2024, Rosa and I worked together on a performance titled Printer Jam. We gave the performance at Gulaschprogrammiernacht 22, in Karlsruhe, Germany. The video recording of the performance has been watched 245 times at the time of writing. Printer Jam brought live coding software and abandoned hardware together to breathe life back into disused printers. She and I have worked together effectively in the past and I am optimistic about this collaboration.

Relation to wider context

Terms of Service
Hosts make clear what constitutes permitted uses of the services. Abiding by these terms is significant in relation to a practice of general adherence which I am inclined towards.

Sever maintenance informed by feminism
Feminist servers, such as Systerserver and Anarchaserver, are operated by feminist collectives who prefer feminist modes of collaboration. Such servers often provide services for like minded groups or projects. Feminist servers are conceptually distinct from and contextually adjacent to the way in which the Klankschool server has been set up and maintained. I plan to write such that my personal responsibilities in relation to maintaining this server gradually decrease. I am keen to draw upon feminist methods, practice and research in the process of doing so. As such, the newsletter addresses attempting single-handed attempts to maintain infrastructure. It does so through it’s collaborative mode of production, optimistic attitude, and reflexive planning.

References

Berends, M., Diakrousi, A. and Gryllaki, A. (2022) ‘Hosting With’, Debug, Linz, Varia [Online]. Available at https://varia.zone/archive/2023-03-Hosting-with-others/hosting-with-zine-booklet.pdf (Accessed 16 October 2024).

Engelhardt, L., Billie, P. and Reinthal, A. (2023) Self-Hosting Guide [Online]. Available at https://self-hosting.guide/dokuwiki/about_this_site (Accessed 16 October 2024).

Strete, A., Cochior C and Mugrefya e (Eds.) (2022) A Traversal Network Of Feminist Servers. Fractalia, Bucharest.