(→Meeting Topics) |
|||
| Line 31: | Line 31: | ||
# Konqueror's save password dialog is unintuitive ([https://bugs.kde.org/show_bug.cgi?id=168060 Bug 168060]) | # Konqueror's save password dialog is unintuitive ([https://bugs.kde.org/show_bug.cgi?id=168060 Bug 168060]) | ||
# Quit should exit totally the application? ([https://bugs.kde.org/show_bug.cgi?id=180466 Bug 180466]) Can this bug be closed? | # Quit should exit totally the application? ([https://bugs.kde.org/show_bug.cgi?id=180466 Bug 180466]) Can this bug be closed? | ||
| + | # problems with small screens (netbooks): mainly kde-pim is not prepared for small screens like the eeepc one (some places with no scrollbar for example). | ||
==Previous Meetings== | ==Previous Meetings== | ||
This is the planning page for KDE Usability Project meetings on #kde-usability on irc.freenode.org. The purpose of the meetings is to Get Usability Stuff Done. These meetings are free for anyone to listen in on; however, they are mostly for designers and developers. For more information scroll and read About the Usability Meetings.
Contents |
The next meeting will be March 18 at 20UTC (21CET/15EST).
The theme for this meeting is Usability Bugs. Please add bugs (with link to bug) to the meeting agenda if you would like to discuss them.
Add meeting topics you would like to discuss. Not all of the topics will be able to be covered in a single meeting and so might be deferred until later. Please include your name/irc nick and a link to a project page or bug.
We will discuss practical usability-related issues and attempt to reach reach a resolution. Usability topics which are too large or too broad may be too much to discuss in a single meeting and should be broken up into smaller issues or schedule a dedicated meeting.
Meetings are structured and attempt to follow a preset agenda. There is a meeting leader/moderator (probably seele) who will control the flow of discussion to help keep the meeting on track.
Meeting format is as follows: An agenda item will be presented, describing the problem and a proposed solution. If the item was suggested by someone in particular, they will be asked to provide additional information about the problem. Those in attendance will then be able to discuss the issues in the problem. The meeting moderator will attempt to keep the meeting on track of the topic.
Meetings are normally at 20UTC, alternating weekday and weekend days. Meetings will last no longer than 2 hours. If we do not get through the list in 2 hours, the topics will be covered in the next meeting. If we get through the list in < 2 hours and people are still responsive, we will possibly add an additional topic from the main meeting topics list if the people necessary for discussion are in attendance.