Post History

Source: https://writers.stackexchange.com/a/44634
License name: CC BY-SA 3.0
License URL: https://creativecommons.org/licenses/by-sa/3.0/

Source: https://writers.stackexchange.com/a/44634
License name: CC BY-SA 3.0
License URL: https://creativecommons.org/licenses/by-sa/3.0/

# Github or similar is a good choice

I can't say I have used it personally for this type of work, however as a software engineer by day it is my collaboration tool of choice for most things.

> Unlike the StackExchange Podcast that inspired this, I am not familiar with GitHub.

I'd like to assure you that learning git/github isn't that difficult. If you can master stack exchange you can handle github. I found [an easy guide](https://guides.github.com/activities/hello-world/) that doesn't require any installation or use of the command line. With a little searching you will find hundreds of guides on what git is and how to use it.

### Why it is a good choice

- **Centralised** : You can have a single repository per project
- **Protected** : Pull requests and review prevent spammers from harming your transcripts
- **Low entrance barrier** : Users can make edits and submit for review directly in the brower
- **Choice of editor** : Users can edit files locally and upload changes for review 
- **Robust version management** : all changes are tracked and can be reverted
- **Format independent** : git deals in raw text so any file format can be used, markdown is rendered on github so can be a good choice.
- **User permissions** : the repository owner has complete control over who has access to their repository and what they can do with that control. Additionally you can delegate permissions to other trusted users 

Original score: 3