On 11-09-09 03:07 AM, Andy Grover wrote:
Hi Jerome and Nick, I happened upon this website: http://www.theopensourceway.org/book/The_Open_Source_Way-How_to_tell_if_a_FLOSS_project_is_doomed_to_FAIL.html
I totted up 70 each for my open source packages so I reckon that list should be taken with a large grain of salt. This one amused me: "Your code tries to install into /opt or /usr/local [ +10 points of FAIL ]" Installing into /usr/local is the default for autotools.
According to my calculations (available upon request), rtsadmin comes in at 220 points: "so much fail, your code should have its own reality TV show". I could also add some more like "primary developer never responds to email", "CLA discourages external contributions", and "uses executable name as corporate marketing tool". Admittedly rtsadmin is a nice piece of code, thanks btw, but your company is falling short of accepted standards for stewardship of a FLOSS project. Please tell me why we all wouldn't be better off if I forked rtsadmin tomorrow.
One reason from the above link: "Your code is a fork of another project [ +10 points of FAIL ]" :-) Doug Gilbert -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
