IdentifyingPrimaryPackages
|
Size: 1769
Comment:
|
Size: 3261
Comment: Initial draft
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| ## page was renamed from UbuntuDevel/IdentifyingPrimaryPackages ## page was renamed from UbuntuDevel |
|
| Line 10: | Line 7: |
| * People: NeedsLead, NeedsSecond[[BR]] | * People: MichaelVogtLead, NeedsSecond[[BR]] |
| Line 43: | Line 40: |
| We have around 3000 binary packages in main right now. When we cut out "libs, devel, doc, tex and translations" we still have around 1500 binary packages. Most packages with .desktop files in them are likely candiates for primary packages because they are applicatons that the user uses directely. Other likely candidates are server programms (like samba, apache). We want to display those primary packages in a special package install application (that was discussed in the [[FindingPackages]] BOF). A use case is: Klaus wants to install a cd burning application. He is not interessted in all the libs/doc packages but only wants to install the application. |
|
| Line 45: | Line 48: |
| === Data Preservation and Migration === | The primary packages needs to indified by the means descriped above. This list is then used in the special application install application. A similar list is usefull for universe. Here we want to split that list up into various subcategories (e.g. "games"). This needs to be done by the MOTU teams (e.g. the MOTU game team). We may review the top 25% of http://popcon.ubuntu.com/universe/by_inst to see what is interessting for universe. |
| Line 49: | Line 52: |
| All the packages in main needs to be reviewed and a list compiled from them. Some of the data can be gathered automatically, but it needs to be reviewed by hand. |
|
| Line 51: | Line 56: |
| Identifing the packages does not requires a user interface. The primary packages will be displayed to the user by a enhanced version of gnome-app-install as descriped in [[FindingPackages]]. The primary packages should probably have i18ned descriptions to make the access for non-english speaking people easier. |
|
| Line 52: | Line 59: |
No work in this area was done so far. |
Identifying Primary Packages
Status
Created: 20/04/05 by MarkShuttleworthBR
Priority: LowPriorityBR
People: MichaelVogtLead, NeedsSecondBR
Contributors: MarkShuttleworthBR
Interested: BR
Status: BrainDump, UduBof, DistroSpecificationBR
Branch: BR
Malone Bug: BR
Packages: BR
Depends: BR
Introduction
This specification describes a way of categorising packages so that people can be presented with a more straightforward package selection. Currently, Ubuntu main consists of well over 1,000 packages. The goal of this specification is to reduce the normal default package list to around 200 packages, by choosing not to display libraries and developer packages.
Rationale
With the number of packages formally supported by the Ubuntu team growing every month, we need to find ways to make it easier for users to find the package they are looking for. One way to do this is to show only the "primary" packages by default, where "primary" denotes a package that is not a library or dev or doc package.
In some cases, a library could be a primary package in its own right, but in general it's unlikely that an end-user would be looking for a specific library. End-users are more likely to be looking for applications and utilities, so we would like to present a list that by default is limited to those "primary" applications.
Scope and Use Cases
We have around 3000 binary packages in main right now. When we cut out "libs, devel, doc, tex and translations" we still have around 1500 binary packages. Most packages with .desktop files in them are likely candiates for primary packages because they are applicatons that the user uses directely. Other likely candidates are server programms (like samba, apache).
We want to display those primary packages in a special package install application (that was discussed in the FindingPackages BOF).
A use case is: Klaus wants to install a cd burning application. He is not interessted in all the libs/doc packages but only wants to install the application.
Implementation Plan
The primary packages needs to indified by the means descriped above. This list is then used in the special application install application. A similar list is usefull for universe. Here we want to split that list up into various subcategories (e.g. "games"). This needs to be done by the MOTU teams (e.g. the MOTU game team). We may review the top 25% of http://popcon.ubuntu.com/universe/by_inst to see what is interessting for universe.
Packages Affected
All the packages in main needs to be reviewed and a list compiled from them. Some of the data can be gathered automatically, but it needs to be reviewed by hand.
User Interface Requirements
Identifing the packages does not requires a user interface. The primary packages will be displayed to the user by a enhanced version of gnome-app-install as descriped in FindingPackages. The primary packages should probably have i18ned descriptions to make the access for non-english speaking people easier.
Outstanding Issues
No work in this area was done so far.
UbuntuDownUnder/BOFs/IdentifyingPrimaryPackages (last edited 2008-08-06 16:32:33 by localhost)