Andrew,
The vocabulary is the issue here:
There are module repositories already in existence which contain data that is
completely compatible with at least some Sword Project programs, but are not
mirrors or even part of the the Sword Project. I know of at least a little
overlap between mod
On 1/11/2013 4:08 PM, Andrew Thule wrote:
Nic, no I didn't miss the point.
You are claiming this privelge is exclusive. If so, the terms of this
agreement must be both registered and public. Anyone can claim anything
they want about what they are able to do, and what others are not able
to do,
- There is no "exclusive" agreement. (You can access the ESV from BibleGateway,
for example.)
- If we are challenged by a copyright holder about our rights to distribute
their content, we then take that up with them. (This happened with the ESV a
few years ago, when the new guy in charge of tha
Nic, no I didn't miss the point.
You are claiming this privelge is exclusive. If so, the terms of this
agreement must be both registered and public. Anyone can claim anything
they want about what they are able to do, and what others are not able to
do, but these claims are only true if the terms
Oh and to be clear I'm happy (and morally obligated) to honour the law.
If I see evidence Crosswire holds exclusive license to control the
distribution of some modules, I will honour that license.
However, if no such legal restrictions apply, I am bound by a greater
commission and intend to distr
Hi Andrew,
You completely miss the point!
CrossWire has the right to distribute certain modules. In order to satisfy our
legal agreement with the copyright holders we can can only distribute from
"CrossWire". We do not own the copyright, we have to abide by the same rules as
anyone else. We ar
Ultimately, the issue is about licensing rights on modules, which appears
to be a very touchy subject around here. I suspect this is so because
without actual licenses, which are essentially legal agreements (I'm not
talking about .conf files which are not legal agreements), its pretty much
imposs
Based on the*.crosswire.org rule I would say the best option when and if
mirrors are needed is to have some sort of round robin dns that picks a mirror
from an internal list the way microsoft.com or my Linux distro does
download.opensuse.org for it's package repos. Sorry for the top post'
Nic C
Agreed. That's another way of stating it: until Crosswire decides on the
issue, there's no sense in developers discussing it..
~A
On Monday, January 7, 2013, Nic Carter wrote:
>
> Sent from my phone, hence this email may be short...
>
> On 08/01/2013, at 8:51, Andrew Thule >
> wrote:
>
> >
> > A
Sent from my phone, hence this email may be short...
On 08/01/2013, at 8:51, Andrew Thule wrote:
>
> As long as Crosswire has policies in place govererning official mirrors there
> should no no worries mirrors are out of sync, in which case preferred mirror
> selection can be left to the use
If you think about Linux distributions, you see a number of approaches:
1 Software makes the mirror selection
2 User makes Mirror selection.
Given the clients cited above, only if the Software chooses the mirror are
coding changes necessary. The Software developer must also make decisions
about
I concur with DM, the Sword/JSword/UIs would have to change. I've had that
issue with having modules in both the normal repo and the (old?) beta
repository. The frontends give a false impression as to which module came
from which repository.
On 7 January 2013 19:50, DM Smith wrote:
>
> On Jan
On Jan 7, 2013, at 2:04 PM, Andrew Thule wrote:
> Ok. In your example you have two levels of mirrors, root and banch.
>
> If we assume all mirrors are synced (exactly the same), the client (if it
> supports more than a preferred mirror) will check its mirrors in the order
> they are specifi
Ok. In your example you have two levels of mirrors, root and banch.
If we assume all mirrors are synced (exactly the same), the client (if it
supports more than a preferred mirror) will check its mirrors in the order
they are specified.
So in your case, Y will check A. D. and E. in that order (a
I guess I need more information on mirrors.
Let's say that there are to mirrors X and Y. For what ever reason, X has A, B,
C, D and Y has A, D, E. Software is configured to use Y. When it goes to get a
list of files, what does it get? If it requests B, what does it get? Same
questions for softw
My experience with mirrors is that mirrors are done at the level of the
Operating Systems. Tools like 'rsync', 'lsync', 'chron' etc manage the
integrity and distribution of these things.
That said, I think what you're saying is that you believe the Sword client
needs some additional support to su
Mirror management is a moot issue if the software doesn't support mirrors. I
have no plans to add such to JSword, unless it is added to SWORD first. I
highly doubt that it will be added to SWORD until a problem with resiliency
creates a real need. Even then, I'm not sure that that will be used a
DM, I agree that not having thought through mirror management procedurally
(policy and best backpractice) is reason enough to hold off on such a
venture, but those problems are typically trivial to solve given effective
communication.
Since technology is subordinat to intent, what needs to be work
Peter, I've not received your email yet, but look forward to it.
Let me address your concern. I have no intention of distributing modules
exclusively licensed to Crosswire. I think I currently am, however (as I
previously said to Chris) I invent you to contact me with concerns and
request.
I lo
Sorry for the top post, but I believe the below text (by Chris Burrell) sums
things up pretty well – there is no problem with people having personal mirrors
of all the CrossWire modules, for personal use only and not for public access.
However, at this point there isn't a major issue with resili
A few more reasons we discourage mirroring:
SWORD and JSword have no means for managing mirrors. They expect each
repository to be a unique collection of modules.
A mirror that is partial, not containing all that is in the master repository,
probably will be confusing to users.
A mirror that is
On Sat, Jan 5, 2013 at 4:17 AM, Chris Little wrote:
>
> So, Andrew, the fundamental problem here is that you seem to believe you
> are never wrong and that any disagreement is always the result of the other
> party being wrong. You believe you interpret the world correctly and that
> every other
On Sat, 2013-01-05 at 01:12 -0500, Andrew Thule wrote:
> Peter, please temper your judgement with mercy. Your claims here are
> neither correct nor fair.
I have sent you a lengthy private reply which deals in detail with the
claims that your repos are filtering out the restricted modules.
Suffic
On 1/4/2013 10:12 PM, Andrew Thule wrote:
Peter, please temper your judgement with mercy. Your claims here are
neither correct nor fair.
So, Andrew, the fundamental problem here is that you seem to believe you
are never wrong and that any disagreement is always the result of the
other party
Peter, please temper your judgement with mercy. Your claims here are
neither correct nor fair.
On Friday, January 4, 2013, Peter von Kaehne wrote:
> On Fri, 2013-01-04 at 16:49 -0500, Andrew Thule wrote:
>
> It is clear. Your lack of respect for what is expressed in the conf file
> re Distributi
On Fri, 2013-01-04 at 16:49 -0500, Andrew Thule wrote:
> 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.
It
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, cha
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 wrote:
>
>
>
> On Fri, Jan 4, 2013 at 4:06 PM, DM Smith wrote:
> Andrew,
>
> I was careful not to say what you proposed. The quote you suggest i
And, a lot of the the tools using mirrors are generally addressed to a
fairly technical community. The other big difference is obviously that the
linux community is massive, and we are small in comparison. But I'm all up
for more resilience if that's something we've had an issue with?
On 4 Januar
Regarding Fedora, I find that the mirrors differ significantly. Some have old
releases, but no new releases. Some have the latest release but no updates.
Some may have the alphas and/or the betas. Using yum, I have had some updates
fail because they have dependencies that have not reached the mi
On Fri, Jan 4, 2013 at 4:06 PM, DM Smith 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 wantin
On Fri, Jan 4, 2013 at 3:06 PM, DM Smith wrote:
> If someone posts to sword-support a problem with the text in a module (we
> get these all the time), having mirrors complicates support.
If Fedora can have many dozen mirrors, and Debian can have many dozen
mirrors and so can every Linux distribut
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.
For example, in your mirror (I think you still have it available), are there
any modules that a
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
From time to time, interest has been expressed in mirroring CrossWire's SWORD
modules. I thought I'd reiterate our policy.
We strongly, very strongly, discourage mirroring of the SWORD module repository.
Those modules for which CrossWire has obtained distribution permission from
copyright holde
35 matches
Mail list logo
