[Libreoffice] Reviewing EasyHacks (was: Re: [Libreoffice-ux-advise] Fwd: [PATCH] Bug 39167)

[Bjoern Michaelsen]

Hi Christoph, Hi all,

On Sat, 06 Aug 2011 00:02:36 +0200
Christoph Noack <christoph at dogmatux.com>
wrote:

> My question is who should review the Easy Hacks before publishing -
> when looking from the Design Team perspective, it would be good to at
> least add a UX (User Experience) statement whether the Easy Hack is
> helpful or not ("not" may also mean that a different solution would
> be even more helpful by resolving some more issues). Personally,
> whenever I got aware of such Easy Hacks (more by accident than by
> using a systematical approach), I've added such statements.

IMHO, both Devs and UXer should have a look at the changes to
the EasyHacks now and then. A query like this:

https://bugs.freedesktop.org/buglist.cgi?status_whiteboard_type=allwordssubstr&chfieldto=Now&query_format=advanced&chfieldfrom=-1w&status_whiteboard=EasyHack&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED

for example shows all EasyHacks changed since last week. This is not
much different from watching the wiki page history.

> However, the question was if additional (whiteboard) tags like
> "UxSimplyGo" or "UxGetAdvice" might help. These tags could be added in
> QA bug hunting sessions, or by a regular review of such tasks by the
> Design Team. In the meantime, I also got sometimes added to be the "ux
> contact" for other issues ...

I am not so much a friend of "UxSimplyGo"/"UxGetAdvice" tags.
"UxSimplyGo" is a tautology: If it is an EasyHack the taker should
simply be able to go for it. For the same reason "UxGetAdvice" would be
a oxymoron on an EasyHack -- if the implementer needs to consult back
with UX first, it is by definition not something to get him started
right away coding. If indeed UX finds an EasyHack that it thinks needs
a lot more funetuning, it should simply be demoted from "EasyHack" to
"ProposedEasyHack" before somebody is working on it. As long we have
more than 100 other EasyHacks, were a newcomer might dig right in, we
do not need him to get struck in lengthly discussions before he even
gets started. If the latter would be the case, it might still be a
valid issue, and it might be well worth the effort, but IMHO it is not
qualifying as an EasyHack.
Just to make myself clear: I am not objecting using a "UxGetAdvice"-tag
-- actually I think it should be used: metadata is a Good Thing(tm).
But I think it immediately kills EasyHack status(*).

Best,

Bjoern (from vacation)

(*) Of course, all such changes should be documented and discussed by
comments in the issue.

-- 
https://launchpad.net/~bjoern-michaelsen