Drupal.org D7 Upgrade: Ready for Community QA!

It’s time! After almost a year and a half of work we are at the finish line. D7 Drupal.org is open for community QA. We invite you all to login to the site, look around, do some of the things you usually do on Drupal.org and report any bugs or problems you encounter. Community QA will last for at least 3 weeks. The launch date will be sometime after DrupalCon Prague and will depend on how many bugs you find. :)

Before You Start

For this upgrade project our goal was a straight port to Drupal 7. No major regressions, no major new features. And indeed nearly all sections and pages on D7 Drupal.org will look the same as they do now on Drupal 6. There is only one page which will change significantly – the issue page. Awhile ago we wrote a detailed explanation of the changes and why they had to happen. Please be sure to review the post before going to the QA site.

Note that patch testing on the QA site may be somewhat delayed relative to production, but with patience, should be fully functional.

Ready to Do Some QA?

Great! We’ve set up a dedicated issue queue for the process. You’ll find instructions on the project page: https://drupal.org/project/d7qa.

We’ve also set up an #drupal-d7qa IRC channel on Freenode, a place for QA participants to talk to each other and the development team.

Any Video Tutorial Available?

Good question. In preparation for the community QA Melissa Anderson and Neil Drumm held a QA orientation session, where they talked about our QA server, and where and how to report issues. They also briefly showed the new Drupal.org issue pages. The recording is available below:

Now go and check out D7 Drupal.org! We do hope you’ll like it.

VOTING is Open! Community elections for the board of the Drupal Association.

UPDATE: Voting is Now Open!

https://association.drupal.org/vote2014

Meet the Candidates!

Voting closes on Thursday 19 Sep 2013

Now is the time! As we announced on August 16, we are looking to fill the two At-Large Director positions that are opening. The At-large Director position is specifically designed to ensure community representation on the Drupal Association board and we strongly encourage anyone with an interest to take part in the process.

The Board of Directors of the Drupal Association are responsible for financial oversight and setting the strategic direction of the Drupal Association. New board members will contribute to the strategic direction of the Drupal Association. Board members are advised of, but not responsible for matters related to the day to day operations of the Drupal Association, including program execution, staffing, etc.

Directors are expected to contribute around five hours per month and attend three in-person meetings per year (financial assistance is available if required). You can learn more about what’s expected of board members by reviewing the board member agreement.

The self-nomination form that will allow you to throw your hat in the ring is open for just a few more days:

Nominate Yourself for the Drupal Association Board

To nominate yourself, you should be prepared to answer a few questions:

  • About Me: Tell us about yourself! Your background, how you got into Drupal, etc.
  • Motivation: Why are you applying for a board position? What initiatives do you hope to help drive, or what perspectives are you going to try and represent?
  • Experience: What Drupal community contributions have you taken part in (code, camps, etc.)? Do you have experience in financial oversight, developing business strategies, or organization governance?
  • Availability: I am able to travel to three in-person board meetings per year (either self-funded, or with financial sponsorship)
  • IRC Handle
  • Twitter Handle

We will also need to know that you are available for the next step in the process, meet the candidate sessions. We are hosting 2 sessions: 

Session One

  • Wednesday, Sept. 11th 2013 at 00:00 UTC
  • 5 PM PST Tuesday Sept. 10th in the US and Canada
  • 8 PM EST Tuesday Sept. 10th in the US and Canada
  • 9 PM Tuesday Sept. 10th in Sao Paulo Brasil
  • 1 AM Wednesday, Sept. 11th in London
  • 8 AM Wednesday, Sept. 11th in Beijing
  • 10 am Wednesday, Sept. 11th in Sydney Australia

Session Two

  • Thursday, September 12 2013 at 16:00 UTC
  • 9 AM PST Thursday, September 12 in the US and Canada
  • 12 noon EST Thursday, September 12 in the US and Canada
  • 1 PM Thursday, September 12 in Sao Paulo Brasil
  • 5 PM Thursday, September 12 in London
  • 00:00 Friday, September 13 in Beijing
  • 2 AM Friday, September 13 in Sydney Australia

The nomination form will be open September 1, 2013 through September 6, 2013 at midnight UTC. For a thorough review of the process, please see our announcement blog post.

