Plasma 5.7 Test Days scheduled for June 19th+20th; report from first prep meeting

[Jens Reuterberg]

Addendum from me:
I'm working on some nice infopgraphic for "How to do a bugreport" - the idea 
being that it should be inviting, simple and suggesting different paths to 
contact devs in a good and friendly way.

The notes I have so far about it is:
1) How to get the relevant data about the bug out
This is tricky because we want someone checking it to feel like they are doing 
a good job without overwhelming them with info. 

2) How to check for duplicates
Here I want to show how to search for the right place to put the bug, but also 
introduce the simplest sort of "bug triaging light" for people just to show 
how it works without scaring people away.

3) How to remain active with a bug
This is where I want to present what to expect with bugs, how bug checking 
works from a dev POV and why its relevant to remain active on a bug report. 
(also a way to prepare for the rather clipped language in Bugzilla)

What I need help with is:
- Suggestion for a way to get the "relevant data" when you encounter a bug
- What devs want users to think about when they may want to talk to you

When I get the notes in a line (this is just the quick notes I took during the 
meeting that I thought I'd expand upon) I would love to pass them around to 
devs with some doodles for graphics just to ensure that everything feels good 
since they may affect you guys and gals eventually. :)

/Jens

On Tuesday, 12 April 2016 19:42:02 CEST Eike Hein wrote:
> Hi everyone,
> 
> below are the notes for our first prep meeting for our upcoming
> Plasma 5.7 Test Days. You can also find the full log attached to
> this mail:
> 
> attendees: eike, bhushan, jens, riddell, notmart, kbroulik
> chair: eike
> 
> intro (excerpt, see full log):
> 
> [19:02] <Sho_> ok, so we want to hold a Plasma Bug Day on June 19th or
> 20th (or both), with developer and user participation, both to find out
> what sort of impact we can have on quality with that sort of thing, and
> also to send a message that we do care about Plasma 5 being reliable at
> this point
> [19:02] <jensreu> Also its about trying to find users who could see
> themselves being part.
> [19:02] <Sho_> the idea will be to give the impending 5.7 release a good
> run-through and find any regressions/problems that need to be addressed
> for the release
> [19:03] <jensreu> So for me the relevant bit is that users who have
> until now not helped out, get a good report with KDE people in general
> and may feel like helping out again
> [19:03] <Sho_> that means we should discuss (a) prereqs, (b) test day
> content, (c) assign some tasks in prep, (d) messaging/promo and (e) nail
> down a date
> 
> (a) prereqs
> - we will need ISO images to base tests on
> -- jens will talk to kaos, opensuse, fedora; riddell (neon) was also
> listening in
> -- rotating isos in future test days can be good for distro relations,
> it's all one team
> 
> (b) test day content
> - we want testcases a la
> https://fedoraproject.org/wiki/Test_Results:Fedora_23_Final_RC10_Desktop
> (final table)
> - avoids everyone bringing their pet bug, instead they get asked to
> accomplish a task and log the results, and find new problems along the way
> - unclear how specific or coarse test cases need to be (example: "add a
> widget and position it to your liking"), experience will tell
> - VDG will produce some example test case content for us to discuss and
> mull more at next week's meeting
> - sample test case areas: widget management, panel management, common
> customization settings, device control (network, audio), launching apps,
> window management, ..
> 
> (c) messaging/promo
> - banners, stickers etc for test days (webbanner - talk to eV about
> sticker printing)
> - blog posts
> - "how to file a bug report" infographic
> - promo launch deadline is first week of june (three weeks before test
> day), materials for blogs need to be ready by then
> 
> (d) workflow during test day
> - direct to bugzilla vs logging results on wiki, then devs generating
> their own reports from it
> - pro bugzilla: educating users to use the real thing
> - pro wiki: avoids torrent of issues on bugzilla; devs have to do triage
> either way
> - no final decision, leaning towards wiki, but may need more feedback
> 
> (e) dates
> - weekly prep meetings; next meeting tuesday 12:00 UTC in #plasma again
> - our test day will be Test Days: June 19th (Sunday) + June 20th
> (Monday) to catch users off-work and devs at-work
> - two stages: Sunday might be focused on collection, giving devs to roll
> in on Monday content to work on
> - means it will collide with plasma monday hangout, though ...
> 
> 
> Cheers,
> Eike