User:Kim/Project Proposal (Gitpub)

What do you want to make?

Gitpub is a tool to create a printed or web-based publication from a git repository including repository metadata. This tool is not bound to any specific environment yet, but could have different interfaces such as a website or a terminal program.
The information stored inside of every local .git folder builds basis of the tool. It allows to select different types of meta data to include, such as Commit Messages, Commit Authors, Timestamps, amount of changes made etc. There will be options for personalizing the appearance of the publication through pre-made styles or custom CSS.

How do you plan to make it?

Prototype documentation

documentation proof of concept (1)

At the moment (fri sep 26th) of first creating this Project Proposal draft I have a proof of concept prototype which consists of two bash scripts: the first script fetches the repositories meta data and writes it to a markdown file. The second script sorts all files and converts them into an impositioned pdf - ready to print as a booklet.
Here are the further steps:

1. make new prototype to get familiar with the technicalities, possibilities and constraints of working with git, not the api but local files. Prototypes can be web facing (javascript) and terminal facing (python) and explore different end formats of the publication, such as a printable pdf or a static website
2. work on more specific features and how to combine them
3. make the tool self contained
4. design choices regarding the tools interface/options but also the publication outcome (how is meta information interacting with the main text?)
5. peer distribution and testing rounds (individual or in the form of collective work sessions)
6. documentation of the tool

What is your timetable?

edit

Why do you want to make it?

edit

"tools as boundary objects that connect different communities of practice" the tool itself and the process and artifacts it makes possible all thrive on the boundaries
By willfully extending and mis-using an existing piece of software I want to challenge its embededness into (white, male, optimization driven) developing culture and an industry that profits from maintaining compartmentalized and hidden labor and the divide between user and programmer. This is the community of practice.

Not only in its process or communities is Gitpub inhabiting boundaries but also in its visual and conceptual outcomes: challenging the authority of a (main) text by breaking with the familiarity of its display that renders its conventions invisible.

Git is a version control software, commonly interfaced with through platforms such as Github, Gitlab or Gittea, to collaborate on code, track versions and progress of code and publish / document code. There are uses outside of this scope, such as the publishing and documenting of fonts or sharing of code unrelated resources
Publishing a git repository in a printed or digital form allows to "connect different communities of practice", to permeate the borders between non (or not so) - and technical environments.
Making meta data part of the publication is an act of decentering the main body of text (or work) where software in use becomes not just a means to an end but presents itself as agential, defiant, political entity. This meta data is produced by means of version control, an integral part of the git software, that in practice is either neglected or exploited to reinforce hypercapitalist modes of production.

Who can help you and how?

I will seek technical support form the prototyping tutors (as of now Michael and Manetta). Other groups or individual I could reach out for technical/ conceptual support could be the community around PrePostPrint and Constant. About Constant I know that they have been doing publications with git already and would be curious about their experience and workflows.

Relation to previous practice

• in its manner of confusing centers of attention and making its own making (processual, structural or meta information) part of its content gitpub poses a continuation to previous projects from the past years. User:Kim/Special Issue 1/Tracing Networks Backwards and Layer browser extension examine these on an interface level, while projects like Writing on the margins of the web workshop and on contamination document performance and essay are more concerned with the inner workings of a text through marginal and paratextual information and their relation to the 'main' work.
• other recent experiments with single source publishing include Terms of servers and SI27 Documentation/Website Manual#print_update

edit contextualize my wider ambitions with this

Relation to a larger context

I understand Gitpub as situated in a lively ecology of experimental publishing tools and practices:
practices:

• Octomode (a tool made by manetta and christina with varia that uses etherpad as a basis for a print or web publication)
• Hackers and Designers with tools such as Chattypub
• publishing efforts by the INC (including "FROM PRINT TO EBOOKS A HYBRID PUBLISHING TOOLKIT FOR THE ARTS", ".expub - Exploring Expanded Publishing", "Screentime, Airtime, Facetime")
• Pre post print
• Constant

concepts:

• I feel there is a convergence with "Print is Flat, Code is deep" but more in the sense of challenging her argument than a full agreement. After all does this notion not reinforce a divide that today with notions of hybridity, post-print or experimental, is simply not there anymore?
• from wendy chuns "On software or: the persistence of visual knowledge" the implications of hiddenness in software
• on invisible writing: "<?php> - "Invisible" Code and the Mystique of Web Writing" Helen Burghes in "From A to <A> Keywords of Markup"
• Historical study of marginalia (such as pecia marks enabling division of labor and separation of skills in print production, or other forms of comments / annotations) 'Manuskrip Culture' https://en.wikipedia.org/wiki/Manuscript_culture
• concept and uses of version control