Skip navigation.

GNOME 2 & 2.1 bug day this Thursday!

Gnome 2.x
Gnome 2.x

Luis Villa writes:
Been a while, but the bug team needs to get organized and happy again :)
So...

Everyone who is interested should sign up for the bug-squad list[1]-
we're trying to get more organized and distribute important work to more
people.[2] It's very low traffic, so if you're curious, don't be bashful
about lurking :)

*Bug Day! It's been too long. Thursday, 9AMEST-9PMEST[3], just like the
good old days. We're going to try to be more organized than we have been
in the past- going forward, we want GNOME programs to have their own QA
teams, and hopefully we can start down that road on Thursday. So... come
on by, say hello, and read a few bugs.

Anyway, hope to see many new faces and some old ones there-
Luis

[1]http://lists.gnome.org/mailman/listinfo/gnome-bugsquad
[2]http://lists.gnome.org/archives/gnome-bugsquad/2002-September/msg00005.html

http://lists.gnome.org/archives/gnome-bugsquad/2002-September/msg00017.html
[3]1400-0200GMT, I /think/... maybe 1500-0300?

Re: GNOME 2 & 2.1 bug day this Thursday!

Sounds good. Thank you for the complete status update. Might I suggest that a page be created on here or gnome.org that displays the current status and also allows a way to suggest changes? Bugzilla may be nice for developers to track shit, but it completely sucks for users. Not only is it too complicated, but it requires creating an account, which takes too much time. I have found that many people will ***** about things here anonymously when they could be creating a feature request or enhancement idea anonymously if it were not for bugzilla. I have had the same issues. I don't want yet another account on another website that I rarely use. I think by creating a simple php mailer page that sends the suggestions to a mailbox that one of the maintainers can filter and put into bugzilla, you'll likely get some really good ideas. Even if you are not taking on any more contributors at this time, use this opportunity to get names and email addresses for the future. When you are ready, shoot an email to them all telling them to back up all the talk and start coding/entering data/reformatting/etc.