Get Involved/Extra Mile: Difference between revisions

From KDE Community Wiki
(→‎Communication: fix typo in ml url)
(https://bugs.kde.org/show_bug.cgi?id=303462#c1)
 
(8 intermediate revisions by 5 users not shown)
Line 1: Line 1:
{{Proposed_deletion|reason=This wiki page is about an initiative that maybe existed in the year 2012.}}
From https://bugs.kde.org/show_bug.cgi?id=extramile "Nate Graham 2020-09-29 04:54:46 UTC This initiative has ended, so I don't think we need the tracking bug to stay open any longer."
== Introduction ==
== Introduction ==


Extra Mile is an initiative to help KDE applications and workspaces fix small bugs and UI issues which gets in the way of the user.
Extra Mile is an initiative to help KDE applications and workspaces fix small bugs and UI issues which get 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.  
KDE products are awesome, but could often be made much more pleasant to use by just ironing out a few quirks here and there.  
Line 11: Line 15:
* Gnome: [https://live.gnome.org/EveryDetailMatters Every Detail Matters]
* Gnome: [https://live.gnome.org/EveryDetailMatters Every Detail Matters]


== Criterias to qualify as an "Extra Mile Bug" (EMB) ==
== Criteria to qualify as an "Extra Mile Bug" (EMB) ==


A bug is an EMB if it satisfies all this criterias:
A bug is an EMB if it satisfies all these criteria:


* It must be a bug or an enhancement, not a feature request
* It must be a bug or an enhancement, not a feature request
* It affects many users
* It affects many users
* It makes using the application harder or less pleasant
* It makes using the application harder or less pleasant
* Agreement from the maintainer
* It is easy to fix (see below)
* It is easy to fix (see below)


Line 24: Line 29:
A bug is said to be "easy to fix" if it can be fixed in one day by one person.
A bug is said to be "easy to fix" if it can be fixed in one day by one person.


The maintainer of the application or component should be able to help deciding if a can be fixed in one day. If it cannot the bug can stay but it should not be marked as extramile anymore.
The maintainer of the application or component should be able to help decide if it can be fixed in one day. If it cannot, the bug can stay but it should not be marked as extramile any more.


== Reporting extra mile bugs ==
== Reporting extra mile bugs ==


Extra mile bugs are tracked on Bugzilla. We created [http://bugs.kde.org/show_bug.cgi?id=extramile|a tracker bug] to group all extra mile bugs. To mark a bug as "extra mile", mark it as blocking the tracker bug, that is: enter "extramile" in the "Blocks" field ("extramile" is the alias for the tracker bug). If you want to be notified of new extra mile bugs, subscribe yourself to this bug.
Extra mile bugs are tracked on Bugzilla. We created [http://bugs.kde.org/show_bug.cgi?id=extramile a tracker bug] to group all extra mile bugs. To mark a bug as "extra mile", mark it as blocking the tracker bug, that is: enter "extramile" in the "Blocks" field ("extramile" is the alias for the tracker bug). If you want to be notified of new extra mile bugs, subscribe yourself to this bug.


We may also setup an email alias for people who want to report such issues but can not or do not want to use Bugzilla. This email alias would be a simple way to reach us so that we can file the bug for them.
 
Here is a Bugzilla search [https://bugs.kde.org/buglist.cgi?f1=blocked&list_id=151096&o1=anywords&query_format=advanced&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&v1=303462 listing all extra mile bugs]. You can also use the "ExtraMile bugs" saved searches on Bugzilla which you can find under Preferences / Saved Searches.
 
We may also set up an email alias for people who want to report such issues but can not or do not want to use Bugzilla. This email alias would be a simple way to reach us so that we can file the bug for them.


== Communication ==
== Communication ==
Line 38: Line 46:
* IRC channel: #kde-quality
* IRC channel: #kde-quality


We also plan to report progress by sending reports on kde-devel, kde-testing and blogging every two weeks.
We also plan to report progress through:
* emails on kde-devel, kde-testing
* blogs every two weeks. Links to reports are collated on the report page: [[Getinvolved/Extra_Mile/Reports]].
* articles on http://dot.kde.org
 
If you fix bugs which qualify as extra mile bugs but do not want to file bugs just for the sake of having your fixes included in Extra Mile reports, you can write them down on the report page.


In the future we may try the following:
In the future we may try the following:
* Set up test days
* Organize test days
* Define quantitative goals
* Define quantitative goals

Latest revision as of 16:19, 14 January 2024

Proposed for Deletion

This page has been proposed for deletion for the following reason:

This wiki page is about an initiative that maybe existed in the year 2012.

Please use the discussion section of this page to voice your opinion on this.

From https://bugs.kde.org/show_bug.cgi?id=extramile "Nate Graham 2020-09-29 04:54:46 UTC This initiative has ended, so I don't think we need the tracking bug to stay open any longer."

Introduction

Extra Mile is an initiative to help KDE applications and workspaces fix small bugs and UI issues which get 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:

Criteria to qualify as an "Extra Mile Bug" (EMB)

A bug is an EMB if it satisfies all these criteria:

  • It must be a bug or an enhancement, not a feature request
  • It affects many users
  • It makes using the application harder or less pleasant
  • Agreement from the maintainer
  • It is easy to fix (see below)

How to determine a bug is easy to fix

A bug is said to be "easy to fix" if it can be fixed in one day by one person.

The maintainer of the application or component should be able to help decide if it can be fixed in one day. If it cannot, the bug can stay but it should not be marked as extramile any more.

Reporting extra mile bugs

Extra mile bugs are tracked on Bugzilla. We created a tracker bug to group all extra mile bugs. To mark a bug as "extra mile", mark it as blocking the tracker bug, that is: enter "extramile" in the "Blocks" field ("extramile" is the alias for the tracker bug). If you want to be notified of new extra mile bugs, subscribe yourself to this bug.


Here is a Bugzilla search listing all extra mile bugs. You can also use the "ExtraMile bugs" saved searches on Bugzilla which you can find under Preferences / Saved Searches.

We may also set up an email alias for people who want to report such issues but can not or do not want to use Bugzilla. This email alias would be a simple way to reach us so that we can file the bug for them.

Communication

This initiative is part of the KDE Quality Team, so we use the team communication channels:

We also plan to report progress through:

If you fix bugs which qualify as extra mile bugs but do not want to file bugs just for the sake of having your fixes included in Extra Mile reports, you can write them down on the report page.

In the future we may try the following:

  • Organize test days
  • Define quantitative goals
Retrieved from "https://community.kde.org/index.php?title=Get_Involved/Extra_Mile&oldid=99739"