By and large, we use the upstream source for a text without modifying it at
all. If we find errors or problems, we feed them back upstream. This benefits
everyone, not just us.
When a source is not copyrighted, we look for the best source we can find. When
it is copyrighted we get it from the publisher in the form that they are
willing to provide.
If we have an error that is due to our import process, we'll fix that and
rebuild the module.
The only text that we maintain is the KJV. I am the pumpkin holder for that. I
get downstream notifications every now and them and am grateful for that.
In Him,
DM
On Jan 3, 2013, at 3:46 PM, Andrew Thule <thules...@gmail.com> wrote:
> If there are prohibitions against distributions of newer revisions of the
> text, this needs to be documented somewhere; for how else will volunteers
> know they are restricted to working with particular versions of text?
>
> ~A
>
>
> On Thu, Jan 3, 2013 at 3:44 PM, Andrew Thule <thules...@gmail.com> wrote:
> I just thought about this a bit more .. I suppose that's what "Version=1.5"
> is for ...
>
> Nevermind.
> ~A
>
>
> On Thu, Jan 3, 2013 at 3:42 PM, Andrew Thule <thules...@gmail.com> wrote:
> Thanks for the clarification DM.
> Perhaps for the sake of clarity then, the .conf file's "DistributionLicense="
> attribute could contain the version for which permission was granted (rather
> than appearing to be generic).
>
> ~A
>
>
> On Thu, Jan 3, 2013 at 3:35 PM, DM Smith <dmsm...@crosswire.org> wrote:
> I can see how you might conclude that.
>
> However, when we get permission for a copyrighted work, we get permission for
> that copyright. If the work is updated, there is a new copyright and we have
> to obtain permission for that.
>
> In Him,
> DM
>
>
> On Jan 3, 2013, at 3:30 PM, Andrew Thule <thules...@gmail.com> wrote:
>
>> I should add that prior to doing anything I did check the isv.conf file
>> which says this:
>> DistributionLicense=Copyrighted; Permission to distribute granted to
>> CrossWire
>>
>>
>> From .conf file at least, any reasonable person would conclude that
>> permission had already been obtained to distribute (and redistribute) ISV
>> and any additional revisions.
>>
>> ~A
>>
>>
>> On Thu, Jan 3, 2013 at 2:56 PM, Andrew Thule <thules...@gmail.com> wrote:
>> Come now Peter, don't be so quick to find fault.
>>
>> The Crosswire repository currently contains version 1.5 of the ISV module.
>> Nic's question was asking about the inclusion of the OT in that module. The
>> Crosswire site doesn't say anything about the status of this module, and
>> Nic's question seems to suggest he was not aware Crosswire was prohibited
>> from distributed a later versions of this module. His comment was
>> specifically asking about the ISV with OT included suggesting this was
>> already direction that was being pursued.
>>
>> I was trying to extend an offer to help (as a volunteer). I certainly
>> wasn't aware that permission hadn't been obtained to distribute the ISV with
>> the OT, and the fact the ISV is already distributed with the NT suggests
>> (perhaps incorrectly) that permission has been already obtained. Once Chris
>> made it known that Crosswire has no such permission to distribute newer
>> versions of the ISV I did exactly as Chris asked. So what infraction have I
>> committed now?
>>
>> Respectfully, if every time a newcomer or volunteer's offer is met with
>> criticism or controversy the treatment of newcomers and volunteers in this
>> group is going to appear somewhat suspect and unwelcoming. It's a very good
>> way to drive people away from a project. If my lack of awareness of this
>> prohibition on the ISV is why you're asking me to leave - that says much
>> about this community.
>>
>> Now that I know Crosswire doesn't have permission to distribute versions of
>> the ISV other than the one currently in the repository, I'll respect that.
>> If others feel as you do, that outside contributions are unwelcome here - I
>> will kick the sand from my sandals and leave
>>
>> ~A
>>
>> On Thu, Jan 3, 2013 at 2:20 PM, ref...@gmx.net <ref...@gmx.net> wrote:
>> Andrew, this is now quite enough. Please desist posting further onto our
>> list. Your presence is undesired
>>
>> Sent from my HTC
>>
>>
>> ----- Reply message -----
>> From: "Andrew Thule" <thules...@gmail.com>
>> To: "SWORD Developers' Collaboration Forum" <sword-devel@crosswire.org>
>> Subject: [sword-devel] ISV status?
>> Date: Thu, Jan 3, 2013 18:53
>>
>>
>> Done.
>>
>> I made it available here only in response to this request ..
>>
>> ~A
>>
>>
>> On Thu, Jan 3, 2013 at 1:28 PM, Chris Little <chris...@crosswire.org> wrote:
>> Andrew, this document is copyrighted. We do not have permission to
>> distribute it. You certainly and absolutely do not have permission to
>> distribute it, much less to distribute it and claim that we have permission
>> to distribute it.
>>
>> Remove it immediately.
>>
>> --Chris
>>
>>
>>
>> On 1/3/2013 9:37 AM, Andrew Thule wrote:
>> I believe there's an OSIS file that contains both testaments ... I can
>> forward it if it helps this effort.
>>
>> There are least two versification problems (I haven't bothered to
>> address yet)
>> INFO(V11N): 1Sam.11 is not in the KJV versification. Appending content
>> to 1Sam.10.27
>> INFO(V11N): Rev.13 is not in the KJV versification. Appending content to
>> Rev.12.17
>>
>> I've placed a mod based on this OSIS file in my repo if anyone interested:
>> Repository: 1XO
>> Host: ftp.1xo.net <http://ftp.1xo.net>
>>
>> /1xo/pub/sword/betaraw
>>
>> ~A
>>
>>
>> On Wed, Jan 2, 2013 at 9:01 PM, Nic Carter <niccar...@mac.com
>> <mailto:niccar...@mac.com>> wrote:
>>
>>
>> Hi Team :)
>>
>> I was wondering where we were at with updating the ISV to include
>> both the OT & NT?
>> There was some chatter here about a year ago about it, but it
>> sounded yuck, given we needed to convert the text from a Word
>> document... :/
>>
>> Thanks, ybic
>> nic... :)
>>
>> _______________________________________________
>> sword-devel mailing list: sword-devel@crosswire.org
>> <mailto: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
>>
>>
>>
>> _______________________________________________
>> 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
>>
>>
>> _______________________________________________
>> 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
>
>
>
> _______________________________________________
> 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
