Person Profile Updates

Package Details

NOTES

Nicolas Mailhot brings up the point that sometimes package maintainers are a named group, not just a list of individuals. He gives the Fonts SIG as an example, I think there is also a gecko group/team that manages those packages. A SIG can maintain an entire grouping of packages (like all of the font packages, all of the gecko packages, etc.). You can see in pkgdb that abyssinica-fonts, for example, is owned by the user 'fonts-sig': https://admin.fedoraproject.org/pkgdb/packages/name/abyssinica-fonts

Nicolas also brings up the point that sometimes a package can be part of different spins, in some instances a star feature of a spin. The package details pages should call out which spins that package is a part of.

Nicolas also suggests that packagers and non-packagers might want to put some arbitrary/freeform info in about packages. For example, for the google droid fonts package, a packager might want to make sure there is a link ot the http://fedoraproject.org/wiki/Google_Droid_fonts wiki page since it has a lot of details about that package.

Nicolas also suggests a queue where people can enter in their wishlist for software to be packaged, maybe other users can vote on it, and non-packagers can fill out the form fields (description, link, license, etc etc) for the package so the packagers don't have to fill out all that stuff.

Nicolas mentioned that Richard Hughes is looking at adding image previews to package kit descriptions, and wonders if there is a way we could access these image previews and display them within the package details screens for a package.

TODO: Nicolas recommends not using red and green tints as bad/good indicators for i18n purposes. We should play with shades of grey and blue as an alternative!

Package Details > Changelogs (*New! 21 Jan)

Package Details > Updates (*New! 21 Jan)

Package Details > Bugs (*New! 22 Jan)

NOTE: updated on 23 Jan, based on suggestions below. Still thinking about adding a statistical summary and maybe a pie chart. Also need to explore X.org/kernel special cases. Maybe add a search for all nautilus bugs too in the dashboard?

Notes on bug displays from #fedora-devel:

Toshio has 36 open bugs right now. He cares mostly about how many open bugs, and how many closed bugs across all of his packages, but he doesn't own many packages. Finer-grained bug states don't typically matter much to him.

The X.org and kernel use cases for this page should be explored. Both have triaging and use fine-grained bug states.

James Antill would like to see a list of bugs he looked at / viewed most recently (he is always logged into BZ) and also a list of bugs *he* most recently modified.

Toshio mentioned that Launchpad has a piegraph of bug states per project. It might be good to get a feel for how actively a project/package is maintained/fixed/etc. Pie graph example: http://bugs.launchpad.net/trac-bzr

As a developer, Toshio is most interested in what bugs are open. Closed bugs are more interested for someone looking at from the outside but as the developer closed bugs aren't as interesting.

From jbowes: <jbowes> mizmo: what would be nice would be like 101 bugs, 30 new. (10 new since your last visit) recently filed bugs is good though

Successful Builds List

Updates

Updates Overview List

Unpushed Updates List

Testing Updates List

Stable Updates List

Reviews

Reviews List

File:Myfedora package review stripped.svg
This is the stripped down version of the package review screen, or rather, what could be reasonably accomplished without a massive overhaul of the back end. More elaborate version below.