<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
This <a moz-do-not-send="true"
href="https://tracker.crosswire.org/projects/MOD/issues/MOD-170">bug</a>
can be closed (I don't know how to do) Not currently a bug. See the
comment on it.<br>
<br>
<div class="moz-cite-prefix">Le 01/12/2018 à 14:22, Cyrille a
écrit :<br>
</div>
<blockquote type="cite"
cite="mid:6f748785-8165-81c8-d681-75e4d98fb714@gmail.com">
<pre class="moz-quote-pre" wrap="">Good idea to send use the link. And the text sources where can we find it?
I'll have a look to MOD-170.
Le 01/12/2018 à 10:38, David Haslam a écrit :
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">If anyone is volunteering, modules issues are tracked at
<a class="moz-txt-link-freetext" href="https://tracker.crosswire.org/browse/MOD">https://tracker.crosswire.org/browse/MOD</a>
Best regards,
David
Sent with ProtonMail Secure Email.
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Thursday, 15 November 2018 08:23, Peter von Kaehne <a class="moz-txt-link-rfc2396E" href="mailto:refdoc@gmx.net"><refdoc@gmx.net></a> wrote:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">Dear all,
I have had yesterday the first time in a long time a serious look at
our module bug tracker - and like so many things it is not a pretty
sight.
There are currently around 138 open bugs - down from some 170 when I
started - and while many may well be valid, many others are already
overtaken by new module releases, are duplicating other bugs or are
simply silly.
While it looks like this no one in their right mind can use the bug
tracker as a invitation to get working. At the same time, many bugs are
are actually easily fixed. Dodgy conf file entries etc should take a
few minutes. Others indicate that a module needs rebuilding - and then
the search for a valid new text source needs to start.
I only worked the "first page" so far, so there is ample hunting ground
left for others.
Can I ask for some volunteer contribution to get this problem fixed?
Basically read a bug and its comments, download the module, check if it
is a valid complaint, use the tools we have (mod2imp, emptyvss,
diatheke, etc to figure out more, if you can) put a clear and well
referenced comment underneath, find a good link for new source if a
rebuild is necessary, reference that link in a comment, keep tab of
what you have done and send me an email from time to time so that I can
close bugs which are invalid. There is plenty to go round and if we can
reduce the valid bug list to say 100 or less, it may well be become a
place which is useful for work.
Thanks!
Peter
sword-devel mailing list: <a class="moz-txt-link-abbreviated" href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a>
<a class="moz-txt-link-freetext" 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
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
_______________________________________________
sword-devel mailing list: <a class="moz-txt-link-abbreviated" href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a>
<a class="moz-txt-link-freetext" 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
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
</pre>
</blockquote>
<br>
</body>
</html>