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] Beta modules question

2013-01-03 Thread Nic Carter
On 04/01/2013, at 12:04 AM, Chris Little wrote: > The only repository not for general public use is not listed in > masterRepoList.conf, and that's the experimental repository. > > The attic repositories are definitely intended for the public to use. If > users care to, they can downgrade fro

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] Patches to fix compiler warnings

2013-01-03 Thread Jaak Ristioja
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02.01.2013 09:22, Nic Carter wrote: > Thanks for these. > > Hopefully some kind soul will apply them? When I first posted the patches I thought I'll wait until 2013 before taking any further steps. But it has been a very busy time for me and possi

Re: [sword-devel] ISV status?

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

Re: [sword-devel] ISV status?

2013-01-03 Thread Greg Hellings
On Thu, Jan 3, 2013 at 2:44 PM, Andrew Thule wrote: > I just thought about this a bit more .. I suppose that's what "Version=1.5" > is for ... No, the Copyright limitation applies to the source material. It's very possible that multiple versions of the module could be made from the same initial s

Re: [sword-devel] ISV status?

2013-01-03 Thread Andrew Thule
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 wrote: > I just thought abou

Re: [sword-devel] ISV status?

2013-01-03 Thread Andrew Thule
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 wrote: > Thanks for the clarification DM. > Perhaps for the sake of clarity then, the .conf file's > "DistributionLicense=" attribute could contain

Re: [sword-devel] ISV status?

2013-01-03 Thread Andrew Thule
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 wrote: > I can see how you migh

Re: [sword-devel] Beta modules question

2013-01-03 Thread Andrew Thule
This site wasn't on my radar, but I find it very useful: http://crosswire.org/wiki/Modules_in_the_beta_repository#Commentary_Modules Many of these (well documented) issues appear easily fixed. For example the 'emptyvss' issues are likely simple problems to fix. It appears the purpose of this pag

Re: [sword-devel] ISV status?

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

Re: [sword-devel] ISV status?

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

Re: [sword-devel] ISV status?

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

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, 2013 18:53 Done. I made it

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] Beta modules question

2013-01-03 Thread Peter von Kaehne
On 03/01/13 13:04, Chris Little wrote: I would suggest that you quit presenting CrossWire Beta as "CrossWire 2". I know Apple doesn't want 'beta' showing up in the delivered app, but I presume you can sidestep this by loading from masterRepoList.conf. I would second that. Beta was meant to be

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

Re: [sword-devel] Beta modules question

2013-01-03 Thread Chris Little
On 1/3/2013 4:03 AM, Nic Carter wrote: On 03/01/2013, at 6:28 PM, Chris Little wrote: At this point, I wouldn't recommend directing users to download from the beta repository. We don't release new content to beta any longer and the content that was reasonably good has long been moved to oth

Re: [sword-devel] Beta modules question

2013-01-03 Thread Nic Carter
On 03/01/2013, at 6:28 PM, Chris Little wrote: > At this point, I wouldn't recommend directing users to download from the beta > repository. We don't release new content to beta any longer and the content > that was reasonably good has long been moved to other repositories. So the > content r