One of the keys for your employer is probably how closely the project is intertwined with your organization’s day to day activities. If it’s a system that provides value to your organization, then it’s much easier to justify the time spent maintaining it and working with outside groups. The danger can sometimes be if the system is working well in production then it can be hard to justify putting more resources into it. I have been trying to finish a java port of our WIBS booking system for months, but it’s soooo difficult to spend time on it when it basically does what we need it to do, and we have so many other systems that don’t (-: If it’s a system that isn’t used actively in-house, and I ran into this with my work on pytheas, you may find it hard to generate much enthusiasm for making it an OSS project. The trick here is probably to see if you can work it into something you need at your workplace, and then you can argue that it benefits everyone to proceed in an OSS direction.
One area where I find gaps with the Cathedral and the Bazaar is that it really describes a sizable development community, Dan has pointed out that cathedrals and bazaars are usually created in urban spaces, and we don’t really have a huge application development community in the library world yet. I almost like the analogy of barn building for libraries better, we are second to none when it comes to co-operating but it seems to help to have some pre-defined building blocks to put it all together.
The good news is that the folks at SourceForge are absolutely amazing. If you want a place to put your project with a good support structure, SourceForge is very accommodating. Let us know what happens.