[scribus-dev] Most Annoying Bugs

[JLuc]

Le 29/05/2014 17:31, Andreas Vox a écrit :
 >> JLuc had writen :
 >> Hard hacks should meet the below requirements:
 >> - Be relatively annoying for a significant amount of people
 >> - Be relatively difficult to solve and/or track down
 >> - Crashes/data loss are good candidates but not necessary
 >> - Backtraces should be done on proposed hard hacks before they become accepted hard hacks
 >> - Enhancement requests should NOT be on the list

 > I don't think we need special requirements for the list except for the first one.

I agree that the first criteria is the most important one.

 > UI quirks and missing functionality should be as legitimate as crashes and bugs.

IMO, coding new functionnalities is not the least cared for aspect of scribus dev,
but in case a missing functionnality is annoying a significant amount of people
then it probably should be candidate to be one of the "Most Annoying Bugs".

 > The first two would just need a clear description of how a solution would work from a user perspective.
 > Any ideas on how you would manage such a list? Should we do it with our bug tracker or do you think of an extra webpage ?

A simple wiki page seems OK as for now
and IMO the new page http://wiki.scribus.net/canvas/Most_Annoying_Bugs
fits the purpose well (thanks Kunda :-)

We should now collect the candidate bugs.
It could be done in a kind of brainstorming round
where everybody tells his favorite worst annoyances :-)
We'd then need to understand the bugs, confirm them (or not),
confront them to the criteria,
and sort them so as to nominate the worst.

We could do that in a new thread :
when possible, say their bugtracker numbers
and describe them in a short sentence.

JLuc