 |
 |
Hi David, We develop software that is released under open source policies but do not have an overarching policy. We joined the Hydra community about 18mos. ago and have been using their licensing practices ever since. You can read more about Hydra's licensing and IP practices here: https://wiki.duraspace.org/display/hydra/Hydra+Project+Intellectual+Property+Licensing+and+Ownership We ran this by our CIO & Vice Provost for IT, who gave us the OK to proceed. -Mike On Tue, May 28, 2013 at 12:39 PM, David Lowe <[log in to unmask]>wrote: > 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 >