Hi Mark, Thanks for pointing this out. I didn't notice the other license on this file.
As helix84 notes, this does look to be self-contained, and our 3-clause BSD license is GPL "compatible". So, we should be safe in redistributing this code. However, we obviously cannot change the existing GPL license. We do have other areas of the code that use different compatible licenses (namely areas of XMLUI & Discovery). Here's how we've dealt with it elsewhere: 1) First, leave the license on the code as-is. 2) Add an exclusion to the specific project pom for that file. 3) We also tend to add a *.LICENSE file alongside which includes the full license details. Here's an example from XMLUI Mirage Theme where we've included code under another License: 1) JQuery (used by Mirage Theme) has its own license: * https://github.com/DSpace/DSpace/blob/master/dspace-xmlui/dspace-xmlui-webapp/src/main/webapp/themes/Mirage/lib/js/jquery-ui-1.8.15.custom.min.js 2) So, we have a separate .LICENSE file (in same directory) detailing license terms: https://github.com/DSpace/DSpace/blob/master/dspace-xmlui/dspace-xmlui-webapp/src/main/webapp/themes/Mirage/lib/js/jquery-ui.LICENSE 3) Finally, we add exclusions to the 'dspace-xmlui-webapp' project so that JQUERY files & its *.LICENSE file are excluded from license check: https://github.com/DSpace/DSpace/blob/master/dspace-xmlui/dspace-xmlui-webapp/pom.xml#L47 So, I think the best option here is to do something similar. In this case, we probably should do the following: 1) Leave the oai2.xsl file as-is (https://github.com/DSpace/DSpace/blob/master/dspace-oai/dspace-oai-webapp/src/main/webapp/oai2.xsl) 2) Place a copy of the GNU GPL v.2 License in a file named "oai2.xsl.LICENSE" (or similar) next to that file. 3) Add necessary license exclusions to the 'dspace-oai-webapp' project POM (similar to 'dspace-xmlui-webapp' POM example above) - Tim On 6/19/2012 1:04 PM, helix84 wrote: > On Tue, Jun 19, 2012 at 5:10 PM, Mark H. Wood <[email protected]> wrote: >> dspace-oai/dspace-oai-webapp/src/main/webapp/oai2.xsl lacks the usual >> DSpace license reference, so mvn license:check fails. The transform >> came from EPrints and has Southampton's copyright and GPL notice. The >> version in DSpace has mod.s made for DSpace. >> >> So how should we satisfy license:check? Let license:format stamp >> DSpace's notice on it? Add it to an exclusion list? Do we need a new >> option? > > I just wanted to point out that the code is self-contained, so we're > not mixing GPL and DSpace's BSD here - the file can have a separate > license. As far as my modifications to the file go, of course they are > GPL-licensed. > > I didn't know about this license:check target, but when I run it it > only complains about some example module. > > Regards, > ~~helix84 > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Dspace-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/dspace-devel > ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Dspace-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-devel
