What would be good workflows for commenting work-in-progress academic texts that don't rely on Microsoft Word or Google Docs? Would love to hear suggestions.

@jaranta When I send people PDFs they often write comments and usually that works out fine.

I write notes to myself in <!-- --> in markdown files and sometimes use a script to turn them into marginal notes. I think I got that idea from somebody here.

I like the idea of CriticMarkup but I have never used it seriously.
criticmarkup.com/

@twsh I guess that's the most obvious solution.

I also use comments in markdown files, but wouldn't force that or CriticMarkup on anyone else.

@jaranta I would like to try this, or something like it:

@twsh I was also thinking of cryptpad, but I'm wary of 1) things on other people's servers 2) forcing new workflows on people.

@jaranta I suppose that you could host it yourself.

@jaranta The open source Okular PDF reader allows you to make annotations, highlights, etc in PDF files. I usually use that when reviewing text.

@abs Oddly enough, PDF files seem to be the most common shared format for files. I guess this could be the easiest way.

@jaranta
Back when editorially.com was still a thing (for like a minute before it was acquired) you could annotate markdown documents and also submit edits for review through a pull request-like process. It was pretty good and I used it with two collaborators once to write a short piece.

I think draftin.com may still have a feature like that, but I have yet to find a co-author/collaborator I can use that process with. Also, I'm a little wary of lock-in.

@jboy Yeah, I prefer workflows that don't require me to have all my work on someone else's server.

I was hoping for solutions that don't involve me forcing other people to adopt new ways of working. I tried that once with Authorea and I don't think either of us was very happy with that.

@jaranta sometimes I joke that I'm only going to write with people that have mastered git workflow from now on. But not a lot of social scientists would clear that bar...

@jboy I think you would also need something like Git(hub/lab) with that for comments etc.

@jaranta no, you could do it entirely through commit messages and branches.

@jboy I dread the idea of having an extended discussion of some complex change through commit messages.

@jaranta