Hi Emilian, A book is a significant investment in time, but dividing up chapters will certainly make a big difference. However, in the end it is a great accomplishment that does pay...albeit very little. Here are the stages to writing a book if we go though Apress.
- First Draft - Technical Reviewer Reads - Second Draft (incorporate feedback from reviewer) - Editor Review - Third Draft (incorporate feedback from editor) - Proof Read As you can see, there are several steps. Even if you only write a chapter or two, you will be re-reading it and editing it a few times. I feel that if we go through Apress they provide a great infrastructure for us. They will provide a project coordinator to help keep us on track, and they also provide an editor. If we are unable to find a technical reviewer (I am sure we can have someone in our community do it), then they also provide that. The tech reviewer also does receive payment on a per-page basis. Lastly, Apress will provide marketing for the book, and they'll distribute free copies of the book to the authors. The book is likely to be a little bumpy, with respect to transition, if we have multiple authors. However, the goal will likely be to make it a book that can be started at any chapter...not read from front to back. Each chapter will have its own beginning and end...and that way it will be a much more cohesive book to the reader. You will not make a great deal of money with the book. However, it is a great accomplishment and you will likely learn a little bit while writing. That is one of the reasons I enjoy writing Java Recipes and Java EE Recipes books...I have to stay on top of the latest in the Java space. It would be great to have you and everyone else who is interested involved in a book for NetBeans. One or two chapters per person is not going to be too huge of a time investment...not at all like writing an entire book solo. Hope this helps. Josh Juneau [email protected] http://jj-blogger.blogspot.com https://www.apress.com/index.php/author/author/view/id/1866 > On Jul 21, 2018, at 1:39 AM, Emilian Bold > <[email protected]> wrote: > > I would be interested in a book but I'm curious what kind of effort this > involves? How much time does a book generally take (I know, it's not an exact > science, but any time range helps)? > > If we publish a book as a group we should think about the fact that the tone > / style of each chapter might come out differently. Perhaps the editor takes > care of unifying this? Also, some people might drop out. > > I assume there is no real money to be made in books, correct? > > I also doubt it makes much business sense even as a self-promotion, so it's > more a labour of love. > > --emi > > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ > >> On 17 July 2018 11:58 PM, Josh Juneau <[email protected]> wrote: >> >> I've just briefly touched base with Apress on the idea and the editor I >> spoke to sounds very interested. He says that they can divide the book up >> amongst any number of authors, and also do bylines for each of the chapters >> so that the respective authors will be noted. Typically in this situation >> there is one person who acts as the lead on the project. That way the >> editors and project coordinators at Apress can work with the lead, rather >> than all of the separate authors. >> >> Anyone interested in taking lead on the book? If so then I can get you in >> touch with the editor and we can get the details of each author/chapter, >> etc. worked out. >> >> Thanks >> >> Josh Juneau >> >> [email protected] >> >> http://jj-blogger.blogspot.com >> >> https://www.apress.com/index.php/author/author/view/id/1866 >> >>> On Jul 17, 2018, at 3:40 AM, Delfi Ramirez [email protected] wrote: >>> >>> +1 Huang Kai 😉 >>> >>> A wonder of myself to the community. Is there exist any intention or >>> interest to include JSF in the topics -- chapters, subchapters -- of the >>> book? >>> >>> Cheers >>> >>> Delfi Ramirez >>> >>> Segonquart Studio >>> >>> https://segonquart.net >>> >>> From: huang kai >>> >>> Sent: 17 July 2018 10:30 >>> >>> To: [email protected] >>> >>> Subject: Re: Apache NetBeans Apress Book >>> >>> Hi, all >>> >>> I live in china and have been using netbeans for swing and java ee dev >>> >>> for about 10 years. I think I can help translate the book to chinese, >>> >>> let's make this great platform speading more faster. >>> >>> cheers. >>> >>> Kain Huang >>> >>>> On 7/16/2018 7:53 PM, Delfi Ramirez wrote: >>>> >>>> Hi All: >>>> >>>> Agreed there is the need of a chapter-by-chapter community written book. >>>> >>>> Count me in. Even if there is the need for the book, once written, of a >>>> single translator for the whole community content. >>>> >>>> Even everyone of us has English as a mother tongue or second tongue, we >>>> may able to reach and target new markets and new loyal fellows in this >>>> world wide world we live in >>>> >>>> Cheers >>>> >>>> Delfi Ramirez >>>> >>>> Segonquart Studio >>>> >>>> https://segonquart.net >>>> >>>> From: Oliver Rettig >>>> >>>> Sent: 16 July 2018 13:47 >>>> >>>> To: [email protected] >>>> >>>> Subject: Re: Apache NetBeans Apress Book >>>> >>>> Hi all, >>>> >>>> I like the idea of a community-written book very much. This can encourage >>>> people to join >>>> >>>> our great community and it show that netbeans is now a apache project ... >>>> For me the >>>> >>>> community is one of the most important facts to work with netbeans and >>>> rarely with eclipse. >>>> >>>> I have some experience with writing a book for Tomcat 5: >>>> >>>> https://www.rheinwerk-verlag.de/tomcat-5_700/ >>>> >>>> and the most important thing I have learned from this book project is: >>>> better not to write >>>> >>>> such books alone. >>>> >>>> It would be a pleasure for me to write a chapter for a community-written >>>> Netbeans book, or >>>> >>>> may be to translate from english to german some parts, if we want to have >>>> a german >>>> >>>> version. >>>> >>>> But I have less experience in organzing such things. In scientific >>>> communities typically you >>>> >>>> have an editor or a small team of editors. Their job is often really a lot >>>> of work: to defines the >>>> >>>> chapters/articles, to find people who can write the articles and to push >>>> the authors to deliver >>>> >>>> in the timeline. >>>> >>>> An other question is where and how to publish the book. My experience with >>>> the Tomcat >>>> >>>> book was that the publisher was a really great help in formatting and >>>> proofreading. And a >>>> >>>> publisher can be a very big help in invertising for apache netbeans. >>>> >>>> But it should be also possible to write the book without a publisher at >>>> our own. In this case >>>> >>>> we can have an open-pdf-Version of the book. Maye we can have this too >>>> with a publisher? >>>> >>>> best regards >>>> >>>> Oliver >>>> >>>>> I've been approached by Apress regarding interest in a book on Apache >>>>> >>>>> NetBeans. I personally do not have enough time to devote to another book >>>>> >>>>> right now, so I wanted to send a note to the Apache NetBeans developer >>>>> >>>>> group to see if there are any developers interested in authoring a book >>>>> >>>>> (perhaps a collaborative effort). >>>>> >>>>> I know things are very busy right now, and I've already told Apress that >>>>> >>>>> the main focus is the release of Apache NetBeans 9 right now, but maybe a >>>>> >>>>> book project could start this fall. There are no timelines right >>>>> >>>>> now...just interest in a book on the new open Apache NetBeans IDE. >>>>> >>>>> If anyone is interested then reply to this message and I can get a list of >>>>> >>>>> names together to send along to Apress. >>>>> >>>>> Thanks >>>>> >>>>> Josh Juneau >>>>> >>>>> [email protected] >>>>> >>>>> http://jj-blogger.blogspot.com >>>>> >>>>> https://www.apress.com/index.php/author/author/view/id/1866 > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > For further information about the NetBeans mailing lists, visit: > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > > >
