<div>This has been stated on numerous occasions.<br></div><div><br></div><div><b>CrossWire as a Society does not maintain the authoritative source text for modules except for very few cases, namely the KJV & KJVA modules.</b><br></div><div><br></div><div>Individual volunteers may indeed have [had] access to working copies of source texts for some modules as part of past or ongoing work in progress.<br></div><div><br></div><div>However, when such module issues were reported, this is generally because the reporting was done in the role of a user making observations from module testing or analysis - rather than as a module developer and/or source text collaborator.<br></div><div><br></div><div>That a certain volunteer went AWOL (having left CrossWire and in effect cut himself off from further contact) this simply means that his knowledge, skills, <i>ad hoc</i> working scripts, customised software tools and file resources are no longer available to other volunteers. The trail went cold. We simply have to begin again from scratch on these issues.<br></div><div><br></div><div>Now of course, there are volunteers such as myself and several others that are active in source text development collaboration with third parties.<br></div><div>This enables us to provide a benefit to those not directly involved in Bible translation activities in the various well-established Bible agencies and societies.<br></div><div>i.e. Because such people are often using something other than ParaTExt (or Bibledit) to maintain their source text. <br></div><div>We have various software skills and some tools that can assist such providers get their source text into a format (USFM & OSIS)<br></div><div> that is more amenable for electronic publishing in forms suitable for Bible software in general and including SWORD modules for distribution by CrossWire.<br></div><div><br></div><div>For the present "modules team", in projects that are likely to go through more than one iteration, every effort is being made to retain copies of source text files.<br></div><div>But keeping a working copy is not the same as maintaining an authoritative source. We're back to ownership, provenance and version control matters.<br></div><div><br></div><div>Generally, for copyrighted works, these should be kept in a private repository, and only shared with others where collaboration is essential.<br></div><div>Even so, that still leaves a lot of collaboration work where the files for work in progress are probably stored only on the individual volunteer's computer rather than in accessible cloud services such as GitHub or GitLab, etc. <br></div><div><br></div><div class="protonmail_signature_block"><div class="protonmail_signature_block-user"><div>Best regards,<br></div><div><br></div><div>David<br></div></div><div><br></div><div class="protonmail_signature_block-proton">Sent with <a target="_blank" href="https://protonmail.com">ProtonMail</a> Secure Email.<br></div></div><div><br></div><div>‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐<br></div><div> On Monday, 3 December 2018 15:01, Cyrille <lafricain79@gmail.com> wrote:<br></div><div> <br></div><blockquote type="cite" class="protonmail_quote"><div><br></div><div><br></div><div class="moz-cite-prefix">Le 03/12/2018 à 14:45, David Haslam a
écrit :<br></div><blockquote type="cite"><div><div>Posting comments on multiple issues that are several years
old that simply ask questions like "Do you have the source?"
don't get us anywhere forward soon.<br></div><div> They can even become a distraction in the originator's email
notifications.<br></div></div></blockquote><div>Ok I understand, but when you (or the team) build the modules you
had some source no? Where are this sources? Didn't you keep the osis
files or usfm file when you had it? Just CPDV as example. I would
like to be sure nobody keeps usfm or osis file before working on it.<br></div><div> <br></div><blockquote type="cite"><div><div><br></div><div>Some of these old issues were originally added by me as long ago
as 2011 when CrossWire still had someone responsible for
building the original modules.<br></div></div><div>They were added on the assumption that this person would have
known the module history and was in a position to do all the
necessary work.<br></div><div><br></div><div>That he went AWOL and these issues are still open essentially
means that to make any progress now, someone will need to
champion each module, do the research, find the latest source
text, do the conversion to OSIS, rebuild and test the module,
and check that the issue is then fixed, before submitting to the
Modules Team.<br></div><div><br></div><div>I will not be adding replies to new comments unless I have
new information to hand that was unavailable when each issue
were created.<br></div><div><br></div><div class="protonmail_signature_block"><div class="protonmail_signature_block-user"><div>Best regards,<br></div><div><br></div><div>David<br></div></div><div><br></div><div class="protonmail_signature_block-proton">Sent with <a target="_blank" href="https://protonmail.com">ProtonMail</a> Secure Email.<br></div></div><div><br></div><div>‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐<br></div><div>On Sunday, 2 December 2018 19:21, Cyrille <a href="mailto:lafricain79@gmail.com"><lafricain79@gmail.com></a> wrote:<br></div><div><br></div><blockquote type="cite" class="protonmail_quote"><div>Please Peter, can you post even if you don't have the
source? It will be easier, because I post on multiples issues,
I don't remember exactly which...<br></div><div><br></div><div><br></div><div class="moz-cite-prefix">Le 02/12/2018 à 18:54, DM Smith a
écrit :<br></div><blockquote type="cite"><div>The Internet Wayback Machine is useful for dead URLs.
I’ve used it to find resources no longer available and to
make contact w people. <br></div><div><br></div><div><br></div><div dir="ltr"><div>— DM Smith <br></div><div>From my phone. Brief. Weird autocorrections. <br></div></div><div dir="ltr"><div><br></div><div>On Dec 2, 2018, at 10:47 AM, "<a href="mailto:refdoc@gmx.net">refdoc@gmx.net</a>"
<<a href="mailto:refdoc@gmx.net">refdoc@gmx.net</a>>
wrote:<br></div><div><br></div></div><blockquote type="cite"><div dir="ltr"><div>Regarding how to find source:<br></div><div><br></div><div>In our newer and better modules a source is given in
the conf file. But sometimes that link is now dead.<br></div><div><br></div><div><br></div><div>Sent from my mobile. Please forgive shortness, typos
and weird autocorrects. <br></div><div style="line-height: 1.5"><div><br></div><div><br></div><div>-------- Original Message --------<br></div><div>Subject: [sword-devel] Modules, Tracker - some
remarks<br></div><div>From: <a href="mailto:refdoc@gmx.net">refdoc@gmx.net</a><br></div><div>To: sword-devel <br></div><div>CC: <br></div><div><br></div><div><br></div><div><br></div><blockquote style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex"><div>Hi to all<br></div><div><br></div><div>1) I am so pleased and grateful for all the
activity checking and testing modules wrt issues
mentioned on the tracker<br></div><div><br></div><div>2) There is a substantial minority of modules we
do have source texts for (around 100) and I hold the
key for them. They can not be shared to anyone,
usually, as they tend to be not public domain texts.
But the upshot for them is, I feel responsible in a
direct way for them and take care of much in these
weeks. So if you see me commenting on a module as
the matter being in work, just move on , as it is in
hand. <br></div><div><br></div><div>3) There is a majority of texts, and some of
them are very old in terms of CrossWire and we need
to find sources for them, because we do not hold
them. So, if you do not see me commenting that
things are in hand, the module clearly requires a
rebuilt and you want to push this actively forward,
go and find the source. <br></div><div><br></div><div>4) How to find sources:<br></div><div><br></div><div>Many public domain texts have been pushed
forward and backward between projects since the
start of the internet, are in a poor state and badly
or not at all marked up, forced into KJV
versification , or sometimes even chopped up in
order to support sectarian views. Commonly for
important texts though there exists somewhere
someone who has decided to fix things. People who do
try and fix things make this often very clear.
Others refer/defer to them. It pays to get into
direct contact with them to establish a link and
maybe even let them produce OSIS or USFM for our
use. We certainly always want to feed back any and
all improvements we make to Mark Up etc.<br></div><div><br></div><div>5)You find good authoritative source, put at
least the link underneath the tracker and explain
shortly why this is in your view the best source,
particularly if there is a big choice. If you want
to go and start working on a module, even better<br></div><div><br></div><div>Thanks again to all!<br></div><div><br></div><div><br></div><div><br></div><div>Sent from my mobile. Please forgive shortness,
typos and weird autocorrects.<br></div><div>_______________________________________________<br></div><div>sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a><br></div><div><a href="http://www.crosswire.org/mailman/listinfo/sword-devel">http://www.crosswire.org/mailman/listinfo/sword-devel</a><br></div><div>Instructions to unsubscribe/change your settings
at above page<br></div></blockquote></div></div></blockquote><blockquote type="cite"><div dir="ltr"><div><span>_______________________________________________</span><br></div><div><span>sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a></span><br></div><div><span><a href="http://www.crosswire.org/mailman/listinfo/sword-devel">http://www.crosswire.org/mailman/listinfo/sword-devel</a></span><br></div><div><span>Instructions to unsubscribe/change your
settings at above page</span><br></div></div></blockquote><div><br></div><pre wrap="">_______________________________________________
sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a>
<a href="http://www.crosswire.org/mailman/listinfo/sword-devel">http://www.crosswire.org/mailman/listinfo/sword-devel</a>
Instructions to unsubscribe/change your settings at above page
<br></pre></blockquote></blockquote><div><br></div><div><br></div><pre wrap="">_______________________________________________
sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a>
<a href="http://www.crosswire.org/mailman/listinfo/sword-devel">http://www.crosswire.org/mailman/listinfo/sword-devel</a>
Instructions to unsubscribe/change your settings at above page<br></pre></blockquote></blockquote><div><br></div>