User:Kim/Assessment 2 (T4) - Revision history

Kim: /* why */

2025-12-08T09:28:09Z

why

← Older revision		Revision as of 11:28, 8 December 2025
Line 74:		Line 74:
	* git software: keep track of changes made in a file and collaborate with others on the same files		* git software: keep track of changes made in a file and collaborate with others on the same files
	* ''softwares means of collaboration and version control produce vast amount of metadata to the code (or text) files contained in a git repository''		* ''softwares means of collaboration and version control produce vast amount of metadata to the code (or text) files contained in a git repository''
	* ''~~that i find~~ either neglected or exploited, reinforce hypercapitalist modes of production''		* ''metadata either neglected or exploited, reinforce hypercapitalist modes of production''


Line 90:		Line 90:

	=== git checkout ===		=== git checkout ===
	gitpub is only one part of the project proposal:		gitpub is only one part of the project proposal: ''(on a new branch I'll briefly outline the second part)''

	writing script(s) - script(s) writing is a series of scores.		writing script(s) - script(s) writing is a series of scores.
Line 150:		Line 150:
	the software as part of the writing		the software as part of the writing

	* ''gitpub explores how we write and are written by software''
	* ''(through example of collaborative version control software as publishing tool)''
	* ''using software for text editing or collaboration (e.g. .git, etherpad, word, google docs, code editors) we assume to be in control of text emerging before us''		* ''using software for text editing or collaboration (e.g. .git, etherpad, word, google docs, code editors) we assume to be in control of text emerging before us''
	* ''But additional to text we consciously form, is a lot more text produced,'' ''not directly by us''		* ''But additional to text we consciously form, is a lot more text produced,'' ''not directly by us''

Kim at 19:40, 7 December 2025

2025-12-07T19:40:19Z

← Older revision		Revision as of 21:40, 7 December 2025
Line 1:		Line 1:
	<p class="websiteref">you are looking at the backend of kims t4 assessment - find the webpage [https://hub.xpub.nl/cerealbox/~kim/t4-assessment-frontend/ here]</p>		<p class="websiteref">'''you are looking at the backend of kims t4 assessment - find the webpage [https://hub.xpub.nl/cerealbox/~kim/t4-assessment-frontend/ here]'''</p>

	''This is an attempt to use the git protocol as presentation protocol, thinking through the actions that the software prescribes. The presentation is structured by main tasks (commands) used when working with the software. for coherence, the order and hierarchy of commands is hereby slightly adjusted, commands might also be interpreted as words rather than code.''		''This is an attempt to use the git protocol as presentation protocol, thinking through the actions that the software prescribes. The presentation is structured by main tasks (commands) used when working with the software. for coherence, the order and hierarchy of commands is hereby slightly adjusted, commands might also be interpreted as words rather than code.''

Kim at 19:39, 7 December 2025

2025-12-07T19:39:55Z

← Older revision		Revision as of 21:39, 7 December 2025
Line 1:		Line 1:
	''<p class="websiteref">you are looking at the backend of kims t4 assessment - find the webpage [https://hub.xpub.nl/cerealbox/~kim/t4-assessment-frontend/ here]</p>''		<p class="websiteref">you are looking at the backend of kims t4 assessment - find the webpage [https://hub.xpub.nl/cerealbox/~kim/t4-assessment-frontend/ here]</p>

	''This is an attempt to use the git protocol as presentation protocol, thinking through the actions that the software prescribes. The presentation is structured by main tasks (commands) used when working with the software. for coherence, the order and hierarchy of commands is hereby slightly adjusted, commands might also be interpreted as words rather than code.''		''This is an attempt to use the git protocol as presentation protocol, thinking through the actions that the software prescribes. The presentation is structured by main tasks (commands) used when working with the software. for coherence, the order and hierarchy of commands is hereby slightly adjusted, commands might also be interpreted as words rather than code.''

Kim at 19:38, 7 December 2025

2025-12-07T19:38:47Z

← Older revision		Revision as of 21:38, 7 December 2025
Line 1:		Line 1:
	''<~~sup~~>you are looking at the backend of kims t4 assessment - find the webpage [https://hub.xpub.nl/cerealbox/~kim/t4-assessment-frontend/ here]</~~sup~~>''		''<p class="websiteref">you are looking at the backend of kims t4 assessment - find the webpage [https://hub.xpub.nl/cerealbox/~kim/t4-assessment-frontend/ here]</p>''

	''This is an attempt to use the git protocol as presentation protocol, thinking through the actions that the software prescribes. The presentation is structured by main tasks (commands) used when working with the software. for coherence, the order and hierarchy of commands is hereby slightly adjusted, commands might also be interpreted as words rather than code.''		''This is an attempt to use the git protocol as presentation protocol, thinking through the actions that the software prescribes. The presentation is structured by main tasks (commands) used when working with the software. for coherence, the order and hierarchy of commands is hereby slightly adjusted, commands might also be interpreted as words rather than code.''

Kim at 19:38, 7 December 2025

2025-12-07T19:38:03Z

← Older revision		Revision as of 21:38, 7 December 2025
Line 1:		Line 1:
	''~~this is~~ the backend of kims t4 assessment~~. you can~~ find ~~its~~ webpage [https://hub.xpub.nl/cerealbox/~kim/t4-assessment-frontend/ here]''		''<sup>you are looking at the backend of kims t4 assessment - find the webpage [https://hub.xpub.nl/cerealbox/~kim/t4-assessment-frontend/ here]</sup>''



	''This is an attempt to use the git protocol as presentation protocol, thinking through the actions that the software prescribes. The presentation is structured by main tasks (commands) used when working with the software. for coherence, the order and hierarchy of commands is hereby slightly adjusted, commands might also be interpreted as words rather than code.''		''This is an attempt to use the git protocol as presentation protocol, thinking through the actions that the software prescribes. The presentation is structured by main tasks (commands) used when working with the software. for coherence, the order and hierarchy of commands is hereby slightly adjusted, commands might also be interpreted as words rather than code.''

Kim at 19:36, 7 December 2025

2025-12-07T19:36:30Z

← Older revision		Revision as of 21:36, 7 December 2025
Line 1:		Line 1:
	this is the backend of kims t4 assessment. you can find its webpage [https://hub.xpub.nl/cerealbox/~kim/t4-assessment-frontend/ ~~<sup>~~here~~</sup>~~]		''this is the backend of kims t4 assessment. you can find its webpage [https://hub.xpub.nl/cerealbox/~kim/t4-assessment-frontend/ here]''

Kim at 19:35, 7 December 2025

2025-12-07T19:35:56Z

← Older revision		Revision as of 21:35, 7 December 2025
Line 1:		Line 1:
			this is the backend of kims t4 assessment. you can find its webpage [https://hub.xpub.nl/cerealbox/~kim/t4-assessment-frontend/ <sup>here</sup>]


	''This is an attempt to use the git protocol as presentation protocol, thinking through the actions that the software prescribes. The presentation is structured by main tasks (commands) used when working with the software. for coherence, the order and hierarchy of commands is hereby slightly adjusted, commands might also be interpreted as words rather than code.''		''This is an attempt to use the git protocol as presentation protocol, thinking through the actions that the software prescribes. The presentation is structured by main tasks (commands) used when working with the software. for coherence, the order and hierarchy of commands is hereby slightly adjusted, commands might also be interpreted as words rather than code.''

Kim: /* git commit -m "gitpub" */

2025-12-07T19:28:40Z

git commit -m "gitpub"

← Older revision		Revision as of 21:28, 7 December 2025
Line 176:		Line 176:

	===git commit -m "gitpub"===		===git commit -m "gitpub"===
	~~''makes snapshot, produces metadata to index it and make it comprehensible.''~~		''creates a snapshot of the staged changes - I am not going to repeat all of the above, commit also adds metadata to index it and render comprehensible across contexts (my metadata in the form of time (table) and next steps)''

	''creates a snapshot of the staged changes I am not going to repeat all of the above, ~~but~~ also adds metadata to index it and render comprehensible across contexts (my metadata in the form of time (table) and next steps)''
	# iterate on writing exercises in different contexts ''(possible further inquiries: look at distribution of roles, methods for personal reflection in the exercise process)''		# iterate on writing exercises in different contexts ''(possible further inquiries: look at distribution of roles, methods for personal reflection in the exercise process)''
	# further prototypes of the gitpub script (use for thesis writing / making)		# further prototypes of the gitpub script (use for thesis writing / making)
Line 202:		Line 200:

	I here want name a few of the many existing publishing tools that, like gitpub, leverage free software.		I here want name a few of the many existing publishing tools that, like gitpub, leverage free software.
	:~~Octomode~~<ref>[https://cc.~~vvvvvvaria~~.~~org~~/~~wiki/Octomode Octomode~~] was developed by ~~Mantetta Berends~~ and ~~Christina Cochior together with Varia.~~</ref> and ~~Chattypub~~<ref>[https://~~www~~.~~hackersanddesigners~~.nl/~~chattypub.html Chattypub~~] was developed by ~~Hackers~~ and ~~Designers~~</ref>, for example, are built for acts of low threshold collaborative publishing, while ikiwiki<ref>[https://ikiwiki.info/ ikiwiki] was developed by Joey Hess</ref> is more focused on converting wiki to html files using version control. Aesthetic programming<ref>here is a link to the [https://aesthetic-programming.net/ web version], and the [https://gitlab.com/aesthetic-programming/book git repository], developed by Open Source Publishing</ref> is a hybrid publication based on a git repository. ''while also using git, Gitpub diﬀers from the last two examples because it involves the version control metadata, not only within the writing process, but also as part of the outcome.''		:Chattypub<ref>[https://www.hackersanddesigners.nl/chattypub.html Chattypub] was developed by Hackers and Designers</ref> and Octomode<ref>[https://cc.vvvvvvaria.org/wiki/Octomode Octomode] was developed by Mantetta Berends and Christina Cochior together with Varia.</ref>, for example, are built for acts of low threshold collaborative publishing, while ikiwiki<ref>[https://ikiwiki.info/ ikiwiki] was developed by Joey Hess</ref> is more focused on converting wiki to html files using version control. Aesthetic programming<ref>here is a link to the [https://aesthetic-programming.net/ web version], and the [https://gitlab.com/aesthetic-programming/book git repository], developed by Open Source Publishing</ref> is a hybrid publication based on a git repository. ''while also using git, Gitpub diﬀers from the last two examples because it involves the version control metadata, not only within the writing process, but also as part of the outcome.''
	Lastly I want to mention a few theoretical approaches, that I relate gitpub to on a more conceptual basis.		Lastly I want to mention a few theoretical approaches, that I relate gitpub to on a more conceptual basis.
	:gitterature (by Servanne Monjour and Nicolas Sauret, as part of the Aprübt publishing collective) as an alternative model for literature and editorial processes. ''While I share their understanding of the git writing environment as inherently processual, performative and conversational, my approach is to create a tool that is not platform based and meant to be shared across different communities.''		:gitterature (by Servanne Monjour and Nicolas Sauret, as part of the Aprübt publishing collective) as an alternative model for literature and editorial processes. ''While I share their understanding of the git writing environment as inherently processual, performative and conversational, my approach is to create a tool that is not platform based and meant to be shared across different communities.''

Kim: /* why */

2025-12-07T19:27:21Z

why

← Older revision		Revision as of 21:27, 7 December 2025
Line 165:		Line 165:
	** ''an industry that profits from maintaining compartmentalised, hidden labor and the divide between user and programmer (Hoff, 2020).''		** ''an industry that profits from maintaining compartmentalised, hidden labor and the divide between user and programmer (Hoff, 2020).''

	metadata ~~as possible space for showing / navigating~~ articulation work		metadata in the context of articulation work
	* articulation work describes the work that enables work to happen		* articulation work describes the work that enables work to happen
	* ''involving mostly communication and organization around work''		* ''involving mostly communication and organization around work''

Kim: /* why */

2025-12-07T19:26:12Z

why

← Older revision		Revision as of 21:26, 7 December 2025
Line 162:		Line 162:
	* ''working with git in day to day operations, the familiarity of its gestures and rhythms conceals the softwares own ways of writing and its cultural situatedness<ref>This goes along with Susan Leigh Star’s concept of naturalization: in which “de-situated” or “naturalized” objects become invisible to members of community of practice through omnipresence and use. A consequence of this process is a communities decreasing criticality towards the object (Star, 1994).</ref>.''		* ''working with git in day to day operations, the familiarity of its gestures and rhythms conceals the softwares own ways of writing and its cultural situatedness<ref>This goes along with Susan Leigh Star’s concept of naturalization: in which “de-situated” or “naturalized” objects become invisible to members of community of practice through omnipresence and use. A consequence of this process is a communities decreasing criticality towards the object (Star, 1994).</ref>.''
	* ''extending and mis-using existing piece of software I want to challenge its embeddedness into''		* ''extending and mis-using existing piece of software I want to challenge its embeddedness into''
	** ''(white, male, optimisation driven) ~~developing~~ cultures''		** ''(white, male, optimisation driven) development cultures''
	** ''an industry that profits from maintaining compartmentalised, hidden labor and the divide between user and programmer (Hoff, 2020).''		** ''an industry that profits from maintaining compartmentalised, hidden labor and the divide between user and programmer (Hoff, 2020).''