Re: new keyword proposal

[Olav Vitters]

Comments from gnome-bugsquad?

On Mon, Aug 17, 2009 at 06:09:23PM -0400, William Jon McCann wrote:

> Hey,
>
> In GNOME Shell development we have plenty of issues that require input
> or decisions from designers (interaction/experience, visual, etc).  It
> would be great to have a way for developers to mark bugs as needing
> this attention and it would be great for designers to have an easy way
> to find out what needs attention.
>
> We already have a number of keywords but none of them really seem to
> fit the bill (or are used for other purposes already):
> http://bugzilla.gnome.org/describekeywords.cgi
>
> Namely:
>   * HIG
>              Bug reporting an area where an application does not
> follow the HIG.
>
>   * ui-review
>              Indicates a bug filed as part of the ui-review. Should be
> used only by the ui-review team.
>
>   * usability
>              This keyword describes a usability/user interface
> change where the correct behavior is not necessarily obvious and input
> from the usability team is desired.
>
> HIG is about compliance with consistency and behavior guidelines.
> ui-review is a process request.  usability is somewhat like a
> combination of the two.  It is not helpful for up-front experience
> design issues.
>
> Would adding a new "design" keyword be reasonable?  This would allow
> the design team for any specific module to look at the bugs for that
> module.  It wouldn't be for any kind of "design team" request.
>
> Thanks,
> Jon
> _______________________________________________
> bugzilla-maintainers mailing list
> bugzilla-maintainers@...
> http://mail.gnome.org/mailman/listinfo/bugzilla-maintainers

--
Regards,
Olav
_______________________________________________
Gnome-bugsquad mailing list
Gnome-bugsquad@...
http://mail.gnome.org/mailman/listinfo/gnome-bugsquad

[Andre Klapper]

Hi,

Am Dienstag, den 18.08.2009, 13:24 +0200 schrieb Olav Vitters:

> Comments from gnome-bugsquad?
>
> On Mon, Aug 17, 2009 at 06:09:23PM -0400, William Jon McCann wrote:
> > In GNOME Shell development we have plenty of issues that require input
> > or decisions from designers (interaction/experience, visual, etc).  It
> > would be great to have a way for developers to mark bugs as needing
> > this attention and it would be great for designers to have an easy way
> > to find out what needs attention.
> >
> > We already have a number of keywords but none of them really seem to
> > fit the bill (or are used for other purposes already):
> > http://bugzilla.gnome.org/describekeywords.cgi
> >
> > Namely:
> >   * HIG
> >              Bug reporting an area where an application does not
> > follow the HIG.
> >
> >   * ui-review
> >              Indicates a bug filed as part of the ui-review. Should be
> > used only by the ui-review team.
> >
> >   * usability
> >              This keyword describes a usability/user interface
> > change where the correct behavior is not necessarily obvious and input
> > from the usability team is desired.
> >
> > HIG is about compliance with consistency and behavior guidelines.
> > ui-review is a process request.  usability is somewhat like a
> > combination of the two.  It is not helpful for up-front experience
> > design issues.
> >
> > Would adding a new "design" keyword be reasonable?  This would allow
> > the design team for any specific module to look at the bugs for that
> > module.  It wouldn't be for any kind of "design team" request.

Problem with "usability" keyword is that way too many reporters set it
without any reason.

I'd go with "ui-review" here and change the description slightly (like
"not meant to be set by reporter unless s/he knows what s/he does").
It has ten open tickets currently, and I don't think that we have an
ui-review team in place at all.

Same potential problems of course.

andre
--
 mailto:ak-47@... | failed
 http://www.iomc.de/  | http://blogs.gnome.org/aklapper

_______________________________________________
Gnome-bugsquad mailing list
Gnome-bugsquad@...
http://mail.gnome.org/mailman/listinfo/gnome-bugsquad

[Max Kanat-Alexander]

Andre Klapper wrote:
> I'd go with "ui-review" here and change the description slightly (like
> "not meant to be set by reporter unless s/he knows what s/he does").
> It has ten open tickets currently, and I don't think that we have an
> ui-review team in place at all.

        You know, you could use flags for this too. You could set "ui-review?"
and then somebody could come along and grant "ui-review+" and then you'd
know who did the ui-review, right there in the flags UI. You could also
control who can request and set it, if you'd like.

        -Max
--
http://www.everythingsolved.com/
Competent, Friendly Bugzilla and Perl Services. Everything Else, too.
_______________________________________________
Gnome-bugsquad mailing list
Gnome-bugsquad@...
http://mail.gnome.org/mailman/listinfo/gnome-bugsquad