Re: taking a stronger stance on the python bugs

2011-05-27 Thread Luca Beltrame
In data Friday 27 May 2011 23:21:39, Aaron J. Seigo ha scritto: Hello Aaron, > * forwarding unique looking backtraces to the bindings components in > bugzilla Judging from the reports I see occasionally in IRC, part of the "loss of functionality" bugs lie in the scripted part, rather than in th

Re: the utter failure of bugzilla (and us?)

2011-05-27 Thread Ruurd Pels
On Thursday 26 May 2011 09.16.46 Aaron J. Seigo wrote: > On Wednesday, May 25, 2011 21:16:13 Kevin Ottens wrote: > > What about the elephant in the room? That is redmine, it's already > > deployed by KDE sysadmins and used, it's just that the ticketing system > > isn't activated. > > redmine real

taking a stronger stance on the python bugs

2011-05-27 Thread Aaron J. Seigo
hi... so dozens of python bindings related crashes have been languishing in plasma's bugs list. i'm currently dealing with them by: * invalidating ones that are invalid (e.g. crashing in the nvidia blob) and closing ones that were fixed because the bug was actually in libplasma and since fixed

Re: Plasma Desktop UX

2011-05-27 Thread Aaron J. Seigo
On Friday, May 27, 2011 21:40:24 Michal Luscon wrote: > #1 - no significant GUI action after right click and unlock widget choice > Tested users was really confused because they expect GUI response after > every of their action in user interface. I think that it would be better > to show right uppe

Plasma Desktop UX

2011-05-27 Thread Michal Luscon
Hi, I would like to put forward several proposals aimed to increase Plasma Desktop usability. As I mentioned in my blog post I was conducting usability testing of new widget addition which revealed some usability shortcoming

Re: Plasma clock bug/wish triage

2011-05-27 Thread John Layt
On Friday 27 May 2011 16:46:15 Aaron J. Seigo wrote: > On Friday, May 27, 2011 16:28:02 John Layt wrote: > > What's then left is a lot of wishes for new visual features that I think > > we can be ruthless with closing if there is no intent to ever implement > > them, so opinions please on: > > The

Re: the utter failure of bugzilla (and us?)

2011-05-27 Thread todd rme
On Wed, May 25, 2011 at 7:14 PM, Aaron J. Seigo wrote: > hi ... > > so, congratulations everyone, plasma is #3 in bugs.kde.org with over 1300 > reports: > >        https://bugs.kde.org/weekly-bug-summary.cgi > > trawling through some right now, it seems that probably ~5% are actual issues, > 5-15%

Re: Plasma clock bug/wish triage

2011-05-27 Thread Aaron J. Seigo
On Friday, May 27, 2011 16:28:02 John Layt wrote: > Hi, > > Following on from the bugs discussion I've gone through the bugs for the > widget-clock componant closing what I can. > > I've previously posted a number of to-do points at > http://community.kde.org/Plasma/Tasks#Calendar.2FClock_Plasmoi

Re: the utter failure of bugzilla (and us?)

2011-05-27 Thread Martin Gräßlin
Hi all, I started to document the current situation and our needs: http://community.kde.org/Plasma/Bugtracker Feel free to extend/correct as you wish. Hopefully we can define a new workflow from that and then go to sysadmin to get support on the implementation part. Personally I think we won'

Plasma clock bug/wish triage

2011-05-27 Thread John Layt
Hi, Following on from the bugs discussion I've gone through the bugs for the widget-clock componant closing what I can. I've previously posted a number of to-do points at http://community.kde.org/Plasma/Tasks#Calendar.2FClock_Plasmoids based on the open bugs. If anyone was to fix/rewrite the