FedoraCommunity/UsabilityTestingRound1/AnalysisAndTakeaways

= Remarks By Topic =

Visibility

 * (-1) Tester #1, a new packager, had never heard of or used Fedora Community before the call for usability testers.
 * (-1) Tester #2, an experienced packager, had never heard of or used Fedora Community before the call for usability testers.
 * (+1) Tester #3, a new packager, had heard of Fedora Community on fedora-announce and also saw the ads on www.fedoraproject.org
 * (-1) Tester #3, a new packager, asks for help a lot on IRC, and the experienced maintainers that help her show her how to use the old tools and never use Fedora Community, so she's more apt to use the other older tools.
 * (-1) Tester #3, had only used Fedora Community 2x since launch.
 * (-1)  Tester #3 wouldn't think to use Fedora Community to search for someone - first instinct to ask on IRC or ask FASbot.
 * (-1) Tester #4 only used Fedora Community a handful of times, and never for the workflows/tasks it supports - only to see if it was up and running.
 * (-1) Tester #4 said he would never think to use Fedora Community to look up what versions of a package are available in Fedora releases - the reason he gave is that the website lags behind the mirrors. He rarely used the web to get packages.
 * (0) Tester #4 found out about Fedora Community from Luke Macken.
 * (+1) Tester #5 had heard of Fedora Community on planet.fedoraproject.org.
 * (+1) Tester #5 had heard of Fedora Community on planet.fedoraproject.org.
 * (-1) Tester #5 had only used Fedora Community twice.
 * (-1) Tester #5 struggled to remember the URL for Fedora Community so he didn't use it often.

Branding

 * (-1) Tester #1 thought the picture of Kyle was a little off-putting :)
 * (-1) Tester #2 thought the picture of Kyle was scary
 * (+1)  Tester #1 felt the site was consistent with Fedora branding and recognizable as an official Fedora site.
 * (+1)  Tester #2 felt the site was consistent with Fedora branding and recognizable as an official Fedora site.
 * (+1)  Tester #2 felt the site was related to package maintenance.
 * (-1)  Tester #2 wasn't sure where to start or why he was on the site.
 * (-1) Tester #3 was not sure what Fedora Community was when he first saw it. It's not clear from the name, and to a new packager the lingo is intimidating.
 * (-1) Tester #3 wondering - why do we need a community? What more do we need? This doesn't seem associated with package management. We already have forums, mailing lists, etc.
 * (+1) Tester #4 thought the site looked packager-centric and also thought the site looked like a way to see what was going on in Fedora.
 * (+1) Tester #5 thought Fedora Community looked clean & professional.
 * (-1) Tester #5 thought 'Community' was a confusing name.
 * (+1) Tester #6 thought the front page looked 'slick'
 * (+1) Tester #6 thought the site looked like a place for Fedora packagers to work with packages and see what people on doing.
 * (-1) Tester #6 thought the fonts on the left were too big.

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.
 * (+1)  Tester #2's package listings and group memberships were correct.
 * (-1)  Tester #2 owns 8 packages, only saw 5 in the sidebar with a link to 'view more.' He would have liked maybe an in-place AJAX expander so he didn't have to load a new page to see all 8.
 * (+1) Tester #2 was able to find out how many packages lmacken owns and whether or not there were unpushed updates for them.
 * (+1) Tester #2 found the listing of IRC nicks very helpful.
 * (+1)  Tester #3's package listings and group memberships were correct.
 * (+1)  Tester #3 really liked that her blog was listed here - a pleasant surprise. It's good additional info to determine if another user is still active in the community or not as well.
 * (-1)  Tester #3 in progress builds are not as useful for me because i only own 3 packages
 * (-1)  Tester #3 would like to see her trac tickets here, but they're not there.
 * (-1) Tester #3 unclear if it's possible to view only the packages the person owns, only the packages they maintain, or both.
 * (-1) Tester #4's profile was missing group memberships.
 * (-1) Tester #4 remarked that most of the groups that were listed in his profile he simply didn't care about. The groups he really cares about are the ones that he has sponsored people in, and the ones that he's a team lead for. (For example, he does not care about cla_done at all or ever.)
 * (-1) Tester #4 found the package affiliations list on his profile confusing. It just shows a list of packages, not what you can do with them.
 * (-1) Tester #4 could not load user profile details pages for people other than himself.
 * (+1) Tester #4 liked the 'hidden goodies' under the my profile > package maintenance tab.
 * (0) Tester #5 noted his personal details on his profile were correct.
 * (-1) Tester #5 noticed one of his group memberships was missing from the list in his profile. It wasn't in the 'view more' view either.
 * (-1) Tester #5 noticed a 'missing data' error on one of his profile pages.
 * (0) Tester #5 thought his packages listing on his profile was accurate.
 * (-1) Tester #5 was unable to load Luke Macken's profile (error - failed to load.)
 * (-1) Tester #6 was missing at least one group from his/her profile.
 * (-1) Tester #6 would like to see the list of packages owned expand in-page without a full page reload.
 * (+1) Tester #6 had accurate package listings on his/her profile.
 * (-1) Tester #6 couldn't complete part of the test because non-self user profiles were not working at all.

