help wanted: technical editing for peeragogy

11 views
Skip to first unread message

Joe Corneli

unread,
Mar 3, 2020, 6:03:48 PM3/3/20
to Peeragogy
Please circulate to your networks.

I'm looking for someone who can take care of the Peeragogy Github organization and other technical aspects of the project in April, May, and June of this year with the possibility that this will become a permanent position. This is a strictly volunteer role.  I can provide some guidance and handover.

- Requirements: Git, Github, Markdown, Jekyll, Bash
- Bonus: LaTeX, XML

skreutzer

unread,
Mar 5, 2020, 3:16:26 PM3/5/20
to Peeragogy
I intent to offer technical assistance along the lines of services provided by the "data department", at least until June (included). The GitHub Projects on the GitHub Peeragogy "Organization" outline a few tasks that could be scheduled for occasionally being carried out over the next few months from my side, or indicate, as examples, what kind of technical editing I'm considering. I'm hesitant to volunteer to manage the GitHub Peeragogy Organization or one of its Repositories, as they're hardly peer/federated (in a digital sense), and instead demand taking responsibility for other peers regarding of what to accept or refuse, what to allow and what to deny, etc. I also want to maintain neutrality towards the content and practices, avoid making decisions (that could affect others) in that realm, avoid actively contributing under copyright licenses that aren't the strongest available in terms of digital freedom, so my potential contributions would likely be limited to questions of technical feasibility/merit, again here too in the sense of digital peer principles. Another thing I'm wondering about are the Handbook version 4 plans and how they might relate to the technical editing and Repositories, as an interim/permanent maintainer of the Peeragogy GitHub Organization probably might eventually be expected to help with the completion/publication of that release, depending on what the planning of the Handbook Version 4 Working Group says. I personally don't know much yet about Jekyll, wonder how one can get away with Markdown, not a git power user, Bash standard, LaTeX semi-decent, and XML: absolutely.

Reply all
Reply to author
Forward
0 new messages