[sword-devel] Maintaining Module Creation Sources and Scripts
Troy A. Griffitts
scribe at crosswire.org
Sat Nov 29 05:30:35 MST 2008
Yes, we haven't had much that we feel the need to maintain yet, save the
token KJV2003 example. This may change in the coming years when our
community projects rev up. I understand your concern to know where the
source documents reside. I guess the general answer to that is that the
.conf file SHOULD have a valid TextSource= entry pointing to where the
source was obtained. To be sure our own modules have a link with
longevity, you are certainly correct that we should standardize a
location other than the likes of crosswire.org/~user/... :) DM?
Greg Hellings wrote:
> On Sat, Nov 29, 2008 at 2:57 AM, Chris Little <chrislit at crosswire.org> wrote:
>> Greg Hellings wrote:
>>> Just a question...
>>> Are both of these accessible to anyone interested? If a confused
>>> person can get the source used and the scripts, then run them, they
>>> can probably figure that much out and have a look at their questions.
>>> But from the looks of it, the sources aren't accessible?
>> No, and nor should they be in in the case of this content.
> For copyrighted and sources available from another site (e.g. CCEL),
> this makes sense. But there is some content that we are the primary
> people for, no? Obviously the KJV2003 is the main example of this,
> but are there others? If so, having some place to host those few for
> which we are the primary might be beneficial, sorta the way the
> KJV2003 is hosted at crosswire.org/~dmsmith. Or, maybe, if we don't
> have a central place, have links to those which we host (KJV2003 and
> the ones that you mentioned earlier) on the wiki's module creation
> sword-devel mailing list: sword-devel at crosswire.org
> Instructions to unsubscribe/change your settings at above page
More information about the sword-devel