Akademy/2012/Extra Mile BoF: Difference between revisions
No edit summary |
No edit summary |
||
| Line 13: | Line 13: | ||
The goal of this BoF is not to start polishing applications right away, but to define the best way to get ourselves organized. | 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 | == Topics to discuss == | ||
* Come up with a set of criterias a bug must meet to qualify as an | * Come up with a set of criterias a bug must meet to qualify as an "Extra Mile Bug" (EMB). Possible criterias: | ||
* How | ** Affects many users | ||
* How | ** Makes using the application harder or less pleasant | ||
** Easy to fix | |||
* How to track EMBs. We can: | |||
** Use bug reports with an EMB tag | |||
** Create a "tracker" bug, which all EMB reports should depend on | |||
** List EMB on a wikipage | |||
* 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 organize test days? | |||
== Actions == | |||
Revision as of 11:49, 2 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
- Come up with a set of criterias a bug must meet to qualify as an "Extra Mile Bug" (EMB). Possible criterias:
- Affects many users
- Makes using the application harder or less pleasant
- Easy to fix
- How to track EMBs. We can:
- Use bug reports with an EMB tag
- Create a "tracker" bug, which all EMB reports should depend on
- List EMB on a wikipage
- 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 organize test days?