My english teacher wants to be able to see document history. He says that my process is more important than the product. Is there any way to do this in libreoffice or some other open source document editor?
Do you have access to an Etherpad-server? (Or better yet, can set one up by yourself?)
It allows petty minute tracking of changes and makes it easy to see how the document evolved over time. It has just enough Rich-Text-capabilities to be suitable for an assignment in English class, without too much distraction. And you can simply share a link to your pad with the teacher. As it also tracks authorship, they can even add redactions and commentary.
The way you normally do this for Word documents is Track Changes. Microsoft Word and Libre Office also have a built-in way to compare two documents, in case you didn’t have Track Changes enabled. I assume if they’re asking for document history, they want to see what changed when revising your draft, not in what order you pressed the keys. Although personally I tend to revise back the past part of the document as I’m writing instead of writing multiple drafts and this wouldn’t really work for me. I guess another option is just to use set a timer and save a new version every so often. Maybe there’s a trick you can do with scripting to make copies of your autosave file and then combine those into a format your teacher can understand.
Using Git is out of touch. It’s incredibly unlikely that a language teacher understands Git or cares to learn how to use Git.
It sounds like your teacher probably has a way they expect students to do this, probably Google Docs or Office 365. Both of these have web versions so you could use them even if you’re running Linux.
Besides track changes in word (already mentioned), I save versions of my work docs by appending the date and time to the file name. This makes it easy to confirm of we’re all looking at the same doc.
Example: worddoc_2026-09-08_16-46
Time uses 24 hour clock, so I never guess AM/PM, and it makes sorting really easy.
Nice thing is this works for any document type.
Don’t forget to add the “final” tag, to your filename. And the “finalfinal”, “absolutelyfinal”, “definitelyfinalthistimeforreal” and so on.
Just save a new copy after each session. Sure, there are more elegant ways to track changes and version history, but if he literally wants progress reports, zip everything up when you send him the final.
might try that. Still better if I can get it into one document but this might be the next best thing
Maybe this helps? https://help.libreoffice.org/latest/en-US/text/shared/01/01190000.html
I just write text docs in Emacs and use Git for version tracking. If he wants real-time tracking it’s possible that one of the collaboration editors can do that and I might look into it. In the extreme you could videotape yourself working and typing, and maybe saying out loud what you are doing. I think the purpose is to show that you were doing the work yourself rather than prompting an AI.
I guess there are also software screen recorders and maybe there’s a way to log X events (keystrokes and mouse movement) if that approach is ok with both of you.
Video is probably a bit of a bloated approach to fulfill this request. Both in filesize and, more importantly, effort to review it.
We gotta keep the teacher’s perspective in mind. They’re gonna have a hard time reviewing video footage of a whole class.
I’d suggest setting up an Etherpad server and sharing a link with the teacher. It allows tracking of changes and authorship and has just enough Rich-Text-capabilities to be suitable for an assignment in English class, without too much distraction.
This might sound stupid but git?
I thought about it, but I don’t think my teacher knows how to use git. He’s already having issues importing a .odt into google drive if that tells you his technical ability.
Okay, so the question is, if you enable tracking changes (seems the easier solution?) in LibreOffice, will that transfer if he opens the file in Google Docs or Word?
I don’t have an answer, I’m not up to date on how G and M$ mess up open file formats. But maybe this is an avenue to explore.
Git is not stupid. It’s common. With markdown of course.
The teacher just wants to see proof that he wrote it himself and not an ai
Git is not stupid. It’s common. With markdown of course.
XKCD 2501.

The nice thing about xkcd is it’s been running for so long that a random one is new again. It’s the modern version of The Far Side.
I couldn’t decide how to comment this better, so here’s two versions of a comment:
- This xkcd is not new, it’s common.
- https://xkcd.com/1053/
It may be common among nerdy IT guys?





