By Developers, For Developers
| PDF Pg | Paper Pg | Type | Description | Fixed on | Comments |
|---|---|---|---|---|---|
| 4 | TYPO | “is” instead of “in” in the second sentence of the second paragraph in “Other Open Movements”. “Anyone is” should be be “Anyone in”. Wikipedia 17 is the most well-known and highly-trafficked of these open | 2018-04-04 | ||
| 12 | SUGGEST | I was very happy to see the mention of how employment agreements need to be carefully read, but there’s one thing in particular I’ve had to get exceptions to that might be worth mentioning. At a few of my employers, the employment agreement has been very ambiguous stating “all work created during your employment is owned by the company” which could be interpreted as work done at home on my own time/hardware. I’ve had to work with hiring managers/legal to get the amendments made as well as a copy of the agreement, but well worth the effort to protect the projects. | 2018-04-04 | ||
| many | TYPO | In the downloadable excerpts, when you use “which”, most of the time it should be “that” instead. They are not interchangeable. “Which” is nonrestrictive, “that” is restrictive". Your editor should have caught all these. Example: “…it prevents you from sharing changes which you don’t want to” should be “…that you don’t want to”. In this case the import of the sentence is altered from what you meant (“sharing changes that you don’t want to share”) to something you didn’t mean (“sharing changes, which is not something you want to do”) | 2018-04-04 | ||
| 22 | TYPO | In “The Origins of Free Software” section, first paragraph first sentence, “you should have probably know something about”, the “have” is likely unintentional. | 2018-04-04 | ||
| n/a | ERROR | The section on Atomic Commits under “Make a Contribution” uses “atomic” as meaning “small”; this is not correct. Atomic means that all changes made are considered as a single (atomic) unit. Most of the discussion is reasonable accurate, but the first paragraph should correctly define “atomic”. | 2018-04-04 | ||
| 11 | ERROR | I know this is not legal advice, but from everything I understand about copyright, the “fixed in a medium” thing is important… a song I create in my head and sing aloud to my dog is not copyrighted, unless I also happen to be recording it. So here: I would instead say: “Any creative work of art — be it painting, music, software code, or any other creative endeavor — is considered copyrighted when fixed in a tangible medium, or when captured so that others can see it or hear it or read it or experience it.” or something like that | 2018-04-04 | ||
| 107 | TYPO | “try to use as good of grammar as you can, including correct capitalisation I think this may have been sarcasm, in which case apologies for my comment, but: I think this should be “Use correct grammar, including correct capitalisation, spelling, and punctuation” I am not sure whether you are oxford comma’ing. I’d use “capitalization” if the author is US and the book is published in US. (Though I prefer British spellings, in general.) | 2018-04-04 | ||
| 25 | TYPO | The paragraph states that numbering begins at “0”. This is true for the PDF version. For the epub version, the number starts at “1”. | 2018-05-03 | Thanks for spotting this! It's a more complex software issue on the production side rather than a problem with the text itself. We're looking into it, but it won't be fixed in the next version of the beta. \n \nThis is now corrected in the new version of the beta that should be going live tomorrow. | |
| 6 | OK | I am reading the MOBI version of the ebook in Kindle. In the list of the Four Freedoms in Chapter 1, the “0.” for the 0th freedom is not displayed. It is displayed properly in the PDF version. | 2018-08-24 | Unfortunately, that's an error in the mobi format that we can't fix. We don't have as much access to the mobi format as we do PDF or epub. | |
| 155 | TYPO | “Pour a nice cup of tea and take a few minute to think it through before starting work on releasing that project of yours.” Looks like “minute” should be plural here. | 2018-08-10 | ||
| 158 | TYPO | “What’s new is that people are recognising that burn-out is bad, that they don’t have to put up with it, and that if they share their stories they may help inspire others not to burn out like they did. “Burnout” is styled inconsistently here: it is hyphenated in one appearance, and not hyphenated in another. Maybe these should be made identical. | 2018-08-10 | ||
| 89 | TYPO | “I covered feedback in Chapter 5, so I won’t trod that ground again.” I believe “trod” is past tense, and this should be “tread” instead. | 2018-08-10 | ||
| 2 | TYPO | In the first paragraph of the “Free and Open Source Software is Everywhere” section, the word proprietary is repeated: | 2018-08-10 | ||
| 28 | TYPO | In this sentence from the middle paragraph on page 28 of the PDF, the word “that” looks like a typo: “This means they have the authority to that approve a contribution (commit) be merged into the main repository of the project.” | 2018-09-17 | ||
| 30 | TYPO | In the second paragraph under the “CONTRIBUTING” section, the number “forty first” appears. This should be hyphenated. | 2018-09-17 | ||
| 34 | TYPO | In the first sentence of the third paragraph under the section “Issue Tracking”, the following appears: “…and many projects won’t even use all to the features available to them.” I believe the word “to” should be “of”, so it would read: “…and many projects won’t even use all of the features available to them.” | 2018-09-17 | ||
| 35 | TYPO | In the third sentence of the middle paragraph on page 35: “A mailing lists allows . . .” The word “lists” should be singular. | 2018-09-17 | ||
| 51 | TYPO | In the first sentence of the paragraph above the section ‘What is “Success”?’: " . . . they allow help you make friends . . . " I think “allow” should be removed, or if “help” is removed, it should be changed to " . . . they allow you to make friends . . ." | 2018-09-17 | ||
| 55 | TYPO | In the last sentence on this page (in the PDF), the word “acceptable” is misspelled, as “acceptible”. | 2018-09-17 | ||
| 60 | TYPO | In the first paragraph under the FOSS project diagram, a quote begins, “I hereby claim . . . ”, but there are no close quotes. | 2018-09-17 | ||
| 61 | TYPO | In the middle of the first paragraph under the section “Atomic Commits”, the word “commits” appears twice in a row. “Atomic commits commits are also much . . . ” | 2018-09-17 | ||
| 79 | TYPO | In the middle of the first paragraph on this page, the following appears: " . . . their contribution and the time the spent on it." The second “the” should be “they”. | 2018-09-17 | ||
| 88 | TYPO | In the first sentence of the middle paragraph on this page, the following appears: “how can you, enterprising new contributor, to locate them?” The word “to” in front of “locate” appears to be a typo. | 2018-09-17 | ||
| 91 | TYPO | In the first sentence under the section “But Usually: It’s Accepted! (eventually)”, “a few rounds or review and revision” should be “a few rounds of review and revision.” | 2018-09-17 | ||
| 91 | TYPO | There is a typo at the very end of the second paragraph from the bottom of this page. It reads, " . . . and then move on.o" | 2018-09-17 | ||
| 95 | TYPO | In the bullet point “Comprehend, then act rather than react”, the third sentence begins, “Listen what the other participants are trying to say . . .” It should be, “Listen to what the other participants are trying to say . . .” | 2018-09-17 | ||
| 98 | TYPO | The last sentence of the section “Communication Channels and How to Use Them” reads, “By updating the documentation you’ll be helping project and new contributors alike.” I believe it should be, " . . . you’ll be helping the project . . ." | 2018-09-17 | ||
| 102 | TYPO | The first sentence of the middle paragraph begins, “Fans of inline replies appreciate that placing the response directly beneath the statement addresses provides clear . . .” I believe the word “addresses” should be removed. | 2018-09-17 | ||
| 105 | TYPO | In the middle of the first paragraph under “Issue Tracker”, this sentence appears: “For them, the issue tracker provides an public record that’s easy to search.” It should be " . . . a public record . . . " | 2018-09-17 | ||
| 106 | TYPO | The last sentence of the first paragraph on this page begins, “Comments on closed issued get lost . . .” The word “issued” should be changed to “issues”. | 2018-09-17 | ||
| 106 | TYPO | Just below the middle of the second paragraph, a sentence begins, “It shouldn’t be too must longer . . . ” It should be “. . . too much longer”. | 2018-09-17 | ||
| 141 | TYPO | The first sentence of the last paragraph begins, “The second option is to fork the project then use your fork instead of the original project: you to create a separate . . . ” The word “to” in " . . . you to create . . . " looks like a typo. | 2018-09-17 | ||
| 148 | TYPO | In the middle sentence of the second paragraph, “respond” is misspelled as “repond.” It reads, “You can see whether people are mean, impatient, or snarky when they repond to questions from others, ” | 2018-09-17 | ||
| 153 | TYPO | In the second paragraph of chapter 10, “Start Your Own Project,” the last sentence ends, “can result in an enormous costs.” I believe “an” should be removed, or “costs” should be singular. | 2018-09-17 | ||
| 23 | TYPO | line 13. respecfully -> respectfully | |||
| 65 | TYPO | line 19. commmand -> command | |||
| 84 | TYPO | line 19. statment -> statement | |||
| 85 | TYPO | line 4. upgrate -> upgrade | |||
| 141 | TYPO | line 18. futher -> further | |||
| 175 | TYPO | line 2. receving -> receiving |