As developers we love writing code, but hate dealing with testing and bug reports and all that rubbish.

As designers you love designing, but probably also hate dealing with testing and bug reports and all that rubbish.

Unfortunately it's part of life that we have to do it, and this means you guys need to help too. To turn a design into reality takes a lot of back and forth and iteration, and sometimes dealing with users.

Everyone here who has helped design plasma next should be running it regularly.
There is a live CD that can be run from a USB pen as well as distro packages.
Instructions can be found here: http://community.kde.org/Plasma/InstallingNext

There several bugs in PlasmaShell that are design related. Some to do with icons and the breeze theme, some questions over design choices.

Current open bugs are here: https://bugs.kde.org/buglist.cgi?list_i ... lasmashell

Bugs that are design related:

https://bugs.kde.org/show_bug.cgi?id=336100
https://bugs.kde.org/show_bug.cgi?id=334922
https://bugs.kde.org/show_bug.cgi?id=335861

We need to decide either "this is a bug that needs fixing" or "I disagree, sorry" and close it.

Otherwise us developers will start taking design decisions, and you don't want that

Thanks for highlighting those three items David. We're all working hard to try address these as well as other design issues so it's a bit of a balance in terms of prioritizing our efforts. As soon as I can carve out some time I'll try to provide feedback on those issues.

3 more.

https://bugs.kde.org/show_bug.cgi?id=335766
https://bugs.kde.org/show_bug.cgi?id=336124 (which has it's own forum thread)
https://bugs.kde.org/show_bug.cgi?id=336220

Most just need:

"this is by design" and close the bug
"I agree" and confirm the bug

it should take 30 seconds max.

Once we release we are going to be getting 10s of bug reports a day, we need to get in the habit of improving this.

david_edmundson wrote:Once we release we are going to be getting 10s of bug reports a day, we need to get in the habit of improving this.

Oh, David is showing a sign of impatience, then it must be really serious. I'd suggest we appoint a small group of people responsible for these small decisions, it shouldn't all fall on Andrew.

david_edmundson wrote:it should take 30 seconds max.

That's just it you see. It takes much more than just 30 seconds. Is the specific issue highlighted really the problem or a symptom of some other design problem? Is it an implementation limitation that the design should change to accommodate? For design decisions not explicitly made by the VDG we probably owe the person making that design decision the opportunity to explain the rationale for that decision and weigh it against the current design direction. Is it a scenario we have not yet considered?

A complete, holistic view of the design and its application to every specific instance of a pixel or animation or interaction is still in its formative stages. We've gotten a good bit of the building blocks in place. But we have the rather tricky task of supporting the rather mature needs of a project while simultaneously working to evolve what is a very new, very young design to meet those needs. I could go on but the point is that it can require far more effort than what appears to be simply a pronouncement of "by design" or "confirmed".

We will work to help disposition bugs in as timely a manner as resources permit. I've have increased my attention to bugs reports over the last week or two and have already provided feedback on several. Highlighting bugs that require VDG input definitely helps. Thomas' suggestion to increase the resources available for this activity is also certainly welcome by me.

I agree, Andrew can't possibly handle this on his own. I guess the people in this group would have to know the HIG and be a rather active part in the VDG community to stay on top of things.

Also: As the reporter of bug 336220 I say, without being biased the slightest bit, make it plain or cover up the entire left side.

I don't want it to all fall on Andrew either, he's doing a very good job, but we need more help.
That's why I'm posting here instead of talking to him directly

david_edmundson wrote:I don't want it to all fall on Andrew either, he's doing a very good job, but we need more help.
That's why I'm posting here instead of talking to him directly

Oh, I don't think anyone perceived your post criticizing Andrew.
I just read it as "we need to fix those things faster in the future" and relying on a single person for something that could become time-critical isn't ever a good idea, hence my suggestion.

Bugs now have a special flag to highlight it as requesting some input from any member of the VDG forums. This link will contain the latest open reports.

https://bugs.kde.org/buglist.cgi?f1=fla ... lasmashell