Woohoo! Awesome work, Andrew. Keep an eye on http://pointieststick.wordpress.com/ tomorrow. :-)

I'm going to pull the automated NEEDSINFO handling from here, since this task is specific to new bug reporter experience. I'll work with Harald or whoever else would like to help. For now, I have a manual set of searches that seem to work well enough. I have some other automation ideas as well, so I'll just track that all in a separate task.

Ok, I created the calendar events, I moved the 25th to the 27th. That whole week will be rough, but we should at least host a day for anyone that does not celebrate Christmas or has nothing to do. ;)

Ok, I've created the next calendar events. Thanks for the suggestions!

@sitter - I just wanted to loop you in here since you had offered to script the NEEDSINFO closure bot.

In T9690#161047, @xyquadrat wrote:

• 25. December (this is a bad date, we'll need to move that)

I'd suggest:

+1. If we do start following that schedule, that'd mean the dates left for 2018 would be:

Perfect. I'll land this shortly, then deploy all three changes to the server.

In D15630#329932, @bcooksley wrote:

Based on how the rest of the text is formatted i'd suggest removing the quotes and turning the newlines into actual newlines.

• Change text formatting

Based on how the rest of the text is formatted i'd suggest removing the quotes and turning the newlines into actual newlines.

Good catch, apparently LibreOffice made a mistake! ;)

• Change default text placement

In D15632#329801, @ngraham wrote:

@bcooksley, I think you'll need to land this since permissions to the websites- repos are quite restricted.

@bcooksley, I think you'll need to land this since permissions to the websites- repos are quite restricted.

@bcooksley, I think you'll need to land this since permissions to the websites- repos are quite restricted.

Looks fine to me.

In D15630#329171, @ngraham wrote:

Yeah if you don't mind, let's do the arcconfig file in another patch. It's good practice to keep commits atomic. :)

• Remove gitconfig

Yeah if you don't mind, let's do the arcconfig file in another patch. It's good practice to keep commits atomic. :)

• One more spacing fix to allow people to use next empty line

• Spacing update to help keep content separate

I thought you'd like this. You can thank the LibreOffice team for pointing me to the repo for their create-guided.html.tmpl file. (I had noticed their "1. 2. 3." they placed into the one field).

Awesome, I'm impressed that you found this! What do you think about adding a link to https://community.kde.org/Get_Involved/Bug_Reporting into the template somewhere? Or should that be done somewhere in the main UI elsewhere?

Some menu options in krita seem to already respond to the release of other mouse buttons, so I believed that it was unnecessary to check which button was pressed. However, I think that checking will lead to safer behavior (no chance of a Qt::NoButton or obscure mouse event triggering an accidental frame color selection.)

In Krita we often mention the bug number in the commit message title, though more often as BUG:XXXXX.

@rempt https://community.kde.org/Infrastructure/Phabricator#Formatting_your_patch
The title of patch becomes the commit message.
The bugzilla ticket number should be in the desciption.

Shubham: I don't know of any guidelines like that...

Sorry about that, I've revised the title of the diff.

Please remove "Bug Fix 394072 -" from the title to conform to the naming guidelines.

Hey everyone, @xyquadrat, @ngraham, @cfeck, myself, and others have continued this over at the Bugsquad project page here on Phabricator, with the idea of keeping a schedule going. Check out the calendar for the next event!

I'm closing this out. The calendar is created, and the first event is up there, with more to come.

I've spoken with @xyquadrat regarding kicking off the Bugsquad schedule with Krita, to align with a goal/fundraiser to eliminate bugs. Awaiting details from him, but tentatively we are scheduling for the 16th of September to start. A second date would be either the 23rd, or during the week.

I've taken the gist of the old Bugsquad page and added it as a section to the main Bug Triaging page. I reviewed the other old floating Bugsquad sub-pages and you're right, the content was mostly re-hash of the same material. So I think this is sufficient, and more visible than previously. I'll mark this resolved.

Bugsquad wiki section created and linked to calendar.

Calendar created thanks to Sysadmin. I've added a link to the Bugsquad menu on the left. It's just a query, so you can make your own if you want, such as for list view. You can also export an ICS of the query results, which is great.

Please don't add Sysadmin to multiple tasks which raise the same issue as this generates duplication.
The Calendar has been sorted out as I commented on the other task.

I hope not, I'd rather keep it in-house.

I'm sure that there is no need to use Google Calendar after all the effort to move part of release schedule and promo stuff out of it...

Hi everyone just thought I'd drop a note here as well. I've had @sysadmin recreate the Bugsquad, but in Phabricator for easy collaboration. I'd like to resurrect it, with a set schedule of triaging days. I've asked @sysadmin about adding a calendar to the project, or allowing other Calendar edit access. If not, I'll create a Google Calendar people can subscribe to I suppose.

Yeah, maybe not all the stuff. Just what Bugsquad is, go check out Phab, here's the calendar, etc. Maybe just put it on the Triaging page. I dunno. I don't want to duplicate work though.

Heh, I was the one who deleted them a few months ago. :/ I thought it was rather confusing to have the same information in multiple places (the "how to triage a bug" page and also scattered piecemeal throughout the BugSquad pages).