- Join the Google Group to follow the progress of the project and help anyone who might have questions.
- Review the latest draft manuscript. Post any suggestions or corrections to the Google Group.
- If appropriate, create a issue ticket and submit a patch to the text or code.
- If a patch is extensive, we may ask for that Contributors License Agreement to be filed with Husted dot Com, Inc.
- Checkout out the project source, and review the slides. Post any suggestions or corrections to the Google Group. The slides and text are meant as companion pieces and should follow the same general outline.
- Planned chapters will follow the slide presentations. There is a slide for every planned chapter, but some presentations are weaker than others.
- Checkout the project source, and try the labs. There are a standalone use case and lab notes for each session (chapter), appropriate for use in a classroom setting.
- The weakest area of the project is figures. (Ted is not a visual thinker!) The screen shots and figures we have are either of poor quality or need to be redrawn for publication. The figures will need to meet LuLu's critera for publication.
- Consider becoming a chapter author. A chapter author is responsible for the initial draft of a chapter, including associated code and figures, along with correcting any errata. Should a print version of the manuscript earn royalties, each chapter author would receive a prorated share based on the page count for his or her chapters. To ensure that the manuscript retains a consistent voice, Ted Husted performs a final edit of each chapter, making gratuitous, stylistic, and ruthless changes.
|
Sign in to add a comment