If you have any questions, please contact Holly Ross, Drupal Association Executive Director, or Donna Benjamin, Drupal Association Board Member.

Update: Git service interruption on drupal.org

Update: Pushes to contributed modules and sandboxes are once again possible, thanks to the work of Sam Boyer and Damien Tournoud. Go forth and contribute!
We are experiencing technical problems with repositories hosted on the Drupal.org git server.
The…

ember 7.x-2.x-dev

Last packaged version: 7.x-2.0-alpha1+23-devLast updated: October 5, 2013 – 01:03View usage statistics for this release

Download

Size

Seeking community input on short-term Drupal.org roadmap

Cross-post from https://association.drupal.org/node/18358

Greetings from the Drupal.org Software Working Group! We are a governance group that has been chartered in order to define the overall strategy and roadmap for *.Drupal.org’s features and functionality.

The Drupal Association Board is having their quarterly retreat at DrupalCon Prague in just a few short weeks, at which point they’ll be reviewing draft 2014 budget for the year, which will include an amount set aside for Drupal.org improvements. We want to ensure that the community has input on what this budget is spent on, but unfortunately the previous data we have on what the community wants is almost two years old. And, because of the tight timeline, we need to do this quickly.

Therefore, the Drupal.org Software Working Group is seeking input from the community to help us determine two to three significant improvements for Drupal.org to be started on by Drupal Association staff at the beginning of 2014 (yes, Drupal.org D7 upgrade will be finished this year!). If you’d like to provide your input on the Drupal.org roadmap for the first part of 2014, please visit the 2014 Drupal.org feature brainstorming group. You can review and “vote up” other peoples’ proposals, or propose your own ideas. We’ll be leaving the call for ideas open until 00:00 GMT on September 2, 2013.

We will then look at the results gathered, consider our constraints (budget, development, other necessary maintenance work, volunteer momentum) and make the best possible choice we can for the next projects. At this time, we are likely to avoid any projects that would block the forward movement of others. That doesn’t mean you shouldn’t include them. Please do. Just know that we have some work to do before the next epic undertaking. Also note that these votes will almost certainly not correspond directly to the initial priorities that we publish. There will be very practical reasons why some of the top-ranked ideas won’t be a part of this batch. We will explain the reasoning behind our choices, but we probably won’t be able to explain the reasoning for every choice we do NOT make.

We acknowledge this interim process to be severely sub-optimal. The timeline is too short, the tools are awkward, we won’t get enough feedback from a broad enough representation of the community, and we acknowledge that different stakeholders will have equally important, competing, or even conflicting priorities. One of our highest priorities as a Working Group is to develop efficient and inclusive process for collecting, prioritizing, and implementing Drupal.org improvements, a process which will allow us to get the widest community feedback possible and make informed decisions. That takes time, however, and we cannot afford to put improvements on hold until it’s worked out.

We will be re-engaging the community in 2014 with more robust process to gather more ideas about how Drupal.org can better serve its varied audiences. We’d love to have you think hard about small-scope ideas with wide-ranging impact in this go-round, but we also want to know the truth about where it hurts.

Express the needs, risks, and benefits of your ideas as clearly as you can, we’ll look at the entire picture to figure the best way we can move forward, and we’ll share the results with you in a few weeks.

Thank you for your participation in making Drupal.org awesome!

Drupal.org Software Working Group

Drupal version: 

Drupal 7.23 released

Update: Drupal 7.24 is now available.
Drupal 7.23, a maintenance release with numerous bug fixes (no security fixes) is now available for download. See the Drupal 7.23 release notes for a full listing.

Download Drupal 7.23
Upgrading your existing Drup…

Important Security Update: Reset Your Drupal.org Password

The Drupal.org Security Team and Infrastructure Team has discovered unauthorized access to account information on Drupal.org and groups.drupal.org.
This access was accomplished via third-party software installed on the Drupal.org server infrastructure…

Drupal.org Downtime: May 9th 5PM PDT (0:00 UTC)

Drupal.org and its sub-sites (api.drupal.org, groups.drupal.org, etc) will be going down for 30 minutes Thursday, May 9, 17:00 PDT (May 10, 0:00 UTC). This maintenance window will be used to remove a core hack. Please follow the @drupal_infra twitter a…

