<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Feb 12, 2009, at 10:48 AM, Victor Kane wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">Remember folks, these are usability experts focusing on people coming to <a href="http://drupal.org">drupal.org</a>.<br><br>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!<br> <br>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.</blockquote><div><br></div><div>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.</div><div><br></div><div>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.</div><div><br></div><div>- Addi</div><br><blockquote type="cite"><br> <br>Victor Kane<br><a href="http://awebfactory.com.ar">http://awebfactory.com.ar</a><br><br><div class="gmail_quote">On Thu, Feb 12, 2009 at 1:25 PM, Greg Knaddison <span dir="ltr"><<a href="mailto:Greg@growingventuresolutions.com">Greg@growingventuresolutions.com</a>></span> wrote:<br> <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="Ih2E3d">On Thu, Feb 12, 2009 at 8:11 AM, Gábor Hojtsy <<a href="mailto:gabor@hojtsy.hu">gabor@hojtsy.hu</a>> wrote:<br> > Note: IMHO we can remove the types of sites vocabulary always, if we<br> > find it is not working well.<br> <br> </div>I agree. Sure, some modules are useful on all sites and will select<br> that, but some modules really are applicable to only a few kinds of<br> sites. The tag issues will cause some additional maintenance problems<br> but we have tools for dealing with it. Let's try this out long enough<br> to see how it works with a faceted search interface.<br> <br> Greg<br> <font color="#888888"><br> --<br> Greg Knaddison<br> <a href="http://knaddison.com" target="_blank">http://knaddison.com</a> | 303-800-5623 | <a href="http://growingventuresolutions.com" target="_blank">http://growingventuresolutions.com</a><br> </font></blockquote></div><br></blockquote></div><br></body></html>