 |
 |
All- If you work at an organization that releases open source software that your staff coders develop, I would be interested in reading your policy on that, if you have one written up that you can share, or otherwise in hearing your common practice, if that's not too much trouble. On or off list as your preference would have it. I've located the following so far: UCSD https://confluence.crbs.ucsd.edu/display/CRBS/Releasing+Open+Source+Software+at+UCSD Stanford http://otl.stanford.edu/inventors/resources/inventors_opensource.html Texas http://www.utexas.edu/cio/policies/pdfs/Procedure%20for%20Releasing%20Software%20as%20Open%20Source%20or%20Contributing%20Software%20to%20Existing%20Projects%20Licensed%20Under%20the%20GNU%20General%20Public%20License.pdf Austrailian Computer Society http://people.oregonstate.edu/~alhasheh/ose/sources/OpenSourcePolicy.pdf Much obliged, --DBL