Plans for a Dolphin bug triage event

[Myriam Schweingruber]

Hi Frank,

On Fri, Aug 31, 2012 at 4:27 PM, Frank Reininghaus
<frank78ac at googlemail.com> wrote:
> Hi everyone,
>
> since the last Dolphin bug day [1], which was a big success and helped
> to clean up the bug database considerably, a lot of time has passed.
> Many new bug reports were filed, and many changes have been made in
> Dolphin's code base, which means that some of the old bug reports
> might not be valid any more. Therefore, I think it's time for another
> collective bug triage event. Jekyll does a fantastic bug triaging job,
> but there are so many open bug reports that any help will be greatly
> appreciated, I think :-)
>
> My goals for a bug triage event are mainly:
>
> 1. Close reports that are not valid any more.
> 2. Assign all reports in the 'general' component to more meaningful components.
> 3. Mark all reports that contain simple steps to reproduce the issue
> reliably with the 'reproduceable' keyword.
> 4. Provide a starting point for KDE users who would like to contribute
> to Dolphin or KDE in general.

May I add one important point:

5. Attribute versions to all open Konqueror bugs.

Currently there are 391 open Konqueror reports with no version set.
Those bugs are hard to track if there is no version field, so I think
if there is a bug triaging event happening these should be first
cleared and have versions set (or be closed as outdated as some are
probably pre-KDE 4.6).

I am usually around to give a hand, but since I am only a triager it
would be good to have a developer around.

As for using the forum: this is a very good idea, but since the forum
is an asynchronous media you would need more time than just a weekend,
usually a week is more useful. I think it is also a good idea to
combine the media: do a bug week in the forum which ends with a bug
squashing weekend on IRC.

Regards, Myriam
-- 
Proud member of the Amarok and KDE Community
Protect your freedom and join the Fellowship of FSFE:
http://www.fsfe.org
Please don't send me proprietary file formats,
use ISO standard ODF instead (ISO/IEC 26300)