Akademy/2012/Extra Mile BoF: Difference between revisions
No edit summary |
|||
| Line 14: | Line 14: | ||
== Topics to discuss == | == Topics to discuss == | ||
* How to report progress, and how often. We can: | * How to report progress, and how often. We can: | ||
** Create a new mailing list | ** Create a new mailing list | ||
| Line 29: | Line 21: | ||
* Should we organize test days like the "Fit and Finish" initiative did? | * Should we organize test days like the "Fit and Finish" initiative did? | ||
* Should we define a quantitative goal like the "Papercut" project did (100 papercuts fixed every 6 months) | * Should we define a quantitative goal like the "Papercut" project did (100 papercuts fixed every 6 months) | ||
== Criterias to qualify as an "Extra Mile Bug" (EMB) | |||
* Is a bug or an enhancement, not a feature request | |||
* Affects many users | |||
* Makes using the application harder or less pleasant | |||
* Easy to fix | |||
== How to determine a bug is easy to fix == | |||
A bug is easy to fix if it can be fixed in one day by one person. | |||
== Tracking EMBs == | |||
* Track them in Bugzilla (either a tag or a tracker bug) | |||
== Actions == | == Actions == | ||
* [Jeroen van Meeuwen] Setup the bugzilla mediawiki extension | * [Jeroen van Meeuwen] Setup the bugzilla mediawiki extension | ||
Revision as of 08:12, 5 July 2012
The goal of this BoF is to set up an initiative to help KDE applications and workspaces "walk the extra mile": fixing small bugs and UI issues which gets in the way of the user.
KDE products are awesome, but could often be made much more pleasant to use by just ironing out a few quirks here and there.
Similar initiatives have already been run by other Free Software projects:
- Ubuntu: Papercuts
- Fedora: Fit and Finish
- Gnome: Every Detail Matters
As far as I know, nothing like this have been done for KDE.
The goal of this BoF is not to start polishing applications right away, but to define the best way to get ourselves organized.
Topics to discuss
- How to report progress, and how often. We can:
- Create a new mailing list
- Post progress on existing lists like kde-devel
- Write blog posts
- Should we create a #kde-extramile IRC channel?
- Should we organize test days like the "Fit and Finish" initiative did?
- Should we define a quantitative goal like the "Papercut" project did (100 papercuts fixed every 6 months)
== Criterias to qualify as an "Extra Mile Bug" (EMB)
- Is a bug or an enhancement, not a feature request
- Affects many users
- Makes using the application harder or less pleasant
- Easy to fix
How to determine a bug is easy to fix
A bug is easy to fix if it can be fixed in one day by one person.
Tracking EMBs
- Track them in Bugzilla (either a tag or a tracker bug)
Actions
- [Jeroen van Meeuwen] Setup the bugzilla mediawiki extension