[sword-devel] Legitimate FTP Mirrors & Module Distribution Rights Question

Karl Kleinpaste karl at kleinpaste.org
Sun Jul 29 18:37:49 MST 2012

I've really had to think about this one a while before following up, and
I have to say that I just don't know from where some ideas emanate.

"Troy A. Griffitts" <scribe at crosswire.org> writes:
> The Xiphos repo hosts brave modules which give newer features, but
> which might not yet be fully tested on all platforms (I hope this is a
> fair characterization).

Well...  No, not really.  Not even close, for at least 3 qualifiers.

I don't know how the adjective "brave" comes into use here.  It's just a
set of ~70 modules in need of a distribution home.  Some of them are
stupefyingly ordinary, some are extraordinarily large, some have styles
of content that aren't found anywhere else.  We've got the only maps
modules, for example.

As for "newer features," er, no -- generally, they use no markup that
isn't commonly seen in many others.  A larger than usual number are ThML
instead of OSIS, for what we consider good and practical reasons that I
won't belabor now, which certainly puts to bed any idea that we're
exploiting capability not already in use elsewhere.

I don't grasp from where the idea of "not tested on all platforms"
comes.  Since I began producing modules of my own, in 2006, I've
regularly tested with Xiphos, BibleCS, BibleTime, and sometimes
BibleDesktop.  I figure that at least one of those would show a problem
if there was something actually wrong.  I've so seldom seen display
problems occur that, these days, I no longer test modules beyond Xiphos
and BibleCS.

This *persistent* but *false* idea that modules found in Xiphos repo are
untested is particularly disturbing and annoying to me.  Download a few
modules in your favorite frontend, experiment, and find me any problem.
Then, and only then, resume complaining about problems of insufficient
testing.  We who have authored modules for public use that are
distributed from Xiphos repo are, in fact, just as good at such tasks as
anyone else producing modules present in any other repo.

More information about the sword-devel mailing list