[sword-devel] Module bug tracker - volunteer(s) needed
dfhdfh at protonmail.com
Sat Dec 1 02:38:40 MST 2018
If anyone is volunteering, modules issues are tracked at
Sent with ProtonMail Secure Email.
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Thursday, 15 November 2018 08:23, Peter von Kaehne <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
> 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.
> sword-devel mailing list: sword-devel at crosswire.org
> Instructions to unsubscribe/change your settings at above page
More information about the sword-devel