[clug] How you know your Free or Open Source Software Project is doomed to FAIL

Scott Ferguson scott.ferguson.clug at gmail.com
Tue Jul 28 15:55:30 UTC 2015


A list of indicators that may interest some list readers:-

http://spot.livejournal.com/308370.html?nojs=1


Some excerpts:-

== Building From Source ==
* There is no documentation on how to build from source [ +20 points of
FAIL ]
* If documentation exists on how to build from source, but it doesn't
work [ +10 points of FAIL ]
* Your source isn't configurable [ +50 points of FAIL ]
* Your source only builds with third-party proprietary build tools [ +50
points of FAIL ]
* You've written your own build tool for this code [ +100 points of FAIL ]

=== Code Oddities ===
* Your code depends on Microsoft Visual Anything [ +100 points of FAIL ]

== Documentation ==
* Your code doesn't have a changelog [+10 points of FAIL]
* Your code doesn't have any documentation [ +20 points of FAIL ]
* Your website doesn't have any documentation [ +30 points of FAIL ]

=== FAIL METER ===
0 points of FAIL: Perfect! All signs point to success!
5-25 points of FAIL: You're probably doing okay, but you could be better.
30-60 points of FAIL: Babies cry when your code is downloaded
65-90 points of FAIL: Kittens die when your code is downloaded
95-130 points of FAIL: HONK HONK. THE FAILBOAT HAS ARRIVED!
135+ points of FAIL: So much fail, your code should have its own reality
TV show.



Kind regards



More information about the linux mailing list