2:32 a.m.
As some of you may have heard over in Bugzappers we are developing
some metrics applications for bugzilla to help us recognize testers,
developers, and other contributors to the project. This is the first
week that we are semi confident that the results are correct, although
there is some concern we are missing some of the bugs causing the
count to be low. If any of you see something that looks wrong let me
know and I will try to track down the issue. Also if there is
information that you would like in this report that is not in here
already let me know and we can see about adding it.
==Top 5 Triagers==
(score is the total number instances where the user has changed any
one of these states: NEW, VERIFIED, MODIFIED, ASSIGNED, CLOSED, POST,
needinfo?)
Steven M. Parrish 133
Matej Cepl 62
Adam Williamson 16
Thomas Janssen 10
Jon Dufresne 4
Paul W. Frields 4
==Top 5 Bug Closers==
Steven M. Parrish 49
Chris Lumens 21
Jens Petersen 14
Michael Schwendt 13
Matej Cepl 12
Lillian Angel 12
==Top 5 Bug Reporters==
Rahul Sundaram 59
Vitezslav Crhonek 13
Gerry Reno 13
Xose Vazquez Perez 10
Tomas Hoger 10
Jussi Lehtola 10
==Top 5 Components Closing Bugs==
inn 18
kdemultimedia 11
avahi 9
sblim-cmpi-base 8
kdebase-workspace 7
Package Review 7
There is much more information that can be pulled via a turbogrears
app we are running. But I am looking to see what is useful in terms
of a weekly report. I have the date tuesday to tuesday as it matches
up with the Bugzappers meeting time.
Best Regards,
Brennan Ashton
3:38 a.m.
On 06/02/2009 07:32 AM, Brennan Ashton wrote:
As some of you may have heard over in Bugzappers we are developing
some metrics applications for bugzilla to help us recognize testers,
developers, and other contributors to the project. This is the first
week that we are semi confident that the results are correct, although
there is some concern we are missing some of the bugs causing the
count to be low. If any of you see something that looks wrong let me
know and I will try to track down the issue. Also if there is
information that you would like in this report that is not in here
already let me know and we can see about adding it.
Great work..
Is it possible to get a wiki page that explains a bit how these
statistics are generated?
Are you filtering maintainers from reporters/triagers ?
Corresponding IRC names would be nice addon.
Release seperation would be nice ( F10, F11, Rawhide )
That would probably mean three different statistic reports.
Instead of top 5 what about "This weeks" "Overall" and
"Top"
of course per release.
==Top 5 Bug Closers==
Does this list contain maintainers or triagers that are closing bugs
or both? If both should it not just only contain maintainers ?
==Top 5 Components Closing Bugs==
I would like to see detail list here ( all not just top ) along with how
they were resolved
( FIXED/WONTFIX/NOTABUG )
Another thing that would be lovely is a talking to infra and getting an
web space that
contains a web page that automatically generates Statistics charts (
rrdtools ) for these
statistics.
Using the wiki to host this is not the way to go ( refeering to
http://fedoraproject.org/wiki/Statistics ).
JBG
8:24 a.m.
2009/6/2 "Jóhann B. Guðmundsson" <johannbg(a)hi.is>:
On 06/02/2009 07:32 AM, Brennan Ashton wrote:
>
> As some of you may have heard over in Bugzappers we are developing
> some metrics applications for bugzilla to help us recognize testers,
> developers, and other contributors to the project. This is the first
> week that we are semi confident that the results are correct, although
> there is some concern we are missing some of the bugs causing the
> count to be low. If any of you see something that looks wrong let me
> know and I will try to track down the issue. Also if there is
> information that you would like in this report that is not in here
> already let me know and we can see about adding it.
>
Great work..
Is it possible to get a wiki page that explains a bit how these statistics
are generated?
Are you filtering maintainers from reporters/triagers ?
Corresponding IRC names would be nice addon.
That is a simple addon, I already link to FAS with the scripts, so if
the IRC nick is in there I can show it.
Release seperation would be nice ( F10, F11, Rawhide )
That would probably mean three different statistic reports.
Instead of top 5 what about "This weeks" "Overall" and
"Top"
of course per release.
I think that could be done, in fact I think I am already putting that
information in the database. This might be a feature that is a little
further down the road.
> ==Top 5 Bug Closers==
>
Does this list contain maintainers or triagers that are closing bugs
or both? If both should it not just only contain maintainers ?
This is both, what
would be hard about taking out the triagers is that
there are people like me who are both. How would you like to see that
handled?
> ==Top 5 Components Closing Bugs==
>
>
I would like to see detail list here ( all not just top ) along with how
they were resolved
( FIXED/WONTFIX/NOTABUG )
Interesting. That might be useful information, and I do
not think it
would be too hard to add, this is another one that would be down the
road though.
Another thing that would be lovely is a talking to infra and getting an web
space that
contains a web page that automatically generates Statistics charts (
rrdtools ) for these
statistics.
Using the wiki to host this is not the way to go ( refeering to
http://fedoraproject.org/wiki/Statistics ).
And I totally agree, right now this web page is not user friendly,
and there are some magic keywords that are not documented this will
change in the next month, as I add search forms and the like.
http://publictest14.fedoraproject.org/triageweb/
Note that the bottom three links on that page do not work.
if you want to limit a report to a certain time frame use these
variables in the url like /triagers?start=2009-06-01&end=2009-06-02
The stats are updated every day at 3:00 UTC
JBG
--
fedora-test-list mailing list
fedora-test-list(a)redhat.com
To unsubscribe:
https://www.redhat.com/mailman/listinfo/fedora-test-list
I hope that helps fill in some missing gaps,
Best Regards,
Brennan Ashton
10:29 a.m.
On Tue, 2009-06-02 at 06:24 -0700, Brennan Ashton wrote:
It is a bit hard to understand the graph on this page. Is it trying to
represent the number of bugs changed _to_ NEW, CLOSED, etc.? Wouldn't
it be more useful to see the number of bugs outstanding in a particular
state on a particular day, so we could see whether the overall count is
trending up or down?
Also, the graph is a bit hard to read. It's blurry, the text is rather
small, and the data points are not align with the grid's vertical lines.
-B.
12:18 p.m.
On Tue, 2009-06-02 at 11:29 -0400, Christopher Beland wrote:
On Tue, 2009-06-02 at 06:24 -0700, Brennan Ashton wrote:
> http://publictest14.fedoraproject.org/triageweb/
It is a bit hard to understand the graph on this page. Is it trying to
represent the number of bugs changed _to_ NEW, CLOSED, etc.? Wouldn't
it be more useful to see the number of bugs outstanding in a particular
state on a particular day, so we could see whether the overall count is
trending up or down?
Also, the graph is a bit hard to read. It's blurry, the text is rather
small, and the data points are not align with the grid's vertical lines.
Brennan would love to have bug reports and suggestions at:
https://fedorahosted.org/triage
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org
http://www.happyassassin.net
12:41 a.m.
On Tue, 2009-06-02 at 10:18 -0700, Adam Williamson wrote:
On Tue, 2009-06-02 at 11:29 -0400, Christopher Beland wrote:
> On Tue, 2009-06-02 at 06:24 -0700, Brennan Ashton wrote:
> > http://publictest14.fedoraproject.org/triageweb/
>
> It is a bit hard to understand the graph on this page. Is it trying to
> represent the number of bugs changed _to_ NEW, CLOSED, etc.? Wouldn't
> it be more useful to see the number of bugs outstanding in a particular
> state on a particular day, so we could see whether the overall count is
> trending up or down?
>
> Also, the graph is a bit hard to read. It's blurry, the text is rather
> small, and the data points are not align with the grid's vertical lines.
Brennan would love to have bug reports and suggestions at:
https://fedorahosted.org/triage
I am unable to file any reports there. My Fedora Infrastructure login
does not work, and I do not see any way to register for an account
there.
-B.
1:03 a.m.
On Wed, Jun 3, 2009 at 10:41 PM, Christopher Beland <beland(a)alum.mit.edu> wrote:
On Tue, 2009-06-02 at 10:18 -0700, Adam Williamson wrote:
> On Tue, 2009-06-02 at 11:29 -0400, Christopher Beland wrote:
> > On Tue, 2009-06-02 at 06:24 -0700, Brennan Ashton wrote:
> > > http://publictest14.fedoraproject.org/triageweb/
> >
> > It is a bit hard to understand the graph on this page. Is it trying to
> > represent the number of bugs changed _to_ NEW, CLOSED, etc.? Wouldn't
> > it be more useful to see the number of bugs outstanding in a particular
> > state on a particular day, so we could see whether the overall count is
> > trending up or down?
> >
> > Also, the graph is a bit hard to read. It's blurry, the text is rather
> > small, and the data points are not align with the grid's vertical lines.
>
> Brennan would love to have bug reports and suggestions at:
>
> https://fedorahosted.org/triage
I am unable to file any reports there. My Fedora Infrastructure login
does not work, and I do not see any way to register for an account
there.
-B.
You do use your fas login to report bugs, there is nothing in the
settings on my end that would keep you from logging in. I would check
with infrastructure, if you are sure you are typing your
username/password combo correctly.
Brennan Ashton
1:59 a.m.
New subject: Fedora Infrastructure logins (was: Fedora Bugzilla Statistics 2009-05-26 - 2009-06-01)
You do use your fas login to report bugs, there is nothing in the
settings on my end that would keep you from logging in. I would check
with infrastructure, if you are sure you are typing your
username/password combo correctly.
Blarg.
To log into bugzilla.redhat.com, I *must* use my email address, but to
log into Trac there, I *must not* use my email address - it requires my
username, "beland". This is not very user-friendly, especially since
there is no link to any registration page.
It also doesn't seem very nice to disallow anonymous bug reporting, but
I guess that's a policy decision.
-B.
2:07 a.m.
New subject: Fedora Infrastructure logins (was: Fedora Bugzilla Statistics 2009-05-26 - 2009-06-01)
On Thu, Jun 04, 2009 at 02:59:09 -0400,
Christopher Beland <beland(a)alum.mit.edu> wrote:
To log into bugzilla.redhat.com, I *must* use my email address, but to
log into Trac there, I *must not* use my email address - it requires my
username, "beland". This is not very user-friendly, especially since
there is no link to any registration page.
I think people are generally agreed that allowing fas logins in bugzilla
would be a nice feature. It is just a small convenience though, so it
isn't going to be a high priority item.
It also doesn't seem very nice to disallow anonymous bug
reporting, but
I guess that's a policy decision.
I think the feeling is here is that anonymous bug reports don't provide
a way to contact the reporter for more information and hence aren't
all that valuable.
8:27 a.m.
New subject: Fedora Infrastructure logins (was: Fedora Bugzilla Statistics 2009-05-26 - 2009-06-01)
On Thu, Jun 4, 2009 at 12:07 AM, Bruno Wolff III <bruno(a)wolff.to> wrote:
On Thu, Jun 04, 2009 at 02:59:09 -0400,
Christopher Beland <beland(a)alum.mit.edu> wrote:
>
> To log into bugzilla.redhat.com, I *must* use my email address, but to
> log into Trac there, I *must not* use my email address - it requires my
> username, "beland". This is not very user-friendly, especially since
> there is no link to any registration page.
I think people are generally agreed that allowing fas logins in bugzilla
would be a nice feature. It is just a small convenience though, so it
isn't going to be a high priority item.
> It also doesn't seem very nice to disallow anonymous bug reporting, but
> I guess that's a policy decision.
I think the feeling is here is that anonymous bug reports don't provide
a way to contact the reporter for more information and hence aren't
all that valuable.
Well I can re enable that but I got sick of deleting spam from trac.
9:42 a.m.
New subject: Fedora Infrastructure logins (was: Fedora Bugzilla Statistics 2009-05-26 - 2009-06-01)
On Thu, 2009-06-04 at 02:59 -0400, Christopher Beland wrote:
To log into bugzilla.redhat.com, I *must* use my email address, but
to
log into Trac there, I *must not* use my email address - it requires my
username, "beland". This is not very user-friendly, especially since
there is no link to any registration page.
Bugzilla is one (the one?) service that does not use your FAS name.
We'd like to fix that, but it's going to be difficult.
It also doesn't seem very nice to disallow anonymous bug reporting, but
I guess that's a policy decision.
Anonymous bug reporting led to massive amounts of spam as bug reports.
--
Jesse Keating
Fedora -- Freedom² is a feature!
identi.ca: http://identi.ca/jkeating
12:18 p.m.
New subject: Fedora Infrastructure logins (was: Fedora Bugzilla Statistics 2009-05-26 - 2009-06-01)
Well, it would be nice to at least have a link on the Trac page that
directs people to where they can sign up for an account if they don't
have one, and mention on the help page what username you need to log in.
-B.
12:35 p.m.
New subject: Fedora Infrastructure logins (was: Fedora Bugzilla Statistics 2009-05-26 - 2009-06-01)
On Thu, 2009-06-04 at 13:18 -0400, Christopher Beland wrote:
Well, it would be nice to at least have a link on the Trac page that
directs people to where they can sign up for an account if they don't
have one, and mention on the help page what username you need to log in.
-B.
Patches would be welcome. I have no idea where to hack that into Trac.
--
Jesse Keating
Fedora -- Freedom² is a feature!
identi.ca: http://identi.ca/jkeating
4:52 p.m.
New subject: Fedora Infrastructure logins (was: Fedora Bugzilla Statistics 2009-05-26 - 2009-06-01)
On Jun 4, 2009, at 10:35, Jesse Keating <jkeating(a)redhat.com> wrote:
On Thu, 2009-06-04 at 13:18 -0400, Christopher Beland wrote:
> Well, it would be nice to at least have a link on the Trac page that
> directs people to where they can sign up for an account if they don't
> have one, and mention on the help page what username you need to
> log in.
>
> -B.
Patches would be welcome. I have no idea where to hack that into
Trac.
--
Jesse Keating
Fedora -- Freedom² is a feature!
identi.ca: http://identi.ca/jkeating
--
fedora-test-list mailing list
fedora-test-list(a)redhat.com
To unsubscribe:
https://www.redhat.com/mailman/listinfo/fedora-test-list
One solution that could be simple would be to patch the apache conf
for the login message to display the info there. I do that with a
local copy of trac I run.
Regards,
Brennan Ashton
4:56 a.m.
New subject: Fedora Infrastructure logins (was: Fedora Bugzilla Statistics 2009-05-26 - 2009-06-01)
Jesse Keating, Thu, 04 Jun 2009 10:35:36 -0700:
Patches would be welcome. I have no idea where to hack that into
Trac.
Trac has plugin for OpenID. Now, somebody should write one for
bugzilla ;-).
Matěj
4:55 a.m.
New subject: Fedora Infrastructure logins (was: Fedora Bugzilla Statistics 2009-05-26 - 2009-06-01)
Christopher Beland, Thu, 04 Jun 2009 02:59:09 -0400:
To log into bugzilla.redhat.com, I *must* use my email address, but
to
log into Trac there, I *must not* use my email address - it requires my
username, "beland". This is not very user-friendly, especially since
there is no link to any registration page.
We really should switch our whole infrastructure to OpenID. /Somebody/
should do it ;-).
Matěj
5500
days inactive
5503
days old
16 comments
8 participants
participants (8)
-
"Jóhann B. Guðmundsson" -
Adam Williamson -
Brennan Ashton -
Bruno Wolff III -
Christopher Beland -
Jesse Keating -
Kevin Kofler -
Matej Cepl