Um. I published it last night but didn't email the list, sorry about that. I saw the same "not readable" messages on the png files. <br><br>I added a link to the front page, I believe. I put it under GNU/Linux. I think that's the right location.<br>
<br>Congrats to Chris and FSLint!<br><br>Anne<br><br><span style="color: black;"><div dir="ltr"><div>
<span style="font-size: x-small;"><span style="font-size: xx-small;"><strong><span style="font-size: 8pt;"><span><span style="font-size: small;"></span></span></span></strong></span></span><div style="padding: 5px; font-size: 11px; color: rgb(102, 102, 102); font-family: sans-serif;">
<strong>Anne Gentle</strong>
<br>
<a href="mailto:annegentle@justwriteclick.com" target="_blank">annegentle@justwriteclick.com</a><br><a href="http://www.facebook.com/conversationandcommunity"></a>
<div style="font-size: 10px;">
<a href="http://justwriteclick.com/" target="_blank">my blog</a> |
<a href="http://xmlpress.net/publications/conversation-community/" target="_blank">my book</a> |
<a href="http://www.linkedin.com/in/annegentle" target="_blank"><span class="il">LinkedIn</span></a> | <a href="http://del.icio.us/annegentle" target="_blank">Delicious</a> |
<a href="http://twitter.com/annegentle" target="_blank">Twitter</a>
</div></div></div></div></span><br><br><div class="gmail_quote">On Wed, Jun 23, 2010 at 6:15 AM, John Curwood <span dir="ltr"><<a href="mailto:marketing@lovinglearning.co.nz">marketing@lovinglearning.co.nz</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">Ok I have published FSlint. The published manual can be found at:<br>
<div class="im"><a href="http://en.flossmanuals.net/FSlint/Introduction" target="_blank">http://en.flossmanuals.net/FSlint/Introduction</a><br>
<br>
</div>I will add the link from the FM front page in the morning as I am now<br>
very tired. Also I had a couple of strange issues come up:<br>
<br>
I had some come up during the process regarding images being "not<br>
readable" in 3 of the chapters, but they were viewable in the published<br>
manual.<br>
<br>
However, The chapter "Common interface items" has only one image that<br>
has loaded properly in the published image, all the others just have<br>
their Alt text displayed. (This chapter did not display any errors<br>
during publishing).<br>
<br>
As a final note, all the images were displayed properly in the pdf<br>
version of the published manual.<br>
<br>
Cheers,<br>
<font color="#888888"><br>
John<br>
</font><div><div></div><div class="h5"><br>
On Wed, 2010-06-23 at 10:15 +0200, adam wrote:<br>
> publish it i rekin!<br>
><br>
> congrats Chris :))<br>
><br>
><br>
> adam<br>
><br>
><br>
><br>
> On Wed, 2010-06-23 at 18:11 +1200, John Curwood wrote:<br>
> > Hi Chris,<br>
> ><br>
> > If you want to see to some of the suggestions that Edward written then<br>
> > let me know once you have finished and I will publish FSlint for you. If<br>
> > you think the manual is ready for publishing with out the additions then<br>
> > let me know and I'll publish it now. Remember You can always publish<br>
> > what you have now and keep making modifications in the write section and<br>
> > republish once those are finished.<br>
> ><br>
> > Cheers,<br>
> ><br>
> > John<br>
> ><br>
> > On Tue, 2010-06-22 at 22:29 -0400, Edward Cherlin wrote:<br>
> > > Sounds quite promising.<br>
> > ><br>
> > > On installation: I hope that we can separate installation into package<br>
> > > installation (apt or yum) and configuration. Within the configuration<br>
> > > section, will it be the same on all Linux distros? What are the use<br>
> > > cases? If there aren't too many cases, can you write a procedure for<br>
> > > each, or break the process down into short, common procedures and give<br>
> > > a list for each case? I see FSlint described as a toolkit. Can we<br>
> > > discuss it in terms of individual tools?<br>
> > ><br>
> > > Do you have a glossary? Are there many terms not familiar to the<br>
> > > novice? Are some terms used differently in FSlint than elsewhere? Are<br>
> > > terms defined on first use? If you cut and paste those definitions<br>
> > > into a Glossary draft, I can take a look at it and do an editing pass.<br>
> > ><br>
> > > These questions apply to many other kinds of software.<br>
> > ><br>
> > > On Sun, Jun 20, 2010 at 10:48, Chris Stackpole <<a href="mailto:c.stackpole@gmail.com">c.stackpole@gmail.com</a>> wrote:<br>
> > > > -----BEGIN PGP SIGNED MESSAGE-----<br>
> > > > Hash: SHA1<br>
> > > ><br>
> > > > Thanks for the feedback John and Adam!<br>
> > > ><br>
> > > > I have indeed been working on many of John's points. One of them being<br>
> > > > to have someone who is a fairly inexperienced user to read through it.<br>
> > > > This has been extremely helpful in flushing it out a bit more. We have<br>
> > > > finished the first couple of chapters together and with any luck we will<br>
> > > > finish the rest either today or tomorrow.<br>
> > > ><br>
> > > > The reason why I was hesitant on adding a install section is that<br>
> > > > because it changes as more distros pick it up and add it to their<br>
> > > > repo's. The homepage of FSlint keeps an up-to-date how-to on<br>
> > > > installation for many different distros. What I did was I added a<br>
> > > > paragraph about this in the intro with a link to the homepage where the<br>
> > > > reader could find the different methods. I am more then willing to<br>
> > > > listen to advice and will create a short install section if that is<br>
> > > > preferred.<br>
> > > ><br>
> > > > It is good advice to contact the developer. I will also send them an<br>
> > > > email later today. They could provide some really good feedback as well.<br>
> > > ><br>
> > > > Thank you for the help!<br>
> > > ><br>
> > > > Chris Stackpole<br>
> > > ><br>
> > > ><br>
> > > ><br>
> > > > adam wrote:<br>
> > > >> i took a quick look also at the manual. i didnt know about fslint and so<br>
> > > >> many thanks for the very good intro to the software (which just goes to<br>
> > > >> show that having a manual in itself is important for promoting a<br>
> > > >> software - the first step to getting a software used)<br>
> > > >><br>
> > > >> I think Johns recommendations were good ones and I see you have taken up<br>
> > > >> some of those. A section on installing, even just to say "its too much<br>
> > > >> to cover here" would be useful as well as a complete list of what<br>
> > > >> versions of Linux it runs on<br>
> > > >><br>
> > > >> but other than that it looks good...i will read through the manual more<br>
> > > >> thoroughly while i learn about the software :)<br>
> > > >><br>
> > > >> (if the developers of the project dont know you have done this you could<br>
> > > >> write to them and see if they would link to it from their project page<br>
> > > >> and/or check the content)<br>
> > > >><br>
> > > >> :)<br>
> > > >><br>
> > > >> adam<br>
> > > >><br>
> > > >><br>
> > > >> On Fri, 2010-06-18 at 06:57 +1200, John Curwood wrote:<br>
> > > >>> Hi Chris,<br>
> > > >>><br>
> > > >>> Sorry for the delay in replying, the manual is shaping up very nicely,<br>
> > > >>> you are doing a great job for your first documentation effort. I had<br>
> > > >>> not herd of FSlint before you asked to create a manual for it, but I<br>
> > > >>> think I will have to get a copy.<br>
> > > >>><br>
> > > >>> In terms of pointers here are a few Ideas I have:<br>
> > > >>><br>
> > > >>> When it comes to writing style, you need a clear idea of the intended<br>
> > > >>> audience for your manual (are they complete novices or are they<br>
> > > >>> technically adept and just need a few pointers). It sounds like you are<br>
> > > >>> leaning more towards the novice end of the scale so to help get a feel<br>
> > > >>> for how it would read get someone you know who falls into that category<br>
> > > >>> to read the manual and see how much they understand or get out of it and<br>
> > > >>> make a note of their comments for helping to target that audience.<br>
> > > >>><br>
> > > >>> They way I would set up each chapter is at the start give a small talk<br>
> > > >>> about the tool covered in that chapter and why you would use it before<br>
> > > >>> going into the graphical Interface and command line sections.<br>
> > > >>><br>
> > > >>> For examples of entries in the command line I would use the 'Formatted'<br>
> > > >>> style in the editor to separate it from the standard text.<br>
> > > >>><br>
> > > >>> I would probably include a chapter on downloading and installing on<br>
> > > >>> different systems (e.g. debian, ubuntu, fetora, etc), especially if the<br>
> > > >>> manual is aimed towards the novice user.<br>
> > > >>><br>
> > > >>> And Finally if you click on the 'Arange Manual Index' link on the FSlint<br>
> > > >>> web home page, you can split the manual up into sections using the 'Add<br>
> > > >>> Section' button. My personal taste would be to split the manual into 3<br>
> > > >>> sections:<br>
> > > >>> 1- Introduction. This would include the introduction chapter, the<br>
> > > >>> Installation chapter (if you decide to add one) and maybe the common<br>
> > > >>> interface items chapter.<br>
> > > >>> 2- Using FSlint. This would include everything from the Duplicates<br>
> > > >>> Chapter down to the Redundant White Spaces Chapter.<br>
> > > >>> 3- Appendix. This would include Other Command Line Tools and the<br>
> > > >>> Credits Chapter.<br>
> > > >>><br>
> > > >>> At the end of the day, most of these comments are more personal<br>
> > > >>> taste/style rather than actual criticisms so feel free to use them or<br>
> > > >>> not. :-)<br>
> > > >>><br>
> > > >>> Keep up the Great Work!<br>
> > > >>><br>
> > > >>> cheers,<br>
> > > >>><br>
> > > >>> John<br>
> > > >>><br>
> > > >>> On Mon, 2010-06-14 at 18:22 -0500, Chris Stackpole wrote:<br>
> > > >><br>
> > > >> Good afternoon,<br>
> > > >><br>
> > > >> I am working on my first FLOSS manual and while it is not yet ready to<br>
> > > >> be released I am at the point where I would like some feedback. I do not<br>
> > > >> consider myself a writer, however, I was inspired to give writing a<br>
> > > >> manual a try after the demonstrations at the Texas Linux Fest.<br>
> > > >><br>
> > > >> FSlint is not a large program and I am not connected to the developers.<br>
> > > >> I just use this software a lot and figured I would try my first manual<br>
> > > >> on something I knew rather well.<br>
> > > >><br>
> > > >> There is one thing that is bothering me about what I have posted so far.<br>
> > > >> I tend to want specific instructions and precise details. So that is<br>
> > > >> what I wrote. I wrote what I would like to see reading about this<br>
> > > >> software and I posted screenshots that I thought were useful and<br>
> > > >> relevant. However, I think I may be too concise in my wording and may<br>
> > > >> have over done the screenshots. There are a few chapters that are a tad<br>
> > > >> short.<br>
> > > >><br>
> > > >> I would really appreciate any feedback anyone may have for me. I am<br>
> > > >> fully aware I have a ways to go and I would love a few pointers in the<br>
> > > >> right direction. I do not mind criticism as long as I also know why and<br>
> > > >> what I may do to improve the situation.<br>
> > > >><br>
> > > >> Thanks everyone. I appreciate your time and help!<br>
> > > >><br>
> > > >> Chris Stackpole<br>
> > > >><br>
> > > >><br>
> > > > _______________________________________________<br>
> > > > Discuss mailing list<br>
> > > > <a href="mailto:Discuss@lists.flossmanuals.net">Discuss@lists.flossmanuals.net</a><br>
> > > > <a href="http://lists.flossmanuals.net/listinfo.cgi/discuss-flossmanuals.net" target="_blank">http://lists.flossmanuals.net/listinfo.cgi/discuss-flossmanuals.net</a><br>
> > > >>>><br>
> > > >>><br>
> > > >>> _______________________________________________<br>
> > > >>> Discuss mailing list<br>
> > > >>> <a href="mailto:Discuss@lists.flossmanuals.net">Discuss@lists.flossmanuals.net</a><br>
> > > >>> <a href="http://lists.flossmanuals.net/listinfo.cgi/discuss-flossmanuals.net" target="_blank">http://lists.flossmanuals.net/listinfo.cgi/discuss-flossmanuals.net</a><br>
> > > ><br>
> > > >> _______________________________________________<br>
> > > >> Discuss mailing list<br>
> > > >> <a href="mailto:Discuss@lists.flossmanuals.net">Discuss@lists.flossmanuals.net</a><br>
> > > >> <a href="http://lists.flossmanuals.net/listinfo.cgi/discuss-flossmanuals.net" target="_blank">http://lists.flossmanuals.net/listinfo.cgi/discuss-flossmanuals.net</a><br>
> > > ><br>
> > > ><br>
> > > > -----BEGIN PGP SIGNATURE-----<br>
> > > > Version: GnuPG v1.4.9 (GNU/Linux)<br>
> > > > Comment: Using GnuPG with Mozilla - <a href="http://enigmail.mozdev.org" target="_blank">http://enigmail.mozdev.org</a><br>
> > > ><br>
> > > > iEYEARECAAYFAkweKkcACgkQA8QwXn4S0qS/lwCgnTSS7FjSdnSf06R6MwmNKGTp<br>
> > > > CicAnA84E+u7UMx49osGH0P2/qHHCxVt<br>
> > > > =MI5q<br>
> > > > -----END PGP SIGNATURE-----<br>
> > > > _______________________________________________<br>
> > > > Discuss mailing list<br>
> > > > <a href="mailto:Discuss@lists.flossmanuals.net">Discuss@lists.flossmanuals.net</a><br>
> > > > <a href="http://lists.flossmanuals.net/listinfo.cgi/discuss-flossmanuals.net" target="_blank">http://lists.flossmanuals.net/listinfo.cgi/discuss-flossmanuals.net</a><br>
> > > ><br>
> > ><br>
> > ><br>
> > ><br>
> ><br>
> ><br>
> > _______________________________________________<br>
> > Discuss mailing list<br>
> > <a href="mailto:Discuss@lists.flossmanuals.net">Discuss@lists.flossmanuals.net</a><br>
> > <a href="http://lists.flossmanuals.net/listinfo.cgi/discuss-flossmanuals.net" target="_blank">http://lists.flossmanuals.net/listinfo.cgi/discuss-flossmanuals.net</a><br>
><br>
><br>
> _______________________________________________<br>
> Discuss mailing list<br>
> <a href="mailto:Discuss@lists.flossmanuals.net">Discuss@lists.flossmanuals.net</a><br>
> <a href="http://lists.flossmanuals.net/listinfo.cgi/discuss-flossmanuals.net" target="_blank">http://lists.flossmanuals.net/listinfo.cgi/discuss-flossmanuals.net</a><br>
><br>
<br>
<br>
_______________________________________________<br>
Discuss mailing list<br>
<a href="mailto:Discuss@lists.flossmanuals.net">Discuss@lists.flossmanuals.net</a><br>
<a href="http://lists.flossmanuals.net/listinfo.cgi/discuss-flossmanuals.net" target="_blank">http://lists.flossmanuals.net/listinfo.cgi/discuss-flossmanuals.net</a><br>
</div></div></blockquote></div><br>