From Fedora Project Wiki
No edit summary
No edit summary
Line 20: Line 20:
=== Initial User walk through ===
=== Initial User walk through ===


The idea is to understand what problems the user is facing when they use the web application interface. For this purpose, we aim to have two initial user walk through based on the users we had identified.  
The idea is to understand what problems the user is facing when they use the web application interface. For this purpose, we did two initial user walk through based on the users we had identified.  


07/12/2016 : User Walk through - 1  
07/12/2016 : User Walk through - 1  
Line 48: Line 48:
Some of the use cases that we identified included the following:  
Some of the use cases that we identified included the following:  


#Some wasted space can be improved as shown in the link (check the arrows):[https://server.famillecollet.com/owncloud/index.php/s/jhq7FymOQiEJzrz#//margins.png]
#Some wasted space can be improved as shown in the link (check the arrows in the margin.png file):[https://server.famillecollet.com/owncloud/index.php/s/jhq7FymOQiEJzrz#//margins.png]
#Some ideas about the "New override" It will be interesting to be able to submit more than 1 package at a time as we can for "new update".
#Some ideas about the "New override" It will be interesting to be able to submit more than 1 package at a time as we can for "new update".
#There is a need to have a checkbox for being able to "push to stable" various package in a single action  
#There is a need to have a checkbox for being able to "push to stable" various package in a single action  
#It could also be nice to be able to change the content like "number of lines" in list or the "time in testing"  
#It could also be nice to be able to change the content like "number of lines" in list or the "time in testing"  
#The content under these tabs can be changed as follows :
#The content under these tabs can be changed as follows :
#"Status" can have some more refined content which can be filtered according to "status since"  
  1."Status" can have some more refined content which can be filtered according to "status since"  
#Similarly "testing" can be filtered according to "testing for 7 days" or "Stable for 2 months"
  2.Similarly "testing" can be filtered according to "testing for 7 days" or "Stable for 2 months"
This would allow the user to have more accurate information about the current state of the process   
This would allow the user to have more accurate information about the current state of the process   


Line 67: Line 67:


*We are going to do a Pre-Interview User Survey to understand in depth our user needs and evaluate those further in the upcoming flock  
*We are going to do a Pre-Interview User Survey to understand in depth our user needs and evaluate those further in the upcoming flock  


=== User Interviews ===
=== User Interviews ===




== Development / Testing ==
== Development / Testing ==




== Design Document ==
== Design Document ==




Line 87: Line 80:




== Fedora 24 Install Process ==


== Fedora 24 Install Process ==


= Other Resources =
= Other Resources =

Revision as of 18:43, 29 July 2016

Bodhi UX review

Bodhi Redesign

Methodology

Goal

  1. To improve the web interface and make it more intuitive for the users

User Identification

Currently we have identified some users for the our Bodhi Redesign project. We have divided them into the following categories:

  1. Testers and release engineers who frequently use the web application
  2. Packagers/ Developers who sometimes use the web UI as well as the command line interface
  3. Any user from the open source community

Initial User walk through

The idea is to understand what problems the user is facing when they use the web application interface. For this purpose, we did two initial user walk through based on the users we had identified.

07/12/2016 : User Walk through - 1

Role : Tester

Use cases that need improvement:


  1. No download link for the koji (he was describing a drop down menu in case of multiple downloads) and command line download link as well
  2. Karma cycle is very confusing as he could not figure out the functionality of the untested button.
  3. No direct contact link to the submitter.
  4. Updates to the bugzilla.

Edge-cases:

  1. Previous searches
  2. Edit the replies to the thread.


29/12/2016 : User Walk through - 2


Role : Packager/Developer

Some of the use cases that we identified included the following:

  1. Some wasted space can be improved as shown in the link (check the arrows in the margin.png file):[1]
  2. Some ideas about the "New override" It will be interesting to be able to submit more than 1 package at a time as we can for "new update".
  3. There is a need to have a checkbox for being able to "push to stable" various package in a single action
  4. It could also be nice to be able to change the content like "number of lines" in list or the "time in testing"
  5. The content under these tabs can be changed as follows :
  1."Status" can have some more refined content which can be filtered according to "status since" 
  2.Similarly "testing" can be filtered according to "testing for 7 days" or "Stable for 2 months"

This would allow the user to have more accurate information about the current state of the process

Edgecases

As developer,these listed functions were not useful:

  1. Previous searches (previously viewed packages)


Pre-Interview User Survey

  • We are going to do a Pre-Interview User Survey to understand in depth our user needs and evaluate those further in the upcoming flock

User Interviews

Development / Testing

Design Document

Ideas / Brainstorms / Mockups

Fedora 24 Install Process

Other Resources