| Variable | Value |
|---|
Whether or not the edit is marked as minor (no longer in use) (minor_edit) | false |
Edit count of the user (user_editcount) | 145 |
Name of the user account (user_name) | 'Amynka' |
Age of the user account (user_age) | 162598056 |
Page ID (page_id) | 25105 |
Page namespace (page_namespace) | 510 |
Page title (without namespace) (page_title) | 'Bug-cleaners' |
Full page title (page_prefixedtitle) | 'Project:Bug-cleaners' |
Action (action) | 'edit' |
Edit summary/reason (summary) | '' |
Old content model (old_content_model) | 'wikitext' |
New content model (new_content_model) | 'wikitext' |
Old page wikitext, before the edit (old_wikitext) | '{{Project
|Name=Bug cleaners
|Description=The Gentoo Bug Cleaners project aims to clean up the oldest bugs in Bugzilla.
|Email=maintainer-wanted@gentoo.org
|IRC=#gentoo-bugs
|ParentProject=Project:Quality Assurance
|PropagatesMembers=No
|LeadElectionDate=2016/04/21
|Members={{Project Member
|Developer=User:Amynka
|Role=Member
|IsLead=No
}}{{Project Member
|Developer=User:Wraeth
|Role=Lead
|IsLead=Yes
}}{{Project Member
|Developer=User:MarekSzuba
|Role=Member
|IsLead=No
}}{{Project Member
|Developer=User:Jstein
|Role=Member
|IsLead=No
}}{{Project Member
|Developer=User:MGorny
|Role=Accidental helper
|IsLead=No
}}
}}
The goal of the Bug cleaners project is twofold:
* The main purpose of the project is to close bugs on Bugzilla that do no longer apply due to versions and/or packages that are no longer present in the Portage tree.
* As a side effect, it also tries to look for solutions for the ''oldest'' bugs.
For those that still have use, it attempts to inform the persons involved in the bug that the bug is still open if the bug is important; inviting them to make a decision on it.
__TOC__
== Resources ==
Queries that can be handy for finding old bugs include:
* Bug cleaners: Oldest bugs: [https://bugs.gentoo.org/buglist.cgi?f1=blocked&f2=blocked&j_top=OR&n1=1&n2=1&o1=anywords&o2=anywords&query_format=advanced&resolution=---&v1=472746&v2=174380&order=Bug%20Number Any bugs] or [https://bugs.gentoo.org/buglist.cgi?email1=%28maintainer-wanted%7Cgames%7Cretirement%7Cjava%29%40gentoo.org&emailassigned_to1=1&emailtype1=notregexp&f1=blocked&f2=blocked&n1=1&n2=1&o1=anywords&o2=anywords&order=Bug%20Number&query_format=advanced&resolution=---&v1=472746&v2=174380 filtered bugs (no retirement, games or m-w)], both filter out bugs that block useful trackers.
* Bug cleaners: Long time untouched bugs: [https://bugs.gentoo.org/buglist.cgi?f1=blocked&f2=blocked&j_top=OR&n1=1&n2=1&o1=anywords&o2=anywords&query_format=advanced&resolution=---&v1=472746&v2=174380&order=Last%20Changed Any bugs] or [https://bugs.gentoo.org/buglist.cgi?email1=%28maintainer-wanted%7Cgames%7Cretirement%7Cjava%29%40gentoo.org&emailassigned_to1=1&emailtype1=notregexp&f1=blocked&f2=blocked&n1=1&n2=1&o1=anywords&o2=anywords&order=Last%20Changed&query_format=advanced&resolution=---&v1=472746&v2=174380 filtered bugs (no retirement, games or m-w)], both filter out bugs that block useful trackers.
* QA-Reports: Bugs last touched by year: [https://bugs.gentoo.org/buglist.cgi?f1=delta_ts&f2=delta_ts&list_id=2084118&o1=lessthaneq&o2=greaterthaneq&query_format=advanced&resolution=---&v1=2007-01-01&v2=2006-01-01 till 2006 (0 bugs)], [https://bugs.gentoo.org/buglist.cgi?f1=delta_ts&f2=delta_ts&list_id=2084118&o1=lessthaneq&o2=greaterthaneq&query_format=advanced&resolution=---&v1=2008-01-01&v2=2007-01-01 2007], [https://bugs.gentoo.org/buglist.cgi?f1=delta_ts&f2=delta_ts&list_id=2084118&o1=lessthaneq&o2=greaterthaneq&query_format=advanced&resolution=---&v1=2009-01-01&v2=2008-01-01 2008], [https://bugs.gentoo.org/buglist.cgi?f1=delta_ts&f2=delta_ts&list_id=2084118&o1=lessthaneq&o2=greaterthaneq&query_format=advanced&resolution=---&v1=2010-01-01&v2=2009-01-01 2009], [https://bugs.gentoo.org/buglist.cgi?f1=delta_ts&f2=delta_ts&list_id=2084118&o1=lessthaneq&o2=greaterthaneq&query_format=advanced&resolution=---&v1=2011-01-01&v2=2010-01-01 2010], [https://bugs.gentoo.org/buglist.cgi?f1=delta_ts&f2=delta_ts&list_id=2084118&o1=lessthaneq&o2=greaterthaneq&query_format=advanced&resolution=---&v1=2012-01-01&v2=2011-01-01 2011] and [https://bugs.gentoo.org/buglist.cgi?f1=delta_ts&f2=delta_ts&list_id=2084118&o1=lessthaneq&o2=greaterthaneq&query_format=advanced&resolution=---&v1=2013-01-01&v2=2012-01-01 2012].
== First steps ==
Because one cannot just rush in and go hunt at random bugs and expect people to agree with one's actions; the very first steps we will take is to raise the necessary discussion to get feedback on what the community wants us to do exactly, which clarifies the further limits and scope of the project.
=== Questions to be answered ===
We will need to get some questions answered to proceed:
* How old is "oldest"?
* When is a bug considered still useful?
* Are there other types of bugs we could or need to look into?
* Can this effort replace the Bug Day that does not receive interest lately?
* Do we need a mail alias so we can get CC-ed on bugs? (Effectively allowing users to help as well.)
* Do we need a mail alias so we can get assigned on bugs? (*unsure*)
* What to do in exceptional cases? (Cannot be answered until we identified them.)
This will be discussed on the mailing lists.
=== Bug summaries ===
Preferably, bugs requesting new packages should have similar formatting for the summary or title. This will allow for easy parsing of the maintainer-wanted bugs and quickly inform readers of the name and purpose of requested packages. Suggested guidelines for package requests are:
* The summary should contain the package name, the category, and a brief description of the package.
** Category suggestions are fine, but if unsure, just leave it out and mention in a comment.
** If the category isn't known, then it can be omitted.
* Version numbers should not be in the summary.
** The request is for the atom to be added in general, versioning will be dependent on the maintainer and upstream availability.
* If the addition of one package is dependent on the addition of another, this should be indicated with the Bugzilla {{c|Depends On}} field.
** Depends On should only be set for the immediate dependency - in the example below, {{c|libbaz}} would is only used for {{c|bar}}, not {{c|foo}}.
Examples of good bug summaries include:
* '''Bug 1234''' - app-editors/foo: a multicoloured text editor
* '''Bug 1236''' - app-dicts/bar: a dictionary of bad words for app-editors/foo ''[depends on 1234]''
* '''Bug 1238''' - libbaz: a library for accessing app-dicts/bar ''[depends on 1236]''
Examples of bug summaries that are less useful:
* Can foo be added to the tree?
* bar is a dictionary
* It would be cool to have libbaz if we get foo
=== This page is to be extended ===
We will need to document our practices and useful resources here (QA reports, good bug queries, ...).
== Criteria for closing a report ==
Each request is important and was made by a real user, so must be carefully evaluated prior to closing. While it is not useful to have thousands of open requests, it's also harmful to unnecessarily close requests that are still valid.
Use these guidelines to help evaluate whether a request still has merit:
{| class="table table-condensed table-striped"
|-
! Metric !! Weight !! Notes
|-
! colspan="3" | Upstream status
|-
| Exists || High || Package must still be available and fetchable (did it move to github, bitbucket, ...?)
|-
| Alive || Medium || Signs of activity - releases, commits, bug reports, mailing list?
|-
! colspan="3" | Technical debt
|-
| Dependency availability || High || Cannot require ancient dependencies that are no longer available (qt3, kde3, ...)
|-
| Toolchain || High || Needs to build in a modern system (recent GCC, glibc, ...)
|-
! colspan="3" | Suitability
|-
| License || High || Package license must be a good fit for Gentoo
|-
| User demand || Medium || Is there continuing interest in the package, or interest from multiple users?
|-
| Wider availability || Medium || Do other distros [https://pkgs.org package] it?
|}
== Project's relationship to Bug wranglers ==
This project attempts to fit side by side with [[Project:Bug-wranglers|Bug wranglers]].
Bug wranglers is a project for bug assignment. Having a separate mail alias and project page makes it easier for people as a separate form of contact, documentation, and recognition.' |
New page wikitext, after the edit (new_wikitext) | '{{Project
|Name=Bug cleaners
|Description=The Gentoo Bug Cleaners project aims to clean up the oldest bugs in Bugzilla.
|Email=maintainer-wanted@gentoo.org
|IRC=#gentoo-bugs
|ParentProject=Project:Quality Assurance
|PropagatesMembers=No
|LeadElectionDate=2016/04/21
|Members={{Project Member
|Developer=User:Wraeth
|Role=Lead
|IsLead=Yes
}}{{Project Member
|Developer=User:MarekSzuba
|Role=Member
|IsLead=No
}}{{Project Member
|Developer=User:Jstein
|Role=Member
|IsLead=No
}}{{Project Member
|Developer=User:MGorny
|Role=Accidental helper
|IsLead=No
}}
}}
The goal of the Bug cleaners project is twofold:
* The main purpose of the project is to close bugs on Bugzilla that do no longer apply due to versions and/or packages that are no longer present in the Portage tree.
* As a side effect, it also tries to look for solutions for the ''oldest'' bugs.
For those that still have use, it attempts to inform the persons involved in the bug that the bug is still open if the bug is important; inviting them to make a decision on it.
__TOC__
== Resources ==
Queries that can be handy for finding old bugs include:
* Bug cleaners: Oldest bugs: [https://bugs.gentoo.org/buglist.cgi?f1=blocked&f2=blocked&j_top=OR&n1=1&n2=1&o1=anywords&o2=anywords&query_format=advanced&resolution=---&v1=472746&v2=174380&order=Bug%20Number Any bugs] or [https://bugs.gentoo.org/buglist.cgi?email1=%28maintainer-wanted%7Cgames%7Cretirement%7Cjava%29%40gentoo.org&emailassigned_to1=1&emailtype1=notregexp&f1=blocked&f2=blocked&n1=1&n2=1&o1=anywords&o2=anywords&order=Bug%20Number&query_format=advanced&resolution=---&v1=472746&v2=174380 filtered bugs (no retirement, games or m-w)], both filter out bugs that block useful trackers.
* Bug cleaners: Long time untouched bugs: [https://bugs.gentoo.org/buglist.cgi?f1=blocked&f2=blocked&j_top=OR&n1=1&n2=1&o1=anywords&o2=anywords&query_format=advanced&resolution=---&v1=472746&v2=174380&order=Last%20Changed Any bugs] or [https://bugs.gentoo.org/buglist.cgi?email1=%28maintainer-wanted%7Cgames%7Cretirement%7Cjava%29%40gentoo.org&emailassigned_to1=1&emailtype1=notregexp&f1=blocked&f2=blocked&n1=1&n2=1&o1=anywords&o2=anywords&order=Last%20Changed&query_format=advanced&resolution=---&v1=472746&v2=174380 filtered bugs (no retirement, games or m-w)], both filter out bugs that block useful trackers.
* QA-Reports: Bugs last touched by year: [https://bugs.gentoo.org/buglist.cgi?f1=delta_ts&f2=delta_ts&list_id=2084118&o1=lessthaneq&o2=greaterthaneq&query_format=advanced&resolution=---&v1=2007-01-01&v2=2006-01-01 till 2006 (0 bugs)], [https://bugs.gentoo.org/buglist.cgi?f1=delta_ts&f2=delta_ts&list_id=2084118&o1=lessthaneq&o2=greaterthaneq&query_format=advanced&resolution=---&v1=2008-01-01&v2=2007-01-01 2007], [https://bugs.gentoo.org/buglist.cgi?f1=delta_ts&f2=delta_ts&list_id=2084118&o1=lessthaneq&o2=greaterthaneq&query_format=advanced&resolution=---&v1=2009-01-01&v2=2008-01-01 2008], [https://bugs.gentoo.org/buglist.cgi?f1=delta_ts&f2=delta_ts&list_id=2084118&o1=lessthaneq&o2=greaterthaneq&query_format=advanced&resolution=---&v1=2010-01-01&v2=2009-01-01 2009], [https://bugs.gentoo.org/buglist.cgi?f1=delta_ts&f2=delta_ts&list_id=2084118&o1=lessthaneq&o2=greaterthaneq&query_format=advanced&resolution=---&v1=2011-01-01&v2=2010-01-01 2010], [https://bugs.gentoo.org/buglist.cgi?f1=delta_ts&f2=delta_ts&list_id=2084118&o1=lessthaneq&o2=greaterthaneq&query_format=advanced&resolution=---&v1=2012-01-01&v2=2011-01-01 2011] and [https://bugs.gentoo.org/buglist.cgi?f1=delta_ts&f2=delta_ts&list_id=2084118&o1=lessthaneq&o2=greaterthaneq&query_format=advanced&resolution=---&v1=2013-01-01&v2=2012-01-01 2012].
== First steps ==
Because one cannot just rush in and go hunt at random bugs and expect people to agree with one's actions; the very first steps we will take is to raise the necessary discussion to get feedback on what the community wants us to do exactly, which clarifies the further limits and scope of the project.
=== Questions to be answered ===
We will need to get some questions answered to proceed:
* How old is "oldest"?
* When is a bug considered still useful?
* Are there other types of bugs we could or need to look into?
* Can this effort replace the Bug Day that does not receive interest lately?
* Do we need a mail alias so we can get CC-ed on bugs? (Effectively allowing users to help as well.)
* Do we need a mail alias so we can get assigned on bugs? (*unsure*)
* What to do in exceptional cases? (Cannot be answered until we identified them.)
This will be discussed on the mailing lists.
=== Bug summaries ===
Preferably, bugs requesting new packages should have similar formatting for the summary or title. This will allow for easy parsing of the maintainer-wanted bugs and quickly inform readers of the name and purpose of requested packages. Suggested guidelines for package requests are:
* The summary should contain the package name, the category, and a brief description of the package.
** Category suggestions are fine, but if unsure, just leave it out and mention in a comment.
** If the category isn't known, then it can be omitted.
* Version numbers should not be in the summary.
** The request is for the atom to be added in general, versioning will be dependent on the maintainer and upstream availability.
* If the addition of one package is dependent on the addition of another, this should be indicated with the Bugzilla {{c|Depends On}} field.
** Depends On should only be set for the immediate dependency - in the example below, {{c|libbaz}} would is only used for {{c|bar}}, not {{c|foo}}.
Examples of good bug summaries include:
* '''Bug 1234''' - app-editors/foo: a multicoloured text editor
* '''Bug 1236''' - app-dicts/bar: a dictionary of bad words for app-editors/foo ''[depends on 1234]''
* '''Bug 1238''' - libbaz: a library for accessing app-dicts/bar ''[depends on 1236]''
Examples of bug summaries that are less useful:
* Can foo be added to the tree?
* bar is a dictionary
* It would be cool to have libbaz if we get foo
=== This page is to be extended ===
We will need to document our practices and useful resources here (QA reports, good bug queries, ...).
== Criteria for closing a report ==
Each request is important and was made by a real user, so must be carefully evaluated prior to closing. While it is not useful to have thousands of open requests, it's also harmful to unnecessarily close requests that are still valid.
Use these guidelines to help evaluate whether a request still has merit:
{| class="table table-condensed table-striped"
|-
! Metric !! Weight !! Notes
|-
! colspan="3" | Upstream status
|-
| Exists || High || Package must still be available and fetchable (did it move to github, bitbucket, ...?)
|-
| Alive || Medium || Signs of activity - releases, commits, bug reports, mailing list?
|-
! colspan="3" | Technical debt
|-
| Dependency availability || High || Cannot require ancient dependencies that are no longer available (qt3, kde3, ...)
|-
| Toolchain || High || Needs to build in a modern system (recent GCC, glibc, ...)
|-
! colspan="3" | Suitability
|-
| License || High || Package license must be a good fit for Gentoo
|-
| User demand || Medium || Is there continuing interest in the package, or interest from multiple users?
|-
| Wider availability || Medium || Do other distros [https://pkgs.org package] it?
|}
== Project's relationship to Bug wranglers ==
This project attempts to fit side by side with [[Project:Bug-wranglers|Bug wranglers]].
Bug wranglers is a project for bug assignment. Having a separate mail alias and project page makes it easier for people as a separate form of contact, documentation, and recognition.' |
Unified diff of changes made by edit (edit_diff) | '@@ -8,8 +8,4 @@
|LeadElectionDate=2016/04/21
|Members={{Project Member
-|Developer=User:Amynka
-|Role=Member
-|IsLead=No
-}}{{Project Member
|Developer=User:Wraeth
|Role=Lead
' |
Old page size (old_size) | 7754 |
Lines added in edit (added_lines) | [] |
Lines removed in edit (removed_lines) | [
0 => '|Developer=User:Amynka',
1 => '|Role=Member',
2 => '|IsLead=No',
3 => '}}{{Project Member'
] |
New page text, stripped of any markup (new_text) | '
Bug cleaners
Description
The Gentoo Bug Cleaners project aims to clean up the oldest bugs in Bugzilla.
Project email
maintainer-wanted@gentoo.org
IRC channel
#gentoo-bugs
Lead(s)
Sam Jorna
(wraeth)Lead Last elected: 2016/04/21
Member(s)
Amy Liffey
(amynka)MemberJonas Stein
(jstein)MemberMichał Górny
(mgorny)Accidental helperMarek Szuba
(Marecki)Member
Subproject(s)(and inherited member(s))
(none)
Parent Project
Quality Assurance
Project listing
The goal of the Bug cleaners project is twofold:
The main purpose of the project is to close bugs on Bugzilla that do no longer apply due to versions and/or packages that are no longer present in the Portage tree.
As a side effect, it also tries to look for solutions for the oldest bugs.
For those that still have use, it attempts to inform the persons involved in the bug that the bug is still open if the bug is important; inviting them to make a decision on it.
Contents
1 Resources
2 First steps
2.1 Questions to be answered
2.2 Bug summaries
2.3 This page is to be extended
3 Criteria for closing a report
4 Project's relationship to Bug wranglers
Resources[edit]
Queries that can be handy for finding old bugs include:
Bug cleaners: Oldest bugs: Any bugs or filtered bugs (no retirement, games or m-w), both filter out bugs that block useful trackers.
Bug cleaners: Long time untouched bugs: Any bugs or filtered bugs (no retirement, games or m-w), both filter out bugs that block useful trackers.
QA-Reports: Bugs last touched by year: till 2006 (0 bugs), 2007, 2008, 2009, 2010, 2011 and 2012.
First steps[edit]
Because one cannot just rush in and go hunt at random bugs and expect people to agree with one's actions; the very first steps we will take is to raise the necessary discussion to get feedback on what the community wants us to do exactly, which clarifies the further limits and scope of the project.
Questions to be answered[edit]
We will need to get some questions answered to proceed:
How old is "oldest"?
When is a bug considered still useful?
Are there other types of bugs we could or need to look into?
Can this effort replace the Bug Day that does not receive interest lately?
Do we need a mail alias so we can get CC-ed on bugs? (Effectively allowing users to help as well.)
Do we need a mail alias so we can get assigned on bugs? (*unsure*)
What to do in exceptional cases? (Cannot be answered until we identified them.)
This will be discussed on the mailing lists.
Bug summaries[edit]
Preferably, bugs requesting new packages should have similar formatting for the summary or title. This will allow for easy parsing of the maintainer-wanted bugs and quickly inform readers of the name and purpose of requested packages. Suggested guidelines for package requests are:
The summary should contain the package name, the category, and a brief description of the package.
Category suggestions are fine, but if unsure, just leave it out and mention in a comment.
If the category isn't known, then it can be omitted.
Version numbers should not be in the summary.
The request is for the atom to be added in general, versioning will be dependent on the maintainer and upstream availability.
If the addition of one package is dependent on the addition of another, this should be indicated with the Bugzilla Depends On field.
Depends On should only be set for the immediate dependency - in the example below, libbaz would is only used for bar, not foo.
Examples of good bug summaries include:
Bug 1234 - app-editors/foo: a multicoloured text editor
Bug 1236 - app-dicts/bar: a dictionary of bad words for app-editors/foo [depends on 1234]
Bug 1238 - libbaz: a library for accessing app-dicts/bar [depends on 1236]
Examples of bug summaries that are less useful:
Can foo be added to the tree?
bar is a dictionary
It would be cool to have libbaz if we get foo
This page is to be extended[edit]
We will need to document our practices and useful resources here (QA reports, good bug queries, ...).
Criteria for closing a report[edit]
Each request is important and was made by a real user, so must be carefully evaluated prior to closing. While it is not useful to have thousands of open requests, it's also harmful to unnecessarily close requests that are still valid.
Use these guidelines to help evaluate whether a request still has merit:
Metric
Weight
Notes
Upstream status
Exists
High
Package must still be available and fetchable (did it move to github, bitbucket, ...?)
Alive
Medium
Signs of activity - releases, commits, bug reports, mailing list?
Technical debt
Dependency availability
High
Cannot require ancient dependencies that are no longer available (qt3, kde3, ...)
Toolchain
High
Needs to build in a modern system (recent GCC, glibc, ...)
Suitability
License
High
Package license must be a good fit for Gentoo
User demand
Medium
Is there continuing interest in the package, or interest from multiple users?
Wider availability
Medium
Do other distros package it?
Project's relationship to Bug wranglers[edit]
This project attempts to fit side by side with Bug wranglers.
Bug wranglers is a project for bug assignment. Having a separate mail alias and project page makes it easier for people as a separate form of contact, documentation, and recognition.
' |
Parsed HTML source of the new revision (new_html) | '<div class="mw-parser-output"><table class="table table-condensed" style="width: 30em; font-size: 95%; border: 1px solid #ddd; background-color: #f9f9f9; color: black; margin-bottom: 0.5em; margin-left: 1em; padding: 0.2em; float: right; clear: right; text-align:left;">
<tr>
<th style="text-align: center; background-color:#3E355A; color: white;" colspan="2"><big>Bug cleaners</big>
</th></tr>
<tr valign="top">
<th> Description
</th>
<td style="text-align: justify;"> The Gentoo Bug Cleaners project aims to clean up the oldest bugs in Bugzilla.
</td></tr>
<tr>
<th> <span title="Mails to member(s) listed below.">Project email</span>
</th>
<td> <a rel="nofollow" class="external text" href="mailto:maintainer-wanted@gentoo.org">maintainer-wanted@gentoo.org</a>
</td></tr>
<tr>
<th> <span title="The link opens a webchat to this project's Freenode IRC channel.">IRC channel</span>
</th>
<td> <a rel="nofollow" class="external text" href="https://webchat.freenode.net/?channels=gentoo-bugs">#gentoo-bugs</a>
</td></tr>
<tr valign="top">
<th> Lead(s)
</th>
<td> <ul><li><a href="/wiki/User:Wraeth" title="User:Wraeth">Sam Jorna</a>
(wraeth)<br /><i>Lead</i></li></ul> <br />Last elected: 2016/04/21
</td></tr>
<tr valign="top">
<th> Member(s)
</th>
<td> <ul><li><a href="/wiki/User:Amynka" title="User:Amynka">Amy Liffey</a>
(amynka)<br /><i>Member</i></li><li><a href="/wiki/User:Jstein" title="User:Jstein">Jonas Stein</a>
(jstein)<br /><i>Member</i></li><li><a href="/wiki/User:MGorny" title="User:MGorny">Michał Górny</a>
(mgorny)<br /><i>Accidental helper</i></li><li><a href="/wiki/User:MarekSzuba" title="User:MarekSzuba">Marek Szuba</a>
(Marecki)<br /><i>Member</i></li></ul>
</td></tr>
<tr valign="top">
<th> Subproject(s)<br /><small style="font-weight: normal;">(and inherited member(s))</small>
</th>
<td> (none)
</td></tr>
<tr>
<th> Parent Project
</th>
<td> <a href="/wiki/Project:Quality_Assurance" title="Project:Quality Assurance">Quality Assurance</a>
</td></tr>
<tr>
<td colspan="2" style="border-top: 1px solid #ddd; font-size: smaller; text-align: center;"><a href="/wiki/Project:Gentoo" title="Project:Gentoo">Project listing</a>
</td></tr></table>
<p>The goal of the Bug cleaners project is twofold:
</p>
<ul><li> The main purpose of the project is to close bugs on Bugzilla that do no longer apply due to versions and/or packages that are no longer present in the Portage tree.</li>
<li> As a side effect, it also tries to look for solutions for the <i>oldest</i> bugs.</li></ul>
<p>For those that still have use, it attempts to inform the persons involved in the bug that the bug is still open if the bug is important; inviting them to make a decision on it.
</p>
<div id="toc" class="toc"><div class="toctitle"><h2>Contents</h2></div>
<ul>
<li class="toclevel-1 tocsection-1"><a href="#Resources"><span class="tocnumber">1</span> <span class="toctext">Resources</span></a></li>
<li class="toclevel-1 tocsection-2"><a href="#First_steps"><span class="tocnumber">2</span> <span class="toctext">First steps</span></a>
<ul>
<li class="toclevel-2 tocsection-3"><a href="#Questions_to_be_answered"><span class="tocnumber">2.1</span> <span class="toctext">Questions to be answered</span></a></li>
<li class="toclevel-2 tocsection-4"><a href="#Bug_summaries"><span class="tocnumber">2.2</span> <span class="toctext">Bug summaries</span></a></li>
<li class="toclevel-2 tocsection-5"><a href="#This_page_is_to_be_extended"><span class="tocnumber">2.3</span> <span class="toctext">This page is to be extended</span></a></li>
</ul>
</li>
<li class="toclevel-1 tocsection-6"><a href="#Criteria_for_closing_a_report"><span class="tocnumber">3</span> <span class="toctext">Criteria for closing a report</span></a></li>
<li class="toclevel-1 tocsection-7"><a href="#Project.27s_relationship_to_Bug_wranglers"><span class="tocnumber">4</span> <span class="toctext">Project's relationship to Bug wranglers</span></a></li>
</ul>
</div>
<h2><span class="mw-headline" id="Resources">Resources</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Project:Bug-cleaners&action=edit&section=1" title="Edit section: Resources">edit</a><span class="mw-editsection-bracket">]</span></span></h2>
<p>Queries that can be handy for finding old bugs include:
</p>
<ul><li> Bug cleaners: Oldest bugs: <a rel="nofollow" class="external text" href="https://bugs.gentoo.org/buglist.cgi?f1=blocked&f2=blocked&j_top=OR&n1=1&n2=1&o1=anywords&o2=anywords&query_format=advanced&resolution=---&v1=472746&v2=174380&order=Bug%20Number">Any bugs</a> or <a rel="nofollow" class="external text" href="https://bugs.gentoo.org/buglist.cgi?email1=%28maintainer-wanted%7Cgames%7Cretirement%7Cjava%29%40gentoo.org&emailassigned_to1=1&emailtype1=notregexp&f1=blocked&f2=blocked&n1=1&n2=1&o1=anywords&o2=anywords&order=Bug%20Number&query_format=advanced&resolution=---&v1=472746&v2=174380">filtered bugs (no retirement, games or m-w)</a>, both filter out bugs that block useful trackers.</li>
<li> Bug cleaners: Long time untouched bugs: <a rel="nofollow" class="external text" href="https://bugs.gentoo.org/buglist.cgi?f1=blocked&f2=blocked&j_top=OR&n1=1&n2=1&o1=anywords&o2=anywords&query_format=advanced&resolution=---&v1=472746&v2=174380&order=Last%20Changed">Any bugs</a> or <a rel="nofollow" class="external text" href="https://bugs.gentoo.org/buglist.cgi?email1=%28maintainer-wanted%7Cgames%7Cretirement%7Cjava%29%40gentoo.org&emailassigned_to1=1&emailtype1=notregexp&f1=blocked&f2=blocked&n1=1&n2=1&o1=anywords&o2=anywords&order=Last%20Changed&query_format=advanced&resolution=---&v1=472746&v2=174380">filtered bugs (no retirement, games or m-w)</a>, both filter out bugs that block useful trackers.</li>
<li> QA-Reports: Bugs last touched by year: <a rel="nofollow" class="external text" href="https://bugs.gentoo.org/buglist.cgi?f1=delta_ts&f2=delta_ts&list_id=2084118&o1=lessthaneq&o2=greaterthaneq&query_format=advanced&resolution=---&v1=2007-01-01&v2=2006-01-01">till 2006 (0 bugs)</a>, <a rel="nofollow" class="external text" href="https://bugs.gentoo.org/buglist.cgi?f1=delta_ts&f2=delta_ts&list_id=2084118&o1=lessthaneq&o2=greaterthaneq&query_format=advanced&resolution=---&v1=2008-01-01&v2=2007-01-01">2007</a>, <a rel="nofollow" class="external text" href="https://bugs.gentoo.org/buglist.cgi?f1=delta_ts&f2=delta_ts&list_id=2084118&o1=lessthaneq&o2=greaterthaneq&query_format=advanced&resolution=---&v1=2009-01-01&v2=2008-01-01">2008</a>, <a rel="nofollow" class="external text" href="https://bugs.gentoo.org/buglist.cgi?f1=delta_ts&f2=delta_ts&list_id=2084118&o1=lessthaneq&o2=greaterthaneq&query_format=advanced&resolution=---&v1=2010-01-01&v2=2009-01-01">2009</a>, <a rel="nofollow" class="external text" href="https://bugs.gentoo.org/buglist.cgi?f1=delta_ts&f2=delta_ts&list_id=2084118&o1=lessthaneq&o2=greaterthaneq&query_format=advanced&resolution=---&v1=2011-01-01&v2=2010-01-01">2010</a>, <a rel="nofollow" class="external text" href="https://bugs.gentoo.org/buglist.cgi?f1=delta_ts&f2=delta_ts&list_id=2084118&o1=lessthaneq&o2=greaterthaneq&query_format=advanced&resolution=---&v1=2012-01-01&v2=2011-01-01">2011</a> and <a rel="nofollow" class="external text" href="https://bugs.gentoo.org/buglist.cgi?f1=delta_ts&f2=delta_ts&list_id=2084118&o1=lessthaneq&o2=greaterthaneq&query_format=advanced&resolution=---&v1=2013-01-01&v2=2012-01-01">2012</a>.</li></ul>
<h2><span class="mw-headline" id="First_steps">First steps</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Project:Bug-cleaners&action=edit&section=2" title="Edit section: First steps">edit</a><span class="mw-editsection-bracket">]</span></span></h2>
<p>Because one cannot just rush in and go hunt at random bugs and expect people to agree with one's actions; the very first steps we will take is to raise the necessary discussion to get feedback on what the community wants us to do exactly, which clarifies the further limits and scope of the project.
</p>
<h3><span class="mw-headline" id="Questions_to_be_answered">Questions to be answered</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Project:Bug-cleaners&action=edit&section=3" title="Edit section: Questions to be answered">edit</a><span class="mw-editsection-bracket">]</span></span></h3>
<p>We will need to get some questions answered to proceed:
</p>
<ul><li> How old is "oldest"?</li>
<li> When is a bug considered still useful?</li>
<li> Are there other types of bugs we could or need to look into?</li>
<li> Can this effort replace the Bug Day that does not receive interest lately?</li>
<li> Do we need a mail alias so we can get CC-ed on bugs? (Effectively allowing users to help as well.)</li>
<li> Do we need a mail alias so we can get assigned on bugs? (*unsure*)</li>
<li> What to do in exceptional cases? (Cannot be answered until we identified them.)</li></ul>
<p>This will be discussed on the mailing lists.
</p>
<h3><span class="mw-headline" id="Bug_summaries">Bug summaries</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Project:Bug-cleaners&action=edit&section=4" title="Edit section: Bug summaries">edit</a><span class="mw-editsection-bracket">]</span></span></h3>
<p>Preferably, bugs requesting new packages should have similar formatting for the summary or title. This will allow for easy parsing of the maintainer-wanted bugs and quickly inform readers of the name and purpose of requested packages. Suggested guidelines for package requests are:
</p>
<ul><li> The summary should contain the package name, the category, and a brief description of the package.
<ul><li> Category suggestions are fine, but if unsure, just leave it out and mention in a comment.</li>
<li> If the category isn't known, then it can be omitted.</li></ul></li>
<li> Version numbers should not be in the summary.
<ul><li> The request is for the atom to be added in general, versioning will be dependent on the maintainer and upstream availability.</li></ul></li>
<li> If the addition of one package is dependent on the addition of another, this should be indicated with the Bugzilla <span style="font-family: monospace; font-size: 95%; font-weight: bold;" class="tripleclick-separator">Depends On</span> field.
<ul><li> Depends On should only be set for the immediate dependency - in the example below, <span style="font-family: monospace; font-size: 95%; font-weight: bold;" class="tripleclick-separator">libbaz</span> would is only used for <span style="font-family: monospace; font-size: 95%; font-weight: bold;" class="tripleclick-separator">bar</span>, not <span style="font-family: monospace; font-size: 95%; font-weight: bold;" class="tripleclick-separator">foo</span>.</li></ul></li></ul>
<p>Examples of good bug summaries include:
</p>
<ul><li> <b>Bug 1234</b> - app-editors/foo: a multicoloured text editor</li>
<li> <b>Bug 1236</b> - app-dicts/bar: a dictionary of bad words for app-editors/foo <i>[depends on 1234]</i></li>
<li> <b>Bug 1238</b> - libbaz: a library for accessing app-dicts/bar <i>[depends on 1236]</i></li></ul>
<p>Examples of bug summaries that are less useful:
</p>
<ul><li> Can foo be added to the tree?</li>
<li> bar is a dictionary</li>
<li> It would be cool to have libbaz if we get foo</li></ul>
<h3><span class="mw-headline" id="This_page_is_to_be_extended">This page is to be extended</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Project:Bug-cleaners&action=edit&section=5" title="Edit section: This page is to be extended">edit</a><span class="mw-editsection-bracket">]</span></span></h3>
<p>We will need to document our practices and useful resources here (QA reports, good bug queries, ...).
</p>
<h2><span class="mw-headline" id="Criteria_for_closing_a_report">Criteria for closing a report</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Project:Bug-cleaners&action=edit&section=6" title="Edit section: Criteria for closing a report">edit</a><span class="mw-editsection-bracket">]</span></span></h2>
<p>Each request is important and was made by a real user, so must be carefully evaluated prior to closing. While it is not useful to have thousands of open requests, it's also harmful to unnecessarily close requests that are still valid.
</p><p>Use these guidelines to help evaluate whether a request still has merit:
</p>
<table class="table table-condensed table-striped">
<tr>
<th> Metric </th>
<th> Weight </th>
<th> Notes
</th></tr>
<tr>
<th colspan="3"> Upstream status
</th></tr>
<tr>
<td> Exists </td>
<td> High </td>
<td> Package must still be available and fetchable (did it move to github, bitbucket, ...?)
</td></tr>
<tr>
<td> Alive </td>
<td> Medium </td>
<td> Signs of activity - releases, commits, bug reports, mailing list?
</td></tr>
<tr>
<th colspan="3"> Technical debt
</th></tr>
<tr>
<td> Dependency availability </td>
<td> High </td>
<td> Cannot require ancient dependencies that are no longer available (qt3, kde3, ...)
</td></tr>
<tr>
<td> Toolchain </td>
<td> High </td>
<td> Needs to build in a modern system (recent GCC, glibc, ...)
</td></tr>
<tr>
<th colspan="3"> Suitability
</th></tr>
<tr>
<td> License </td>
<td> High </td>
<td> Package license must be a good fit for Gentoo
</td></tr>
<tr>
<td> User demand </td>
<td> Medium </td>
<td> Is there continuing interest in the package, or interest from multiple users?
</td></tr>
<tr>
<td> Wider availability </td>
<td> Medium </td>
<td> Do other distros <a rel="nofollow" class="external text" href="https://pkgs.org">package</a> it?
</td></tr></table>
<h2><span class="mw-headline" id="Project.27s_relationship_to_Bug_wranglers">Project's relationship to Bug wranglers</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Project:Bug-cleaners&action=edit&section=7" title="Edit section: Project's relationship to Bug wranglers">edit</a><span class="mw-editsection-bracket">]</span></span></h2>
<p>This project attempts to fit side by side with <a href="/wiki/Project:Bug-wranglers" title="Project:Bug-wranglers">Bug wranglers</a>.
</p><p>Bug wranglers is a project for bug assignment. Having a separate mail alias and project page makes it easier for people as a separate form of contact, documentation, and recognition.
</p>
<!--
NewPP limit report
Cached time: 20190630065239
Cache expiry: 86400
Dynamic content: false
[SMW] In‐text annotation parser time: 0.006 seconds
CPU time usage: 0.093 seconds
Real time usage: 0.123 seconds
Preprocessor visited node count: 371/1000000
Preprocessor generated node count: 1337/1000000
Post‐expand include size: 3531/2097152 bytes
Template argument size: 666/2097152 bytes
Highest expansion depth: 7/40
Expensive parser function count: 0/100
-->
<!--
Transclusion expansion time report (%,ms,calls,template)
100.00% 99.453 1 -total
98.43% 97.889 1 Template:Project
42.06% 41.833 5 Template:ProjectMemberLine
18.17% 18.070 5 Template:ProjectMemberLineNickname
10.24% 10.184 4 Template:Project_Member
0.98% 0.970 4 Template:C
-->
</div>' |
Unix timestamp of change (timestamp) | 1561877559 |
Wiki