Timeline for Should I suggest to use version control for writing a paper with new collaborators?
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 3, 2018 at 21:16 | comment | added | Carol | @qsp - correction: Sharelatex has review mode that can be turned on (and since overleaf and sharelatex are somewhat merged), I assume overleaf does also). Turning it one means that all changes show up in the document, as well as who did what, and the authors can reject/accept the changes. (And there always has been 'history', but which is a lot more tedious to go through to see who did what and to revert since the history of changes are so finely grained). Its possible these are not available for the 'free' account. | |
| Feb 1, 2018 at 15:06 | comment | added | Frank Hopkins | The problem with such an evaluation is - git (or SVN) prevents a lot of potential time loss that you don't see when you use it. If you have a handcrafted exchange system for word docs or send latex files around you will loose quite some time if at some point something with the versions gets mixed up and you need to figure out how to undo part of the changes - or which is the version you want. That being said, for small projects Google Doc can do an awesome job too. | |
| Feb 26, 2017 at 4:34 | comment | added | AJK | In my experience as a new git user (but an experienced coder), I didn't start seeing benefits until 1 yr+ into a collaboratively written paper. I suspect the learning curve is going to be worse for, e.g. a senior faculty member who has less time to spend debugging! | |
| Feb 26, 2017 at 4:32 | comment | added | AJK | "This is trivial if you use git right" "Check stack overflow." Of course! But in my experience, it is not trivial to learn to use git right, and if every time you make an error, you need 30 minutes on SO to debug it... not great. | |
| Feb 26, 2017 at 3:56 | comment | added | sean | Your problems: discard changes, bad commits were asked several times in stackoverflow. This is trivial if you use git right. | |
| Feb 26, 2017 at 3:55 | comment | added | sean | The main purpose of tools like Git/Mercurial/SVN is version control. If somebody modifies your awesome paragraph in a way that you don't like, you want to know who did it, when they did it, how to revert back etc. This could be done easily with version control tool, and not overleaf I guess. | |
| Feb 26, 2017 at 3:29 | history | answered | AJK | CC BY-SA 3.0 |