Word's review functions appear as pretty colored bubbles and a bunch of icons on the Ribbon. It's easy enough even for Humanities professors to use on a daily basis, despite the fact that as a VCS, it's strictly inferior to something like git. Actually, I think it's popular precisely because it ain't git. Most professors who are fluent in Word's review functions would be hopelessly lost when faced with a Dropbox conflict, let alone merging git repos.
As for git's complexity, it's all in its completely opaque display of its internal state. A chain of deltas - diffs - isn't complicated. It's all git's (perverse) desire to follow the exact-same command-line interface as cat and awk, when neither contain persistent state.
Word shows pretty bubbles next to sections that have been edited. The bubbles are color-coded so it's easy to tell who did what. The edits can be accepted, rejected, or further modified with a couple of clicks. There is no list of commands or keyboard shortcuts to memorize. Just a bunch of icons, menus, and clicking around.
Word doesn't require your content to be made up of neat lines of verse, either. Natural languages don't organize themselves into 78-char lines. It should be OK to edit a few words in a long paragraph of prose. Even Wikipedia's messy "Revision History" is probably better than git in this regard.
It is a horrible representation for stuff where edits may consist of both typo fixes, and separate wording changes in a single sentence - where you might want to accept change to one word and reject change to another word, despite that they came from a single "commit" to a single line.
For collaborative text editing both word's track changes and google docs features are far superior to git.
We're bringing version control to people who collaborate by email, starting with Gmail. All people have to do is exchange drafts by email (like normal!), and we infer the history, as if they've been using git.
We're looking for beta testers:
https://draftable.com/gmail/faq
with the answer to your question (and more), but I'll answer here too:
We don't modify the data in your Gmail account, so if you try Draftable, then uninstall it, your Gmail account won't be altered. Furthermore, if you disable Draftable before uninstalling it, we'll delete our index and revoke our access to your account.
It's meant for people who exchange documents by email.
Collaboration in physics research: hand-written notes on margins of said pile
The issue with git etc is that everyone involved has to understand how it works and accept and appreciate the benefits over the system outlined above (which works quite well for papers with few authors). If even one author doesn't care, you cannot implement the system. And good luck getting professors to care about things that aren't research or funding.
And if some of them can't use it, teach them. And revert to the previously non-fucked up version (it's on someone's email by the name of Article_1_fixed_2_corrections_10_10.docx)
Something I like about version control is that it at least ensures continuity of the version.
Yours sincerely, a graduate student whose thesis is written in LaTeX and then converted to RTF and then hand edited so his supervisor(s) can give him comments.
I sent them a link to my github repository, but they never took me up on my offer :(
I've found that collaboration on documents via Markdown is not too crazy bad. Otherwise, I ask for comments on the PDF or on hard copy. Going back to latex from RTF is an exercise in madness.
And I second the pandoc recommendation if you can get it to work
The worst part was that they didn't even use the track changes feature on anything I sent them.
I actually do make bit of things in LaTeX through Org-mode at the office, and sending things in PDF actually makes it clear what kind of handling I'm looking for. If I'm actually expecting someone to revise my writing, then I'll just send them plaintext.
Now considering even Adobe Reader allows commenting, I don't think there are many of issues any more...
I don't know the state of visual tools for git but tortoisehg for mercurial is quite easy to get started with.
After forgetting to push after commit and then dropping your laptop, you'll know.
Nope, like regularfry rightly pointed out.
>The only difference is that you still can use your local git repository if your server burns down, but you can't do that with svn. Even then I can `svn relocate`.
Look, I am not defending SVN for software development, I am a happy git camper. But git for technical writing is simply the wrong tool for the wrong job.
I have had various beginner git users get very confused when dealing with conflicts -- I have got myself quite confused on occasion too.
1. http://www.wired.com/wiredenterprise/2013/06/cades-witty-hea...
Word has version control though, and it's appreciated by many in academia. Version control for humans is a Big Startup Idea, I wouldn't be surprised if Dropbox and Github were trying to tackle it (from 2 different angles: Dropbox from the "how do we get average the user to get features for nerds", and Github from the "how do we get the average non-nerd to use us")