Community Spotlight: Scott Reynen

Scott Reynen has done some fun things in the Drupal community. Some notable examples:

  • Coordinated many meetups in Denver ensuring they happen, with interesting topics, and tasty pizza options
  • Helped to organize several Drupalcamps in Colorado (which will be June 29th/30 in 2013)
  • Presents on various topics at Drupalcamps
  • Helps as one of the 3 site maintainers for groups.drupal.org
  • Is an active Project Application queue reviewer heavily interested in new-contributor-onboarding and project quality
  • Takes care of abandoned projects and ownership requests in the Webmasters queue
  • And does a pretty darn good job as the maintainer for modules like @font-your-face.

How did you get involved with Drupal?

About 4 years ago, I took a job as a developer with Aten Design Group, where we do mostly Drupal projects. At the time, I was pretty skeptical of content management systems, after frustrating experiences with both WordPress and Joomla. But I quickly grew to appreciate Drupal’s modular architecture.

What do you do with Drupal these days?

Most of my Drupal time is spent building websites for clients. I’m fortunate to be able to work on projects I really care about, like the International Center for Transitional Justice, the National Center for Women & Information Technology, and the United Nations Development Programme. Apart from client work, I use Drupal as a platform to explore new ideas. With a wide variety of code and a huge active community, Drupal serves as a great incubator.

You’re involved with the Drupal community locally and internationally – can you describe some of the things you do and why you like them?

I co-maintain Drupal Groups (groups.drupal.org), deal with abandoned projects on Drupal.org, do some work on project review applications, help organize the local Denver Drupal meetup, actively mentor a few people, and contribute some modules. I think I like all of this because I feel like I’m actively building the future, either through directly improving the web, or by enabling other people to improve the web.

What got you started in the project application review process?

I didn’t go through the application review process to get my own Git (previously CVS) access, and didn’t realize the process existed for a long time. So I think some feeling of debt played a part in my getting involved. But I also believe the future of Drupal depends on people who aren’t yet involved, and the application process, if not handled well, can very easily be a point where we turn away this next generation of contributors.

What are some of your favorite moments from that process?

It’s always nice to get thanks from new contributors for my feedback, or to discover a cool new module before it even has a release. But I think my favorite moment was when klausi arrived. Before that, I felt like I had to stay actively involved or the whole process might fall apart. When klausi started doing a superhuman number of reviews, I could comfortably step away from the queue for a short (or even long) period of time and avoid both catastrophe and burnout.

Read a previous Community Spotlight about Klaus Purer (klausi).

Are there any cool projects you’ve learned about through that process?

Commerce Registration is, I think, a great example of why the review process is important to the wider community. After some quick minor bug fixes in the review process, that project was approved and is now part of the Conference Organizing Distribution, used in every DrupalCon site. And the maintainer has gone on to contribute several other modules, a few to Drupal Commons that will be part of the next version of the Drupal Groups site. A more frustrating project review could have easily meant the Drupal community losing all of this.

What changes do you hope will come in the project review process?

Mostly I think we just need more people with the right mindset. Right now, the “needs review” backlog is gradually disappearing, largely thanks to a lot of new reviewers. I think we just need to keep more of these reviewers involved and make sure they know, as jthorson recently wrote, “the role of reviewers in this process is that of a ‘mentor’, not ‘traffic cop’”.

What is your favorite part about the Drupal community?

It’s rare to hear someone say “I don’t care” in the Drupal community. There’s plenty of work that goes off the rails on passionate debate over what color to paint the bike shed, and that can grow tedious. But our bike sheds are the best-painted on the web (12 coats!), because people really care. I like that.

Tell us a little about your background or things that interest you outside Drupal?

When I was young, I hit myself in the forehead with a boomerang. I wasn’t entirely unfamiliar with the concept, but I’d never had one actually come back. This one did, just as I was turning to see where it had landed. Stitches weren’t great back then, so I still have a scar. I still have problems with tools doing what I say rather than what I expect.

Drupal 7.22 released

Drupal 7.22, a maintenance release with numerous bug fixes (no security fixes) is now available for download. See the Drupal 7.22 release notes for a full listing.

