How you know your open source software project is doomed to fail
spot.livejournal.com
spot.livejournal.com
>* The source code is more than 100 MB.
Excluding images, example usage, and generated documentation, sure.
>* Your code tries to install into /opt or /usr/local [ +10 points of FAIL ]
Installing to /usr/local is the accepted default for linux. Plus, I actually use the package manager on my system. I want compiled software to install to /opt or /usr/local so I can find it later and remove it if necessary.
Now trying to install to /opt on windows is just stupid.
>* Your code does not have per-file licensing [ +10 points of FAIL ]
This is pedantic. If the entire codebase is under the same license which is given as LICENSE in the program's folder you're good. (You should make it clear in README that LICENSE does apply to the entire project.) If not, any inconsistent licensing should be explicitly defined either in a visible top level document next to LICENSE which lists each exception clearly (e.g. stuff in multiverse/ is proprietary, see multiverse/<project>/LICENSE for details) or at the top of each file that doesn't match the license in LICENSE.
I think this one bothered me the most. `/usr/local` is the correct default location for user installed software, per the "Filesystem Hierarchy Standard". If the software's static file must be contained in a `./<package>`or `./<provider>` directory (vs bin, lib, share...), it should probably go in `/opt`.
Linus Torvalds wants to have a word with you.
Conversely, Emacs certainly deserve a few fail points for being the sole user of its programming language (Emacs Lisp).
(Bye the way, I love Emacs)
I'd go so far as to say that being able to build and run in a POSIX environment without needing any platform-specific configuration (or autoconfiguration) is worth at least 20 points of WIN.
People are happy to rant and rage, but the value of these large projects persists.
I put the source on Github btw- http://github.com/zackster/hip-hop-goblin
I am not that familiar with GitHub, so I can't give you specific instructions or examples, but the project I'm working on uses Mantis for this, and it works a treat - we integrated it with SVN and now svn commits create new Product Versions, revision commit messages are automatically posted as issue comments + issues get marked as "resolved" if applicable, changelogs for latest changes, roadmaps for future plans, etc.