How to mark bugs - was - Re: Some interesting info while researching mkisofs

[Jeremy Whiting]

Yep, I sent my reply, then thought a page on community would be easier
to find and have more audience, so suggested that on irc instead. Good
idea.

On Sat, Sep 27, 2014 at 8:14 AM, Albert Astals Cid <aacid at kde.org> wrote:
> El Divendres, 26 de setembre de 2014, a les 17:47:08, Jeremy Whiting va
> escriure:
>> Ah, good point, I was thinking we would sort the bug search by date
>> modified and see those that had our comments at the top. Maybe putting
>> a url of each bug on the kanban task would be good though.
>
> Right, but that's "hard" to sell, i want something i can point someone that is
> bored and he can see something to do in 5 seconds, maybe as you mentioned a
> wiki in community where we store the "curated shortlist" of bugs?
>
> Cheers,
>   Albert
>
>>
>> BR,
>> Jeremy
>>
>> On Fri, Sep 26, 2014 at 5:40 PM, Albert Astals Cid <aacid at kde.org> wrote:
>> > El Divendres, 26 de setembre de 2014, a les 17:21:14, Jeremy Whiting va
>> >
>> > escriure:
>> >> I thought we would just add a comment to the bug itself (and maybe
>> >> mark it as confirmed, or assigned etc.)
>> >
>> > But that doesn't help external people finding it, i want to have a place i
>> > can point other gardeners for the bug, and what are they going to do, go
>> > to the list again searching for comments on bugs saying that's an easy
>> > bug?
>> >
>> > Doesn't sound something like someone would do if they have 30 min free and
>> > want to try something.
>> >
>> > Cheers,
>> >
>> >   Albert
>> >>
>> >> On Fri, Sep 26, 2014 at 4:59 PM, Albert Astals Cid <aacid at kde.org> wrote:
>> >> > El Divendres, 26 de setembre de 2014, a les 12:22:51, Scarlett Clark va
>> >> >
>> >> > escriure:
>> >> >> On Friday, September 26, 2014 12:57:52 PM Jeremy Whiting wrote:
>> >> >> > My first thought for going through the list in a distributed manner
>> >> >> > is
>> >> >> > to use the list itself? Maybe we could filter on last comment, and
>> >> >> > as
>> >> >> > we investigate each one, leave a comment in the bug itself saying
>> >> >> > what
>> >> >> > we think of it? If we want to keep the investigation separate from
>> >> >> > the
>> >> >> > bugs themselves (to not generate a bunch of bugzilla e-mails or
>> >> >> > something) notes.kde.org would work with bug numbers and such.
>> >> >>
>> >> >> I think we should go through the actual bugs, so we all know what bugs
>> >> >> have
>> >> >> what progress and not repeating effort. Plus it shows activity to the
>> >> >> users. Scarlett
>> >> >
>> >> > But how do we mark bugs?
>> >> >
>> >> > e.g. https://bugs.kde.org/show_bug.cgi?id=337428 seems like it would
>> >> > one
>> >> > of
>> >> > the "easy ones" to fix, where do i had it? the kanboard?
>> >> >
>> >> > Cheers,
>> >> >
>> >> >   Albert
>> >> >
>> >> > _______________________________________________
>> >> > Kde-gardening mailing list
>> >> > Kde-gardening at kde.org
>> >> > https://mail.kde.org/mailman/listinfo/kde-gardening
>> >>
>> >> _______________________________________________
>> >> Kde-gardening mailing list
>> >> Kde-gardening at kde.org
>> >> https://mail.kde.org/mailman/listinfo/kde-gardening
>> >
>> > _______________________________________________
>> > Kde-gardening mailing list
>> > Kde-gardening at kde.org
>> > https://mail.kde.org/mailman/listinfo/kde-gardening
>>
>> _______________________________________________
>> Kde-gardening mailing list
>> Kde-gardening at kde.org
>> https://mail.kde.org/mailman/listinfo/kde-gardening
>
> _______________________________________________
> Kde-gardening mailing list
> Kde-gardening at kde.org
> https://mail.kde.org/mailman/listinfo/kde-gardening