There have been various KDE bug triaging days/sessions in the past (see https://tsdgeos.blogspot.com/2015/09/september-26-systemsettings-and-kcms.html for a more recent example), but there haven't been such events in the last few years. Holding bug triaging days has many advantages:
- Regular bug triagers are motivated to do an extra effort and "kill" as many bugs as possible
- New (or to-be) contributors get an easy way to dive in, and can get help from others (-> onboarding initiative)
- The product that is in the focus will have less old cruft and developers mainly have good, high-quality bug reports left
- Those event foster a sense of community inside KDE
Therefore I propose to revive bug triaging days/sessions. Of course, there are a few challenges and questions that we need to overcome first. I've written down everything that came to my mind, but please add more content if you have additional things to discuss.
- Where?: A good meetup place might be #kde-bugs, people can connect via IRC or Matrix (not currently briged, we'd probably need to ask #kde-sysadmin)
- When?: We should try to make those events happen regularly, for example once a month. Alternating between weekends and weekdays might also be a good idea so that everybody can participate at some point (thanks @davidedmundson for the suggestion)
- Who?: We should have somebody who has experience with bug triaging online all the time if possible, so we'll need people from different time zones and continents (America, Europe and maybe Asia). We should also try to get a domain expert for the topic of the day involved.
- How? The topic should be decided in advance so that we can spread the news through dot.kde.org, reddit or twitter. We strive to attract as many new contributors as possible and then help them diving right in.
- decide on a first date
- decide on a product or timeframe
- make timetable (who is online during which period of time)
- ask domain experts if they are available
- come up with a way to give everyone a batch of bugs efficiently
This is currently a rough draft, so please give feedback about whatever you'd like to improve or change.