Re: [sword-devel] ISV status?

2013-01-07 Thread DM Smith
On Jan 7, 2013, at 3:09 PM, Andrew Thule wrote: > Let's not reopen the DSS issue Agreed. I think that it was the foundation for the tone of responses you received. I think it was the elephant in the room. I thought you'd like to know that. In Him, DM _

Re: [sword-devel] ISV status?

2013-01-07 Thread Andrew Thule
DM, Let's not reopen the DSS issue, thought it is the same issue. Crosswire is not the Copyright Owner of a single DSS translations. So as long as Crosswire is playing no official role in their digitization or distribution, CrossWire has absolutely nothing to say on the matter. That said, I was

Re: [sword-devel] ISV status?

2013-01-07 Thread Greg Hellings
On Mon, Jan 7, 2013 at 1:37 PM, Andrew Thule wrote: > Greg, respectfully you're still missing the point. > > Because a work is Copyright, doesn't grant Crosswire the right to inform me > of anything, since CrossWire is not the CopyRight owner. Correct. Nor does it mean CrossWire is required to in

Re: [sword-devel] ISV status?

2013-01-07 Thread DM Smith
On Jan 7, 2013, at 1:19 PM, Andrew Thule wrote: > DM, all of which you said is reasonable; no issues from me. My point was in > the efforts to assist with module develoment, I apparently crossed some line. > I offered to send an OSIS update, and made a testing version of it available. > The

Re: [sword-devel] ISV status?

2013-01-07 Thread Andrew Thule
Greg, respectfully you're still missing the point. Because a work is Copyright, doesn't grant Crosswire the right to inform me of anything, since CrossWire is not the CopyRight owner. It is only if the Copyright Owner grants Crosswire rights (and restrictions) though the use of a license to use t

Re: [sword-devel] ISV status?

2013-01-07 Thread Greg Hellings
On Mon, Jan 7, 2013 at 12:43 PM, Andrew Thule wrote: > Greg, its not clear you understand copyright law. > > Copyright Law is generic .. it applies generally. If you read American, > Canadian, or European copyright law you won't find anything mentionion > CrossWire, ISV, ESV specifically. That m

Re: [sword-devel] ISV status?

2013-01-07 Thread Andrew Thule
Greg, its not clear you understand copyright law. Copyright Law is generic .. it applies generally. If you read American, Canadian, or European copyright law you won't find anything mentionion CrossWire, ISV, ESV specifically. That means it lays down principles. Therefore, copyright law with re

Re: [sword-devel] ISV status?

2013-01-07 Thread Greg Hellings
On Mon, Jan 7, 2013 at 12:19 PM, Andrew Thule wrote: > What I did have a hard time with was being publicly held accountable to > license restrictions reasonably unknown to me (and apparently secret), while > having the issue made personal. It isn't reasonable to assume I knew > sharing a compiled

Re: [sword-devel] ISV status?

2013-01-07 Thread Andrew Thule
DM, all of which you said is reasonable; no issues from me. My point was in the efforts to assist with module develoment, I apparently crossed some line. I offered to send an OSIS update, and made a testing version of it available. The debate started (as you note) because of my making a testing v

Re: [sword-devel] ISV status?

2013-01-06 Thread jhphx
On 1/6/2013 1:54 AM, Andrew Thule wrote: I'm currently reviewing its contents to ensure no module exclusive to Crosswire was available. I will be putting it back up on completion of my review. ... I am not sure how you think being exclusive to Crosswire works in this context, but, IF:

Re: [sword-devel] ISV status?

2013-01-06 Thread DM Smith
Regarding module development, that wasn't the problem (though there may be other problems with that). The problem was the distribution of the developed module. Permission for CrossWire to distribute a module does not extend to its members individually. I maintain the ESV module (which is about t

Re: [sword-devel] ISV status?

2013-01-06 Thread Andrew Thule
he modules subfolder. > > Once you have done that you will indeed be free to host our public domain > or otherwise freely distributable texts. > > Sent from my HTC > > - Reply message - > From: "Andrew Thule" 'thules...@gmail.com');>> >

