[sword-devel] CrossWire mirroring

Fri Jan 4 15:41:44 MST 2013

I don't actually have ssh access to CrossWire, so I'm not using the rsync
protocol, rather I do have ftp access so using ftp, if a module is removed
from CrossWire, the change is detected and removed from my mirror.

Basically I'm using FTP to replicate RSYNC functionality, but yes -
additions, changes and deletions are all reflected, otherwise the mirror
would fall out of sync.  (Each directory has a .listing file that helps
with this book-keeping).

~A

On Fri, Jan 4, 2013 at 5:07 PM, DM Smith <dmsmith at crosswire.org> wrote:

> Andrew,
>
> How do you handle modules that are removed from CrossWire? Do you use
> rsync w/ --delete?
>
> -- DM
>
> On Jan 4, 2013, at 4:49 PM, Andrew Thule <thulester at gmail.com> wrote:
>
>
>
>
> On Fri, Jan 4, 2013 at 4:06 PM, DM Smith <dmsmith at crosswire.org> wrote:
>
>> Andrew,
>>
>> 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.
>>
>
> You're (licensing) reasons for wanting to manage this are also good and
> right (and legally required).  I support what Crosswire is doing and is
> trying to do completely.  That said, whatever you decided to do with
> respect to (re)distribution rights will be honoured, but it needs to be
> clearly communicated.  If modules are not to be redistributed, impose that
> constraint and be transparent about it.
>
>
>> 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?
>>
>
> All of my 'more current' modules, and other works I'm working on are in a
> separate private repo that does not permit anonymous access.  What goes
> into my public repo are only those things I purposefully intend to share
> (primarily with you folks). With respect to modules in the mirror copied
> from CrossWire, you can check - they are exactly the same as at Crosswire.
>
> When a change happens at Crosswire, my mirror detects and duplicate (only)
> the changed modules (just like an rsync).  If a module does not change,
> nothing happens (thus the only BW consumed is when a change occurs).  You
> have asked me not to redistribute modules with
> "DistributionLicense=Copyrighted; Permission to distribute granted to
> CrossWire".  So when the filesystem (on my end) changes, i.e. a file is
> copied over, the filesystem (using lsyncd) checks the contents of the file
> for DistributionLicense and prevents access to the ones you don't wish be
> redistributed. In a sense my mirror is a perfect mirror though it doesn't
> share those modules you don't want me to share.
>
>
>> If someone posts to sword-support a problem with the text in a module (we
>> get these all the time), having mirrors complicates support.
>>
>
> I don't see the problem.  As mentioned linux distro mirrors do this all
> the time.  That is why tools such as rsync and lsyncd have been created.
>
>
>>
>> We can figure out how to state it.
>>
>
> Simply and clearly.
>
>
>>
>> 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.
>>
>
> I wouldn't mind working through some of the Beta module issues as
> previously mentioned, so I may just head over to the wiki.
> In faith.
>
> ~A
>
>
>
>>
>>
>> On Jan 4, 2013, at 3:39 PM, Andrew Thule <thulester at gmail.com> wrote:
>>
>> It's a good idea to put this in the wiki.  Might I recommend (since it
>> appeared previously on this list "Legitimate FTP Mirrors & Module
>> Distribution Rights Question") that the following be added:
>>
>> "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."
>>
>> This is implied from the following dialogue:
>>
>> On Wed, Jul 25, 2012 at 12:10 PM, Andrew Thule thulester at gmail.com wrote:
>> >> Since Crosswire freely allows modules to be downloaded and governs the
>> >> use of these modules afterwards through the each modules' licensing
>> >> rights, is there something else that precludes their downstream
>> >> redistribution so long as the original license is honoured and
>> >> preserved?  (In other words, if the licenses is established by the
>> >> original module creator, or the license holder for the text, is
>> >> Crosswire able to impose additional restrictions on the use of the
>> >> text?  Should it (not)?)
>>
>> On Wed, Jul 25, 2012 at 12:27 PM, Greg Hellings <greg.hellings at gmail.com>
>> wrote:
>>
>> > So long as the license requirements are fulfilled, there is nothing
>> preventing redistribution.
>> > As I recall, the initial reaction to your announcement was not that you
>> must take it down but
>> > that you must filter those modules which are licensed for only
>> Crosswire's distribution. Any
>> > modules which are in the Public Domain or which have licenses that do
>> not restrict their
>> > distribution to e.g. CrossWire only, you are free to mirror. However,
>> you would have to manually
>> > create such a list by inspecting each module's license individually by
>> hand.
>>
>>
>> Inclusion of the above constraint (to limit redistribution to Crosswire
>> licensed modules) would explicitly clarify Crosswire's position.
>>
>> ~A
>> _______________________________________________
>> sword-devel mailing list: sword-devel at 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 at 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 at 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 at crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.crosswire.org/pipermail/sword-devel/attachments/20130104/1640bf52/attachment.html>