View Single Post
Old 06-26-2017, 05:03 PM   #81
gwynevans
Wizzard
gwynevans ought to be getting tired of karma fortunes by now.gwynevans ought to be getting tired of karma fortunes by now.gwynevans ought to be getting tired of karma fortunes by now.gwynevans ought to be getting tired of karma fortunes by now.gwynevans ought to be getting tired of karma fortunes by now.gwynevans ought to be getting tired of karma fortunes by now.gwynevans ought to be getting tired of karma fortunes by now.gwynevans ought to be getting tired of karma fortunes by now.gwynevans ought to be getting tired of karma fortunes by now.gwynevans ought to be getting tired of karma fortunes by now.gwynevans ought to be getting tired of karma fortunes by now.
 
gwynevans's Avatar
 
Posts: 1,402
Karma: 2000000
Join Date: Nov 2007
Location: UK
Device: iPad 2, iPhone 6s, Kindle Voyage & Kindle PaperWhite
Quote:
Originally Posted by dwig View Post
In this day of false news and deliberate attacks alter data on sites like Wikipedia I don't want books from sites that let random users alter the books. Sending suggested "fixes" to their editors is fine, but direct access to Git is a red flag for me.
To be fair to them, the main route for minor fixes appears to be as posts to their mailing list, while the Git route is via GitHub, which doesn't imply direct access to the project's Git repo.

That workflow would be to 'fork' it into your own personal Get repo, make the changes there then send the original project's maintainer a 'pull' request, inviting them to review and incorporate the changes they approve into the mainstream project - if someone were to be regularly providing high quality edits, they might give them direct access, but that's a different ball-game.
gwynevans is offline   Reply With Quote