Re: [sword-devel] ISV status?

2013-01-06 Thread Andrew Thule
I'm currently reviewing its contents to ensure no module exclusive to Crosswire was available. I will be putting it back up on completion of my review. In the meanwhile, as previously requested .. if you specifically know of any that were missed, please say so (and don't make it seem like it was

Re: [sword-devel] ISV status?

2013-01-06 Thread Andrew Thule
>> Wrt submission of modules, the wiki describes the process well. To be >> submitted osis files are to be sent to modules@crosswire. Org. >> Sent from my HTC >> >> - Reply message - >> From: "Andrew Thule" >> To: "SWORD Developers'

Re: [sword-devel] ISV status?

2013-01-06 Thread Andrew Thule
our guidance sound hollow and thoroughly dishonest to me. > > Wrt submission of modules, the wiki describes the process well. To be > submitted osis files are to be sent to modules@crosswire. Org. > Sent from my HTC > > - Reply message - > From: "Andrew Thule"

Re: [sword-devel] ISV status?

2013-01-05 Thread ref...@gmx.net
The public repo mirroring Crosswire is now finally down. Thanks for that. Please remove also xiphos, ibt, bible.org mirrors. Sent from my HTC - Reply message - From: "ref...@gmx.net" To: "SWORD Developers' Collaboration Forum" Subject: [sword-devel] ISV

Re: [sword-devel] ISV status?

2013-01-05 Thread ref...@gmx.net
Sent from my HTC - Reply message - From: "ref...@gmx.net" To: "SWORD Developers' Collaboration Forum" Subject: Re: [sword-devel] ISV status? Date: Sun, Jan 6, 2013 07:08 Sorry for top posting. You were yesterday off list notified, with detailed evidence t

Re: [sword-devel] ISV status?

2013-01-05 Thread ref...@gmx.net
Thule" To: "SWORD Developers' Collaboration Forum" Subject: [sword-devel] ISV status? Date: Sun, Jan 6, 2013 06:06 Chris, I should add in response to your last comment, if you ever find I'm distributing something I shouldn't be - please don't hesitate to tell me.

Re: [sword-devel] ISV status?

2013-01-05 Thread Andrew Thule
Chris, I should add in response to your last comment, if you ever find I'm distributing something I shouldn't be - please don't hesitate to tell me. I'm more than happy to remove it. As it stands now however I have done exactly what you asked when you've asked - so you should have no complaint aga

Re: [sword-devel] ISV status?

2013-01-05 Thread Andrew Thule
On Sat, Jan 5, 2013 at 2:55 AM, Chris Little wrote: > > I credit you for taking it down, but you haven't explained why YOU felt it > was YOUR place to do it in the first place. 'Andrew Thule posts the module > on his FTP site' is not part of our release process. Because I was trying to help. I

Re: [sword-devel] ISV status?

2013-01-04 Thread Chris Little
On 1/4/2013 12:11 PM, Andrew Thule wrote: On Fri, Jan 4, 2013 at 1:35 AM, Chris Little mailto:chris...@crosswire.org>> wrote: We've actually had specific discussions with you about our not wanting you to redistribute our modules, specifically because of copyrighted content such as

Re: [sword-devel] ISV status?

2013-01-04 Thread Andrew Thule
On Fri, Jan 4, 2013 at 1:35 AM, Chris Little wrote: > We've actually had specific discussions with you about our not wanting you > to redistribute our modules, specifically because of copyrighted content > such as this for which WE have permission. YOU are not CrossWire. Any > reasonable person w

Re: [sword-devel] ISV status?

2013-01-03 Thread Chris Little
On 1/3/2013 12:30 PM, Andrew Thule 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 a

Re: [sword-devel] ISV status?

2013-01-03 Thread Andrew Thule
On Thursday, January 3, 2013, Peter von Kaehne wrote: > On Thu, 2013-01-03 at 18:51 -0500, Andrew Thule wrote: > > Resistance comes about when someone with a severe case of stubbornness > ignores being told that a particular "contribution" is not desired, not > asked for nor even legal. Cases in p

