Slashdot Mirror
The LDP Responds to Suggestions
Thanks a lot to Slashdot readers for the comments they submitted.
Our announcement may have seemed "empty" but you provided us with lots of good feedback regarding the LDP in general, and that will help us in improving our quality.
While reading the comments, I took a paper and wrote down the different problems people had.
Some will not be solved immediately, some are now solved, others are outside our scope while others can be solved if we get more people to help in the effort.
- web site design : FIXED
Each of your comments were precious to help us improve its appearance and ease of use. Please try out the new version.
- provide direct access to important links : FIXED
We now have big links for each of the major document types (HOWTOs, FAQs...) on the first page. Please check "non-English" where you should find a link to your local LDP with translated documents.
- provide security bulletins & link to RFC archives
I'm sorry, but this is not within the current goals of the LDP. However, we will add links to other sites with this information in our "Links" section.
- provide DocBook and PDF documents : FIXED (Docbook format and ">PDF format are online now
I converted each of the LinuxDoc HOWTOs and mini HOWTOs to DocBook and PDF, uploaded them two days after the Slashdot article ; they are now available on each of the formats as another output, just like the html and ps versions.
- move to DocBook because LinuxDoc sucks - stick to LinuxDoc because DocBook sucks
The HOWTOs are now provided in both LinuxDoc and DocBook; however for the moment we can only accept LinuxDoc source for the HOWTOs.
In the next weeks both DocBook and LinuxDoc SGML source will be accepted for the HOWTOs. We are currently testing DocBook output formats.
You can already submit your DocBook only document which will be put in the DOCBOOK section. (a new major section, like FAQs and HOWTOs)
- "tables don't scale to window size and resolution and 10 pt font size is hardcoded
Our Webmasters are working on these problems.
- How can I submit my work to the LDP? You can read the HOWTO-HOWTO
three possibilities depending on the format:
a. you can write in LinuxDoc : call your document an HOWTO b. you can write in DocBook : call your document a DOCBOOK :-) c. you are a master of TeX/LaTeX, pdf or any specific format : call your document a GUIDE or a FAQ, depending on its contents.
Please use a license compatible with our requirements (GNU Free Documentation License is IMHO the best choice but feel free to take any other license) and mail your document to ldp-submit@lists.linuxdoc.org
If your LinuxDoc or DocBook source contains errors, I'm sorry but we will not process it until the errors are fixed. Please test it first
- You should check the documents : FIXED
We have since November! We would like to be able to have our peer review team proofread each submitted document.
However, there are far too many docs submitted to ldp-submit for our small team to adequately proofread each document. If you would like to help us please subscribe to ldp-submit (mail ldp-submit-request@lists.linuxdoc.org).
- XXXX and YYYY HOWTOs are outdated/unmaintained
Please update the document and submit the new version to the LDP if the license allows modifications. We will be happy to include your new version (News HOWTO and SCSI HOWTO are especially old!).
- I just found ZZZZ HOWTO which is not part of the LDP yet
Then please contact the author and ask him to send his document to ldp-submit@lists.linuxdoc.org Chances are we will include it, unless it contains errors, has a non- free license, or duplicates an existing document.
- license problem, GNU/Linux... FIXED
We have a manifesto and a license guide on the first page. There is an ongoing discussion and both may be revised.
We will not impose any license but rather have some criteria and requirements (free redistribution for ex.)
And if you don't like "LDP", just remember netscape/mozilla : it's written LDP but it reads GNU Linux Documentation Project.
Writing documentation is not as sexy as writing software (To quote a Slashdotter, "Honestly, how many users want to read documentation? How many of them see a fat manual and feel happy?")
We do need more authors. Unfortunately, not everyone can be a good author. It requires a combination of writing skills, technical knowledge, and the willingness to accept criticism that improves your final product. Thank you all for your responses--we hope that you continue to let us know your opinions on the LDP.
i'd like to see an iso image of the ldp, and all it contains, have it be searchable, indexed, and running locally on a live webhost, etc.
I don't know about the other distros, but SuSE has at least a good portion of the LDP included, and if you install the whole help system, at least everything in HTML is indexed in a full-text search.
If you install dochost, and... well everything in the doc series, you end up with a pretty decent amount of documentation accessible and searchable from the default Apache start page. I'd be pretty surprised if the other distros don't have something comparable.
Chris
San Francisco values: compassion, tolerance, respect, intelligence
"The relevant results will come up immediately because it will have a very high relevance coefficient. "
:-)
That's not really true, is it. MSDN and technet are pretty good. It's depressing the number of times you search for a problem on the net and find 50 pointers to different archives of the same mailing list, all of which reveal someone with exactly the same problem as you - someone who got no response from the mailing list beyond a couple of 'me too' followups.
More to the point, MSDN/Technet is simply more convenient. There's alot to be said for putting some of that stuff on CD-Rom and giving it a real search engine. Imagine something like all the documentation of every app in a standard Linux distribution on CD-Rom. With a proper search engine. Properly searchable Man pages would be a start, but then add to that the contents of every user-foo and admin-foo and devel-foo mailing list archive for each application. Then add to that all the documentation branches of the applications' respective home pages. Then add all the howto's and the rest.
Then update the CD-set quarterly or bi-monthly. Sounds like a useful thing to me.
If I had to choose MSDN style or Internet style, I'd probably go for Internet - but both together would be much nicer than either on it's own. Sitting around saying "No Linux documentation? Just search the ***ing net man" is actually not too helpful.
So, gratz to the LDP, but if anyone's looking for business plan I'd go for a Linux Technet CD-Rom set. Errr, only I use Solaris at work. But otherwise I would
-----
(apologies if i'm missing something basic and fundamental - it's been a long day)
The only Good System is a Sound System
i'd like to see an iso image of the ldp, and all it contains, have it be searchable, indexed, and running locally on a live webhost, etc.
one completely exellent tool that i've used for years which does this, but for IRIX, is the IRIX developer's toolbox. there's an online mechanism, and a mirror which you can get cds of, and use offline. excellent tool for IRIX devrs (and lots of code for stuff like opengl too). check out:
http://toolbox.sgi.com
i'm curious if other slashdotters who work offline would find a tool like this (say ldp on a cd) useful.
Nah, those are howtos for slow people...
When I run RedHat 6.1, I truly and honestly don't give a rats ass about how things are done with Linux Kernel 1.7.009 or Debian/Suse/Slackware or whatnot. I don't know how many times I've gone through a document only to find that nothing (or little) within it applies to my problem.
The ultimate functionality enhancer for Linux documentation, would be an interface where you specify whatever hardware/software setup that applies to you, and then get documentation specifically for that purpose.
However, this may be a point more suited for attention from the distributors. RedHat indiscriminatorily doles out a ton of HowTo's that for a large part do little but waste its customer's time, and if someone starts doing this better, I'll switch in a New York minute. The product from the distros should be facilitation of setup and maintenance, not randomly collected material of little relevance...
Oh, and by the way, adding a "Troubleshooting"-section to the howto's would be a blessing for newbies...
It would be nice if LDP followed something similar to Slashdot or Freshmeat whereupon people could comment or ask questions if they run into trouble. The authors can't update the docs all the time. If we could communicate the trials and tribulations while working with a package, it could provide valuable feedback to the document writer and the developers.
Also if you have a chapter to contribute or propose, post it and wait for it to be integrated or ignored.
Putting up a two-year-old dead document may not be very useful, nor are you going to have experts on the topic critiquing the work. On the other hand, if somebody posts, "Hey, the feature described in section 3.2 has been changed!", or "see CERT advisory 2000-09-12.3!" it is better that it be found in a dedicated forum than through hours of probing on IRC or searching through Usenet.
I thought I posted this idea to the original suggestions...
sgml2latex --output=tex index.sgml
sed -e '/\\usepackage{t1enc}/d' \
-e '/\\usepackage{babel}/d' \
-e '/\\usepackage[latin1]/d' \
-e 's/\\usepackage{null}/\\usepackage{null}\\usepack
index.tex > index2.tex
mv index2.tex index.tex
pdflatex index.tex
This seems to generate good PDF files ( at least with my HOWTO, it does )
Writing documentation is not as sexy as writing software (To quote a Slashdotter, "Honestly, how many users want to read documentation? How many of them see a fat manual and feel happy?")
Hmmph. Software that is crap because of lack of adequate documentation is not very sexy at all. Said users, if they want to use sexy software, better learn to see the beauty of good documentation. It's not first and foremost for the users (*learn to program first!*), it's for the hackers that make Linux the sexy system it is today. Of course, it sure doesn't hurt users to be able to find out how there systems work when they want to, in as much detail as they want to.
I thank everyone involved in LCP profusely, but I'm not getting involved - I'll respectfully keep hacking on my own project, and I promise to write proper draft documentation for it when it's done.
Life's a bitch but somebody's gotta do it.
Remember that those O'Reilly books have considerable structure in common; they are all of similar form factors, which means that you can readily drop them onto a single shelf and expect them to fit nicely. If they had varying shapes, sizes, and bindings, this wouldn't work out nearly so well, as they'd need to (for instance) come up with a customized kind of book binding for each book.
If your docs are written using LaTeX, they have no way of automatically integrating it into a single comprehensive document.
If your docs are written using whichever DTD they favor today, it is a relatively straightforward task to integrate this together.
Thus, there are actually two classes of documents:
If you're not part of the solution, you're part of the precipitate.
What the hell is a "desaster" ? Anyway, writing in LinuxDoc isn't very hard. Anyone who's written in HTML before can pick it up in minutes. ( "writing in SGML" doesn't make much sense. One writes to an SGML DTD like LinuxDoc, HTML, or Docbook ) For those who can't handle the simple task of learning a simple DTD, there's Lyx ( it'd be good if they'd point to Lyx as an authoring tool )
I am curious as to what format you'd propose over LinuxDoc or Docbook. The requirements are that it should be convertable into several formats, and it should have some logical structure ( so that you can convert it ).
You will not attract a huge bunch of professional technical writers if you don't lower the bar.
I don't like the idea of making the bar too low. I wouldn't want someone who is unwilling to spend a few minutes reading the HOWTO-HOWTO as a HOWTO maintainer ( you know, HOWTOs are not write-only )
The front page should have three or four words of explanation for the different doc types, e.g.:
Guides - longer, more in depth books
HOWTOS - subject-specific help
FAQs - Frequently Asked Questions
man pages - Help on individual commands
Linux Gazette - on-line magazine
Gerv
Wrong, buddy. Upgrading glibc is plain difficult, because it requires upgrading everything that links to it which is basically every dynamically linked program on your system. The only sensible way to "upgrade" is leave your old libc there and run a hybrid install, but this is difficult, and has a lot of technical difficulties, none of which are Redhat's fault.
If RatHead would make it easy, there would be an RPM to upgrade your libc.
THere is. It's called glibc. The problem is that you also need to upgrade every single application at the same time to a version that is built against the new upgraded glibc.
If you compile all the applications in a distribution in a way that they need the libc at runtime, you would have to recompile every app you use.
Exactly.
and YES, it IS the best way to handle programs, but it's also the best way to force someone to reinstall everything again (read: BUY AGAIN).
Get a grip, buddy. Linux is free ! And CDs are available for next to nothing. Hell, you can probably get someone in your Linux users group to burn you one. My group are always giving out CDs.
SOLUTION: Let the customer who buys a distribution decide whether to trade upgradabiltiy (nice word, hey?) for small apps, with better, overall performance (unless RAM is not an issue and your CPU is fast enough). Let him have the choice to have bigger programs (not dynamically linked) and the chance to upgrade the ESSENTIAL libc. I don't see this happen in my lifetime.
There is little demand for apps statically linked to libc , because most users don't want to load one copy of libc for each process on their system. I have 55 processes running right now. My libc is 4MB. Do the math -- most users don't have this much RAM to burn.
But would you work on producing it? That's what has brought us this far, and judging from commercial efforts, it's the only thing that will take us further.
But, on a more immediate subject, do you know know about the -K (that's a capital) switch for man? See man(1) (type 'man man') for more information. Of course, it won't help much with GNU projects, but...
(Yes, i should quote from man(1) but i want people to actually look at it.)
cheers,
sklein
Well I'll vote for the CD dist. I did have a problem where my modem was not working. Had problems with PNP stuff. Had to shutdown, reboot to m$, go online, read HowTo's, jot down ideas, reboot to linux, try ideas, repeat as nessecary. Now I should mention that part of the problem was I did not realize the install I had done included the howto's with it. I found those eventually and stopped the rebooting part. Which kinda proves the point that I like having local copies of some stuff.
-cpd
I wouldn't mind working on it. Obviously not the whole thing, and I don't think I have the knowledge to really organize anything like that. However I'd be pretty interested in helping if there was an org doing that.
:-)
As for the keyword search your describing, oh yeah, I know of it, I live and swear by and at it sometimes.
BTW, they are not "crying" for authors, and they are not so desperate for authors that they are willing to accomodate to laziness. As much as making it easy is good, you have to understand that HOWTOs don't write themselves, it does actually involve some effort on the part of the author. I'll say it again, the technical skills requirements for writing HOWTOs are minimal. The real work is in writing the content.
And you didn't answer my question -- what format do you propose as an alternative to Linuxdoc ?
oh man.....they should have a Withstanding-The-Slashdot-Effect-HOWTO
Sgt Pepper
Lame Sig Shamelessly Ripped from
Fortune:
I can hire one half of the working class to kill the other half.
-- Jay Gould
They will need a lot of help.
/. readers who have knowledge and experience of related issues to get involed (get their keyboard dirty) and be part of the big picture :)
The Linux Documentation Project will need all the help it can get; this at the moment can only be an uphill struggle. Linux software development is undoubtedly at its most prolific it has ever been so as soon as something is documented; it will have been revised (something that LDP have taken note of)
It seems therefore that the only way to win this is to increase the manpower available and signup to help...
I emplore
Linuxdoc.org has already proved invaluble to me so I will be doing whatever I can.....
Ripping an new rectum in the fabric of spacetime.
Has anyone tried making something like a MSDN library for Linux? This is one of the things that is really nice about programming for Windows (esp. when developing using a pay per minute internet connection). Having everything in one place (including journal articals) makes finding obscure information so much easier.
That categorization is required *because* the LDP is a documentation effort. The results should be usable on web servers, printed material, PDAs, and the Goodyear Blimp if required.
Documents written in HTML will remain in HTML. Documents written in TeX will convert to text and postscript, but not info format (modulo the use of texinfo macros, of course).
LinuxDoc and DocBook can be a real pain, but these formats are designed to be sufficiently abstract that the documents can be converted to any reasonable format. That means it's far more likely that a HOWTO will be maintained for the indefinite future, while a GUIDE may be dropped once the author moves to a new format himself.
For every complex problem there is an answer that is clear, simple, and wrong. -- H L Mencken
Be sure to check out their page, because they have a link to a site where you can vote on which open project will get funding from the proceedes of an LDP-based book.
--
Sheesh, evil *and* a jerk. -- Jade
What you don't see there in Netscape are the character control codes that only work on terminals.
I read the internet for the articles.
We do need more authors.
Then please make it easier for authors to contribute. Setting up the whole SGML tool-chain is a major desaster. Having to write in SGML is a desaster, too.
You will not attract a huge bunch of professional technical writers if you don't lower the bar. "All" you will get are the programmers who are just a little bit tired of coding and who relax by glueing together some documentation.
Second, I have a humble suggestion: the front page of the site should be written with the newbie Linux user in mind. Think in terms of a brand new Linux users who is trying to figure out how to format a floopy disk, transfer files from his Windows drive, or read files from a CDROM. As soon as Joe Newbie hits the front page he should know where to go next. Unfortunately the current page design the most useful links are crammed up in the top left corner of the page, and the prime realestate is being used for the News column on the front page, which is basically the webmasters journal, although interesting, should not be the fropnt page of the site -- save that for the What's New page.
So I would humbly suggest the front page be a Yahoo-like category index of the various kinds of documentation on the site -- put the table of contents on the front page in plain view.
I'd like to point out that those of you that struggled with LinuxDoc, either getting it installed or running, will have fewer problems with DocBook, mostly because it is so well documented. One excellent resource is the DocBook: The Difinitive Guide from ORA, available at your local dead tree store and online at www.docbook.org.
-- Ever notice that fast-burning fuse looks exactly the same as slow-burning fuse? I didn't... (Edgar Montrose)
a. you can write in LinuxDoc : call your document an HOWTO b. you can write in DocBook : call your document a DOCBOOK
Why are the documents being titled according to filetype first, and contents second. That's like Yahoo categorizing sites by whether they use PHP or Perl, and not by what the site is about.
Yes, I realize that they are still considering content, however, the quoted statement indicates that the title category is decided by the file format. "I'm looking for a HOWTO on ???. What? I need the GUIDE instead? There's no HOWTO because the expert doesn't use the right file format?" Good documentation relies on consistency. I thought that was one of the main points for the LDP: you can go there to get all of your questions answered. Companies like O'Reilly have it figured out. All of their "???? in a Nutshell" books are fairly similar in style and content. You can intuit from the title category what type of book it is. You ought to be able to do the same with LDP documents.
I'm sure someone will ask why I don't have any HOWTO's in the LDP.
LetterJ
The Glass is Too Big: My Take on Things