Chapter 1: Collectivities and Methods

Collectivities and Methods (to serve and publish)

Pad for working https://ctp.cc.au.dk/pad/p/servpub_methods

Coordinator: Winnie & Geoff Contributors: In-grid, CC, Systerserver, Winnie & Geoff

+++ What does it mean to publish? Publishing is the act of sharing and passing on knowledge, creating a dynamic relationship between authors/writers/producers and readers. It makes space for others to tune in a particular theme or topic, shaped by a specific medium, format, approach, and structure. At its core, publishing is inherently a social and political process—it builds communities, invites action, and inspires new ways of thinking. To put simply, publishing means making something public, but in this apparently simple act, there’s a lot at stake, not simply what we publish, but how. The process involves resources, tools, technology and infrastructures. In other words, publishing also entails recognizing the post-digital landscape and understanding the political and economic forces that shape the practice.

This book is an intervention in these ongoing debates [ref], emerging out of a particular history of experimental publishing and shaped by the collaborative efforts of various art-tech collectives, operating both within and beyond academic contexts, who are all invested in how to make things public and find ways to publish outside of commercial and institutional norms [1]. Crucially, the ethics of Free/Libre and Open Source Software (FLOSS), particular its emphasis on the freedom to study, modify and share (Klang 2005; Mansoux and de Val 2008), operate as one of our core principles in working on this book, enabling possibilities for modification and versioning with a broader community in mind. What links these traditions is the need to address the social relations that experimental publishing can help to expose and activate differently.

Our working premise is that despite the trend towards open access (White 2023; Leigh-Ann et al 2023), relatively little has changed in academic publishing and scholars still seek to distribute their work through enclosures and based on lumpen workflows that still follow a model that is largely unchanged since industrialism. This book is an attempt to draw attention to these material conditions for the production of books, and to strengthen the possibility of working alternatives to mainstream publishing [2]. Our concern is that books, and academic books in particular, follow a model of production that belies their criticality. By criticality, we mean to go beyond a criticism of conventional publishing and acknowledge the ways in which we are implicated at all levels in political choices when we engage in how to produce books. It's this kind of reflexivity that has guided our approach.

The book is a kind of a manual to build and think with -- to register the importance of its own coming into being as a book (as an onto-epistemological object if you like). It is produced in a reflexive manner so that the content and the form through which it is produced are recognised as interconnected. [winnie to winnie note: will think more with this and how to talk more about reflexivity]

Background

More pragmatically, the aim is to develop a radical alternative platform and workflow for publishing. We build upon previous projects and collaborations in the field of experimental publishing such as Aesthetic Programming (Soon & Cox, 2020) in which the authors developed a book about software as if it were software. All the contents were offered as an open resource, to encourage others to fork copies and customize their own versions of the book. In FLOSS culture, more than one programmer contributes to writing and documenting code. Contributors might be unknown and are able to update or improve the software by forking—making changes and submitting merge requests to incorporate updates—in which the software is built together as part of a community. To merge, in this sense, is to agree to make a change, to approve it as part of a process of collective decision-making and with mutual trust. This is common practice in software development particularly in the case of FLOSS in which developers place versions of their programs in version control repositories (such as GitLab) so that others can download, clone, and fork them. We were curious to explore how the concept of forking in software practice might inspire new practices. By encouraging new versions to be produced by others, the book set out to challenge publishing conventions and make effective use of the technical infrastructures through which we make ideas public. Clearly wider infrastructures are especially important to understand how alternatives emerge from the need to configure and maintain more sustainable and equitable networks for publishing.

It is with this in mind that we have tried to engage more fully with the politics of infrastructure that supports the production and distribution of books. In this way we would argue that the project responds to the pressing need for publishing to acknowledge its broader apparatus. This follows both a technical and social protocol, and it is crucially important that this is a collective enterprise, taking further inspiration from "A Transversal Network of Feminist Servers", a collaborative project that builds on selfhosting infrastructural practicies that follow intersectional feminist principles. The aim is to rethink the current landscape of publishing infrastructure and digital knowledge organization, and offer a viable alternative which can support new and existing publishing initiatives. Part of the motivation was the perceived need to develop a community of shared interest around experimental publishing and affective infrastructures in London. We could see similar initiatives elsewhere, in particular in the Netherlands and Belgium, and were envious.

[to be continued...]

1. Structure

The book charts the development of a bespoke publishing infrastructure that draws together previously separated processes such as writing, editing, peer review, design, print, distribution. Each chapter unpacks practical steps alongside a discussion of some of the poltical implications of our approach.

[go on to describe each chapter in detail]

2. Collectivities

- short semi-structured interviews with each collective

.......0. What characterizes your collective as collective?  

.......1. What are your approaches in working together as a group and working with others?

.......2. How does your group work with infrastructure?

.......3. What do you want to work on Servpub?

.......4. How do social relations become transformed?

[minor composition]

2a. social relations meets tech

....... and minor compositions here

2b. ideas of the commons and autonomia/anarchism

3. Methods

Feminist, intersectionality, queer, radical referencing

doing and making and thinking

development of tools perhaps too

artistic practice/research/artivist approach

end chapter with idea of Book as reflexive practice - reiteratung this point - book about its own making.

+++footnote+++ [1] need to check in: such as xpub, hackers and designers, ATHOS, Varia, OSP and a list of people and communities [2] here can add open humanities press - liquid series, data browser e.g volumetric regimes wiki to print, and MIT Press pubpub

++++Bibilography+++ - Mathias Kling 2005, Free software and open source: The freedom debate and its consequences, first monday: https://firstmonday.org/ojs/index.php/fm/article/view/1211 - Mansoux, Aymeric and de Val, Marloes. 2008. Floss + Art. Poitiers: GOTO10 - Daley White 2023: Historical Trends and Growth of OA: https://blog.cabells.com/2023/02/08/strongopen-access-history-20-year-trends-and-projected-future-for-scholarly-publishing-strong/ - Leigh-Ann et al 2023, The oligopoly’s shift to open access: How the big five academic publishers profit from article processing charges, https://direct.mit.edu/qss/article/4/4/778/118070/The-oligopoly-s-shift-to-open-access-How-the-big