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, let's try this.

• Remove patch wording

Seeing "Root" written as such, also makes me think of /root, which makes no sense to have there. The odds of needing quick access to / via Dolphin are extremely rare, and there is already a link anyway. People are used to clicking the primary drive to get to root dir.

In T8707#146178, @ngraham wrote:

The resize area issue was rendered moot for smaller-than-normal border sizes at some point in the past with a clever change that allowed windows with "No Borders" to keep the extended resize areas of a window with "Normal" borders.

Ok, v2.0

Changed to OBSERVED.

Done. :)

• Fix wording some more

Improved wording so I don't scare people. ;)

Good point, @broulik thoughts?

In D15731#331200, @broulik wrote:

+1
Thanks!

• Wording tweak

The text is current set to be italicized ("emphasized"). Not sure if you'd prefer bold, or what. Let me know if you want a change.

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)

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

Good catch, apparently LibreOffice made a mistake! ;)

• Change default text placement

Yeah I think that is a mistake. D42047 which precedes the current diff, makes much more sense.

In D15632#329801, @ngraham wrote:

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

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

• 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).

How cool is this, how have I not seen this yet?

Thank you @andersonbruce for all of your work on this, and quickly working on feedback changes! This will be a great addition.

Are you able to edit the Tags on this? For some reason Event: Bugsquad is listed and is showing on that calendar.

In D15418#325344, @broulik wrote:

All of that is reserved for being "Muted". Just because it doesn't play something doesn't mean it couldn't start producing sound any moment.
We shouldn't use anything that could be confused as "muted" ("can never make any sound") for "not playing currently"

How about changing the volume icon for the non-playing application to audio-volume-muted.svg? Then, when it is playing audio, it reverts to low/high icons as usual, based on slider location.

In T9634#159893, @rempt wrote:

Bug squad instructions:

I've tested this patch on my system. Although it does not resolve the scaling issue I experience, it does not cause any regressions I see. Ship it! :)

I like it. I agree though to maybe make them a bit lighter.

In D15406#324063, @ngraham wrote:

@acrouthamel, could you test this patch to make sure it doesn't regress anything for High DPI users?

Yeah exactly, something like that. Where they can git clone (making sure their gitconfig is correct, like how mine wasn't recently), make a branch (and track master), mess it up (lol I've never done that!), submit it via arc diff, tell them how their Git commit is too wordy and needs to break at 80 chars (*ehm* again, never done that before), have someone (newcomer group?) review it and accept it, and then have them arc land it.

I just realized the output was HTML. Ok, I can see what is going on now. If you could let me know if I am missing the "code-editor" though, that would be great!

In D15340#322631, @dhaumann wrote:

Sure, please use kdesrc-build as described here:
https://community.kde.org/Guidelines_and_HOWTOs/Build_from_source

Once setup, you can build everything by invoking ./kdesrc-build
You can also pass a module to build:

./kdesrc-build syntax-highlighting

Ideally, you should build with dependencies:

./kdesrc-build --include-dependencies syntax-highlighting

If you need help, feel free to ask.

I highly recommend AsciiDoc (specifically Asciidoctor)! It has a ton of great features, has standardized syntax (unlike Markdown), can easily include sections of source code from other files (super cool and useful for KDE code documentation), can include other AsciiDoc files to make document management easy, requires no special XML formatting application, and if you follow their recommendations (keeping all sentences on one line each, using ATX sections, etc.) it makes source control via Git a breeze. And you can export to any format, including DocBook.