--- xml/htdocs/proj/en/glep/glep-0017.html 2004/11/11 21:40:36 1.2 +++ xml/htdocs/proj/en/glep/glep-0017.html 2006/10/10 20:25:14 1.3 @@ -8,9 +8,252 @@ -->- +
|Author:||Caleb Tennis <caleb at gentoo.org>|
Many of the ebuild scripts found within Gentoo's Portage have come as a direct result of user submission via Gentoo's Bugzilla interface. However, a large number of open ebuild requests remain in Bugzilla. This GLEP attempts to resolve these requests.
As of the first draft of this GLEP, there are 1517 EBUILD bug requests in Gentoo's bugzilla database. These requests generally fall into three categories:
1. The package is important to Gentoo users, but has simply has not yet made @@ -94,44 +336,44 @@
Furthermore, having a policy in place as to how ebuild bug requests are handled is important for consistency and accountability.
Portage simply cannot contain an automated ebuild for every software package available. Ebuilds that are included are done so mostly based on the whim and knowledge of developers. Many software packages are of interest only to a small subset of end users, and as such would be a misuse of resources by including in Portage.
This implementation applies only to requests which have been idle in the database for an extended period of time. The recommended time is 90 days.
After this period, the bugs should be handled in the follow manner:
The (systematic) denial of the inclusion of ebuilds into the Portage tree may leave some users to feel slighted because their ebuild was not accepted into Portage. This is an unfortunate side effect of a system that relies on acceptal or denial.
It may be desirable to provide an official repository for abandoned ebuilds to go. Any attachments to these bug reports could be placed here, so that the author's effort has not gone in vein.
No current policies exist that interfere with this document.