head	1.3;
access;
symbols
	fourth_edition:1.2;
locks; strict;
comment	@# @;


1.3
date	2002.12.29.02.57.23;	author grog;	state Exp;
branches;
next	1.2;

1.2
date	2002.04.14.05.08.39;	author grog;	state Exp;
branches;
next	1.1;

1.1
date	2002.04.07.01.27.47;	author grog;	state Exp;
branches;
next	;


desc
@@


1.3
log
@Updates.
@
text
@       <!-- -*- html-fill -*- -->
       <!-- $Id: dear-reviewer-1a,v 1.2 2002/04/14 05:08:39 grog Exp $ -->
      </font>
    </center>

    <p>
    This directory contains draft files for the upcoming fourth edition of ``The Complete
    FreeBSD''. This is not freely available information. You should not be here unless you are a
    reviewer.</p>

    <p>
    If you are a reviewer, please:</p>

    <ul>
      <li>
      respect the confidentiality of this site. Don't give the URL to anybody else.</li>

      <li>
        <p>
        use the texts only for review purposes. Assuming reasonable review feedback, you'll get
        a free copy of the book on publication, so there's no need to keep the drafts unless you're
        an incurable packrat.</p>
      </li>

      <li>
        <p>
        review! The chapters you should be looking at are shown as ``review draft'' in the <a
        href="STATUS.txt">status</a> files included in this directory. I prefer feedback as
        comments in the .txt files.</p>
      </li>
    </ul>

    <p>If you are not a reviewer, please <a href="mailto:grog@@lemis.com">
    contact me</a> and let me
    know that the cover has been broken. You, too, can be a reviewer! All you have to do is to
    contact me and promise to respect the conditions shown above.</p>

    <h2>Draft status</h2>
    The status indications in the <a href="STATUS.txt">status</a> file have approximately the
    following meanings: 

    <ul>
      <li>
      Draft: I'm working on it, but it's not done yet.</li>

      <li>
        <p>
        Review draft: I've worked on it, and I think it's good enough to look at now. The text
        may not be properly laid out yet (expect widows and orphans, maybe partial pages not
        intentionally left blank, and missing cross-references to other chapters), but the content
        should be correct. Complain if it isn't. Don't worry about the missing cross-references:
        I'll fix them at the very end. The formatter spits out error messages, so I won't miss
        one.</p>

        <p>
        Some of the chapters were marked ``review draft'' while the book was still targetted at
        4.x. They may need substantial changes for 5.x. If you see any such discrepancy, check the
        modification date of the chapter: if it's before, say, September 2002, don't worry too
        much.</p>
      </li>

      <li>
        <p>
        Final draft: It's been reviewed, I've applied comments by the reviewers, and I think
        it's ready to print. With the exception of some small format issues, it should look
        correct. The format issues relate to some bugs in my build environment which cause comments
        to get indented incorrectly. They'll be gone in the final book.</p>
      </li>

      <li>
        <p>
        4th edition: It's gone to print.</p>
      </li>
    </ul>

    <h2>How to submit feedback</h2>
    It's up to you how you submit feedback, but I find it easiest if you read the PDF version
    (since there could be format issues) and mark up the text version of the chapter. You can
    remove extraneous data if you want. Quote the text as in mail and add your own comments without
    quotes. For example: 
<pre>
&gt; Your mileage may vary.  During the review phase of an earlier edition of this
&gt; book, one of the reviewers stated that he was very happy with his machine,
&gt; which has a 486-33 processor, 16 MB main memory, and 1 MB memory on his
&gt; display board.  He said that it ran a lot faster than his Pentium 100 at work,
&gt; which ran Microsoft.  The moral: if your hardware doesn't measure up to the
&gt; recommended specification, don't be discouraged.  Try it out anyway.

I think you should add a paragraph stating that minimum system
requirements are very dependent *what* work you want to do.
</pre>

    <p>
    When sending feedback, please refer to the chapter title, not the chapter number: the latter
    may change between the time you review the chapter and the time I look at the review. Also,
    page numbers don't help very much, since they keep changing. Context is better.</p>

    <p>One thing that makes it <i>
    very</i> difficult is badly wrapped text, such as described at <a
    href="http://www.lemis.com/email/email-format.html">Internet mail: formats</a>. If you have to
    use an MUA which performs this kind of mutilation, it would be better to look for an
    alternative way to supply feedback.</p>

    <h2>How I handle your feedback</h2>
    You'll get feedback from me for everything you send in. If you don't, I've lost it. The trouble
    is, I won't look at your feedback immediately. It might take up to a month before I look at it:
    I'll look at it next time I look at the chapter. Don't wait the month, though: I might look at
    it very soon, and then your comments might come too late. 

    <h2>Files in this directory</h2>

