We are already using Gitlab in our development process. We want to integrate our specification files (which currently are Word documents) into our repository, in order to leverage the versioning of Git. Our stakeholders are not engineers, so my quesiton is: how could we use that setup to let them modify easily the specifications and store them in Gitlab? And more broadly, if you have done something like that, I'm interested in your feedback.
-
If you want versioning on Word documents, Word has Track Changes which you can enable in your files. You can then store them on Git for safe keeping, while Word itself will allow you to make diffs. However, this requires some level of discipline from your stakeholders to not mess up the files. Online Word files stored in something like Office365 or sharepoint should help with that. If that's not an option, and if discipline is needed, you might just as well have them learn to use GitLab.– BogdanMar 2, 2021 at 14:08
-
Why the downvote?– Alexis DufrenoyMar 16, 2021 at 14:22
1 Answer
You won't be able to use Word documents effectively within a git repository. You could use your repo to check in the Word document file and version it, but you wouldn't be able to do diffs or handle merge conflicts. It could even add overhead to the team, depending on who has the right access permissions and knowledge to be able to use git to control the version.
If you want to use GitLab features, GitLab has a wiki, a static site editor, and issues that are more friendly for stakeholders, but they would need some level of access to GitLab. If you want to continue using a Word document, you may want to look at document management tools that are designed to work with Word documents (which would also likely work with other Microsoft Office formats, like Excel and PowerPoint).