3 ms·
I find if I enable edit permissions, people can do more than suggest changes, they can make them. An editor can turn off tracking, that has to be done frequentl
by prepend 6y ago
I find if I enable edit permissions, people can do more than suggest changes, they can make them. An editor can turn off tracking, that has to be done frequently to fix formatting and layout issues, and changes aren’t visibly tracked.
I wish there was a “pull request” for office with a permission that allowed suggestions but not edits.
- robenkleene 6y agoThis sounds great... in theory. But has a pull request feature ever been created for a non-plain text format? Intuitively, this doesn't really seem possible to me for a sophisticated document format. E.g., how would you represent a change to an embedded graph in a pull request? (And would that same approach scale to any form of embedded media?)
- TheCloudlessSky 6y agoIt's not an easy task, but it's doable! I co-founded a company called ProcedureFlow[0], that allows change requests but for hyperlinked flowcharts. My inspiration was 100% GitHub/pull requests. A procedure is made up of many flows that are linked together. Everyone that uses the procedure views the "live" flows (like a master branch). Each user gets their own branch which we call a "draft". In a draft, a user is free to make any changes they want (add/delete/modify flows) and then submit all the changes for approval. Approving the change request then merges the changes into the "live" for everyone else to see/use. I even went so far as to build side-by-side diff of the flowcharts, rebasing/merging with live, and conflict resolution. It's simplified in the UI so the terminology isn't 100% like git. But, one of our biggest hurdles though is actually teaching users how this works why it's better than the current mode of document locks/real time editing. And when our customers "get it", they really fall in love with the concepts and why it's better! [0]: https://procedureflow.com/ https://procedureflow.com/