Glorp Relicensing
Alan Knight is looking into relicensing Glorp:
At this point, it seems to me that it's desirable to go further than that, and actively relicense Glorp under a more open license. I don't think the threat of someone taking the code base and making something proprietary from it is as significant as the impediment to usage that being under the LGPL causes. So to that end, I'm going to be going through old records and trying to get in contact with previous contributors to do a relicensing under another license. I'm thinking MIT, or something in that vein.
Suggestions on licenses, process involved in doing this, arguments, or other commentary are welcomed.
