 |
 |
Hi David, > 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, I did a presentation on that general topic at Code4lib 2007: The Intellectual Property Disclosure Process: Releasing Open Source Software in Academia http://code4lib.org/2007/doran ...and have some additional info on this page: http://rocky.uta.edu/doran/ip/ -- Michael # Michael Doran, Systems Librarian # University of Texas at Arlington # 817-272-5326 office # 817-688-1926 mobile # [log in to unmask] # http://rocky.uta.edu/doran/ > -----Original Message----- > From: Code for Libraries [mailto:[log in to unmask]] On Behalf Of > David Lowe > Sent: Tuesday, May 28, 2013 11:40 AM > To: [log in to unmask] > Subject: [CODE4LIB] Open Source release policies > > 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+Soft > ware+at+UCSD > > Stanford > http://otl.stanford.edu/inventors/resources/inventors_opensource.html > > Texas > http://www.utexas.edu/cio/policies/pdfs/Procedure%20for%20Releasing%20So > ftware%20as%20Open%20Source%20or%20Contributing%20Software%20to%20Existi > ng%20Projects%20Licensed%20Under%20the%20GNU%20General%20Public%20Licens > e.pdf > > Austrailian Computer Society > http://people.oregonstate.edu/~alhasheh/ose/sources/OpenSourcePolicy.pdf > > Much obliged, > --DBL