Sidebar Widgets

 * (-1)  Tester #2 didn't have any interest in the 'all packages' widget in the sidebar - "Maybe Jesse would care about that. I don't."
 * (-1)  Tester #3 found that on her profile, the 'go to my packages' widget in the right was labeled 'go to users packages' - BUG
 * (-1) Tester #3 is there a difference between what the alerts and packages i own widgets are telling me, or is it just redundant?
 * (-1) Tester #3 when clicking on lmacken's profile, on a link that indicated it would point to lmacken's succeeded builds - it brought her to *her* builds, not lmacken's. This bug seemed to affect all build and update links in that widget. BUG.
 * (-1) Tester #4 noticed the alerts widget was broken.
 * (-1) Tester #4 noted the 'my tasks' widget in the lower right was cut off prematurely.
 * (-1) Tester #5 noted the 'my tasks' widget in the lower right was cut off prematurely.
 * (-1) Tester #6 noticed the alerts widget on their profile was broken (not loading?)
 * (-1) Tester #6 wanted the sidebar that showed "packages i own > unpushed updates" to have counts for each. Instead he/she had to click and load another page to get the number.

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!)
 * (-1) Tester #2 made several attempts to find Dennis Gilmore's FAS name using search with no luck.
 * (-1) Tester #2 found pagination on the bottom of search results page very difficult to see.
 * (0) Tester #2 for package results, would have liked to see the maintainer's name listed by the package in the results page - would asve him a click and a page load since that is what he's usually looking for.
 * (-1) Tester #2 misspelled yelp while looking for it, and the search return nothing. It is very unforgiving for misspelling.
 * (+1) Tester #2 was easily able to lmacken via search.
 * (-1) Tester #2 clicked on search in the lower left and for the first time saw the search guide. Whoops. First instinct was to use searchbox at the top which means otherwise he'd never have seen those instructions.
 * (+1) Tester #3, found Fedora Community very helpful in looking up information about package maintainers in the past.
 * (-1) Tester #3 found that people search doesn't work without being logged in, and it doesn't advertise that people search is possible at all if you try to use it while not logged in. it's a very valuable part of the site...
 * (-1) Tester #3 made several attempts to find Dennis Gilmore's FAS name using search with no luck.
 * (+1) Tester #3 was able to find yelp with no trouble.
 * (+1) Tester #3 was able to find lmacken's profile with no trouble.
 * (+1) Tester #3 was happy to note that search didn't require caps for 'Network Manager' and was able to find it without trouble.
 * (+1) Tester #3 had no problem finding ruby.
 * (-1) Tester #4 could not find Dennis Gilmore in people search.
 * (-1) Tester #4 would not normally use the web to look up a package maintainer - he would use zodbot.
 * (-1) Tester #5 could not find Dennis Gilmore in people search.
 * (-1) Tester #5 was not offered an alternate spelling when he misspelled Dennis' name 'Denis.'
 * (+1) Tester #6 really liked being able to search for packages and people.
 * (-1) Tester #6 could not find dennis.

