Re: [CODE4LIB] Open Source release policies
We just went through that formal process internally at the University of Florida to get approval for some software that we had actually released the code for already, since it was partly paid for by federal grants. Overall the process wasn't super-streamlined and one felt they needed to be arguing for the lack of commercial viability. (This won't be the next Gatorade.. I promise...) Here are some comments from Laurie Taylor who drove most of the process here at UF: The University of Florida handles all software and licensing, open source and otherwise, through the Office of Technology Licensing. The official process is there for legal compliance, to ensure the correct open source licenses are used as is required when components are already open source and released under viral licenses. The official statements on policy for this aren't super clear from the outside. Our open source software releases state what open source license (https://code.google.com/p/sobekcm/ and http://ufdc.ufl.edu/software/download) but don't link people back to the main policy pages, which are complex. As we do more with data/digital curation and more data and software in our repository (http://ufdc.ufl.edu/), we've started talking with the Office of Technology Licensing (OTL) about doing new trainings and workshops for UF researchers who are releasing their data sets, digital materials, and open source software to parse, visualize, and otherwise interpret the raw materials. We're looking into how to best do combined trainings to fit the OTL concerns and support researchers with the least amount of additional work and confusion over complex policies. Cheers! Mark Sullivan / UF Libraries From: Code for Libraries [CODE4LIB@LISTSERV.ND.EDU] on behalf of Doran, Michael D [do...@uta.edu] Sent: Tuesday, May 28, 2013 3:37 PM To: CODE4LIB@LISTSERV.ND.EDU Subject: Re: [CODE4LIB] Open Source release policies 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 # do...@uta.edu # http://rocky.uta.edu/doran/ -Original Message- From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of David Lowe Sent: Tuesday, May 28, 2013 11:40 AM To: CODE4LIB@LISTSERV.ND.EDU 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
[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+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
Re: [CODE4LIB] Open Source release policies
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 david.l...@lib.uconn.eduwrote: 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
Re: [CODE4LIB] Open Source release policies
Hello David, We purposefully kept our policy wording as simple as we could by only licensing our offerings under GPL v3.0. http://rucore.libraries.rutgers.edu/open/ License: All programs are free software distributed under the terms of the GNU General Public License v. 3.0 as published by the Free Software Foundation. All terms within the GNU GPL v. 3.0 license apply without reservation. Regards, Chad - Original Message - From: David Lowe david.l...@lib.uconn.edu To: CODE4LIB@LISTSERV.ND.EDU Sent: Tuesday, May 28, 2013 12:39:36 PM 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+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
Re: [CODE4LIB] Open Source release policies
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 # do...@uta.edu # http://rocky.uta.edu/doran/ -Original Message- From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of David Lowe Sent: Tuesday, May 28, 2013 11:40 AM To: CODE4LIB@LISTSERV.ND.EDU 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