@


1.2
log
@Add request to refer to chapter name.
@
text
@d1 80
a80 85
<!-- $Id: dear-reviewer-1a,v 1.1 2002/04/07 01:27:47 grog Exp grog $ -->
</font></center><p>
<p>
This directory contains draft files for the upcoming fourth edition of
``The Complete FreeBSD''.  This is not freely available information.
You should not be here unless you are a reviewer.

<p>
If you are a reviewer, please:

<ul>
<li>
respect the confidentiality of this site.  Don't give the URL to
anybody else.
</li>
<p>

<p>
<li>
use the texts only for review purposes.  Assuming reasonable review feedback,
you'll get a free copy of the book on publication, so there's no need to keep
the drafts unless you're an incurable packrat.
</li>
<p>
<li>
review!  The chapters you should be looking at are shown as ``review draft'' in
the <a href="STATUS.txt">status</a> files included in this directory.  I prefer
feedback as comments in the .txt files.
</li>
</ul>
<p>
If you are not a reviewer, please <a
href="mailto:grog@@lemis.com">contact me</a> and let me know that the
cover has been broken.  You, too, can be a reviewer!  All you have to
do is to contact me and promise to respect the conditions shown above.

<h2>Draft status</h2>

The status indications in the <a href="STATUS.txt">status</a> file have
approximately the following meanings:

<ul>
<li>
Draft:  I'm working on it, but it's not done yet.
</li>

<p>
<li>
Review draft: I've worked on it, and I think it's good enough to look
at now.  The text may not be properly laid out yet (expect widows and
orphans, maybe partial pages not intentionally left blank, and missing
cross-references to other chapters), but the content should be
correct.  Complain if it isn't.
</li>

<p>
<li>
Final draft: It's been reviewed, I've applied comments by the reviewers, and I
think it's ready to print.  With the exception of some small format issues, it
should look correct.  The format issues relate to some bugs in my build
environment which cause comments to get indented incorrectly.  They'll be gone
in the final book.
</li>

<p>
<li>
4th edition: It's gone to print.
</li>
</ul>

<p>

In mid-March, I changed the page dimensions to match O'Reilly books.  This
caused some format problems in chapters marked as review draft.  Don't worry,
I'll see them again.  At present, you'll find some computer output samples which
are too wide; I'm waiting for feedback from O'Reilly before fixing them.

<h2>How to submit feedback</h2>

It's up to you how you submit feedback, but I find it easiest if you read the
PDF version (since there could be format issues) and mark up the text version of
the chapter.  You can remove extraneous data if you want.  Quote the text as in
mail and add your own comments without quotes.  For example:

<p>
d82 6
a87 6
> Your mileage may vary.  During the review phase of an earlier edition of this
> book, one of the reviewers stated that he was very happy with his machine,
> which has a 486-33 processor, 16 MB main memory, and 1 MB memory on his
> display board.  He said that it ran a lot faster than his Pentium 100 at work,
> which ran Microsoft.  The moral: if your hardware doesn't measure up to the
> recommended specification, don't be discouraged.  Try it out anyway.
d93 18
a110 20
<p>
When sending feedback, please refer to the chapter title, not the chapter
number: the latter may change between the time you review the chapter and the
time I look at the review.

<p> 
One thing that makes it <i>very</i> difficult is badly wrapped text,
such as described at <a
href="http://www.lemis.com/email/email-format.html">Internet mail:
formats</a>.  If you have to use an MUA which performs this kind of
mutilation, it would be better to look for an alternative way to
supply feedback.

<h2>How I handle your feedback</h2>

You'll get feedback from me for everything you send in.  If you don't, I've lost
it.  The trouble is, I won't look at your feedback immediately.  It might take
up to a month before I look at it: I'll look at it next time I look at the
chapter.  Don't wait the month, though: I might look at it very soon, and then
your comments might come too late.
a111 1
<h2>Files in this directory</h2>
@


1.1
log
@Initial revision
@
text
@d1 1
a1 1
<!-- $Id$ -->
d98 5
a103 1

@
