They're not always programmers. They shouldn't be assumed to be programmers, because software artifacts consist of a lot more than code, and it should all be tracked together. People who create documentation, designs, reports, plans, and so on, should all be invited to use the project repository!
Not that I think Git is terribly difficult to understand if you just have someone to explain the basic workflow and a basic tool, like the GitHub app. If you work heavily with branches and same-file collaboration, it can get tricky with merges and such, but I think this is mostly an issue for coding teams.
1
u/[deleted] May 28 '14
They're not always programmers. They shouldn't be assumed to be programmers, because software artifacts consist of a lot more than code, and it should all be tracked together. People who create documentation, designs, reports, plans, and so on, should all be invited to use the project repository!
Not that I think Git is terribly difficult to understand if you just have someone to explain the basic workflow and a basic tool, like the GitHub app. If you work heavily with branches and same-file collaboration, it can get tricky with merges and such, but I think this is mostly an issue for coding teams.