<HTML><BODY style="word-wrap: break-word; -khtml-nbsp-mode: space; -khtml-line-break: after-white-space; ">Hello, I conducted 5 interviews today and began the process of summarizing the findings leading to a Drupal administration survey. My hope is to do 4 more interviews tomorrow and collect interview notes from Dries and Steven Peck. I'll then put out a draft survey for comments and deploy on the home page of Drupal.org ASAP.<DIV><BR class="khtml-block-placeholder"></DIV><DIV>Summary:</DIV><DIV><SPAN class="Apple-style-span" style="text-decoration: underline;">Usage of Drupal</SPAN></DIV><DIV>Daily for 30-60 minutes of website management</DIV><DIV>Daily for several hours in site development and deployment</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV><SPAN class="Apple-style-span" style="text-decoration: underline;">Motivations for using Drupal</SPAN></DIV><DIV>Speed of feature and requirements deployment is critical to choosing Drupal</DIV><DIV>Quality of people, their contributions, helpfulness, and community building domain knowledge is critical to choosing Drupal</DIV><DIV>Drupal website end users benefit from fast feature deployment and Drupal feature innovation</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV><SPAN class="Apple-style-span" style=""><SPAN class="Apple-style-span" style="text-decoration: underline;">Tasks</SPAN>-Drupal software</SPAN></DIV><DIV>Logging to identify the state of the web site as well as events that indicate upcoming website issues are critical.</DIV><DIV>Managing users, content, and spam are top activities for administrators. Better contextual interfaces are need to manage this. e.g. Banning, un-publishing should be beside username or content not in administer >> somewhere</DIV><DIV>Discovery of administration settings is hard. Grouping settings into situational use is important. Situations include: site building, new feature testing and deployment, and ongoing maintenance</DIV><DIV>User interfaces for large scale management of Drupal (blocks, menus, content, categories, users) do not scale adequately. e.g. interface assume individual changes and not bulk changes of hundreds of items.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV><SPAN class="Apple-style-span" style="text-decoration: underline;">Tasks</SPAN>-Drupal processes</DIV><DIV>Testing features and getting feedback from site users is an important activity. e.g. provide testing role with feedback block for that role</DIV><DIV>Process of discovering features, downloading, installing, configuring, testing, filing issues, working with developers, evaluating, and abandoning broken modules is a major cost associated with administering Drupal</DIV><DIV>Integrating features(module X and module Y) produces errors and makes theming hard. Despite difficulties it is a net positive.</DIV><DIV>Upgrading and versioning Drupal and the ability to make informed decisions about this process is currently inadequate.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>Here is table collecting responses from the interviews: <A href="http://drupal.org/node/77193">http://drupal.org/node/77193</A></DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>Interview 1: <A href="http://groups.drupal.org/node/1136">http://groups.drupal.org/node/1136</A></DIV><DIV>Interview 2: <A href="http://groups.drupal.org/node/1135">http://groups.drupal.org/node/1135</A></DIV><DIV>Interview 3: <A href="http://groups.drupal.org/node/1133">http://groups.drupal.org/node/1133</A></DIV><DIV>Interview 4: <A href="http://groups.drupal.org/node/1137">http://groups.drupal.org/node/1137</A></DIV><DIV>Interview 5: <A href="http://groups.drupal.org/node/1134">http://groups.drupal.org/node/1134</A></DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>Cheers,</DIV><DIV>Kieran</DIV><DIV>CivicSpace</DIV></BODY></HTML>