Note: You are currently viewing documentation for Moodle 2.0. Up-to-date documentation for the latest stable version is available here: Student projects/Usability issues.

Student projects/Usability issues

From MoodleDocs

Note: This page outlines ideas for the Usability issues project. It's a specification under construction! If you have any comments or suggestions, please add them to the page comments.


The main objective of this project is to detect and solve specific usability issues.

Index

Main tasks

  • Research in the tracker, forums, etc. to create a hitlist of the top 10 (or 20) specific usability issues.
  • For each issue, identify the problem clearly (screenshots) and clearly describe one or more solutions (incl mock screenshots) for the community to evaluate.
  • Create code to solve the problem with the best decided solution (optional, depending on Moodle community thoughts).
  • Take a look at Fluid Project (who we are involved with already) to

see where some of their components can be used in Moodle (optional).

To do

  • Classify specific usability issues
  • Identify the solutions
  • Create code to solve the problem
  • Take a look at Fluid Project

Done

  • AI test
  • Usability test
  • Research in the tracker, forums, and hitlist
  • Research the bibliography

This is the timeline I envision:

T1: Research tracker, research forums, wikis, mailing lists(2 weeks)

T2: Try to find out other possible usability issues to address(1 weeks)

T3: See how Moodle's usability can benefit from the Fluid project (2 weeks)

T4: Classify and propose different solutions for the found usability problems (3 weeks)

T5: Solve the problem (3 weeks)

T6, (T7): Writing the documentation of the project (the guideline is optional) (2 weeks)

The timeline considering that in May/June I will be working half time in GSoC:

  • T1: Deadline 1st May
  • T2: Deadline 15th June
  • T3: Deadline 4th July
    • Google: July 7: Mentors and students can begin submitting mid - term evaluations
    • Google: July 14th: Mid - term evaluations deadline
  • T4: Deadline 20th July
    • Google: August 11: Suggested 'pencils down'. Take a week to scrub code, write tests, improve documentation
  • T5: Deadline 16th August
    • Google: August 18: Firm 'pencils down' date. Mentors, students and organization administrators can begin submitting final evaluations to Google.
  • T6/T7: Deadline 29th August
    • Google: September 1: Final evaluation deadline.
    • Google: September 3: Students can begin submitting required code samples to Google.

See also