Thanks for continueing the project :)

I like the collection as it is a good representation of often used programs.

One question though: are the projects which bugs we triage aware of the plan?
I got the feeling last year a few times that there was no communication of us and the team (e.g. Krita).

That looks great to me. I'm new here and hope to help out as much as I can. Where do I start?

In T10409#174681, @Sebelbrecht wrote:

One question though: are the projects which bugs we triage aware of the plan?
I got the feeling last year a few times that there was no communication of us and the team (e.g. Krita).

It's indeed important that developers get involved beforehand. Especially digiKam developers, because they have long established bugzilla practices.

In T10409#174695, @cfeck wrote:

In T10409#174681, @Sebelbrecht wrote:

One question though: are the projects which bugs we triage aware of the plan?
I got the feeling last year a few times that there was no communication of us and the team (e.g. Krita).

It's indeed important that developers get involved beforehand. Especially digiKam developers, because they have long established bugzilla practices.

Good to know. I'll certainly contact devs.

@acrouthamel I was just thinking about the fact that we need to kick off some more Bug days for this year when I saw the notification that you were a tiny bit faster than me... :)
List sounds very reasonable, and I do agree that it is important to contact as many of the developers in advance to ensure we are as efficient and productive as possible. My only concern is that we might not have enough KCalc bugs to triage for two sessions, so we might need to search an additional alternative. Are we going to keep the two-week-rhythm?

@oussemabouaneni Great to hear that you'd like to help! I'd suggest that you subscribe to our calendar (https://phabricator.kde.org/calendar/query/Tp0Fc0J7sB6v/) so that you are always informed about new bug triaging days. You can also join our IRC (#kde-bugs). Of course you are also invited to just start triaging yourself (going through the new bugs that were reported today can be a great starting point). Welcome to the Bugsquad!

Thank you, will sure do

In T10409#174698, @xyquadrat wrote:

@acrouthamel I was just thinking about the fact that we need to kick off some more Bug days for this year when I saw the notification that you were a tiny bit faster than me... :)
List sounds very reasonable, and I do agree that it is important to contact as many of the developers in advance to ensure we are as efficient and productive as possible. My only concern is that we might not have enough KCalc bugs to triage for two sessions, so we might need to search an additional alternative. Are we going to keep the two-week-rhythm?

Yeah, good point, maybe we combine ark with kcalc since they're both small. I wanted to pick some easy, smaller ones that were common utilities, since activity was light end of 2018. Open to suggestions. :)

The same rhythm works for me, I did notice less people attended the weekend events last year.

I made some tweaks to the list based on @xyquadrat's observations on bug load.

Any other comments/changes? Otherwise I'll send out some emails in the coming days.

I made lot of triage in Kdenlive bugtracker. I think it's a bid tricky on which version to concentrate: 18.12 or the upcoming refactoring release. My suggestion would be: Bugsquash should concentrate on the marked 70 Junior-jobs. But ask JBM about as well.

I've gone ahead and created the current schedule in the calendar. Please mark yourself as attending for whichever ones you are interested in. That way you receive updates on any discussion or updates on the event.

I'll be reaching out to developers this week!