Have y'all considered using GitHub for tracking and controlling document versions and updated? I know that would mean having people become acquainted with the concepts of fetching, push, pull requests, and so on. But it would make it easier to coordinate work.
Thoughts?
Using GitHub for version management
Using GitHub for version management
Kerc | Dice Pencil & Paper | @dicepencilpaper
- toddlyons
- Posts: 890
- Joined: Fri Sep 18, 2020 5:25 am
- Location: Unceded Algonquin Territory
- Contact:
Re: Using GitHub for version management
I suggested it recently. It was a non-starter.
- coureur_d_bois
- Posts: 1148
- Joined: Thu Jul 07, 2022 1:44 pm
- Location: Montréal, Québec
Re: Using GitHub for version management
Not everyone works in IT, let alone is a developer. Using Libre Office removes most of barriers to entry for contributors.
Re: Using GitHub for version management
Oh, I am not suggesting to replace LibreOffice for editing (it's pretty much great), but rather to manage versioning.
Kerc | Dice Pencil & Paper | @dicepencilpaper
- Solomoriah
- Site Admin
- Posts: 12535
- Joined: Thu Nov 13, 2008 8:15 pm
- Location: LaBelle, Missouri
- Contact:
Re: Using GitHub for version management
Git would treat the documents as binary lumps, which is not space-efficient.
My personal site: www.gonnerman.org
- ThorinSchmidt
- Posts: 139
- Joined: Fri Jul 28, 2017 11:11 am
- Location: Bowling Green, MO
Re: Using GitHub for version management
Git did start life as an IT development tool, but viewing it with such a lens is like saying that calculators are only useful to statisticians, or word processing software is only useful to secretaries.coureur_d_bois wrote: ↑Mon Jan 23, 2023 12:10 pm Not everyone works in IT, let alone is a developer. Using Libre Office removes most of barriers to entry for contributors.
The command-line interface of Git can be intimidating, and GUI versions of it have long been available because of that. Solo's comment about space inefficiency does have some merit, although modern storage capacities, coupled with the very real benefits of version control, along with specific merge capabilities outweigh that somewhat.
As an example off the top of my head: No two people can work on the same document at the same time. Git's merge feature would allow several to work on the document, make changes, and seamlessly incorporate them simultaneously. In the event where two people make changes to the same area? It gets flagged, and the person doing the merging simply picks which one they want (there's that pesky 'wokeism' again... ) Anyhow, I'll stop pretending I'm still a teacher and go back to lurking.
"If more of us valued food and cheer and song above hoarded gold, it would be a merrier world" – Thorin
Re: Using GitHub for version management
Simultaneous editing, at least for this, would not be a plus.ThorinSchmidt wrote: ↑Mon Jan 23, 2023 1:52 pm As an example off the top of my head: No two people can work on the same document at the same time. Git's merge feature would allow several to work on the document, make changes, and seamlessly incorporate them simultaneously.
This has been asked and answered, both in this thread and previously. Closing thread.
Who is online
Users browsing this forum: Ahrefs [Bot], Bing [Bot] and 59 guests