Around three years ago we spent quite a bit of time coming up with a new license for our open source software and got it approved by OSI, the Open Source Initiative. I was involved, and it wasn't easy. Unfortunately, we've become disenchanted with it. The closer I read it, the less I understand it, and most people that want to use our software come up with some questions, most of which are hard to answer.
So what should we do? From Research's perspective, we would like as wide use of our software as possible. The cooperative, however, might like to get more back than just recognition, such as fees for commercial use, and it would certainly be nice if we had access to modifications people make to our code. I don't really believe, however, that the GNU GPL would solve our problems, being fairly well persuaded by Eric Raymond's arguments that it actually inhibits the use of open source software.
I've looked at the MIT license, which is very close to the BSD license. They are certainly short and sweet! The Apache license is longer, but seems to accomplish much the same thing (you can do anything with the software, but include this notice with it).
Are there other directions we should be considering? How should a not-for-profit research organization license its code?