And even at that point, no copyright will be violated unless someone attempts to mirror or host format shifted versions of the modules.
On Sep 27, 2016 11:37 AM, "Greg Hellings" <greg.helli...@gmail.com> wrote: > Unless and until this fork is unable to read a Sword module format, this > discussion is moot. The distribution had no bearing on the software that > does the parsing of the file. > > On Sep 27, 2016 11:32 AM, "DM Smith" <dmsm...@crosswire.org> wrote: > >> >> On Sep 27, 2016, at 7:52 AM, Matěj Cepl wrote: >> >> On 2016-09-26, 21:10 GMT, DM Smith wrote: >> >> A fork of the CrossWire library (SWORD or JSword) may or may >> not be seen by the copyright holders to be mechanism of >> distribution and access that they are willing to license their >> work. I know of one publisher of a popular module in >> particular that would not. >> >> >> Of course, this is yet another example of the complete mess >> about the Biblical modules. Is there somewhere a list of all >> modules with their appropriate licenses under they are >> distributed, or are all of them (except for the three >> I maintain) proprietary? Which modules are explicitly permitted >> to be used only with the code you control? >> >> I would like to know so that I can file a bug against SwordJS, >> that it must eliminate some modules to comply. >> >> See DistributionLicense in https://crosswire.org/wiki/DevTools:conf_Files >> . >> Basically if it says: >> Copyrighted; Permission to distribute granted to CrossWire >> then it is specific to CrossWire. >> Note, compare this as case insensitive, allowing whitespace and >> variations in punctuation. In one instance it has “CrossWire Bible >> Society”. In another it has a couple extra words after copyrighted. >> Our wiki says it should be verbatim which is meant to allow simple >> filtering. >> >> Modules from other repositories might have a different company name. >> I’d suggest the following regexp: >> m/.*permission\s+to\s+distribute\s+granted\s+to.*/i >> >> If it merely says: >> Copyrighted >> then we haven’t stated any further distribution restrictions, but it’d >> probably be best to exclude as well unless the conf says elsewhere it is >> ok. We try not to use this string, but it is present in 5 modules. >> >> Hope this helps. >> >> In His Service, >> DM Smith >> >> >> >> _______________________________________________ >> sword-devel mailing list: sword-devel@crosswire.org >> http://www.crosswire.org/mailman/listinfo/sword-devel >> Instructions to unsubscribe/change your settings at above page >> >
_______________________________________________ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page