<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Andrew,<div><br></div><div>I was careful not to say what you proposed. The quote you suggest is technically/true/correct/good as far as it goes. The other bullets I gave are why we discourage mirroring even for those.</div><div><br></div><div>For example, in your mirror (I think you still have it available), are there any modules that are more current on the CrossWire server than in yours? Or visa versa?</div><div><br></div><div>If someone posts to sword-support a problem with the text in a module (we get these all the time), having mirrors complicates support.</div><div><br></div><div>We can figure out how to state it.</div><div><br></div><div>But the way the wiki works is that everyone is welcomed to get an account and create content. Using the Talk pages is an excellent place to discuss what should be on the page. David, Chris and I moderate the content, after the fact.<br><div><br></div><div>In Him,</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>DM</div><div><br><div><div>On Jan 4, 2013, at 3:39 PM, Andrew Thule <<a href="mailto:thulester@gmail.com">thulester@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr"><div>It's a good idea to put this in the wiki. Might I recommend (since it appeared previously on this list "<span id=":1i8" tabindex="-1">Legitimate FTP Mirrors & Module Distribution Rights Question"</span>) that the following be added:</div>
<div> </div><div>"Modules specifically licensed to Crosswire may not be redistributed. For all others, as long as the license requirements are fulfilled, there is nothing preventing redistribution."</div>
<div> </div><div>This is implied from the following dialogue:</div><div> </div><div>On Wed, Jul 25, 2012 at 12:10 PM, Andrew Thule <a href="mailto:thulester@gmail.com" target="_blank">thulester@gmail.com</a> wrote:</div>
<div>>> Since Crosswire freely allows modules to be downloaded and governs the<br>>> use of these modules afterwards through the each modules' licensing<br>>> rights, is there something else that precludes their downstream<br>
>> redistribution so long as the original license is honoured and<br>>> preserved? (In other words, if the licenses is established by the<br>>> original module creator, or the license holder for the text, is<br>
>> Crosswire able to impose additional restrictions on the use of the<br>>> text? Should it (not)?)</div><div><br>On Wed, Jul 25, 2012 at 12:27 PM, Greg Hellings <<a href="mailto:greg.hellings@gmail.com" target="_blank">greg.hellings@gmail.com</a>> wrote:</div>
<div> <br>> So long as the license requirements are fulfilled, there is nothing preventing redistribution.</div><div>> As I recall, the initial reaction to your announcement was not that you must take it down but</div>
<div>> that you must filter those modules which are licensed for only Crosswire's distribution. Any </div><div>> modules which are in the Public Domain or which have licenses that do not restrict their </div><div>
> distribution to e.g. CrossWire only, you are free to mirror. However, you would have to manually<br>> create such a list by inspecting each module's license individually by hand.</div><div> </div>
<div> </div><div>Inclusion of the above constraint (to limit redistribution to Crosswire licensed modules) would explicitly clarify Crosswire's position.</div><div> </div><div>~A</div></div>
_______________________________________________<br>sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a><br><a href="http://www.crosswire.org/mailman/listinfo/sword-devel">http://www.crosswire.org/mailman/listinfo/sword-devel</a><br>Instructions to unsubscribe/change your settings at above page</blockquote></div><br></div></div></body></html>