Download Drupal 7.22
Upgrading your existing Drupal 7 sites is recommended. There are n…

Drupal 7.21 released

Update: Drupal 7.22 is now available.
Drupal 7.21, a maintenance release which fixes incompatibilities introduced in the Drupal 7.20 security release, is now available for download. See the Drupal 7.21 release notes for further information.

Download D…

Drupal 7.20 released

Update: Drupal 7.21 is now available.
Drupal 7.20, a maintenance release which contains fixes for security vulnerabilities, is now available for download. See the Drupal 7.20 release notes for further information.

Download Drupal 7.20
Upgrading your e…

Drupal.org Downtime: February 12th 5PM PST (01:00 UTC)

Drupal.org and its sub-sites (api.drupal.org, groups.drupal.org, etc) will be going down for 30 minutes Tuesday, February 12, 5:00 PST (February 13, 01:00 UTC). This maintenance window will be used to upgrade our single sign on system. Please follow th…

Drupal 7.19 and 6.28 released

Update: Drupal 7.20 is now available.
Drupal 7.19 and Drupal 6.28, maintenance releases which contain fixes for security vulnerabilities, are now available for download. See the Drupal 7.19 and Drupal 6.28 release notes for further information.

Downlo…

The countdown begins: 26 days to DrupalCon Sydney!

Only local images are allowed.
6-9 February 2013
Crowne Plaza Coogee Beach
Sydney, Australia
http://sydney2013.drupal.org

DrupalCon Sydney, our first DrupalCon in the Asia Pacific region, has sold out!
We are so excited by the positive response from attendees, we wish we’d booked the opera house instead!

We’ve opened a waiting list for those who missed out on tickets, and will be releasing tickets as they become available, however there are still many opportunities to participate in all the wonderful events surrounding DrupalCon.

The Business Day program on Wednesday 6 February, keynoted by long-time open source advocate Pia Waugh , targets the conference theme of growing Drupal Downunder, and is a great event for business leaders, evaluators and decision makers to hear real stories and strategies around adopting Drupal. http://sydney2013.drupal.org/drupal-business-day

DrupalCon is a great opportunity to access hands on instruction from some of the world’s top Drupal trainers. Training programs on Git, Drupal Commerce and Building a Drupal site from scratch also kick off the conference on Wed 6 Feb 2013. If you missed on a ticket to DrupalCon why not snap up a ticket to one of these great training workshops.

The main conference on Thursday and Friday is filled with a rich and diverse selection of sessions from speakers from around the world, as well as home grown talent from the Australian Drupal community. Here’s a selection of our featured sessions.

Two “floating” tracks may be unfamiliar to diehard fans of DrupalCon. The Content Authoring and Case Studies tracks are aimed at broadening the appeal of DrupalCon beyond the traditional audience of geeky Developers, to try and engage a broader audience of non-technical Drupal users.

Our Advanced audience is invited to attend the Core Conversations Summit on Friday, which features a D7 to D8 module upgrade demo with webchick and an hour long D8 open forum with Dries and many Drupal Core Contributors.

Keynotes are always a big part of DrupalCon, and what kind of DrupalCon would it be without Dries Buytaert’s famous Driesnote? Dries will set the scene for the true state of Drupal 8 development and give a view of the road ahead.

After hearing about the future of Drupal, attention shifts to our second keynote, the Honourable Senator Kate Lundy, detailing how open source software makes it possible for governments and their people to engage with each other more directly, during her Friday morning keynote, “From Open Source, to Open Government.” Senator Lundy has been a powerful advocate for the adoption of Free and Open source software, and has been internationally recognised for blazing a pathway for a more open approach to government.

The conference concludes with a full Sprint Day on Saturday 9 February, which is open to anyone who wishes to attend. Make the most of the Drupal expertise in town and find out how to make your mark in the Drupal project. Let us know you’re coming!

New to contributing or just sprints in general? Come to Community Tools Workshop on Saturday morning get your Drupal Toolbox in order and level up your skills with Sprint leads xjm, ZenDoodles and add1sun, and other leading contributors. Sign up here!

Many in the Aussie Drupal community have made the pilgrimage North to attend DrupalCon in Europe or North America, so we are incredibly excited to welcome the world to join us in February Downunder.

