Posted by carlitus on September 8, 2008 at 5:11pm
edit: Carlitus, sorry to hijack your post, but this is an important discussion we'd like to get sorted quickly. Let's try and do this here. - yoroy
The behaviour of the autocomplete when only one term (with one or more words) is needed its very odd: you need to hit the enter two times
Example: the drupal API search
I've found a very similar issue in 2007 http://drupal.org/node/171918
Comments
OT
We need some rules when to have discussions over UI issues here and when in the issue queue. This particular case seems to be a perfect candidate as an issue -- bumped up and tagged as 'usability' of course.
What needs to be different in Carlitus post in order to run the discussion here first?
I agree
What about a new link in the Quick links panel, labeled "Want to contribute? Read this first.", that links to a page making it clear when (and how) people should create an issue in the queue, and when to create a discussion in our humble group.
It's great that people want to help out with usability, but things that belong in the issue queue shouldn't be posted here just to get attention. The group frontpage shouldn't bee noisy. Any suggestions for good wording on such a readme page?
Re: Issue Queue items
How about a Create Issue menu item? That should be clear enough. Anything else would just get repeated anyway.
Captcha tries: 6 times. I about gave up.
Is it possible?
Can we add external links up there in the Usability block?
Still, we'd want to make it clear when one should create an issue in the queue and when to start a discussion here. Or we'll just keep seeing discussions that should've been issues.
Let's sort this out indeed.
Again, carlitus sorry for hijacking your post, but we should get this sorted quickly:
What goes where? When is something an issue, when do we want to work on things here?
Discuss larger topics here? Say, a wiki page per topic, everybody who wants to connect their specific issue or wants to help, or point out related issues etc: comment on the wikipage?
Basically, do we want to go easy on the number of nodes created here and get more comments on fewer nodes?
What are the basic things we can do to get a bit more structure?
Re: sort this out
A clear description of what should be an issue, group post or possibly both needs to be made before this can be answered. Features certainly need to be discussed here but once ironed out should be turned into an issue. Broken things need to be an issue. Things not broken but could be improved is a feature so should be discussed here. An aggregated feed of the Usability issues should also be available for easy tracking.
If this happens a glossary of the topics needs to be made.
Fewer nodes are easier to control but each topic deserves its own node. What makes a topic for this group is the question to answer.
What are other groups doing? Is there a forum to get ideas for this from?
UX-process: What goes where?
I would argue that having more comments on fewer nodes makes it harder for someone new to jump in and figure out what's going on. There's a natural tendency for the comments to drift in different directions as the thread gets longer. And at some point, often about two screens down, you just stop reading because there's no return on the time investment.
So I agree with earnie@drupal.org that each topic needs to be a node. Otherwise, it's going to be hard to persuade people to take a look at a usability issue that was discussed in a comment thread four screens down on an node whose title doesn't reflect that the comments talk about that issue.
A couple of articles on data collection:
A couple of sites that might be useful:
Uppps
Sorry for posting this here. ¿The right place is in the issue queue of Drupal Core?
Neurotic web design
no worries
It's good that you want to point out things like this. We're just wondering how to best collect this kind of input. A post here for each 'thing' is just not ideal.
For example: could you make a list of 5 related, existing and relatively small usability issues for Drupal core? What other little annoying things are going on in our forms? That would make for an interesting call for a usabilty review.
You can even post it here! :-)
Ok
I've put it in Those little annoying UI things
Neurotic web design
What is the status/decision
What is the status/decision of this topic? I don't see a clear answer on the "usability group" conversation either
I have usability issues/screenshots I have gathered- but I am stalled as to where to put it... Do I make an issue and then link within the wiki pages? Which wiki page? And when is it appropriate to start a new discussion, or when to add to an on-going discussion.
If you imagine coming to this group for the first time... what does someone expect to see? what do they need to be told? where should we direct them?
Well.. it would be nice to be able to make a little survey- or make the submission form a kind of path?
Someone wants to contribute to usability:
- They have a specific issue with core or a contributed module --> make an issue in the queue
- They have general issues which affect multiple modules and/or core --> search for existing discussion or issue queue --> add a new discussion
Still not entirely sure how the wikis fit into the flow? Are we to find existing issues and post them on the wiki?
I'm sorry if I missed this all somewhere in the forum, where it was explained clearly!.. if someone has a link that would be good too.
"New Here?" Wiki page
(This is strange, I had some text ready to post but it disappeared.)
How about a quick link titled "New Here?" and that link leads to a wiki page with details on which issues should appear here and which should be filed in the issue queue.
On the "New Here?" page, the following information can also appear:
-How to contribute instructions
-Instructions on how to make a post in the group (The og block could be improved by having 'Create Discussion' appear above 'Create Poll')
-Previous achievements of the group
-Issues that are previously discussed but are likely to be of interest to newer group members.
As for images, how about a horizontal latest images block that appears above or below the tracker?
Thank you for asking the
Thank you for asking the right questions here!
Let's work this out, I planned an IRC chat for tomorrow:
http://groups.drupal.org/node/14885