Barriers to the use of git by scientists
- Dominant language
- Shell
- Stars
- 86
- Forks
- 25
- PR merge metrics
- No merged PRs in 30d
Description
Although I agree that:
> the basic features of git can be readily used without any knowledge of command line tools
I don't think the command line is the greatest barrier for wider git use in academia.
I think that it takes some time to wrap your head around the pull-edit-commit-edit-commit-...-push workflow and that merging, branching, forking and pull-requesting (not to mention cherry-picking, rebasing and other horrors) are not so simple. So I think there is a steep learning curve, but it can be mitigated with new online courses such as the one offered by [code school and github](http://try.github.com/).
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue contains discussion about barriers to Git adoption in academia but names no file, test, or entry point. First clarify whether this feedback should change the review paper and define the expected documentation change; completion cannot be judged from the current issue alone.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100