See you on the beach!

PS. If you’re coming from overseas – Don’t forget you need a visa!

Predictions for 2013

Ever since node 4877 in 2003 we have a “prediction” post up on Drupal.org, where Drupal coders and users can share their vision on what will happen the year ahead with their beloved tool. Ever? Well, we skipped 2012, so we can not look back to the predictions you made last year on this site.

But that should not stop you from making some predictions for 2013. And you are welcome to do so in the comments below. Will parts of Drupal end up in another CMS or framework? Will “WSCCI first” be the slogan or will the consolidation in the CMS landscape and the trend to leave our small island make new bridges towards other PHP projects or even make a new Pangaea, beyond PHP and the web? Will Drupal be the answer in Jeopardy on the question “what is the best CMS?”. Time will tell.

Or you.. In the comments below

Drupal 7.18 and 6.27 released

Update: Drupal 7.19 and Drupal 6.28 are now available.
Drupal 7.18 and Drupal 6.27, maintenance releases which contain fixes for security vulnerabilities, are now available for download. See the Drupal 7.18 and Drupal 6.27 release notes for further inf…

Drupal.org Downtime: December 13th 5PM PST (01:00 UTC)

We will be having a very short downtime at 5PM PST (01:00 UTC) this Thursday December 13th. The outage should be no more than 2-3 minutes while we reboot a switch. Thank you.

Report from BADCamp 2012 Views Usability Testing

On Nov 1 2012, we tested the Views UI (7.x-3.5) with intermediate-level Drupal users at the BADCamp UX/UI Summit to provide the community with a clear picture of the usability bottlenecks in the Views UI, which is now in development in Drupal 8. We have identified a number of major problems and a large number of small ones, each of which now has an issue in the Drupal Core issue queue, where we discuss solutions, provide code patches with screenshots of the changes, come to agreement and put these changes into Drupal 8.

The study planning, participant profile, findings, videos and more are explained below.

Contents

Overall findings
Study summary
Screeners and study guide
Findings from study
Next steps
Video recordings (YouTube)

Overall findings

Participants thought that Views was “powerful” but complained about the steep learning curve to understand the concept and using the Views UI when they were first introduced to it. They relied on extensive Googling, face to face explanations from colleagues and video tutorials to learn Views. When they were thrown into unknown territories, their frustrations with using the UI were palpable.

Study summary

  • Number of participants: 8 (1 advanced user, 6 intermediate users, 1 beginner user)
  • Session length: 45 minutes
  • Study Focus: Using Views in Drupal 7
    • Understand existing user’s views usage & experience [behavior focused]
    • Uncover critical/major issues with existing users [UI focused]
    • How users navigate and operate the advanced settings
    • Gather data quickly so that actionable improvements can be incorporated into Drupal core before the feature freeze
  • Compensation offered: Google Open Source t-shirt
  • Recruitment method: Twitter (from BADCamp, @lisarex, @dcmistry), email to BADCamp UX Summit attendees. The email was quite successful.
  • Date: November 1, 2012
  • Type of study: Moderated usability study (in-person)
  • The sessions moderated by Dharmesh Mistry (dcmistry) and Lisa Rex (lisarex). Our volunteer note takers were Olga Biasotti, Angie Byron, Neerav Mehta, Lewis Nyman, Bojhan Somers, and Brian Young. Other volunteer contributors to the usability study planning include Bohjan Somers, Becky Gessler and Garen Checkley. Special thanks to Jen Lampton for coordinating the UX/UI Summit and putting up with us!
  • All the sessions were streamed live on Google+ and are available on YouTube (linked below)
  • Still from usability session with Kim

Screeners and study guide

Potential participants filled in a screener survey to see if they matched our profile, and a followup screener was used to help us clarify, when the scope of the study was narrowed.

We wrote a Views usability study guide (like a script), with the input from the Views in Core team.

Participant profile

  • Participants were targeted to be intermediate users who have done Drupal site building and have familiarity with Views (They have created basic Views and have dabbled with the advanced views). To keep the data focused, this is a report of findings of 6 intermediate users and 1 advanced user only. Data from the beginner participant will be added to future beginner level study data.
  • All participants were screened to be fluent in English.
  • Participants are comfortable with technology in their personal and professional lives.

