Typos can be reported by email on SE too. Git is only required when you’re publishing a new book. My observation from watching the mailing list is that emailed typos are fixed quickly. (I always fix typos using pull requests, and those are acted on quickly too.)
You don't have to use Github if you don't want to, but you do have to use Git. We've had more than a few producers successfuly produce ebooks without using GitHub or Google Groups.
Re:Standard Ebooks
by starkparker on Monday January 01, 2024 @06:47PM
(#38836405)
> We've had more than a few producers successfuly produce ebooks without using GitHub or Google Groups.
Can you share or document how? https://standardebooks.org/contribute suggests that "Technically inclined readers can produce ebooks themselves" but doesn't provide any point of entry to do so other than a link to the GitHub org, and "No technical experience is necessary. Contact the mailing list if you want to help." just links to the Google Group.
On the other side of the coin, Standard Ebooks's heavy endorsement/buy-in of GitHub-based workflows are offputting to broader audiences. (It's pretty offputting to me, and I'm not even non-technical; I just recognize it as a sort of Conway's Law + Law of the Hammer sort of thing, and it chafes.) I.e., for others what you describe is far less than "ideal".