Dedicated bug (system) discussion list? [was: Bug#45196: KDE bugs database needs a spring cleaning]
Vadim Plessky
lucy-ples at mtu-net.ru
Tue Jul 16 17:06:31 BST 2002
On Sunday 14 July 2002 1:30 pm, Aaron J. Seigo wrote:
| On Monday 15 July 2002 03:31, Stephan Binner wrote:
| > On Monday 15 July 2002 10:56, Jesper Juhl wrote:
| > > > You are not volunteering, or?
| > >
| > > Ok, I'll try going through some bugs over the next few days and try to
| > > compile a list. Then I'll post it somewhere (what mailing-list or
| > > person
| >
| > Can we have it, do we need it? Discussions about bugs.kde.org,
| > organizing bug hunting days (Aaron volunteered IIRC) and allow users to
| > post hints?
|
| yes, i've mentioned my desire to organize bug hunt days a few times on
| IRC.
Wy we should delay Bug Hunting Day to October or November?
Let's try to do it next week.
We need to place announcement on www.kde.org, and also - send a mail to people
who reported bugs "please upgrade to KDE 3.0.2 and check wether this bug is
still present"
|
| i'd like to start sometime in october or november, since that seems to be
| a good hacking time for those of us in the northern hemi, what with summer
| being well past and all.
|
| i've been thinking about it for some months now and basically i'd like to
| get a bunch of people on IRC and focus on cleaning out the bugs system:
|
| o get rid of the unreproducable / poorly reported bugs
| o get rid of wishlist items that are bogus
| o get rid of already fixed bugs
I can help here :-)
| o fix the easy-to-fix bugs (e.g. <3 hours of hacking time)
There are some KHTML / KJS bugs with a testcase.
I think such bugs can be fixed first.
| o analyze the harder bugs and figure out what it would require to
| implement (and hopefully kill a few of them, too)
I think that completed CSS2 should be implemented in KHTML.
I have several 'wishlist' bugs opened for this.
| o prioritize remaining bugs
Good idea!
| o document the reproducable bugs
|
| it would be best IMO if 2-4 apps were a focus at each bug fest so that we
| can get a bunch of eyes on the same code base at the same time. it would
| also be good if the maintainers of those apps can be around to help make
| deffinitive suggestions and decisions (e.g. "whacky wishlist #XYZ will
| never be implemented. get rid of it.", "the proper fix is to .....") and to
| review and OK patches as they roll in ...
|
| we'd keep a "kill list" and post it after the bug fest as a record of our
| accomplishments ... each bug fest could run anywhere from 16-48 hours,
| depending on interest and participation.
|
| anyways.. i'm not planning on actually kicking up any real dust on this
| idea for a couple months yet. but now that my nefarious plot has been
| uncovered:
|
| be warned! beware! be ready!
Are we developing clone of BeOS now? :-)
|
| - --
| Aaron J. Seigo
--
Vadim Plessky
http://kde2.newmail.ru (English)
33 Window Decorations and 6 Widget Styles for KDE
http://kde2.newmail.ru/kde_themes.html
KDE mini-Themes
http://kde2.newmail.ru/themes/
More information about the kde-core-devel
mailing list