Detailed findings

Positive comments

  • The first screen of Views UI get’s the user’s foot in the door
  • Participants rated their experience ratings higher as they got more exposure to views
  • Participants like the ability to preview and create custom CSS
  • Participants found theme template information useful

Critical, major and moderate usability issues

  1. Critical Lack of guidance: The views UI wizard page helps participants get the foot in the door but provides little guidance when they land on the second page. This is because the terminology is unclear and the visual hierarchy is flat. The problem gets severe under “Advanced” section.

    Possible solutions:

    • Use the Views UI wizard anytime a new display type is created.
    • More visual hierarchy on labeling and/or positioning
    • Contrib module with guided tour of Views
    • tooltip on hover of difficult labels

    [needs exploration + design]

  2. Major Too many items under configuration options for fields/ filters/contextual filters/ relationships: Participants feel “overwhelmed” when they see the long scrolling list of options. The problem gets worse because the participants do not necessarily see the “Search” option. The search option is visible only when you are on the top of the modal.

    Screenshot showing huge list of options for filters/fields

    Possible solutions:

    • Limit initial list to user created fields/filters.
    • Reduce visual clutter caused by descriptions.
    • Divide ‘filter’ (e.g. content, global) and criteria (e.g. Body, Comment count) into two columns, making the criteria more scannable
    • Search box has no visual weight and/or fixed positioning.

    #1832862: Users feel overwhelmed by handler listings

  3. Major Using “Contextual Filter” is difficult: When a participant selects a field in contextual filter, they are presented with a lot of options in a flat structure making them unsure how to proceed. This is mostly because of lack of workflow. The expectation was to select a default argument first and then move into related steps based on the choice. A related issue is the help text was unclear “Also look for node and node author ID” The advanced tools like contextual filter, relationship, exposed form require more guidance because it is a harder thing to do.

    Possible solutions:

    • Progressively disclose the functionality instead of all at once
    • Revise the text to be less Boolean, more human
    • Provide short UI / help text in a standard help block on these section to explain what they are

    [needs exploration + design]

  4. Major Several participants forgot to save/didn’t realise they need to save in order to see their changes to the view when they click “view page”. On smaller screens you can’t see the drupal_set_message() warning of unsaved changes.

    Possible solutions:

    • Provide an ‘Unsaved changes’ signal/notification within the main area of the Views UI, where they are looking [needs design]
    • Move save to button towards the bottom of the page (between preview, or at the end, or both)

    #1831894: Users miss “save” button and can’t distinguish “editable” and “preview” areas

  5. Major Participant had difficulty determining where the view showed up. If it’s a Page you can see the path. If it’s any other display type, you have no way of knowing where those displays appear on the site (P4).

    Possible solutions:

    • Show on the views listing the region where the block appears
    • Show in the views ui where the block appears (Attachment does this!)
    • Show when there’s an attachment in the Views listing (Block, Feed, Page appear in alphabetical order)

    #1834576: Improve details on the Views listing page

  6. Major Disconnect in the workflow of adding a block, as you have to create the block display, then save, then go out to the Blocks UI.

    Possible solutions:

    • Add “place block in region’ to the Views wizard.
    • Add “place block in region”to the advanced views.

    #1836390: Add “place block in region’ to the Views wizard to help workflow and #1836394: Add “place block in region’ to the Blocks settings in Views UI

  7. Moderate People often forget to add a path on a page, and if they hit save, they don’t see see the dsm() letting them know. If they haven’t saved, they still don’t realise the path is missing because the default / is very small and subtle. It’s also a very small target area for such a critical step in creating a page view. (P3)

    screenshot of the Views UI page showing the easy-to-miss default path setting

    Possible solution:

    • Replace the / with text such as ‘path is undefined’

    #1831142: Path is never empty in option summary.

  8. Moderate ‘View page’ link goes to the home if the path isn’t set, causing confusion because people think that is what they created when in fact its not.

    Possible solution:

    • ‘View page’ is not an active link until the view has been saved

    #1831696: View page link goes nowhere, if you have not saved

  9. Moderate ‘All displays” is the default option, even when there’s only a single display. This is unnecessary and is one more decision a new user has to fret over.

    Possible solutions:

    • Hide “all display/This page” options e.g. filtering when there is only one.
    • Significantly decrease the visual importance of this functionality.

    #1836384: The views UI should display “All Displays” option only when there are more 1 displays.

  10. Moderate Other related issue to “All displays”/ “Override this display”: In order to override a display you have to go to the drop down on the top left of the modal and to apply the display you have to go to the bottom right. As users are focused on the task at hand, they don’t realize that they have to change the filter and may accidentally apply to all displays. What makes the matter worse is that when it is changed to “Override this display”, the label changes to “Apply (this display)” but the difference is so subtle that the user did not register the difference.
    #1836392: In the Views UI, the interaction pattern of “All displays”/ “Override this display” is confusing
  11. Moderate Participant did not understand the Preview was updated automatically. They didn’t use it, and just went straight to ‘view page’.

    Possible solution:

    • Show when the last time the preview was updated

    #1836470: Participant did not understand the Preview was updated automatically

  12. Moderate On Views listing, participants have trouble determining what’s active and what’s disabled.

    Possible solutions:

    • Split them into two tables, with disabled underneath
    • Have the inactive views on a separate page, which is a gallery of possible views.
    • Change them to a tabbed display, with Active being the default tab
    • Fix the accessibility of the listing:

    #1830822: Split the Views UI listing into two tables for enabled and disabled

  13. Moderate The More section only contains the Administrative title. The “More” area is perceived as this magical area, where you might find something magical. Participants opened it and were disappointed to only find the administrative title.

    Possible solutions:

    • Move it out of this section until there’s more than one item, or label it with something less vague.:
    • Only show it upon clicking a checkbox using states, e.g. Add administrative title.

    #1831080: Remove the “More” area from the bottom of handler configuration

  14. Moderate ‘Theme: information’ label is misleading.

    “Theme information name is misleading because we are talking about templates. I have been on this page so many times and it’s still complicated. How are you supposed to know that this has theme’s real output?” (P4)

    Another participant didn’t know what Theme: information meant.

    Possible solution:

    • It should be relabeled to something like Theming: templates (P4)

    #1833834: Theme: information label is unclear

  15. Moderate People often click the “Settings” link when they see “HTML list | Settings” which causes them to miss how to change the main formatter settings.

    Possible solutions:

    • Merge the two settings
    • Make settings a tab of HTML list.
  16. Moderate When adding a field, “Create a label” is checked by default but we observed most people deselecting this. It’s only mostly useful for table display. (P4, P6, P7, P3). Needs more discussion to determine if this observation is accurate.

    Possible solution:

    • Deselect by default, collapse options. Limit # of items isn’t labeled so participant was unsure how to limit items on a block display. Assumed Pager label was specific to pages.

    #1831674: “Create a label” should be off by default, with an opt-in for style plugins