Re: [sword-devel] ISV status?

2013-01-03 Thread Peter von Kaehne
On Thu, 2013-01-03 at 18:51 -0500, Andrew Thule wrote: > Have you read [James 2:13]? It's not clear why the hostility, but I'm > trying to contribute here (albeit with lots of resistance). Resistance comes about when someone with a severe case of stubbornness ignores being told that a particul

Re: [sword-devel] ISV status?

2013-01-03 Thread Andrew Thule
Peter, Have you read [James 2:13]? It's not clear why the hostility, but I'm trying to contribute here (albeit with lots of resistance). If there's some secret handshake, application form, or process other than signing up on this list that helps transition folks from being outsiders to being ins

Re: [sword-devel] ISV status?

2013-01-03 Thread Peter von Kaehne
On 03/01/13 19:56, Andrew Thule wrote: If others feel as you do, that outside contributions are unwelcome here - I will kick the sand from my sandals and leave I will correct that... On 03/01/13 1956 Andrew Thule should have written: > If others feel as you do, that my contributions are > unw

Re: [sword-devel] ISV status?

2013-01-03 Thread Peter von Kaehne
On 03/01/13 20:46, Andrew Thule 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? You are no CrossWire volunteer. Peter

Re: [sword-devel] ISV status?

2013-01-03 Thread DM Smith
ribute 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

Re: [sword-devel] ISV status?

2013-01-03 Thread Greg Hellings
d >>>> 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 permis

Re: [sword-devel] ISV status?

2013-01-03 Thread Andrew Thule
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

Re: [sword-devel] ISV status?

2013-01-03 Thread Andrew Thule
t; 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,

Re: [sword-devel] ISV status?

2013-01-03 Thread Andrew Thule
ions 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 wrote: >> >>> Andrew, this is now quite enough. Please desist posting further onto our >>> list. Your presen

Re: [sword-devel] ISV status?

2013-01-03 Thread DM Smith
2:20 PM, 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" > To: "SWORD Developers

Re: [sword-devel] ISV status?

2013-01-03 Thread Andrew Thule
e desist posting further onto our >> list. Your presence is undesired >> >> Sent from my HTC >> >> >> - Reply message - >> From: "Andrew Thule" >> To: "SWORD Developers' Collaboration Forum" >> Subject: [sword-devel

Re: [sword-devel] ISV status?

2013-01-03 Thread Andrew Thule
s now quite enough. Please desist posting further onto our > list. Your presence is undesired > > Sent from my HTC > > > - Reply message - > From: "Andrew Thule" > To: "SWORD Developers' Collaboration Forum" > Subject: [sword-devel] ISV st

Re: [sword-devel] ISV status?

2013-01-03 Thread ref...@gmx.net
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" To: "SWORD Developers' Collaboration Forum" Subject: [sword-devel] ISV status? Date: Thu, Jan 3,

Re: [sword-devel] ISV status?

2013-01-03 Thread Andrew Thule
Once (if?) you obtain permission to distribute, please let the list know so that volunteers can continue to move this effort forward. (Conversion from a Word document may no longer be necessary). ~A On Thu, Jan 3, 2013 at 1:56 PM, Andrew Thule wrote: > I guess that answers the question posed b

Re: [sword-devel] ISV status?

2013-01-03 Thread Andrew Thule
I guess that answers the question posed by Nic then .. These efforts are apparently on hold pending permission to distribute. ~A On Thu, Jan 3, 2013 at 1:53 PM, Andrew Thule wrote: > Done. > > I made it available here only in response to this request .. > > ~A > > > On Thu, Jan 3, 2013 at 1:2

Re: [sword-devel] ISV status?

2013-01-03 Thread Andrew Thule
Done. I made it available here only in response to this request .. ~A On Thu, Jan 3, 2013 at 1:28 PM, Chris Little 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

Re: [sword-devel] ISV status?

2013-01-03 Thread Chris Little
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 T

Re: [sword-devel] ISV status?

2013-01-03 Thread Andrew Thule
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 i

[sword-devel] ISV status?

2013-01-02 Thread Nic Carter
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... :) __