From Fedora Project Wiki

Remarks By Topic

Visbility

  • (-1) Tester #1, a new packager, had never heard of Fedora Community before the call for usability testers.

Branding

  • (-1) Tester #1 thought the picture of Kyle was a little off-putting :)
  • (+1) Tester #1 felt the site was consistent with Fedora branding and recognizable as an official Fedora site.

User Profiles

  • (-1) Tester #1 was a maintainer (not owner) of one package - sssd. He could not see sssd in his list of packages because he is just a maintainer. This would cause him issues using the site.
  • (-1) Tester #1 had a group he should have been a member of missing from his group memberships list on his profile.
  • (-1) Tester #1 at another point in his profile saw that sssd was listed as being owned rather than simply maintained by him. So there's an inconsistency somewhere between ownership and maintainership.
  • (-1) Tester #1 experienced incredibly slow loading time for Luke Macken's profile. He clicks on it at 16:51 in the video, and it fails to load up until 18:00 in the video (1 minute 9 seconds wait!). He refreshes and it then loads very quickly.

Search

  • (-1) Tester #1 could not figure out Dennis Gilmore's FAS name using people search. He could not sort by first name or last name. He simply could not complete the task using the tool.
  • (+1) Tester #1 very much liked that he could search for a package and see its subpackages as well.
  • (-1) Tester #1, while searching for Luke, experienced noticeably slow search time. His search started at 16:35 in the video, and he didn't receive results until 16:51 in the video (16 second delay)
  • (-1) Tester #1 experienced a very slow search time for 'ipa-server'. He starts his search at 23:23. The search continues to load up until 23:07 (44 sec!), at which point he gives up and hits the back button. Firefox appears to lock up slightly. This sucks as well, it goes on to reload the page he had been on previously (sssd package details), the page takes from 23:07-24:02 in the video to reload (55 sec!)

People Directory =

  • (-1) Tester #1 took one look at it and didn't even attempt to use it, he jumped straight to search.

Package Details

  • (-1) Tester #1 would have liked to see a listing of what packages a build of the package would kick off rebuilds for based on dependencies.
  • (-1) Tester #1 could not find a link to Fedora 9 releases for a package because it is a now-retired release. there was no link to an archive or a way to view the 'active releases' table across ALL fedora releases.
  • (0) Tester #1 noted maintainers list for yelp is quite long.
  • (-1) Tester #1 experienced a slow loading time for the bugs tab of package details. He clicks on it at 19:56 in the video, and it doesn't fully load until 20:20 (24 seconds!)
  • (+1) Tester #1 found it very easy to access ruby's changelog.

Package Maintenance

  • (-1) Tester #1 was unable to find 'unpushed updates' for packages he owned, and ended up searching for individual packages to get the information.
  • (-1) Tester #1, when navigating from a package details page, had a bit of trouble finding a list of all the builds of packages related to him.
  • (-1) Tester #1 wasn't sure what to do in order to check up on someone else's packages. He would have liked to see some kind of alerts system, email based maybe, to let him know what needs attention.
  • (-1) Tester #1 wanted to be able to kick off package builds and didn't see a way how.
  • (-1) Tester #1 also wanted to be able to kick off rebuilds, eg if the deps bumped because of an .so file change.
  • (-1) Tester #1 wanted to be able to view a dependency tree for a given package.

Navigation

  • (-1) Tester #1 ended up getting confused when he was looking at a package details page, clicked on 'package maintenance', and was brought to the package details overview page rather than the main / all-packages overview page.

Overall Site Functionality

  • (0) Tester #1 noted the site seemed more about monitoring than *doing*.

Remarks By Implication

The Good

  • (+1) Tester #1 found it very easy to access ruby's changelog.
  • (+1) Tester #1 very much liked that he could search for a package and see its subpackages as well.
  • (+1) Tester #1 felt the site was consistent with Fedora branding and recognizable as an official Fedora site.

The Bad

  • (-1) Tester #1 was unable to find 'unpushed updates' for packages he owned, and ended up searching for individual packages to get the information.
  • (-1) Tester #1, when navigating from a package details page, had a bit of trouble finding a list of all the builds of packages related to him.
  • (-1) Tester #1 wasn't sure what to do in order to check up on someone else's packages. He would have liked to see some kind of alerts system, email based maybe, to let him know what needs attention.
  • (-1) Tester #1 wanted to be able to kick off package builds and didn't see a way how.
  • (-1) Tester #1 also wanted to be able to kick off rebuilds, eg if the deps bumped because of an .so file change.
  • (-1) Tester #1 wanted to be able to view a dependency tree for a given package.
  • (-1) Tester #1 ended up getting confused when he was looking at a package details page, clicked on 'package maintenance', and was brought to the package details overview page rather than the main / all-packages overview page.
  • (-1) Tester #1 experienced a slow loading time for the bugs tab of package details. He clicks on it at 19:56 in the video, and it doesn't fully load until 20:20 (24 seconds!)
  • (-1) Tester #1 would have liked to see a listing of what packages a build of the package would kick off rebuilds for based on dependencies.
  • (-1) Tester #1 could not find a link to Fedora 9 releases for a package because it is a now-retired release. there was no link to an archive or a way to view the 'active releases' table across ALL fedora releases.
  • (-1) Tester #1 took one look at it and didn't even attempt to use it, he jumped straight to search.
  • (-1) Tester #1, while searching for Luke, experienced noticeably slow search time. His search started at 16:35 in the video, and he didn't receive results until 16:51 in the video (16 second delay)
  • (-1) Tester #1 experienced a very slow search time for 'ipa-server'. He starts his search at 23:23. The search continues to load up until 23:07 (44 sec!), at which point he gives up and hits the back button. Firefox appears to lock up slightly. This sucks as well, it goes on to reload the page he had been on previously (sssd package details), the page takes from 23:07-24:02 in the video to reload (55 sec!)
  • (-1) Tester #1 could not figure out Dennis Gilmore's FAS name using people search. He could not sort by first name or last name. He simply could not complete the task using the tool.
  • (-1) Tester #1 was a maintainer (not owner) of one package - sssd. He could not see sssd in his list of packages because he is just a maintainer. This would cause him issues using the site.
  • (-1) Tester #1 had a group he should have been a member of missing from his group memberships list on his profile.
  • (-1) Tester #1 at another point in his profile saw that sssd was listed as being owned rather than simply maintained by him. So there's an inconsistency somewhere between ownership and maintainership.
  • (-1) Tester #1 experienced incredibly slow loading time for Luke Macken's profile. He clicks on it at 16:51 in the video, and it fails to load up until 18:00 in the video (1 minute 9 seconds wait!). He refreshes and it then loads very quickly.
  • (-1) Tester #1 thought the picture of Kyle was a little off-putting :)
  • (-1) Tester #1, a new packager, had never heard of Fedora Community before the call for usability testers.

The Meh

  • (0) Tester #1 noted the site seemed more about monitoring than *doing*.
  • (0) Tester #1 noted maintainers list for yelp is quite long.