Less-actionable issues

  • There are 3 places the user sees for titling the page. (P2) http://screencast.com/t/S3BL6wdcflj
  • Medium: Help text is not helpful “also look for node and node author” (P4)
  • Large: Participants arent’ clear on what contextual filters are or when to use them (P2, P4)
  • Large: Participants arent’ clear on what relationships are or when to use them (P2, P4)
  • Medium: Grouping on fields is not widely understood
  • Grid display is not responsive because it is table based (P1)
  • Format level doesn’t signal about display (HTML/settings) (P6 & P7)
  • Preview contextual filter doesn’t have format settings (P6)
  • Large: observed people applying changes to All displays when they meant to override

Next steps

We will discuss the issues and explore other alternatives in the Drupal core issue queue. Relevant issues are tagged BADCamp2012UX.

Video recordings (YouTube)

Participant 1
Participant 2
Participant 3
Participant 4
Participant 5
Participant 6
Participant 7
Participant 8 (new user)

Upcoming Network Maintenance (Sat. Nov 10th, Mon. Nov 12, Wed. Nov 14th)

The OSL’s network provider is preparing to upgrade a core router. This is a large upgrade, but they have devised a plan to limit impact to us. All network outages should be short (5-10Min), but there will be a few of them. The first will be Saturday No…