[sword-devel] Module bug tracker - volunteer(s) needed

[Cyrille]

Le 15/11/2018 à 14:54, Greg Hellings a écrit :
> 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.
>
This is a good idea! I propose gitlab...
> 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.
>
> --Greg
>
> On Thu, Nov 15, 2018 at 2:24 AM Peter von Kaehne <refdoc at gmx.net
> <mailto:refdoc at gmx.net>> wrote:
>
>     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: sword-devel at crosswire.org
>     <mailto:sword-devel at crosswire.org>
>     http://www.crosswire.org/mailman/listinfo/sword-devel
>     Instructions to unsubscribe/change your settings at above page
>
>
>
> _______________________________________________
> sword-devel mailing list: sword-devel at crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.crosswire.org/pipermail/sword-devel/attachments/20181115/949f37e5/attachment.html>