From Fedora Project Wiki
Line 9: | Line 9: | ||
== allows rating and tagging applications == | == allows rating and tagging applications == | ||
* | Requirement: | ||
* pkgdb exports a sqlite db of tags=>binary rpm names for each release that bodhi incorporate into yum repodata. /tagger needs to do that as well. | |||
Ideas: | |||
* Do we need to keep Tags in the pkgdb view? We could simply remove Tags from the Application Info pane and provide a link next to "User Comments | Builds" like "User Comments | Builds | Tags" that redirect the user to https://apps.fedoraproject.org/tagger/geany | |||
== shows open bugz against a package. == | == shows open bugz against a package. == |
Revision as of 15:56, 14 August 2012
pkgdb code that needs migrating:
shows applications (anything that has a .desktop)
shows builds (binrary rpm packages in the repositories)
Idea: Consider https://admin.fedoraproject.org/pkgdb/applications/Geany -- we could remove the "Available Builds" section and have the link at the top instead redirect the user to https://apps.fedoraproject.org/packages/geany/builds and "be done with it".
allows rating and tagging applications
Requirement:
- pkgdb exports a sqlite db of tags=>binary rpm names for each release that bodhi incorporate into yum repodata. /tagger needs to do that as well.
Ideas:
- Do we need to keep Tags in the pkgdb view? We could simply remove Tags from the Application Info pane and provide a link next to "User Comments | Builds" like "User Comments | Builds | Tags" that redirect the user to https://apps.fedoraproject.org/tagger/geany