People Directory

 * (-1) Tester #1 took one look at it and didn't even attempt to use it, he jumped straight to search.
 * (-1) Tester #2 could not find Dennis Gilmore using the people directory - difficult and slow to browse.

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.
 * (-1) Tester #2 could not find Fedora 9 (retired release) information on inkscape active releases widget.
 * (-1) Tester #2 did not know that the 'builds' link with the koji icon in the center of the page linked out externally to koji - he would have retreated there to find Fedora 9 release version information for inkscape there since it wasn't in active releases. Also, there was no link to koji in the builds pages for the package.
 * (-1) Tester #2 the updates page for the package didn't have a link to that package's details in bodhi.
 * (-1) Tester #2 the SRPM is not on the 'sources' tab of the package. An obvious place to look for it.
 * (+1) Tester #2 was easily able to find maintainer's name right on the front page of package details.
 * (+1) Tester #2 was able to the bugs dashboard for NetworkManager on first try.
 * (-1) Tester #2 found package bugs tab very slow to load (but understands that BZ is slow in general)
 * (-1) Tester #2 did not notice the changelog menu item, and clicked over to the spec to view it rather than see the nicely formatted one. Changelog is under maintenance tools - perhaps it belongs in details?
 * (-1) Tester #2 clicked on updates in main content area to go offsite to bodhi - did not notice the 'updates' link in the right sidebar that keeps you inside fedora community
 * (-1) Tester #3 could not find Fedora 9 (retired release) information on inkscape active releases widget.
 * (-1) Tester #3 was confused by the external links bar in the package details page. Clicked on source to find SRPM and instead ended up on viewcvs - did not notice source item in right toolbar that would have kept her inside Fedora Community.
 * (-1) Tester #3 confused by the difference between maintainers and owners, especially in the right sidebar - not sure which to click.
 * (-1) Tester #3 noticed the external-linking 'bugs' icon for Bugzilla in the main content area before the Fedora-Community-centric bugs dashboard item in the right sidebar 'Bugs' - whoops. Our bugs dashboard is a better experience.
 * (-1) Tester #3 confused by the placement of the bugs nav item for package details. It's not really package maintenance, more helping out with a package to report a bug?
 * (-1) Tester #3 looked for a changelog on the updates page - nothing.
 * (-1) Tester #3 wanted a way to get a diff for changelog - there isn't a way to do this now.
 * (0) Tester #3 did not see right nav 'changelog' nav item, found changelog during second attempt looking at the main content area for package details landing page.
 * (+1) Tester #4 was successfully able to determine if verisno 0.47 of Inkscape was available for F10.
 * (-1) Tester #4 found the SRPM for Inkscape, but had a very difficult time doing so.
 * (+1) Tester #4 was successfully and easily able to determine the package owner for yelp.
 * (+1) Tester #4 was successfully able to find the changelog for ruby.
 * (+1) Tester #4 found the bugs page for NetworkManager without much difficulty.
 * (+1) Tester #5 was able to successfully locate Inkscape .47 for Fedora 10.
 * (+1) Tester #5 was able to successfully locate an Inkscape SRPM for 0.47.
 * (+1) Tester #5 was easily able to find the maintainer for yelp.
 * (-1) Tester #5 was unable to load the NetworkManager bugs page.
 * (+1) Tester #5 figured out where to report bugs on NetworkManager relatively easily.
 * (+1) Tester #5 found the ruby changelog easily.
 * (-1) Tester #6 didn't know what the karma face meant.
 * (+1) Tester #6 was able to find inkscape in F10 updates testing.
 * (+1) Tester #6 found yelp's maintainer easily.
 * (-1) Tester #6 didn't expect the inkscape version in the active releases table to link to bodhi. was hoping it'd link to downloads.
 * (+1) Tester #6 found the bugs page for NetworkManager.
 * (+1) Tester #6 found ruby's changelog without issue.

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.
 * (+1) Tester #2 was able to find his unpushed updates via 'my pending updates' in the right sidebar of his profile.
 * (+1) Tester #2 was able to find a list of all his builds by looking at the right bar of his profile and clicking on builds - overview.
 * (0) Tester #2 was unsure if the 'in-progress builds' widgets/page would automatically update or if he'd have to refresh the page to get updated information on those builds.
 * (+1) Tester #3 was able to find her unpushed updates via 'my pending updates' in the right sidebar of her profile ('packages i own').
 * (+1) Tester #3 was able to find her builds via the alerts right sidebar in her profile.
 * (-1) Tester #3 had no idea what karma was and could not finding it using search nor searching in a package details page using Firefox to scan the page.
 * (-1) Tester #4 had a difficult time (it took about 4 false starts, but he did find it) finding where he could get a list of his own unpushed updates.
 * (+1) Tester #4 had no problems finding the list of his builds in the right sidebar.
 * (+1) Tester #4 was able to find his packages in updates testing.
 * (+1) Tester #4 liked that you can work with testing updates in Fedora Community and noted this was not possible in the CLI tools.
 * (-1) Tester #4 did not like that he couldn't see non-update builds in Fedora Community. (scratch builds? Is that what he was referring to? --Duffy 19:39, 8 March 2010 (UTC))
 * (-1) Tester #4 wanted to be able to push several updates at once (not possible in Fedora Community today).
 * (-1) Tester #4 felt the general package list under the packages tab was not useful.
 * (-1) Tester #5 could not locate where unpushed package updates would go.
 * (-1) Tester #5 struggled to find an overview of his builds.
 * (+1) Tester #5 found unpushed testing updates.
 * (-1) Tester #6 sees builds that failed 3 months ago in their builds overview. If the build has been fixed since then - don't display the old failures! it's depressing.
 * (-1) Tester #6 was confused about the difference between testing updates and unpushed updates.

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.
 * (+1) Tester #3 found that both the left nav 'my profile' item and her name in the upper right corner brought her to her profile - she was pleased with this as she prefers using the link in the upper right.
 * (-1) Tester #5 thought the right sidebar was a general sidebar when it was package specific. Clicked' updates' for the ruby package when wanting to see updates across all packages.
 * (-1) Tester #6 found their profile without issue.
 * (-1) Tester #6 had a confusing time finding the SRPM for inkscape. too many tools on the right side of the page.
 * (-1) The central 'links' bar on the package details overview screen was generally confusing - many of the testers didn't realize it went off-site.

