linux documentation project (ldp) faq rahul sundaram rahulsundaram yahoo dot co 2004-05-31 revision 1.4 revised by: rs added faq's minor modifications emma jane hogbin updated creative commons attribution-sharealike 2.0 license per tm. 1.3 2003-11-15 em editorial update 1.2 2003-11-09 tm corrections 1.1 2003-11-07 1.0 2003-02-24 initial release, reviewed ldp introductory users across introduction it. legal q: ldp? guide? howto? page? faq? documents? documents licensed? topics related linux? contributes contribute? format documentation? docbook lyx user me. it? submit document accepted collection? hasn't answered here? a: loosely knit volunteers aspects linux. forms documentation: guides, howtos, pages, faqs. typically longer broader coverage subject; instance, network administration guide. intent understand subject, opposed performing task. aspect linux, guides handy. howto usually step-by-step describe, detail, perform specific example, installation install system, not web server focus (manual) standard available applications utilities. pages using command. gnu utilities detailed help, called info pages. (frequently asked questions) questions mailing lists. used avoid answering repetitive users. answers like, "what linux?" "how pronounced?" distributions documents, already you've installed latest versions site, . license, license. means allowed distribute, modify, copyright licensing terms. yes. applications, languages, operating systems covered ldp. accepts linux+windows explains, coexist windows. relate directly accepted. application developers, files programs, increasingly, issues others community. authors providing ensures everyone benefited documents. benefits contribute ldp: hosts formats, including text, html, pdf, platform-independent manner. and, hence, community comments, suggestions, additional content reliable whenever necessary. crucial solved own. contribution source depends its growth. publish own, monetary process. topic well, , documentation. something available, contact author e-mail, probably within document, coordinate together. maintained. entirely one, subscribe discussion discuss@en.tldp.org propose peers first, feedback. feedback draft, instructions guide, /ldp/ldp-author-guide advise followed steps listed avoids having someone later acceptable (which rarely case). coordinator site expert help. steps, ensured following benefits: interested contributing, up. aware of; e-mail work. guidance tools, resources writing. because informal organisation volunteers, membership contribute. encouraged whatever can. like! maintained xml linuxdoc converted volunteer. editing suite (like openoffice.org) you. scripts convert ascii docbook. it's this, here's answer... hundreds collection. into human-readable formats (html, postscript pdf). time, collection visually similar, requested readers (read http://ask.slashdot.org/article.pl?sid=04/03/30/0041253 information. descriptive markup specifically desgined technical active development, output variety html slide shows, pdf printed materials. hearing tools converting text ideas "discuss" list. /help/xml/lyx2db/t1.html convenience, summarized according reviewer reviews: technical, meta-data. reviews howto. faq, ( ) subscribing information /mailinfo.html included here, received document. author's address page.