Pay 4 FOSS
feeling guilty ? [Free Open Source Software]
THEN PAY ! (No purchase necessary)

Manuals

Documentation
This is the big one, a major hole in the FOSS world.
Even if projects have manuals/man files they are often out of date as it takes time and dedication to maintain them.
Manuals need to have (commonly) at least ;

  • Intro: What is the project/file, commonly also found in the README file.
  • Usage: command switches, etc
  • How to compile , dependencies commonly in the INSTALL file
  • Detailed usage instructions and preferably examples, coding info(how plug ins work), etc
I would like to know what the command line switches are.

What does config files does this use ?

How can I help ?
Availability in other languages(localisation) is good start.

Finally
The axiom "something is better than nothing" fits well here, if you research an issue and resolve it and it is not a bug nor an ideal candidate for a howto or tutorial or faq then it maybe suited for manual/man pages inclusion. "Build your forts defences with knowledge and watch it stand"

All the pages here at pay4foss.org are released into the public domain, meaning simply there is no restrictions on their use or miss-use.
Any links leading to pages external of the pay4foss.org server are provided in good faith but can not be garentied to lead to where you expect them to.
If you have any questions please review the FAQ before trying to contact me.

web hosting is provided by 1and1.co.uk