Re: To Understand and Improve GNOME Bug Workflow

shin zhu <[email protected]> Sat, 14 Nov 2015 13:22:06 +0800
Newsgroups gmane.comp.gnome.bugsquad,gmane.comp.gnome.general
Message-ID <CAKQMixfakQXYN0N_u07-zsjCZ4LC=rL-63+UbfMqruj29dyerQ@mail.gmail.com>
--===============6170622270718198233==
Content-Type: multipart/alternative; boundary=001a11396b6a6714b80524795b30

--001a11396b6a6714b80524795b30
Content-Type: text/plain; charset=UTF-8

Andre, many thanks for the comments and stories, very helpful.

Yes, the term "service quality" means time to respond to / fix an issue.
We are considering to describe it in a more proper and straightforward way
:)

Regards,
Jiaxin


2015-11-14 0:43 GMT+08:00 Andre Klapper <[email protected]>:

> On Sat, 2015-11-14 at 00:20 +0800, shin zhu wrote:
> > We designed a tool which visualizes historical issue tracking
> > (Bugzilla) data
> > to support analysis of issue status workflow, such as identification of
> different
> > workflows in the past and evaluation of their effectiveness.
> >
> > For more information about the tool, please visit
> https://passion-lab.org/pee.php.
> > To download and install the tool, please refer to
> https://passion-lab.org/subtopic/pee_sbsg.php.
> > A quick start guide is attached in this email,
> > and here is an online demo video:
> https://www.youtube.com/watch?v=fXitsaDFtzU.
> >
> > We invite you to have a look at the tool, have a try and give your
> comments or
> > reviews to help us to evaluate and improve it.
> > For example, consider the following questions:
> > does it make it easier to look at the historical issue workflow?
> > do you discover something that you have not been aware of before?
> > do you come up with some ideas about the issue maintenance or other
> effort
> > related to issues.
>
> The video is interesting, thank you for sharing it!
>
> The workflow change in 2007 to bypass NEEDINFO was discussed here:
> https://mail.gnome.org/archives/gnome-bugsquad/2007-April/thread.html
> ...and it's good to see that it really saved triagers some time.
>
> The large number of incoming bug reports in late 2006 was also covered
> here with a potential explanation:
> https://blogs.gnome.org/aklapper/2006/11/30/bug-flood-2/
>
> Bug-Buddy got deprecated in the late GNOME 2.x days as automated crash
> reporting became more and more a distribution-level thing.
>
> I was not always entirely sure what the term "service quality" meant.
> It seems to be used like "time to respond"?
>
> Cheers,
> andre
> --
> Andre Klapper  |  [email protected]
> http://blogs.gnome.org/aklapper/
>
>
>

--001a11396b6a6714b80524795b30
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><br></div><div>Andre, many thanks for the comments an=
d=C2=A0stories, very helpful.</div><div>=C2=A0</div><div>Yes, the term &quo=
t;service quality&quot; means time to respond to / fix an issue.</div><div>=
We are considering to describe it in a more proper and straightforward way =
:)</div><div><br></div><div>Regards,</div><div>Jiaxin</div><div><br></div><=
/div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">2015-11-14 0=
:43 GMT+08:00 Andre Klapper <span dir=3D"ltr">&lt;<a href=3D"mailto:ak-47@g=
mx.net" target=3D"_blank">[email protected]</a>&gt;</span>:<br><blockquote clas=
s=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;pad=
ding-left:1ex"><span class=3D"">On Sat, 2015-11-14 at 00:20 +0800, shin zhu=
 wrote:<br>
&gt; We designed a tool which visualizes historical issue tracking<br>
&gt; (Bugzilla) data<br>
&gt; to support analysis of issue status workflow, such as identification o=
f different<br>
&gt; workflows in the past and evaluation of their effectiveness.<br>
&gt;<br>
&gt; For more information about the tool, please visit <a href=3D"https://p=
assion-lab.org/pee.php" rel=3D"noreferrer" target=3D"_blank">https://passio=
n-lab.org/pee.php</a>.<br>
&gt; To download and install the tool, please refer to <a href=3D"https://p=
assion-lab.org/subtopic/pee_sbsg.php" rel=3D"noreferrer" target=3D"_blank">=
https://passion-lab.org/subtopic/pee_sbsg.php</a>.<br>
&gt; A quick start guide is attached in this email,<br>
&gt; and here is an online demo video: <a href=3D"https://www.youtube.com/w=
atch?v=3DfXitsaDFtzU" rel=3D"noreferrer" target=3D"_blank">https://www.yout=
ube.com/watch?v=3DfXitsaDFtzU</a>.<br>
&gt;<br>
&gt; We invite you to have a look at the tool, have a try and give your com=
ments or<br>
&gt; reviews to help us to evaluate and improve it.<br>
&gt; For example, consider the following questions:<br>
&gt; does it make it easier to look at the historical issue workflow?<br>
&gt; do you discover something that you have not been aware of before?<br>
&gt; do you come up with some ideas about the issue maintenance or other ef=
fort<br>
&gt; related to issues.<br>
<br>
</span>The video is interesting, thank you for sharing it!<br>
<br>
The workflow change in 2007 to bypass NEEDINFO was discussed here:<br>
<a href=3D"https://mail.gnome.org/archives/gnome-bugsquad/2007-April/thread=
.html" rel=3D"noreferrer" target=3D"_blank">https://mail.gnome.org/archives=
/gnome-bugsquad/2007-April/thread.html</a><br>
...and it&#39;s good to see that it really saved triagers some time.<br>
<br>
The large number of incoming bug reports in late 2006 was also covered<br>
here with a potential explanation:<br>
<a href=3D"https://blogs.gnome.org/aklapper/2006/11/30/bug-flood-2/" rel=3D=
"noreferrer" target=3D"_blank">https://blogs.gnome.org/aklapper/2006/11/30/=
bug-flood-2/</a><br>
<br>
Bug-Buddy got deprecated in the late GNOME 2.x days as automated crash<br>
reporting became more and more a distribution-level thing.<br>
<br>
I was not always entirely sure what the term &quot;service quality&quot; me=
ant.<br>
It seems to be used like &quot;time to respond&quot;?<br>
<br>
Cheers,<br>
andre<br>
<span class=3D"HOEnZb"><font color=3D"#888888">--<br>
Andre Klapper=C2=A0 |=C2=A0 <a href=3D"mailto:[email protected]">[email protected]<=
/a><br>
<a href=3D"http://blogs.gnome.org/aklapper/" rel=3D"noreferrer" target=3D"_=
blank">http://blogs.gnome.org/aklapper/</a><br>
<br>
<br>
</font></span></blockquote></div><br></div>

--001a11396b6a6714b80524795b30--

--===============6170622270718198233==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
gnome-bugsquad mailing list
[email protected]
https://mail.gnome.org/mailman/listinfo/gnome-bugsquad

--===============6170622270718198233==--