Overview

 * (-1) Tester #4 wasn't sure why he was seeing packages that were built that he didn't build (front page, not logged in.) Did not like the planet feed either.
 * (-1) Tester #4 did not find the latest stable and latest testing updates section of the overview to be useful.
 * (+1) Tester #4 thought the latest builds section of the overview was useful.

Overall Site Functionality

 * (0) Tester #1 noted the site seemed more about monitoring than *doing*.
 * (+1) Tester #2 likes how the site keeps all the information in one spot rather than across different systems (koji, bodhi, pkgdb)
 * (+1) Tester #2 likes how in Fedora Community, if you're not sure how to do something the 'Fedora Community way' it's very easy to revert back to the old way of doing things with the links to pkgdb, koji, bodhi, etc
 * (-1) Tester #2 thinks the fonts are a little small
 * (-1) Tester #2 would like the text to be easier to scan.
 * (+1) Tester #2 likes that Fedora Community is not another password/login - uses the same account he's used to using for Fedora.
 * (-1) Tester #3 would like to see more documentation/tutorials geared towards new package maintainers to not only help them use the site, but learn how to maintain a package.
 * (0) Tester #3 was at first unsure if she already had a login for the site.
 * (-1) Tester #3 visited the create new login page, dumps you over to the FAS site which looks completely different - very bewildering for a new user. Doesn't tell her what she's signing up for.
 * (-1) Tester #3 very confused by the concept of karma and disappointed about documentation turned up when she searched the web for it.
 * (-1) Tester #4 noticed slowness in loading the front page of Fedora Community.
 * (-1) Tester #4 noticed slowness in loading the 'active releases' widget for the cacti package.
 * (-1) Tester #4 noticed slowness in loading the 'maintenance tools' top tab for the cacti package.
 * (-1) Tester #4 prefers using a CLI rather than the web to maintain packages - his fingers hardly ever leave the home row of his keyboard. He didn't find Fedora Community a compelling improvement over his current way of doing things.
 * (-1) Tester #4 thought the page that loads when you log out is weird (he was the only user to log out during the test.)
 * (-1) Tester #6 tried to use it to look up a package owner before this test, but found that it was must faster to go to koji.
 * (-1) Tester #6 saw some UI niggles on the front page (sidebar widgets getting cut off / etc)
 * (-1) Tester #6 felt the spinners loading areas of the page took too long, even on a fast connection.
 * (-1) Tester #6 said it took forever to load his/her unpushed updates. (right sidebar > packages i own > unpushed updates)
 * (-1) Tester #6 wasn't able to get the main 'builds' tab to load the first time he/she clicked on it.
 * (-1) Tester #6 thought Fedora community was much slower than the command line tools he/she used.
 * (+1) Tester #6 thinks bodhi is hard and Fedora Community makes it easier.
 * (+1) Tester #6 likes seeing builds and updates in one place.
 * (-1) Tester #6 confused over own vs. maintain packages.

