Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Using git for manuscripts #8

Open
yoavram opened this issue Jan 17, 2013 · 1 comment
Open

Using git for manuscripts #8

yoavram opened this issue Jan 17, 2013 · 1 comment
Labels

Comments

@yoavram
Copy link

yoavram commented Jan 17, 2013

I think it would be interesting to share more of the experience of collaborating on manuscript writing in github.
I find that collaborating with Word with more than one person is a real pain: file versions, track changes becoming a jungle, comments getting lost, version control via email, people forgetting to send (push) revised draft to the main author, people revising the wrong version, merging two different revisions of the same version (branch merge), bibliographies...
Everyone knows this.
How does git+github make it better? You discuss this in Use cases 3., but maybe give an actual example from that project - an event in which the main author asked for contribution via an issue, two authors branched, edited, pushed, and the main author merged. Something like that.
I think that this is where you can really sell git for manuscripts (and of course the draft_v1_v2_221012_final_final.doc thing...), even for non-programming scientists.

karthik added a commit that referenced this issue Jan 18, 2013
This could be one concrete example of why git is better for writing than using MS Word and track changes.
@FADHLyemen
Copy link

Any updates about this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants