Bugs

The GNOME Women group is holding its first Bug Day! All are welcome to join in the fun:

Date: Saturday, January 28th
Time: 9 AM - 9 PM EST
Location: #bugs on irc.gnome.org
Bug Topic: TBD

Bugday Masters: Christian Kirbach (nazgul), Luis Villa (luis)
Deputies: Olav Vitters (bkor), Guilherme Pastore (fatalerror)
Gnome Women Hosts: Máirín Duffy (mizmo), Christine Spang (christine)

(For more details about bug days, see: http://live.gnome.org/Bugsquad/BugDays)

Our much beloved bugzilla is getting a face lift this upcoming week. Those wanting a sneak peak at Olav Vitters' incredible work can point their browsers at http://bugzilla-test.gnome.org/.

The bugmaster has spoken:

Bug day tomorrow. Goal: find showstoppers. If you come to IRC tomorrow, and you can find something embarassing in GNOME 2.11 or in bugzilla that is worth stopping 2.12 for... well, I'll do something. Probably that embarasses me and (hopefully) that makes you happy. Or something. (In the past I have literally eaten portions of my boxers. I hope not to have to do that tomorrow, but you never know. And if you're not in IRC, you'll miss it...) More details below the fold.

A new bug day will happen tomorrow. Everyone should come, especially since Luis should hug everyone who joins #bugs.

The focus will be on UNCONFIRMED bugs: we'll try to read them all, and mark them as NEEDINFO, or confirm them, or close them. It's not hard. Everyone can do it and is welcome to do it.

Tomorrow's bug day will occur at the usual place (#bugs on irc.gnome.org) at the usual time (1500GMT->0300GMT) tomorrow (Thursday, August 18th).

You can also read the

It is that time of the week^Wmonth^Wyear where we gather on IRC and take a hack at bugzilla in order to help make the next GNOME release higher quality. It's obviously been a while since we had these regularly (though there was a small one last week) and they are needed :)

Yes, you understand well: bug days are back! And the next bug day is tomorrow (thursday, july 21st, 8am EST->7pm EST or 1200GMT->2300GMT if you prefer :-)). All this happens in #bugs (on irc.gnome.org). Our dear Luis will be the bugmaster of this bug day.

So, some information for those who haven't heard of our bug days:

Bugzilla.mozilla.org announced a contest for when they'd reach bug number 300.000. Such a bug number for a product that just reached 1.0 is not right. As GNOME is at 2.10, GNOME should be using bug numbers in the 300.000 range well before Mozilla. We (bugzilla.gnome.org bugmasters) have concluded this needs to be resolved. This requires bugzilla.gnome.org to be down Saturday 9 April from 17.00 - 20.00 UTC. The downtime is needed to make the bug numbers start from 300.000.

http://developer.gnome.org/projects/bugsquad/statistics/2003and2004/ has some interesting statistics from Gnome bugzilla for 2003 and 2004. (These were also discussed on desktop-devel-list)

Tomorrow Thursday the 22nd will be a bug day again! This is a great
opportunity for people to help the GNOME project keep track of all those
bugs people report, and make sure they're clear enough that developers
can actually get round to fixing them. So it's an integral part of
making GNOME the best desktop out there...

I have trouble with timezones. I'm going to be on irc.gnome.org in #bugs
from 1600 GMT to 2000 GMT (I think that's 1100 EST to 1500 EST), though
other people might be around at other times. If you want to get
involved, please drop in!

If you don't know what a bug day is, or what we do, please read the FAQ.
But it will all become clear tomorrow.......Thanks! -Andrew

In all my self-centered-ness over my own birthday last week, I missed another birthday- it's been a touch over two years since the first gnome bug day. We're still plugging away, helping gnome developers organize, communicate, and generally write better software, every week on Thursday.

Tomorrow, February 26, our Bugmaster is turning 26. So come by #bugs on irc.gnome.org, wish Luis happy birthday, and triage a bug for him to help stabilize Gnome 2.6.

It's that time of the week again, where we seek understanding of the
state of bugzilla and hence the state of our project. (And your project
too.) This week's goal will be attacking new nautilus bugs and general
crashers.

It's that time of the week again, where we seek understanding of the
state of bugzilla and hence the state of our project. (And your project
too.) This week's goal will be nailing UNCONFIRMED bugs- there are many
of them, and we need to clean them out[1].

It's not really bugday 2.5.3 but to celebrate all the hard work the devels have been doing to stabilize GNOME 2.5, it's probably time to help them out by cleaning out bugzilla.

We are having a short Bug Day tomorrow (from 1-7 pm, EST), and a short Bug Day deserves a short announcement (at least that's my excuse for being uncreative). Basically, Bug Day is a great way to start contributing to Gnome whether you know how to program or not. The first few questions of the FAQ will tell you more about what the Bugsquad is and how you can help it during Bug Day. To get started, read the triage guide, then join us in #bugs on irc.gnome.org or mail us on the gnome-bugsquad mailing list.

Regular bug days have started up again and one is occuring today until 9PM EST.
We apologize for forgetting to post this yesterday to this site, but here's the announcement sent from Luis to gnome-bugsquad and gnome-list:

It's time for regular bug days to start up again.[1] So... tomorrow, from 9 AM EST to 9PM EST tomorrow I'll be making a fool of myself saying 'hello' to every new face I see in #bugs on irc.gnome.org and asking, nay, begging, them to help work on untriaged GNOME 2.4 and 2.5 bugs. I can beg everyone because virtually anyone with decent ability to read English can be a great bug volunteer- some user experience with gnome and some amount of common sense are the only other real requirements. There is lots more information in the FAQ. But the important thing is that anyone with 1/2 hour to spare can hangout tomorrow and help move GNOME closer to a stable, cool GNOME 2.6.0. See you tomorrow- 9:00AM EST-9:00PM EST (1400UTC->2400UTC)

[1] Of course, I just booked myself to be on a plane all next Thursday. Idiot, Idiot, Idiot. I'm going to get better about that, I promise.