Randy McMurchy wrote: > You say this, but don't have to do any of the work. Perhaps you don't > realize how difficult it is to put together text *for a book*. Text > that needs to be accurate, well-reading, concise, grammatically > correct and to the point.
I do realize that it's difficult. I readily admit that in the LFS world, you do more of that work than I do, but I have done several textual edits on LFS and Cross-LFS. Also, I have had to do much of the text on the website. Lastly, I have done a great deal of writing and public speaking in arenas outside of LFS, for many, many years. I know it can be a challenge to write in the manner you described. > Much different than blabbering in a mail list. The text needs to be > professional. Which mean professionally summarizing all this you > mentioned. Yes, of course. But what is the main purpose of BLFS? Is it not to educate? If so, the *whys* are just as, if not more, important than the *hows*. > This is hard work. What do you expect us to do, put a bunch of URLs > in the book leading to threads in the mail lists? I cannot see this. No. What you said above. Well summarized texts. They can be based on threads to the lists however. For a well summarized and finished piece of text, you could always cast it out to the list and ask for opinions/suggestions before you commit. In most cases, waiting a day or two for a piece of summary text to drop into the already finished technical page of the book won't hurt anything. -- JH -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
