On 3/11/2014 10:32 AM, Spencer Krum wrote: > Thanks so much for reading attentively and posting your feedback. I'm > sorry you don't want to help us more formally.
I want to make it clear that the reason for this is because since this is a closed-source book, I'd need some form of payment for a formal relationship (I've done massive free edits of Pro Git and Managing Jenkins because these are open-source books). At this point, such things only complicate my taxes and make me feel obligated to get things done to meet deadlines. Since I have a fulltime day job I can't commit to anything with fixed deadlines. It wouldn't be fair to you or Apress. > I don't think its realistic to open source the book at this point, but I'll > open the > conversation with Apress and the other authors. OK. If you do change your mind then I'd be more than glad to work with you. Jon On Tue, Mar 11, 2014 at 10:32 AM, Spencer Krum <krum.spen...@gmail.com> wrote: > > Hi Jon, > > I'll ask my editor to link the errata from the github repository to the > eratta page on the Apress website. I want to assure you we went through > several rounds of editing, but errors are always going to fall through. > Thanks so much for reading attentively and posting your feedback. I'm sorry > you don't want to help us more formally. I don't think its realistic to open > source the book at this point, but I'll open the conversation with Apress > and the other authors. > > Thanks again, > Spencer > > On Monday, March 10, 2014 4:31:26 AM UTC, Jon Forrest wrote: >> >> >> >> On Wednesday, March 5, 2014 10:29:07 AM UTC-8, Spencer Krum wrote: >> Hi Jon, >> >> > My name is Spencer Krum. I am one of the authors of Pro Puppet. I want >> > to thank you for going through the book with such a fine toothed comb. >> > I wish I had known you were so committed to making this book a success >> > months ago. I would have gotten you an advance copy so you could >> > have helped make the final version better. >> >> What concerns me most is how Apress could have released a book with so >> many issues. >> Somehow their production process broke down. >> >> > From what I understand from Apress, we don't have the ability to >> > directly address these problems in newly sold versions of the book. >> > These errors will be with us until a 3rd edition comes out, maybe >> > sometime around Puppet 4. >> >> I'm sorry to hear that. That seems like a long time to wait. What's worse >> is that people who don't read this email list >> will have no idea that this book is full of issues. Even now, after I've >> been releasing these lists for ~2 weeks, the >> errata page on the Apress web site (http://www.apress.com/9781430260400) >> still says there are no errata for this book. >> That's not fair. >> >> > Here is what we can do. I have created a github repository to collect >> > the errata in a single place. >> > https://github.com/pro-puppet/pro-puppet-errata >> > I don't think we can get that link added to the front matter, but we can >> > probably get it added to the description of >> > the book on Amazon, and can link to it in the online/supplemental >> > materials. This repository is one central place >> > we can collect all the errors/corrections about Pro Puppet 2n'd edition, >> > not just yours. >> > I've already added your ch1-4 reviews to that project. Would you be >> > willing to work on the rest of the chapters with us? >> >> Since I haven't received any money from Apress, nor will I request >> anything other than my own copy of the book (which >> they've now given me), I'm not inclined to formally work on this project >> (see below) >> >> > If you feel comfortable with git/github I can give you contributor >> > access or I can add the text if you want to send it to me. >> > I think collecting all the errors in the github repository is a better >> > solution than posting them all to separate messages >> > to the Puppet users mailing list, a list of over a thousand people. >> > What do you think? >> >> What I'm planning on doing is continuing on as I have been. I'm going to >> post my lists, chapter >> by chapter, to this list. You, and anybody else, are free to do whatever >> you want with them, such as putting >> them up on GitHub. I clearly label these postings so anyone who isn't >> interested in them can easily >> skip them. >> >> Is this a reasonable approach? >> >> Jon Forrest >> >> P.S. Have you considered putting the sources for Pro Puppet 2nd ed. up on >> GitHub the way >> Scott Chacon did for Pro Git? > > -- > You received this message because you are subscribed to a topic in the > Google Groups "Puppet Users" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/puppet-users/dzXe29iNwtQ/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > puppet-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/puppet-users/52ee6a2c-8cbd-4d2d-a687-4a5cee33aa6a%40googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAF0Z9ioVx-O_QkqxHHzUaEKU4L%3DRr%2BCSEN4me%2BurtJ3T%3DMQfTQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
