Day 22 – Release some software under an open source license that you haven’t released before.
While I love lots of open source software packages, and support the licensing model, I am going to have to take a mulligan here.
(I work with software all day, and am blogging in the evenings, so I do not have the time at the moment to do more work. I am doing this set of blogs for fun after all, not just to take up time.)
Does this sounds like an excuse? Yes, it is. But it is my blog so I can do what I want 🙂
Andy Dingfelder 
Do open source for work not for fun or during spare time. Unless they’re backed by a large community or highly committed individuals, open source projects go nowhere.
But that’s not the point. Producing open source code is good for business and a long-term safety net.
The software that you produce in the open is likely to be better tested, documented and modular than stuff you produce in-house and that no one knows about. When you move on, who’s gonna know about that critical (to the software, not to the business) piece of code that’s getting dusted on your company’s SVN repo?
If instead, a single module is opensourced on GitHub, first you may find someone else that may be interested and may help fixing bugs and evolving it. Then, when the author moves on, she can keep maintaining it in the future, because she’s the best qualified person to do it.
Examples that we’ve started and/or contributed to on GitHub:
Construct: a java library for encoding and decoding binary protocols
Siena: a persistence layer for SQL and NoSQL databases
Vosao: a CMS for Google App Engine
And also, smaller projects like UI components:
Google Earth for OpenLayers
A timeline for OpenLayers
An Ajax progress bar
https://github.com/Sirtrack
https://github.com/ZiglioNZ