Fwd: Heads up on Extra Mile initiative

[Aurélien Gâteau]

On Tue, 4 Sep 2012 14:26:30 +0100, David Edmundson wrote:
> On Tue, Sep 4, 2012 at 12:55 PM, Aurélien Gâteau <agateau at kde.org> 
> wrote:
>> Le lundi 3 septembre 2012 16:04:31 vous avez écrit :
>>> On Mon, Sep 3, 2012 at 3:40 PM, Aurélien Gâteau <agateau at kde.org> 
>>> wrote:
>>> > Le dimanche 2 septembre 2012 14:46:59 David Edmundson a écrit :
>>> >> Started a notepad for some sort of blog/dot post about extra 
>>> mile:
>>> >> We need to get this started soon.
>>> >>
>>> >> http://quality.notes.kde.org/3
>>> >
>>> > Thanks for picking this up.
>>> >
>>> > I have been wondering how to get the initiative bootstrapped. I 
>>> thought I
>>> > would start with fixing a few extra mile bugs, so that we get 
>>> something to
>>> > report about. Do we have a reliable way to list all extramile 
>>> bugs fixed
>>> > in the last n weeks?
>>>
>>> This should do it:
>>>
>>> 
>>> https://bugs.kde.org/query.cgi?query_format=advanced&short_desc_type=allword
>>> 
>>> ssubstr&short_desc=&longdesc_type=allwordssubstr&longdesc=&bug_file_loc_type
>>> 
>>> =allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_id=&bug_i
>>> 
>>> d_type=anyexact&votes=&votes_type=greaterthaneq&emailassigned_to1=1&emailtyp
>>> 
>>> e1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailty
>>> 
>>> pe2=substring&email2=&emailtype3=substring&email3=&chfieldvalue=&chfieldfrom
>>> 
>>> =&chfieldto=Now&j_top=AND&f1=blocked&o1=equals&v1=303462&f2=noop&o2=noop&v2=
>>> 
>>> &f3=noop&o3=noop&v3=&cmdtype=doit&order=Reuse%20same%20sort%20as%20last%20ti
>>> me
>>>
>>> You'll want to edit dates and such as appropriate.
>>
>> Thanks. I actually changed it to this one:
>>
>> 
>> https://bugs.kde.org/query.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&longdesc_type=allwordssubstr&longdesc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_id=&bug_id_type=anyexact&votes=&votes_type=greaterthaneq&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&emailtype3=substring&email3=&chfieldvalue=&chfieldfrom=&chfieldto=Now&j_top=AND&f1=blocked&o1=equals&v1=303462&f2=days_elapsed&o2=lessthaneq&v2=14&f3=noop&o3=noop&v3=&f4=noop&o4=noop&v4=&cmdtype=doit&order=Reuse%20same%20sort%20as%20last%20time
>>
>> That is: using the "Days since last changed < 14" in the "Custom 
>> Search"
>> block.
>>
> That does have the problem that it will pick up any change not just
> changes where the resolution changes to fixed. Probably not a big
> deal.

True, it gives us the opportunity to mention progress on some bugs
though, even if they are not fixed yet.

>> Looking at the bug database, I see we right now have 27 reported 
>> bugs, of
>> which 7 are fixed and 1 is a duplicate. That's not much but it's a 
>> start. It's
>> not worth a dot article but I can blog about it this week.
>>
>> I propose to draft a blog post for review tomorrow and publish it on 
>> thursday.
>> This post would explain how to get this started and present these 
>> first
>> results. Does it make sense?
>
> +1 from me.
> I can get an extra bug or two fixed by then. (got one on RB already)

Cool!

> I would also like to suggest as most our changes are very visual the
> "things we've fixed" section should have lots of "before => after"
> screenshots. It will give a better example of the sort of thing we're
> setting out to fix, and it looks a lot better. They should be
> available in the review request most the time anyway.

Makes sense.

Aurélien