<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<font face="Helvetica, Arial, sans-serif">Hi John -<br>
<br>
Thanks for that explanation, I really appreciate it.<br>
<br>
It looks like a chapter's status doesn't affect whether or not it
gets published. Is that correct?<br>
<br>
Mark<br>
</font><br>
On 11/15/2010 04:39 PM, John Curwood wrote:
<blockquote cite="mid:1289857198.1848.33.camel@curwood-laptop"
type="cite">
<pre wrap="">With the publish button is pressed, an HTML version of the book is
created, which can then be linked to from the FM front page.
The link will need to be manually created by one of the FM admins once
the manual is published (To see what the manual will look like, visit
any of the manuals that are linked from the front page). When you
publish the manual only chapters that have been added to the Table of
Contents using the "arrange manual index" tool will be published. So, if
you have most chapters ready for publishing but a couple that need a lot
of work before being ready for publishing, but you want to publish the
book now, click and drag the unfinished chapter into the left hand
column in the 'arrange manual index' tool and when you click publish
that particular chapter wont get published.
Once published you can keep modifying the manual without worrying that
the published version will get changed and then when enough changes have
been made you can click the publish button again to update the HTML
manual with the changes you have made.
If that isn't clear, which reading over it now it may not be, or you
have any other questions then just ask the list.
Cheers,
John
On Mon, 2010-11-15 at 16:08 -0500, Mark wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Hello John -
Please email feedback to the list.
Also, what happens when someone pushes the Publish button?
Thanks,
Mark
On 11/15/2010 03:47 PM, John Curwood wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Hi Mark,
I think for the checking the Chapters marked "Feedback Please" it's
a good idea to use people on the list so that you get fresh
perspective from people that aren't involved in writing the
Thunderbird manual at all let alone the specific chapter requiring
feedback.
By the way how do you want feed back to be received?
Via an email to the List or via the "Chapter Talk" link.
Cheers,
John
On Mon, 2010-11-15 at 11:59 -0500, Mark wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Hello All -
The Thunderbird manual team has been figuring out what it needs to
do to finish the book and get it published. Adam thought that it
would be good to share this discussion with the FM list. Please
take a look and join in with suggestions and comments.
Thanks,
Mark
-------- Original Message --------
Subject:
Re: Thunderbird Floss Manual -
tasks and status
Date:
Mon, 15 Nov 2010 11:27:46 -0500
From:
Mark <a class="moz-txt-link-rfc2396E" href="mailto:mark.brennan@gmx.com"><mark.brennan@gmx.com></a>
To:
<a class="moz-txt-link-abbreviated" href="mailto:jen@mozillamessaging.com">jen@mozillamessaging.com</a>, Scott
Nesbitt
<a class="moz-txt-link-rfc2396E" href="mailto:nesbitt.scott@gmail.com"><nesbitt.scott@gmail.com></a>
CC:
<a class="moz-txt-link-abbreviated" href="mailto:adam@flossmanuals.net">adam@flossmanuals.net</a>
Hi Jen and Scott-
I was a little unclear about how the statuses work, too. Once upon
a time I was a print production manager for a publisher and a part
of my job was getting documents through an editorial department.
So, trying to put that experience to good use, here's my suggested
process for how we can finish this project.
- Unpublished: Writing is in progress
- Needs Feedback!: The chapter needs to be reviewed and commented
on by someone other than the writer. This is when someone should
test the task descriptions to confirm that they are correct.
- To Be Copy-edited: Copy-edit the chapter for grammar and style
but not for content.
- To be proofed: One last check before completion.
- Complete: Chapter is ready for publication
- Published: Chapter is in production
At this point, we have many chapters that are ready for
proofreading or for copy-editing plus a few that are unpublished
or that need feedback. Let's start going through them one by one
until we are finished. After proofreading is done for a chapter,
we should set it to complete. When all the chapters are complete,
we can go ahead and publish the manual. Are you comfortable with
is approach? Should we do it differently?
About the image that doesn't appear when viewing the page, I had
the same issue when reviewing the Composing chapter.
I don't know what caused it and I couldn't fix it. I ended up
deleting the picture and re-inserting it. Deleting the picture
from the page doesn't delete it from the system so I just grabbed
the existing picture and put it back where it belonged.
When you say the build tools, are you referring to the "Publish"
button on the left side of the FLOSS screen? Do you know what
happens when you push it? I'm always a little hesitant to push a
button when I'm not sure about what happens next...
Mark
On 11/12/2010 07:30 PM, Jennifer Zickerman wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Hi Mark. On the main Thunderbird page (where the chapters are
listed), I see that each chapter has a status-like value
("unpublished", "to be proofed", etc). Can you tell me what
these statuses mean, and how I can help? What is the general
status on the project?
Also, do you know why the link at the bottom of that page (to
view the manual) is 404? Adam asked me in IRC if I'd tried the
build tools yet - I don't know whether that was a hint or
what. :)
Also, I have a technical problem on the Getting Support page
(<a class="moz-txt-link-freetext" href="http://en.flossmanuals.net/bin/view/Thunderbird/GettingSupport">http://en.flossmanuals.net/bin/view/Thunderbird/GettingSupport</a>). When I edit the page, there is a graphic. But when I view the page, I only see the graphic's alt tag ("thunderbird_support_search_engine "). Any ideas?
No worries if you don't know the answers to any of these
questions - I just thought I'd ask you first. :)
jen.
</pre>
</blockquote>
<pre wrap="">_______________________________________________
Discuss mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Discuss@lists.flossmanuals.net">Discuss@lists.flossmanuals.net</a>
<a class="moz-txt-link-freetext" href="http://lists.flossmanuals.net/listinfo.cgi/discuss-flossmanuals.net">http://lists.flossmanuals.net/listinfo.cgi/discuss-flossmanuals.net</a>
</pre>
</blockquote>
<pre wrap="">
_______________________________________________
Discuss mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Discuss@lists.flossmanuals.net">Discuss@lists.flossmanuals.net</a>
<a class="moz-txt-link-freetext" href="http://lists.flossmanuals.net/listinfo.cgi/discuss-flossmanuals.net">http://lists.flossmanuals.net/listinfo.cgi/discuss-flossmanuals.net</a>
</pre>
</blockquote>
<pre wrap="">_______________________________________________
Discuss mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Discuss@lists.flossmanuals.net">Discuss@lists.flossmanuals.net</a>
<a class="moz-txt-link-freetext" href="http://lists.flossmanuals.net/listinfo.cgi/discuss-flossmanuals.net">http://lists.flossmanuals.net/listinfo.cgi/discuss-flossmanuals.net</a>
</pre>
</blockquote>
<pre wrap="">
_______________________________________________
Discuss mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Discuss@lists.flossmanuals.net">Discuss@lists.flossmanuals.net</a>
<a class="moz-txt-link-freetext" href="http://lists.flossmanuals.net/listinfo.cgi/discuss-flossmanuals.net">http://lists.flossmanuals.net/listinfo.cgi/discuss-flossmanuals.net</a>
</pre>
</blockquote>
</body>
</html>