UI: "The sorting icon is ugly." UX: "Sorting is confusing."
That being said, I agree that most people won't be able to make the distinction. I'd say that we should just add a single boolean flag. I don't want to call it "Design" so as not to confuse people with DDN tickets. "UI/UX"? "DesignHelp"? I'd be happy with any of these. Again, my practical goal is to having something I can use to filter trac, and a visible signal to non-code contributors that we desire their involvement. -I On Wednesday, June 8, 2011 at 8:34 AM, Julien Phalip wrote: > On Jun 8, 12:25 am, Luke Plant <[email protected] (http://cantab.net)> > wrote: > > On 07/06/11 11:32, Idan Gazit wrote: > > > I'd like to propose adding two flags to Trac, "UI" and "UX". > > So would it be better to have just "UI/UX"? > > I totally agree that Trac needs something specific for this, as it's a > shame we have to remove admin-related tickets from the contrib.admin > component. > > I also agree with Luke that having two different fields could be > confusing. UX encompasses UI so both are not completely orthogonal > from each other. How about a single "User experience" flag? Or maybe > something more explicitly targeted to the end goal, like a "Needs > designer's talents" flag? > > Julien > > -- > You received this message because you are subscribed to the Google Groups > "Django developers" group. > To post to this group, send email to [email protected] > (mailto:[email protected]). > To unsubscribe from this group, send email to > [email protected] > (mailto:[email protected]). > For more options, visit this group at > http://groups.google.com/group/django-developers?hl=en. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
