<div dir="ltr">Do we have a standard repository set from which the conf files are pulled? For instance, it would be great if all our module sources were available in dedicated repositories so that if a volunteer found a valid bug in, eg, a conf file they could submit a PR or patch to the appropriate repository, you could review it and merge it, and the new module release could be fired off automatically.<div><br></div><div>Obviously each module would need to have its own, slightly different, script file that would point to its upstream text source for those modules we don't maintain the original copies of. I'd be happy to help with setting this process up so it can be completely automatic for you in the future. I'm waiting for Troy to restore the Jenkins config (I broke the permissions access back in the Spring and can't fix them, because one of the permissions I messed up is the permission to change permissions), but that would be an ideal place to put automation surrounding the module build process.</div><div><br></div><div>--Greg</div></div><br><div class="gmail_quote"><div dir="ltr">On Thu, Nov 15, 2018 at 2:24 AM Peter von Kaehne <<a href="mailto:refdoc@gmx.net">refdoc@gmx.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Dear all, <br>
<br>
I have had yesterday the first time in a long time a serious look at<br>
our module bug tracker - and like so many things it is not a pretty<br>
sight. <br>
<br>
There are currently around 138 open bugs - down from some 170 when I<br>
started - and while many may well be valid, many others are already<br>
overtaken by new module releases, are duplicating other bugs or are<br>
simply silly. <br>
<br>
While it looks like this no one in their right mind can use the bug<br>
tracker as a invitation to get working. At the same time, many bugs are<br>
are actually easily fixed. Dodgy conf file entries etc should take a<br>
few minutes. Others indicate that a module needs rebuilding - and then<br>
the search for a valid new text source needs to start. <br>
<br>
I only worked the "first page" so far, so there is ample hunting ground<br>
left for others. <br>
<br>
Can I ask for some volunteer contribution to get this problem fixed? <br>
<br>
Basically read a bug and its comments, download the module, check if it<br>
is a valid complaint, use the tools we have (mod2imp, emptyvss,<br>
diatheke, etc to figure out more, if you can) put a clear and well<br>
referenced comment underneath, find a good link for new source if a<br>
rebuild is necessary, reference that link in a comment, keep tab of<br>
what you have done and send me an email from time to time so that I can<br>
close bugs which are invalid. There is plenty to go round and if we can<br>
reduce the valid bug list to say 100 or less, it may well be become a<br>
place which is useful for work. <br>
<br>
Thanks!<br>
<br>
Peter <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>