home/ modules/ free-software-as-political-and-ethical-stance

Free software as political stance: ethics, access, and the commons

  • learner can articulate why writing your own tools in free software reframes music-making as a refusal of proprietary control, and how live coding aligns with open-source/hacker ethics of sharing and DIY access
  • learner can analyse the access politics of free tools — the hardware/internet digital divide that gates entry unevenly by region and income — as a first barrier to participation
  • learner can frame adopting FOSS as feminist praxis against gatekeeping in music tech

Write a short position piece arguing whether a live-coding workshop should mandate free/open-source tools: ground it in the political-act and open-source-ethics framing, weigh the digital-divide access barrier, and address the feminist-praxis argument — arriving at a concrete, defensible policy.

Sooner or later every algorave organiser, workshop facilitator, or community-lab founder faces a real policy call: do we require SuperCollider, TidalCycles, and Hydra, or let participants bring Ableton? The answer isn’t a taste question — it decides who can afford to show up, whose laptop can run the session, and what values the space performs. This module builds toward making that call in writing: a position piece that takes a side and defends it against the strongest counterarguments.

The arc starts with the foundational framing — writing your own tools as a refusal of proprietary control — the L0 orientation that makes the whole debate legible. From there, the learner works through how live coding’s open-source character enabled participation in Mexico and India where commercial software was out of reach, then hits the complication that keeps the argument honest: free software is not free access, because hardware cost and connectivity gate entry unevenly by region and income (with Raspberry Pi and low-spec rigs as the practitioners’ answer). The L3 capstone-adjacent move is the feminist-praxis framing — FOSS adoption as a stance against gatekeeping in music tech — which the position piece must engage directly, not just cite. A supported first exercise might defend one framing in isolation; the unsupported capstone must weave all three into one defensible policy.

The four required atoms gate the capstone outright: without any one of them, a whole clause of the argument collapses into assertion. The supporting atoms enrich rather than gate — the history of women-only workshops and structural barriers gives the feminist argument texture, and the book’s own CC-BY-SA license offers a neat concrete example of the ethos in action.

Atoms in this module

Required — these gate the capstone

Writing your own tools in free software reframes music-making as refusal of proprietary control
Concept L0 Orientation PF
Live coding aligns with open-source, hacker ethics of sharing, transparency, and DIY access — especially enabling participation in communities with fewer resources
Concept L2 First instrument POF
Hardware cost and internet access are the first barrier to live coding, unevenly by region and income
Concept L1 Foundations PF
Adopting free/open-source tools is framed as feminist praxis against gatekeeping in music tech
Principle L3 Craft PF

Supporting — enrichment, not gating

Women have participated in live coding since its inception but face structural barriers; active advocacy and women-only spaces have been necessary to sustain diversity
Concept L3 Craft P
Live Coding: A User's Manual is published CC-BY-SA, enabling free use with attribution and share-alike — a license choice that itself reflects live coding's ethos
Fact L0 Orientation P