I have a number of old applications which I'm unlikely to do any further work on but could be quite useful to others (two examples being a sudoku generator/solver and an easy-to-use assembler/graphical-emulator tool for a fictitious CPU).
Does anyone have any ideas on what I should do with them? I've thought of the obvious "starting a sourceforge project" but I suspect that would die pretty quickly if I didn't actively maintain it.
I'm open to any suggestions.
If you think its actually useful, then make a small website or for it or something, make yourself a crappy free website with www.spruz.com or .net I'm not really that sure, if your that attached the the programs. Or if you do want to maintain it make a sourceforge project. But If it's not anything useful I doubt it's gonna really be used.
Put them on Github as public projects and see what the reaction is. You may get more interest on Github rather than on sourceforge because there are fewer projects and I think more people like to browse through the available projects on Github.
A free website (geocities etc) to upload them onto and add a bit of information is probably your best bet.
Find something that doesn't require maintenance and will allow you to just upload the files you want to, put a title and description up (so that search engines will find them) and then will let you forget about them.
Putting them up for free as others suggest is probably the most altruistic thing to do, and does have the benefit of giving you good press... if the application is either mature enough that the chance of a critical bug is low, or if you intend on actually still supporting it if a bug shows up. For this specific case, putting it up for free is probably best, though no, probably not on sourceforge, not Yet Another Unsupported Project.
The most important thing you do with your old applications is learn from them. Do a postmortem, writing down what you did right, what you did wrong, what you'd do differently. Especially important are things that caught you, interestingly difficult bugs, or anything that repeatedly caused trouble. You may never do another piece of similar code, but you might hit the same kind of bug 50 times.