Suggestions

 * (0) Tester #4 suggested having a widget that indicates whether or not rawhide is working.
 * (0) Tester #4 suggested having a widget that indicates if koji is down or not.
 * (0) Tester #4 suggested having some indication of the release schedules / milestones / deadlines in Fedora Community to help make them more visible.
 * (0) Tester #5 would have liked to see more discussion / interactivity on the site.
 * (0) Tester #6 suggested having hudson weather report data on the builds overview page.
 * (0) Tester #6 would use Fedora Community if it had a bug cache faster than bugzilla.
 * (0) Tester #6 would like to see a list of bugs that are open against all his/her packages in one single view - bug dashboard.
 * (0) Tester #6 would like Fedora Community to be faster.
 * (0) Tester #6 would like to see a web-based editor for spec files to commit them.
 * (0) Tester #6 would like to see CVS urls for packages to make it easy to copy/paste and grab a package locally.
 * (0) Tester #6 would like to see group membership info on the main profile page.

= 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.
 * (+1) Tester #3, a new packager, had heard of Fedora Community on fedora-announce and also saw the adds on www.fedoraproject.org
 * (+1)  Tester #2 felt the site was consistent with Fedora branding and recognizable as an official Fedora site.
 * (+1)  Tester #2 felt the site was related to package maintenance.
 * (+1)  Tester #2's package listings and group memberships were correct.
 * (+1) Tester #2 was able to find out how many packages lmacken owns and whether or not there were unpushed updates for them.
 * (+1) Tester #2 found the listing of IRC nicks very helpful.
 * (+1)  Tester #3's package listings and group memberships were correct.
 * (+1)  Tester #3 really liked that her blog was listed here - a pleasant surprise. It's good additional info to determine if another user is still active in the community or not as well.
 * (+1) Tester #3 was able to find yelp with no trouble.
 * (+1) Tester #3 was able to find lmacken's profile with no trouble.
 * (+1) Tester #3 was happy to note that search didn't require caps for 'Network Manager' and was able to find it without trouble.
 * (+1) Tester #3 had no problem finding ruby.
 * (+1) Tester #2 was easily able to lmacken via search.
 * (+1) Tester #3, found Fedora Community very helpful in looking up information about package maintainers in the past.
 * (+1) Tester #2 was easily able to find maintainer's name right on the front page of package details.
 * (+1) Tester #2 was able to the bugs dashboard for NetworkManager on first try.
 * (+1) Tester #2 was able to find his unpushed updates via 'my pending updates' in the right sidebar of his profile.
 * (+1) Tester #2 was able to find a list of all his builds by looking at the right bar of his profile and clicking on builds - overview.
 * (+1) Tester #3 was able to find her unpushed updates via 'my pending updates' in the right sidebar of her profile ('packages i own').
 * (+1) Tester #3 was able to find her builds via the alerts right sidebar in her profile.
 * (+1) Tester #3 found that both the left nav 'my profile' item and her name in the upper right corner brought her to her profile - she was pleased with this as she prefers using the link in the upper right.
 * (+1) Tester #2 likes how the site keeps all the information in one spot rather than across different systems (koji, bodhi, pkgdb)
 * (+1) Tester #2 likes how in Fedora Community, if you're not sure how to do something the 'Fedora Community way' it's very easy to revert back to the old way of doing things with the links to pkgdb, koji, bodhi, etc
 * (+1) Tester #2 likes that Fedora Community is not another password/login - uses the same account he's used to using for Fedora.

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.
 * (-1) Tester #2, an experienced packager, had never heard of or used Fedora Community before the call for usability testers.
 * (-1) Tester #3, a new packager, asks for help a lot on IRC, and the experienced maintainers that help her show her how to use the old tools and never use Fedora Community, so she's more apt to use the other older tools.
 * (-1) Tester #3, had only used Fedora Community 2x since launch.
 * (-1)  Tester #3 wouldn't think to use Fedora Community to search for someone - first instinct to ask on IRC or ask FASbot.
 * (-1) Tester #1 thought the picture of Kyle was a little off-putting :)
 * (-1) Tester #2 thought the picture of Kyle was scary
 * (-1)  Tester #2 wasn't sure where to start or why he was on the site.
 * (-1) Tester #3 was not sure what Fedora Community was when he first saw it. It's not clear from the name, and to a new packager the lingo is intimidating.
 * (-1) Tester #3 wondering - why do we need a community? What more do we need? This doesn't seem associated with package management. We already have forums, mailing lists, etc.
 * (-1)  Tester #2 owns 8 packages, only saw 5 in the sidebar with a link to 'view more.' He would have liked maybe an in-place AJAX expander so he didn't have to load a new page to see all 8.
 * (-1)  Tester #3 in progress builds are not as useful for me because i only own 3 packages
 * (-1) [[FedoraCommunity/UsabilityTestingRound1/UsabilityTester3 | Tester #3] would like to see her trac tickets here, but they're not there.
 * (-1) Tester #3 unclear if it's possible to view only the packages the person owns, only the packages they maintain, or both.
 * (-1)  Tester #2 didn't have any interest in the 'all packages' widget in the sidebar - "Maybe Jesse would care about that. I don't."
 * (-1)  Tester #3 found that on her profile, the 'go to my packages' widget in the right was labeled 'go to users packages' - BUG
 * (-1) Tester #3 is there a difference between what the alerts and packages i own widgets are telling me, or is it just redundant?
 * (-1) Tester #3 when clicking on lmacken's profile, on a link that indicated it would point to lmacken's succeeded builds - it brought her to *her* builds, not lmacken's. This bug seemed to affect all build and update links in that widget. BUG.
 * (-1) Tester #2 made several attempts to find Dennis Gilmore's FAS name using search with no luck.
 * (-1) Tester #2 found pagination on the bottom of search results page very difficult to see.
 * (-1) Tester #2 misspelled yelp while looking for it, and the search return nothing. It is very unforgiving for misspelling.
 * (-1) Tester #2 clicked on search in the lower left and for the first time saw the search guide. Whoops. First instinct was to use searchbox at the top which means otherwise he'd never have seen those instructions.
 * (-1) Tester #3 found that people search doesn't work without being logged in, and it doesn't advertise that people search is possible at all if you try to use it while not logged in. it's a very valuable part of the site...
 * (-1) Tester #3 made several attempts to find Dennis Gilmore's FAS name using search with no luck.
 * (-1) Tester #2 could not find Dennis Gilmore using the people directory - difficult and slow to browse.
 * (-1) Tester #2 could not find Fedora 9 (retired release) information on inkscape active releases widget.
 * (-1) Tester #2 did not know that the 'builds' link with the koji icon in the center of the page linked out externally to koji - he would have retreated there to find Fedora 9 release version information for inkscape there since it wasn't in active releases. Also, there was no link to koji in the builds pages for the package.
 * (-1) Tester #2 the updates page for the package didn't have a link to that package's details in bodhi.
 * (-1) Tester #2 the SRPM is not on the 'sources' tab of the package. An obvious place to look for it.
 * (-1) Tester #2 found package bugs tab very slow to load (but understands that BZ is slow in general)
 * (-1) Tester #2 did not notice the changelog menu item, and clicked over to the spec to view it rather than see the nicely formatted one. Changelog is under maintenance tools - perhaps it belongs in details?
 * (-1) Tester #2 clicked on updates in main content area to go offsite to bodhi - did not notice the 'updates' link in the right sidebar that keeps you inside fedora community
 * (-1) Tester #3 could not find Fedora 9 (retired release) information on inkscape active releases widget.
 * (-1) Tester #3 was confused by the external links bar in the package details page. Clicked on source to find SRPM and instead ended up on viewcvs - did not notice source item in right toolbar that would have kept her inside Fedora Community.
 * (-1) Tester #3 confused by the difference between maintainers and owners, especially in the right sidebar - not sure which to click.
 * (-1) Tester #3 noticed the external-linking 'bugs' icon for Bugzilla in the main content area before the Fedora-Community-centric bugs dashboard item in the right sidebar 'Bugs' - whoops. Our bugs dashboard is a better experience.
 * (-1) Tester #3 confused by the placement of the bugs nav item for package details. It's not really package maintenance, more helping out with a package to report a bug?
 * (-1) Tester #3 looked for a changelog on the updates page - nothing.
 * (-1) Tester #3 wanted a way to get a diff for changelog - there isn't a way to do this now.
 * (-1) Tester #3 had no idea what karma was and could not finding it using search nor searching in a package details page using Firefox to scan the page.
 * (-1) Tester #2 thinks the fonts are a little small
 * (-1) Tester #2 would like the text to be easier to scan.
 * (-1) Tester #3 would like to see more documentation/tutorials geared towards new package maintainers to not only help them use the site, but learn how to maintain a package.
 * (-1) Tester #3 visited the create new login page, dumps you over to the FAS site which looks completely different - very bewildering for a new user. Doesn't tell her what she's signing up for.
 * (-1) Tester #3 very confused by the concept of karma and disappointed about documentation turned up when she searched the web for it.

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.
 * (0) Tester #2 for package results, would have liked to see the maintainer's name listed by the package in the results page - would save him a click and a page load since that is what he's usually looking for.
 * (0) Tester #3 did not see right nav 'changelog' nav item, found changelog during second attempt looking at the main content area for package details landing page.
 * (0) Tester #2 was unsure if the 'in-progress builds' widgets/page would automatically update or if he'd have to refresh the page to get updated information on those builds.
 * (0) Tester #3 was at first unsure if she already had a login for the site.