In 2007 I wrote a javascript charting package named chartWidget. I intended to pursue business oportunities with it, that didn’t work out (another post).
Take a look at the site. You can view the javascript source, but it is obfuscated, I modified the YUI Compressor to munge global variables somewhat safely.
Anyway, I think I wrote some pretty cool code. I’m not currently doing anything with it, and many friends have recommended that I open source it. So I am thinking about it
I have questions
1. Which license to choose? I’m leaning towards GPL, because it is still a bit hard to let go.  Which license puts me in the best position should someone want to use it (for me to possibly receive consulting fees)?
2.Should I include my whole subversion repository, about 700 revisions, I’m worried to do this, because it quite likely includes passwords ( I know bad practice)? On the plus side including the whole repository could show thought patterns, to help other people debug the code
3.Will anyone care? I guess I can find out by doing it.
4. My code is idiomatic to say the least, in some places wrong, and in many more places just hard to understand. How much will this matter for me, if someone looks at the code will they consider me an idiot?
5.What questions am I not asking that I should be?
Yes to opening up the repository! Given how important version control is for most developers, I think the repository is essential when opening up a codebase. I have some homebrew tools to help me browse repositories and find the best version to start reading code in, the one with a lot less complexity, but the basic functionality in place. When I can browse history I am more likely to work on a codebase.
I understand about passwords, but I can help you understand how much of a problem they are if you like.