[arch-dev-public] Bug Day
Hi! I would like for the next Bug Day to happen on 14th of April. The reason for this is to reduce the amount of old reports and feature requests. We should clear outdated reports, fix/implement those that already have patches provided or are trivial to fix/implement, discuss the pros & cons of implementing some feature requests, look at reports assigned to inactive/resigned devs. If you cannot take part in the Bug Day, then choose any day when you'll have free time to do this work and plase notify other devs so they would know to take a closer look at your reports too. Please all users help us too. There are bugrepors that are probably already fixed but developers may not be aware of this because of lack of user feedback. Please review all bugs that were reported by you if they still are valid. If report are old enought and no further information from reporter is provided then developers will most likely close such bugs assuming they are fixed. We cannot fix bugs without your feedback. Join us at #archlinux-bugs channel on irc.freenode.net during 14th of April. As we leave in different timezones not all devs will be available at the same time, but feel free to report your issues to any dev available on-line. Also please check your mailboxes that may contain notifications about comments made by devs and other users. I would like to hear any proposals about possible improvements to the Bug Day effectiveness. P.S.: this is my first official announcement so don't beat me hard if something is wrong. :-P -- Roman Kyrylych (Роман Кирилич)
Roman Kyrylych schrieb:
I would like for the next Bug Day to happen on 14th of April. The reason for this is to reduce the amount of old reports and feature requests. We should clear outdated reports, fix/implement those that already have patches provided or are trivial to fix/implement, discuss the pros & cons of implementing some feature requests, look at reports assigned to inactive/resigned devs.
Good.
If you cannot take part in the Bug Day, then choose any day when you'll have free time to do this work and plase notify other devs so they would know to take a closer look at your reports too.
I am absent that whole weekend.
I would like to hear any proposals about possible improvements to the Bug Day effectiveness.
First, as you are our "bug guy", it is good that you organize this. To improve effectiveness it may be good to have a list of bugs that shold be looked at, ordered into categories like you suggested above. Maybe you should provide a wiki page "Bug Day" where users can add bugs to the respective categories. Then there should be a rough timeline on what will happen when. Maybe it will also be good that you moderate the #archlinux-bugs channel and kick people that do not discuss bugday-related stuff to keep the discussion on topic. IF we do the latter, there should be an announcement about it with clear rules, so people won't be pissed when they are kicked or muted.
2007/4/4, Thomas Bächler <thomas@archlinux.org>:
Roman Kyrylych schrieb:
I would like to hear any proposals about possible improvements to the Bug Day effectiveness.
First, as you are our "bug guy", it is good that you organize this. To improve effectiveness it may be good to have a list of bugs that shold be looked at, ordered into categories like you suggested above. Maybe you should provide a wiki page "Bug Day" where users can add bugs to the respective categories. Then there should be a rough timeline on what will happen when.
That's exactly what I was thinking about after the last bug day, but then forgot. Thank you for reminding this. :-) I will make announcement when I create such wiki page.
Maybe it will also be good that you moderate the #archlinux-bugs channel and kick people that do not discuss bugday-related stuff to keep the discussion on topic. IF we do the latter, there should be an announcement about it with clear rules, so people won't be pissed when they are kicked or muted.
Good idea. Though I don't remember any such issues during previous bug day, but we should expect more users to join this time, so it won't hurt anyway. -- Roman Kyrylych (Роман Кирилич)
2007/4/4, Roman Kyrylych <roman.kyrylych@gmail.com>:
2007/4/4, Thomas Bächler <thomas@archlinux.org>:
Roman Kyrylych schrieb:
I would like to hear any proposals about possible improvements to the Bug Day effectiveness.
First, as you are our "bug guy", it is good that you organize this. To improve effectiveness it may be good to have a list of bugs that shold be looked at, ordered into categories like you suggested above. Maybe you should provide a wiki page "Bug Day" where users can add bugs to the respective categories. Then there should be a rough timeline on what will happen when.
That's exactly what I was thinking about after the last bug day, but then forgot. Thank you for reminding this. :-) I will make announcement when I create such wiki page.
Here's a quick beginning: http://wiki.archlinux.org/index.php/Bug_Day_TODO -- Roman Kyrylych (Роман Кирилич)
On Wed, 2007-04-04 at 18:07 +0200, Thomas Bächler wrote:
Maybe it will also be good that you moderate the #archlinux-bugs channel and kick people that do not discuss bugday-related stuff to keep the discussion on topic. IF we do the latter, there should be an announcement about it with clear rules, so people won't be pissed when they are kicked or muted.
IMHO #archlinux-bugs is very inactive and only people reporting/investigating bugs visit it. People don't sit around to chat in that channel, so I don't think moderation is needed.
participants (3)
-
Jan de Groot
-
Roman Kyrylych
-
Thomas Bächler