ayatana-ux team mailing list archive

["Murat Gunes" <mgunes@xxxxxxxxxx>]

Hi everyone,

Below is a tentative list of topics for tomorrow's Ayatana UX team
meeting (August 12th, 12:00pm UTC, #ubuntu-meeting). Please post your
additions, if any.

== Firefox 4 theme / Firefox button UX ==
 
In his recent update [1] on the goals of the Firefox UX Team for the
next Firefox 4 beta, Alexander Limi mentioned once again that they need
help with the Linux side of things. As was previously discussed on the
relevant Firefox bug [2] (particularly well summed up by Michael Monreal
in comment #14), they initially wanted to implement drawing in the
window title bar for the new Firefox button "the proper way" through
CSD, but since GTK+ 3.0 was delayed, and the situation regarding the CSD
API making it in was unclear, they're now considering the GNOME Shell
app button control. There seems to have been some discussion at GUADEC,
but details are sparse.

If any GUADEC attendees among us have further details, it would be
useful to share them, and for us to investigate whether we can help with
this in any way as soon as possible, since FF4 is progressing rather
fast, there's an apparent shortage of good communication among the
stakeholders, and time is running out.

== Heuristic bug tagging progress ==

Where do we stand regarding the implementation of heuristic evaluation
and bug tagging [3]? Is the list of heuristics listed in the blueprint
considered final, or should we discuss adding more? Can the team assist
with the first work item (Create examples for each of the tags with
reference to Gnome HIG)?

== Update Manager redesign ==

I recall that mpt was considering a redesign of Update Manager during
the Karmic cycle, a blueprint was drafted regarding requirements for the
update / upgrae experiences for the Lucid cycle, whose outcome is not
very clear [4], and we have a blueprint [5] targeting specific
improvements to u-m for Maverick now, some of which involve partial
redesign. Can we get involved either with the work items for Maverick,
or the complete redesign, if it's still planned, perhaps for Maverick+1?

== Team resources ==

My impression is that while everyone is generally busy with UX / design
work, much of the activity so far that's specific to the team is
centered around the meetings, and better continuity and some more "team
spirit" can be gained by utilizing different resources. Should we push
towards making more active use of the mailing list, or other resources
such as the wiki or an IRC channel? Any other ideas (that don't involve
non-trivial infrastructure work)? A good starting point might be
creating a wiki home page.

m.

---

[1] http://limi.net/articles/firefox-ux-team-update-19/
[2] https://bugzilla.mozilla.org/show_bug.cgi?id=513159
[3]
https://blueprints.launchpad.net/ubuntu/+spec/design-m-heuristics-and-bugs
[4]
https://blueprints.launchpad.net/ubuntu/+spec/desktop-lucid-update-upgrade-requirements
[5]
https://blueprints.launchpad.net/ubuntu/+spec/foundations-m-update-manager-improvements