On Feb 12, 2009, at 10:48 AM, Victor Kane wrote:

Remember folks, these are usability experts focusing on people coming to drupal.org.

That means, the main concern in our minds is, given a pressing need, how can I obtain a list of modules that might be just what I'm looking for! Cool!

So if we stop analyzing it from the module author's point of view (another chore to do in creating/updating a project, having to pick out tags) and start analyzing it from the "how can I do what I need to do with contributed modules real quick" point of view, the tags start making sense as a basis for building that kind of functionality.

My concern is simply what Kathleen articulated. That if 90% of modules pick every category, then usability is greatly reduced. It would be *much* more useful if all modules are assumed useful for all sites, except for ones that are specifically limited to a niche category. I'd rather get 5 results for E-learning for modules that only apply to that category rather than 4000 modules, 3995 of which apply to all sites plus 5 for E-learning.

That said, I'm not opposed to just turning it on and seeing how it goes, but I know that all of my modules are applicable to all sites and there aren't many that I use when site building that aren't used everywhere as well.

- Addi



Victor Kane
http://awebfactory.com.ar

On Thu, Feb 12, 2009 at 1:25 PM, Greg Knaddison <Greg@growingventuresolutions.com> wrote:
On Thu, Feb 12, 2009 at 8:11 AM, Gábor Hojtsy <gabor@hojtsy.hu> wrote:
> Note: IMHO we can remove the types of sites vocabulary always, if we
> find it is not working well.

I agree.  Sure, some modules are useful on all sites and will select
that, but some modules really are applicable to only a few kinds of
sites.  The tag issues will cause some additional maintenance problems
but we have tools for dealing with it.  Let's try this out long enough
to see how it works with a faceted search interface.

Greg

--
Greg Knaddison
http://knaddison.com | 303-800-5623 | http://growingventuresolutions.com