[17:00] agentrickard: Question 1: How would you describe yourself as a Drupal.org user?
[17:00] developer, contributor
[17:01] occassional helper (support and docs)
[17:01] Ok, great.
[17:01] Question 2: How often do you visit Drupal.org?
[17:01] every work day, probably three times
[17:01] more if i have an issue
[17:01] Question 3: When you visit Drupal.org, how long do you spend on the site?
[17:01] but i don't do Drupal work full-time
[17:01] agentrickard: ok, got it.
[17:02] that depends, it can be 2 minutes or less (checking issue queue and my Track list). Sometimes, when I'm in helper mode, up to an hour
[17:02] Question 4: What would you describe as your goals for visiting Drupal.org?
[17:02] if contributing, about 10-15 min
[17:02] I am too quick
[17:03] :-)
[17:03] to solve problems (for me and others)
[17:03] no
[17:03] so since I have problems to solve, I try to lend a hand to those who are repeating my mistakes
[17:03] :-)
[17:04] (for IRC, you should tell people to send a symbol when they are done answering)
[17:04] like @
[17:04] @
[17:04] Ok, we can use that
[17:05] Ready for question 5?
[17:05] @
[17:05] yup
[17:05] Question 5. What is easy to do on Drupal.org?
[17:05] Wait
[17:05] I don't think I got an answer to question 4
[17:05] Question 4: What would you describe as your goals for visiting Drupal.org?
[17:05] to solve problems (for me and others)
[17:05] ok, got it.
[17:05] @
[17:06] Question 5. What is easy to do on Drupal.org? @
[17:06] check issues queues (if they aren't too big)
[17:06] track issues in my tracker list
[17:06] spend lots of time answering newbie questions
[17:06] use the API ++easy
[17:07] find core download
[17:07] find modules you know the names of
[17:07] contact a user
[17:07] @
[17:07] Question 6. What is hard to do on Drupal.org?@
[17:07] find handbook pages
[17:07] that answer specific questions
[17:08] find forum threads (I always just use the block nav)
[17:08] find new modules
[17:08] find modules that match a known feature set (but you don't know anything about the modules)
[17:08] @
[17:09] Last question: Is there anything else important about Drupal.org that we haven't discussed?
[17:09] I think that it's text heavy (especially on public front pages) and that can be off-putting to new users
[17:09] server problems are obvious and common
[17:10] groups isn't integrated that well
[17:10] Go ahead and give details for the record
[17:10] ?
[17:10] server problems etc.
[17:11] there are frequent lags in server response, where you can tell that you're waiting in the apache queue for an open process
[17:11] so it can take 30 sec to load my issues sometimes
[17:11] that's what I mean by obvious
[17:11] ok,
[17:11] How would you like to see groups integrated?
[17:11] that's typically during high traffic times
[17:12] i haven't thought about it too much, but how about by linking taxomies to groups?
[17:12] maybe a block that is sensitive to what the page is about and suggestts groups that a re related
[17:12] a re = are
[17:12] anything else import about Drupal.org to discuss?
[17:13] taxomies = taxonomies
[17:13] it does, in fact, rock
[17:13] oh, and Google search is usually better than d.o. search
[17:13] @
[17:13] can you give an example of how Google search is usually better than d.o. search?
[17:14] let me try one right now
[17:15] the results are typically comparable. but Google is faster
[17:15] Google is also better at string searches
[17:16] I sent a note to the deve list this morning referencing a search for "patch unexpectedly ends in middle of line"
[17:16] you can't really search that on d.o