[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-kimageshop
Subject: Choosing Krita's most annoying bugs and most sought after features
From: JL VT <pentalis () gmail ! com>
Date: 2012-08-16 16:38:04
Message-ID: CAMTAOStN6jwHaSqtT_DHYotWFCLwUVrx4sr8npaN9eDoCn7chg () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
I have a proposal:
--Let's ask our users for their most hated bugs, or most wanted features,
in Krita.
--If they are grouped in something large, which could be turned into a
project instead of a set of bug fixes, then let's give shape to that
project.
--Let's propose it.
--People vote on it.
--I will do it.
Let me elaborate a bit further. I want to find an efficient way to
prioritize what to work on, for an extended period of time.
Slangkamp has his own vision for bug priority:
<slangkamp> Pentalis: priority should be data loss->crash->regressions
->often report things->normal bugs->minor bugs
<slangkamp> at least that's how I see it
My own POV answer:
<Pentalis> well, it depends, we all hate crashes, but a crash that happens
once a week is less annoying than a feature that doesn't work properly and
you use it every 5 minutes
I want to resurrect my blog on Krita, update it weekly, and make buzz about
new exciting features or new equally exciting bugfixes. What makes a bugfix
exciting?, when it kills bugs you really hate; same with features, they're
exciting when you really wanted them.
So I need YOU, dear Krita user, to help us find these most sought after
features and most hated bugs. Give us your own list of horrors and dreamed
features, explain those you think merit explaining (specially new
features), and give us your insight on what more efficient way we can use
to determine which improvements rank as the most needed for our application.
I'll be giving a face-lift to my blog on the meanwhile.
[Attachment #5 (text/html)]
<div><div>I have a proposal:</div><div>--Let's ask our users for their =
most hated bugs, or most wanted features, in Krita.</div><div>--If they are=
grouped in something large, which could be turned into a project instead o=
f a set of bug fixes, then let's give shape to that project.</div>
<div>--Let's propose it.</div><div>--People vote on it.</div><div>--I w=
ill do it.</div></div><div><br></div><div>Let me elaborate a bit further. I=
want to find an efficient way to prioritize what to work on, for an extend=
ed period of time.</div>
<div>Slangkamp has his own vision for bug priority:</div><div><div><slan=
gkamp> Pentalis: priority should be data loss->crash->regressions =
->often report things->normal bugs->minor bugs</div><div><slang=
kamp> at least that's how I see it</div>
</div><div><br></div><div>My own POV answer:</div><div><Pentalis> wel=
l, it depends, we all hate crashes, but a crash that happens once a week is=
less annoying than a feature that doesn't work properly and you use it=
every 5 minutes</div>
<div><br></div><div>I want to resurrect my blog on Krita, update it weekly,=
and make buzz about new exciting features or new equally exciting bugfixes=
. What makes a bugfix exciting?, when it kills bugs you really hate; same w=
ith features, they're exciting when you really wanted them.</div>
<div><br></div><div>So I need YOU, dear Krita user, to help us find these m=
ost sought after features and most hated bugs. Give us your own list of hor=
rors and dreamed features, explain those you think merit explaining (specia=
lly new features), and give us your insight on what more efficient way we c=
an use to determine which improvements rank as the most needed for our appl=
ication.</div>
<div><br></div><div>I'll be giving a face-lift to my blog on the meanwh=
ile.</div><div><br></div><div><br></div>
_______________________________________________
kimageshop mailing list
kimageshop@kde.org
https://mail.kde.org/mailman/listinfo/kimageshop
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic