abbiodiversity / abmi-git Goto Github PK

Here are some thoughts that might help 'selling' the git idea:

1. Other orgs are using it, some quite effectively:

• BC Govt: https://github.com/bcgov/
• CWS: https://github.com/PredictiveEcology/
• BAM: https://github.com/borealbirds/

2. There is precedent within ABMI:

• Joan & IC has used SVN in the past (i.e. as early as 2008) to version code
• Julia is using BitBucket for private ABMI repos (at the time GitHub did not offer free private repos)

3. There are other managed git services out there besides github:

• BitBucket (I personally find it clunky, but it integrates nicely with Jira if that is a thing we want to consider)
• GitLab (this is the best! awesome CI/CD without messing around with TravisCI/Appveyor)

Collaborating on reports manuscripts

People use MS Word or Google Docs for collaboration (tracked changes and commenting certainly beats git diff). So it becomes difficult to collaborate (bo back and forth between doc and md). I am not talking about having a doc output, but using thet doc to make changes and put it back to md/git repo.

We can version doc files in git. But that still does not address the workflow. I haven't seen a good way so far if at least one of the collaborators is unable/unwilling to use git.

Options:

• separate the workflows (analytics & text)
• find a platform that is convenient enough and people start using git (ABMI might want to consider paying for RStudio Connect: it works with python and R and offers a lot of cool stuff out of the box)