[Kolab-devel] How to get Kolab server patches accepted / issues resolved? (was: Re: [issue4496] off by one error in RSS feeds on portal page (number of articles to display))

[Gunnar Wrobel]

Hi Gavin,

Quoting Gavin McCullagh <gavin.mccullagh at gcd.ie>:

> Hi,
>
> On Mon, 16 Aug 2010, Gavin McCullagh wrote:
>
>> New submission from Gavin McCullagh <gavin.mccullagh at gcd.ie>:
>>
>> If you add an RSS feed to the portal page in Kolab v2.2.4 (and v2.2.3), and
>> specify N articles to be displayed, you will get N+1 articles displayed.
>
> I've submitted a patch to fix this.
>
> 	https://issues.kolab.org/issue4496
>
> is there some process to get this approved/accepted?

The are different possibilities how you can get stuff like this in.

1) Wait

    At some point somebody (probably me) will look at the issue and try to
    resolve it.

    Problem: This make take quite a while (maybe years) especially if the bug
    does not have a high priority.

    issue4496: I classified issue4496 as "minor" and as long
    as we have stuff that is "critical" or "urgent" it is unlikely that we find
    the time to resolve the issue.

2) Try to get a higher priority

    The higher the priority the faster the process.

    Problem: Depends on the nature of the issue.

    issue4496: Not very likely for the problem described in issue4496.

3) Try upstream

    Check if the same bug exists upstream and try to report the bug there.

    Problem: As we use sometimes use modified upstream packages for the Kolab
    server this can be difficult. The upstream devs might not be able to
    reproduce the problem and simply reject the report. The problem might also
    already have been solved upstream and we are just too slow to pick it up.
    And finally it might take quite some time until the Kolab server ships with
    the new version.

    issue4496: In case of issue4496 the first two problems probably do not
    apply. The issue does not affect Kolab specific functionality and the code
    remains unchanged even in the Horde Git repository  
(http://git.horde.org/co.php/horde/lib/Block/feed.php?r=fabc7e43b5dc1d9e651f5a343eb49266e46a0b63)

4) Write to the mailing list

    Try to discuss the issue further on the Kolab development mailing list. As
    we usually ensure that most messages are being answered chances  
are high that
    somebody takes the time to look at the problem even if it has low priority.

    Problem: It takes some effort/time to write the mails and there is no
    guarantee that it helps.

    issue4496: Well, you actually did choose this way of action. And I took the
    time to check if the problem persist in Horde upstream. So in  
contrary to my
    last comment in issue4496 (https://issues.kolab.org/msg26061) I  
can now tell
    you to go upstream and submit a bug report there.

5) Pay Kolab Systems for getting the issue resolved.

    Pretty much guaranteed to work.

    Problem: Costs money.

    issue4496: As this wouldn't be much work (probably less than writing this
    long mail) it wouldn't cost much :)

Of course the small issue does not warrant such a long mail. But I  
felt it was necessary to explain the process of how we currently  
handle issue reports again.

Cheers,

Gunnar

>
> Gavin
>
> _______________________________________________
> Kolab-devel mailing list
> Kolab-devel at kolab.org
> https://kolab.org/mailman/listinfo/kolab-devel
>



-- 
____ http://www.pardus.de _________________ http://gunnarwrobel.de _

E-mail : p at rdus.de                                 Dr. Gunnar Wrobel
Tel.   : +49 700 6245 0000                         Bundesstrasse 29
Fax    : +49 721 1513 52322                        D-20146 Hamburg
--------------------------------------------------------------------
    >> Mail at ease - Rent a kolab groupware server at p at rdus <<
--------------------------------------------------------------------