[FM Discuss] FLOSS Manual for FSlint

[Anne Gentle]

Hi Chris -

Great questions. The "editor" model for FLOSS Manuals is that there is
typically a maintainer per project, and that person (or group) has the
ability to publish the book. The publish command (in a drop down list
available to maintainers) is what makes the "complete manual." There are
basically two sides to FLOSS Manuals, the READ side and the WRITE side. A
maintainer decides when a book is ready to "publish" and go to the READ side
for all to review. So the "editor" role is distributed across maintainers.

As a maintainer, I can click Publish for you on the book, and any time you
think it's ready, just send a request to the list for a "Publish" of the
book, and one of the maintainers will publish it for you and the updates
will be available. There are several maintainers on this list and we have
pretty quick turnaround if you need it. We also add a link to the book on
the READ page when its ready.

To get an idea of the maintainer's role, read
http://en.flossmanuals.net/FLOSSManuals/Maintainers. It's not just a
permissions-level role, it's wider than that. I think for the FSlint
project, you're the likely maintainer, so you could decide (with others
help) when it is ready for general use.

I hope this clarifies! Feel free to ask more questions.
Anne


**
*Anne Gentle*
annegentle at justwriteclick.com
<http://www.facebook.com/conversationandcommunity>
my blog <http://justwriteclick.com/> | my
book<http://xmlpress.net/publications/conversation-community/>|
LinkedIn <http://www.linkedin.com/in/annegentle> |
Delicious<http://del.icio.us/annegentle>|
Twitter <http://twitter.com/annegentle>


On Mon, Jun 21, 2010 at 6:17 PM, Chris Stackpole <c.stackpole at gmail.com>wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hello everyone!
>
> I have a few questions I am hoping someone can answer.
>
> Yesterday I had a computer novice go through the manual and point out a
> few corrections (ok...a lot :). Today I had a few emails on a few
> corrections that I have either fixed or am in the process of fixing
> (still working on Janet's suggestion). I am getting really close to
> finishing this step of compiling the information and smoothing it out.
> What's next? What steps are there between where I am at and having
> FSlint posted as a complete manual? Is there a FLOSS manuals editor that
> needs to go through it?
>
>
> Also, it was pointed out to me that when you visit the 'homepage' for
> the FSlint manual[1] there is a note at the bottom that states:
> "Note : This page is not the manual, to see the complete manual look
> here : FSlint[2]."
> However, that link[2] is an old version and does not reflect a lot of
> changes that have been made. What do I need to do to update that
> information? I looked around but I didn't see anything. Did I just miss it?
>
>
> [1] http://en.flossmanuals.net/bin/view/FSlint/WebHome
> [2] http://en.flossmanuals.net/FSlint/Introduction
>
>
> Thanks everyone!
> Chris Stackpole
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iEYEARECAAYFAkwf8yAACgkQA8QwXn4S0qTN7gCfRJy1u2DilSXYz2GhgEsu1Kx7
> VKAAoNOyiemE8SuNuyctrp0ZwipO+xLQ
> =5eP6
> -----END PGP SIGNATURE-----
> _______________________________________________
> Discuss mailing list
> Discuss at lists.flossmanuals.net
> http://lists.flossmanuals.net/listinfo.cgi/discuss-flossmanuals.net
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.flossmanuals.net/pipermail/discuss-flossmanuals.net/attachments/20100621/e9f05e95/attachment.htm>