Re: [Openvpn-devel] Bug Handling

[Eric Crist]

On Jul 8, 2013, at 08:20:05, Samuli Seppänen  wrote:

> 
>> Hi,
>> 
>> On Sun, Jun 30, 2013 at 10:32:31PM +0200, Max Muster wrote:
>>> So maybe it would be a simple idea to think of a switch in "bug
>>> handling". Why not simply use this list as "#1 input" for bug reports.
>> This list isn't always working better or quicker...  it really comes down
>> to whoever has time to go through open issues.  (We *do* have plans to
>> improve the ticket handling...)
>> 
>> So - as I said before, things have improved as far as community involvement
>> and feedback goes, but still have quite a way to go.  Working on it.
>> 
>> gert
> 
> I think it would probably make sense to configure Trac to send
> notifications of new tickets to this list. Although it would not
> increase the time at our hands, it would at the very least keep us
> updated on new issues. I'm also hoping that it would encourage others
> outside the current core developer team to review the new bug reports.
> I've reviewed quite a few bug reports in the past, and many of them seem
> to be simple configuration errors or based on misunderstandings. These
> non-valid bug reports could be fairly easily be filtered out by people
> who would not normally participate in writing OpenVPN code.
> 
> Looking at the past record of new bug reports[1] we could expect maybe
> 0-3 new tickets each week. Would this amount of extra mails be acceptable?


I think it's more than acceptable.  Anyone interested in working on bug reports 
is welcome to do so.  Either Samuli or myself can grant them the needed 
permissions in Trac.

-
Eric F Crist

Re: [Openvpn-devel] Bug Handling

[Samuli Seppänen]

> Hi,
>
> On Sun, Jun 30, 2013 at 10:32:31PM +0200, Max Muster wrote:
>> So maybe it would be a simple idea to think of a switch in "bug
>> handling". Why not simply use this list as "#1 input" for bug reports.
> This list isn't always working better or quicker...  it really comes down
> to whoever has time to go through open issues.  (We *do* have plans to
> improve the ticket handling...)
>
> So - as I said before, things have improved as far as community involvement
> and feedback goes, but still have quite a way to go.  Working on it.
>
> gert

I think it would probably make sense to configure Trac to send
notifications of new tickets to this list. Although it would not
increase the time at our hands, it would at the very least keep us
updated on new issues. I'm also hoping that it would encourage others
outside the current core developer team to review the new bug reports.
I've reviewed quite a few bug reports in the past, and many of them seem
to be simple configuration errors or based on misunderstandings. These
non-valid bug reports could be fairly easily be filtered out by people
who would not normally participate in writing OpenVPN code.

Looking at the past record of new bug reports[1] we could expect maybe
0-3 new tickets each week. Would this amount of extra mails be acceptable?

-- 
Samuli Seppänen
Community Manager
OpenVPN Technologies, Inc

irc freenode net: mattock

[1]