Making Your Code OSS-Appealing?
goldcd writes "A while back I wrote some pretty reasonable forum code, a PHPBB alternative. A few years down the line it's pretty stable, I've stopped tinkering with it, and it's standing up by itself. I have neither the time, inclination, nor inspiration to do anything more with it, but would very much like to give the code to the world to use and expand upon. Now I could just upload it as it is onto SourceForge, but currently it's very specific in its usage and I'd be ashamed of what 'proper' coders would think of my amateur offering — I'm afraid it would be laughed at and ignored. On the other hand, I don't want to waste hours of my own time perfecting it for people just to 'rip off' as is, and never contribute anything. My question is, what do you have to do to make your code 'OSS appealing?'"
I released my first OSS project as a horrifically badly organised mess of dissertation code. I got feedback from some domain specialists and better coders, and the codebase got better.
Now its a mature project with a very specialised user base, but its provided me with more fun then I ever imagined.
Code is never finished though.
Incidentally, I'd have replied to the main article, but for me there was no reply button, don't know why.
The reply button is on that annoying little floating widget to the left (or above comments, if you press the button with the arrow point up).
Not the best visibility, though, admittedly.
I dont read