1. The license you choose probably won't make anyone more inclined to hire you for consulting. You're better off trying to decide how open you want code and co

1. The license you choose probably won't make anyone more inclined to hire you for consulting. You're better off trying to decide how open you want code and contributions to remain. 2. While a revision history is nice to have available, odds are most people aren't going to really look back at older versions of the code. Some code cleanup and documentation would be preferable (but does require your setting aside time to do that). 3. You'll never know until you do. And it doesn't cost you anything to do it. (With some exceptions... see #5) 4. You're not claiming its perfect so don't stress too much about it. Part of what open source is about is allowing someone to see what makes everything tick, warts and all. Because someone could always contribute back fixes. 5. Have you thought about where you're going to make your code available (Sourceforge, GitHub, etc.)? Is there going to be a Google Group or something so people can ask questions or share their experiences with the code? Even if you're not expecting a massive wave of adoption, having some of that in place can make everything better (both for people interested in your code and yourself).