<div dir="ltr"><p dir="ltr">On Jan 6, 2016 12:53 PM, "Troy A. Griffitts" <<a href="mailto:scribe@crosswire.org" target="_blank">scribe@crosswire.org</a>> wrote:<br></p><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><br>
I don't want to fight about this yet again.<br>
<br>
This is a commercial module to be sold by Lockman. That is a different<br>
scenario from other modules. For this module, I have reasonably asked:<br>
<br>
1) That we have a scripted, reproducible way to transform their data<br>
from their pristine source to a module.<br></blockquote><div><br></div><div>Complete as I know it at this time. I left the lexica alone for the time being because no one has ever presented me with concrete problems the module has. I've only ever heard a vague "it has issues". I'll take another look soon to see what those problems might be and see if I need to make changes. The conversion for the Bible + notes has been completely rewritten into Python with a load of unit tests - every time someone has pointed out a bug in it to me, I add a unittest that is the actual text from the module that causes the bug and then I fix the unittests. This has made my iterations much more stable with regards to regressions.</div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
2) That we support their entire dataset which they have given us for<br>
this module (base text + footnotes / crossrefs + lexica)<br></blockquote><div><br></div><div>I'm unaware of deficiencies here at present. I'd be happy to verify that and the onus then falls to me at this time if we aren't supporting some portion of it.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
3) That the result works generally in all major SWORD/JSword frontends.<br></blockquote><div><br></div><div>Last I heard from DM, there was a fix in the development versions of JSword/BD for whatever outstanding features it was missing. And he had promised to make a release "this weekend" in the Spring of last year. I don't believe that release was ever cut. </div><div><br></div><div>--Greg</div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
<br>
It is not as simple as-- just release it and fix it later. This is to<br>
be sold by Lockman.<br>
<br>
Historically, we have had at least 4 people own this effort over the<br>
years. It is not simply that one person has sat on this and hasn't<br>
finished it for 12 years.<br>
<br>
I think we are close. In my mind, the current owner (Greg) simply needs<br>
to have a list of outstanding items which keep us from satisfying 1-3<br>
and push each of them down the road until they are done.<br>
<br>
I don't know what those items are. I am just concerned that we meet 1-3<br>
before we give the data to Lockman to sell and I feel these 3 items are<br>
reasonable requests.<br>
<br>
Troy<br>
<br>
<br>
<br>
On 01/06/2016 11:04 AM, Karl Kleinpaste wrote:<br>
> On 01/06/2016 10:56 AM, Greg Hellings wrote:<br>
>> but no one has told me what those issues are<br>
> It comes down to this:<br>
> We need to look for the way to say Yes, and stop coughing up any and all<br>
> possible, weak, ham-handed excuses to say No.<br>
><br>
> A long time ago -- late '08 -- I flamed at length here about Getting<br>
> Stuff Done. The fact that NASB has languished for significantly longer<br>
> than a decade and _/*STILL*/_ hasn't found its way out the door is an<br>
> existential statement about Crosswire in this regard. Crosswire as a<br>
> whole has an indecent problem with the idea of Getting Stuff Done, where<br>
> "done" means "out the door."<br>
><br>
> If you consider this from the perspective of an outside observer, it<br>
> looks like someone literally doesn't want NASB ever to be released.<br>
> Consider: In the last 12 years, one of my sons graduated high school,<br>
> took a couple years off, went to college, finished college, got married,<br>
> began a career, and had his first child, who will be a year old very<br>
> soon. In that same time period Crosswire couldn't get the NASB module<br>
> (set) finished.<br>
><br>
> Any reason to say No is completely obliterated by saying "12 years."<br>
> It's time to say Yes.<br>
><br>
><br>
> _______________________________________________<br>
> sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org" target="_blank">sword-devel@crosswire.org</a><br>
> <a href="http://www.crosswire.org/mailman/listinfo/sword-devel" rel="noreferrer" target="_blank">http://www.crosswire.org/mailman/listinfo/sword-devel</a><br>
> Instructions to unsubscribe/change your settings at above page<br>
><br>
<br>
_______________________________________________<br>
sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org" target="_blank">sword-devel@crosswire.org</a><br>
<a href="http://www.crosswire.org/mailman/listinfo/sword-devel" rel="noreferrer" target="_blank">http://www.crosswire.org/mailman/listinfo/sword-devel</a><br>
Instructions to unsubscribe/change your settings at above page<br>
</blockquote></div>
</div>