Slashdot Mirror

← Back to Stories (view on slashdot.org)

Writing Open Source Documentation?

Posted by Cliff on from the open-source-needs-more dept.

An anonymous reader asks: "I'm an Open Source guy that runs Linux, and suggests Firefox and OpenOffice to friends. Now, I'd like to give back, but the problem is that I'm not a coder. So, how do I go about writing documentation, and what kind of projects should I look into? What are some stellar examples?"

5 of 92 comments (clear)

  1. RTFM on writing documentation by Timesprout · · Score: 4, Funny

    Oh wait....

    --
    Do not try to read the dupe, thats impossible. Instead, only try to realize the truth
    What truth?
    There is no dupe
    1. Re:RTFM on writing documentation by Anonymous Coward · · Score: 3, Funny

      shouldn't it be W(rite)TFM? WTFM, dude.

    2. Re:RTFM on writing documentation by laejoh · · Score: 4, Funny

      You sig inspires me!

      Do not try to read the documentation--thats impossible. Instead, only try to realize the truth

      What truth?

      There is no documentation


      Sad actually...

  2. 3 cheers for this guy by simm1701 · · Score: 5, Funny

    Just remember:

    Documentation is like sex, when its good, its very very good, and when its bad its better than nothing.

    --
    $_="Slashdotter";$syn="OTT";s;..;;;sub _{print shift||$_};s!ash!Perl !;s=$syn=ack=i;tr+LLEd+BLAH+;_"Just Another ";_
    1. Re:3 cheers for this guy by Wordplay · · Score: 3, Funny

      Ah, that explains why I'm the only one who ever reads my documentation.