3 ms·

> Part of the problem, though, is that PG's errata process (https://www.gutenberg.org/help/errata.html https://www.gutenberg.org/help/errata.html) is quite cumb

by cxr 3y ago

> Part of the problem, though, is that PG's errata process (https://www.gutenberg.org/help/errata.html https://www.gutenberg.org/help/errata.html) is quite cumbersome since you have to write an email to their errata team with each individual error. That's a real hassle to try to keep track of and submit. Ideally, if PG had something like a pull request system, I would just be able to[...] 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".

acabal 3y ago
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.
- deleted 3y ago
  [deleted]
- starkparker 3y ago
  > 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 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.
  - acabal 3y ago
    It's very uncommon, if you want to do that then just email me privately and we can set something up.
bentley 3y ago
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.)

by cxr 3y ago

acabal 3y ago

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.

deleted 3y ago
[deleted]
starkparker 3y ago
> 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 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.
- acabal 3y ago
  It's very uncommon, if you want to do that then just email me privately and we can set something up.

bentley 3y ago

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.)