Talk:The Case for Using Wiki Version History

I agree that given that you are using a wiki as a repository you would want to just upload a new version of a file and use it. I just think that MediaWiki was not intended to be used as a repository.

If I understand correctly the reason you gave for not using Git are

1. You don't control the data with Gitlab
2. Visual Version History
3. Collaboration on a scale
4. It is currently used for a large set of parts (this was not included originally but I think it is important)

I still think Git has major advantages and want to give counterpoints to the arguments above

1. You don't control the data with Gitlab

I don't understand this, why don't you own the data, you can host it on your server.

2. Visual Version History

I think that Visual Version History should not be a problem, you can either just continue using the wiki and then link to the git files. Even better, the visual version history could be automatically created as a commit hook and on GitLab.

3. Collaboration at a scale

I think there is a case that the access privileges are much better with Git. I believe that pull requests are probably necessary on a very large scale collaboration.

4. It is currently used for a large set of parts

I think this point is very strong and that the transition could be a lot of work. But I still think that it could be worth it, and it should be tried out.