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

From XPUB & Lens-Based wiki
(How do you plan to make it?)
No edit summary
Line 1: Line 1:
<span id="how_do_you_plan_to_make_it"></span>
= How do you plan to make it? =
During October 2024 I set up a variety of services on the Klankschool Server. This included a [https://files.klank.school FTP server], [https://funk.klank.school federated audio sharing platform], [https://calendar.klank.school federated public calendar], [https://code.klank.school Gitea instance] and a [https://live.klank.school live coding environment]. The artwork which Rosa and I create will be publicised on the Calendar. Code we produce for the piece will be shared on the Gitea. Audio recordings may appear on the Funkwhale. Other files, such as photo and video documentation, can be uploaded via FTP. The server thus plays an integral role in supporting our creative endeavours. I have an interest in ensuring the services remain up and running, both for myself and for the wider community.
<span id="why_do_you_want_to_make_it"></span>
<span id="why_do_you_want_to_make_it"></span>
= Why do you want to make it? =
= Why do you want to make it? =
Line 35: Line 29:


<span id="live_coding"></span>
<span id="live_coding"></span>
== Klankschool ==
A community and a space in South Rotterdam where people work with, learn from and teach each other about sound. I'm maintaining the Klankschool's server along with log. I have an interest in ensuring the services remain up and running, both for myself and for the wider community. That's because the server plays an integral role in supporting creative endeavours. During October 2024 I set up a variety of services to motivate and facilitate (inter-)community activity.  This included a [https://files.klank.school FTP server], [https://funk.klank.school federated audio sharing platform], [https://calendar.klank.school federated public calendar], [https://code.klank.school Gitea instance] and a [https://live.klank.school live coding environment]. The artwork which Rosa and I create will be publicised on the calendar. Code we produce for the piece will be shared on the Gitea. Audio recordings may appear on the Funkwhale. Files, such as photo and video documentation, can be uploaded to the server via FTP. Flok will likely feature in the piece itself.
== Live Coding ==
== Live Coding ==


Live Coding is a performance practice in which, with code, music or graphics are generated in real time before an audience (Ledesma, 2015, p. 112–117). I set up Flok, a collaborative live coding environment, on a [https://live.klank.school subdomain] of the [https://klank.school klank.school] website. Flok allows for networked performances which reiterate and re-imagine the social dimensions of free software. I hope that hosting such an environment may strengthen community relations between the Klankschool and [https://netherlands-coding-live.github.io/ Live Coders in the Netherlands]. Flok was essential to the piece which Vitrinekast and I developed for the public moment on November 4th.
Live Coding is a performance practice in which, with code, music or graphics are generated in real time before an audience (Ledesma, 2015, p. 112–117). I set up Flok, a collaborative live coding environment, on a [https://live.klank.school subdomain] of the [https://klank.school klank.school] website. Flok allows for networked performances which reiterate and re-imagine the social dimensions of free software. I hope that hosting such an environment may strengthen community relations between the Klankschool and [https://netherlands-coding-live.github.io/ Live Coders in the Netherlands].


<span id="references"></span>
<span id="references"></span>

Revision as of 17:37, 23 October 2024

Why do you want to make it?

  1. To publicise and support sonic practices
  2. To cultivate inter- and infra-community relationships as a way of gaining insight into what free software based server does in social contexts.
  3. To build knowledge around server maintenance through collaborative practice
  4. To advance my understanding of what server maintenance consists of in a production environment whilst supporting cultural expression.

Who can help you and how?

In alphabetical order:

Alex Olloman - Wants to organise events

decentral1se - Boosting Klankschool events on the Fediverse

joak - Technical support

knoflook - Sharing events on radar

log - Co-sysadmin

vitrinekast - Collaborator

Relation to a larger context

Klankschool

A community and a space in South Rotterdam where people work with, learn from and teach each other about sound. I'm maintaining the Klankschool's server along with log. I have an interest in ensuring the services remain up and running, both for myself and for the wider community. That's because the server plays an integral role in supporting creative endeavours. During October 2024 I set up a variety of services to motivate and facilitate (inter-)community activity. This included a FTP server, federated audio sharing platform, federated public calendar, Gitea instance and a live coding environment. The artwork which Rosa and I create will be publicised on the calendar. Code we produce for the piece will be shared on the Gitea. Audio recordings may appear on the Funkwhale. Files, such as photo and video documentation, can be uploaded to the server via FTP. Flok will likely feature in the piece itself.

Live Coding

Live Coding is a performance practice in which, with code, music or graphics are generated in real time before an audience (Ledesma, 2015, p. 112–117). I set up Flok, a collaborative live coding environment, on a subdomain of the klank.school website. Flok allows for networked performances which reiterate and re-imagine the social dimensions of free software. I hope that hosting such an environment may strengthen community relations between the Klankschool and Live Coders in the Netherlands.

References

Ledesma, E. (2015) ‘The Poetics and Politics of Computer Code in Latin America: Codework, Code Art, and Live Coding, Revista de Estudios Hispánicos, Washington University in St. Louis, vol. 49, no. 1, pp. 91–120 [Online]. DOI: 10.1353/rvs.2015.0016 (Accessed 13 September 2022).