Drupalcon Denver 2012 Call for Speakers

Drupalcon Denver 2012 header

Denver, CO is hosting the next North American DrupalCon happening on March 19-23, 2012 at the massive, well-appointed Colorado Convention Center. The worldwide Drupal Community is what makes DrupalCon so fun and exciting, and Colorado’s community is thrilled to be the home of “Drupal Elevated” — tickets go on sale soon, so be sure to follow us on twitter and we’ll tell you what’s going on, @drupalcondenver.

DrupalCon is a world-class conference with a world-wide audience. If you or your organization actively use Drupal, or even if you never have but want to learn, DrupalCon is your chance to engage the community, learn from others, and share your experiences.

DrupalCon Denver is now accepting session submissions — go to http://denver2012.drupal.org/ to submit your idea today! If you want to present in Denver, now is the time to start thinking about what this year’s theme, “Collaborative Publishing for Every Device,” means to you, and we’re accepting sessions in the following tracks:

  • Site building
  • Coding and development
  • Design and user experience
  • Drupal community
  • Business and strategy
  • Mobile
  • Commerce
  • Nonprofit, Government and Education

Read descriptions of each track at http://denver2012.drupal.org/about

Sponsoring DrupalCon is a great way to get your message before a targeted audience of Drupal users, developers, businesspeople, and other Web professionals. And, you earn karma points because your investment helps make DrupalCon passes affordable so more community members can attend.

Sponsor packages provide various levels of lead generation, branding, networking and recruitment opportunities. Contact megan@association.drupal.org with questions or go to http://denver2012.drupal.org/

Follow Drupalcon Denver on Twitter @drupalcondenver, to stay informed on the latest details!

Continue reading…

 

Core office hours start this week

Drupal core needs more eyes and more contributors to decrease the very high amount of unresolved issues.

We’re going to hold the first core “office hours” this week in #drupal-contribute on freenode:

Depending on how this goes, we may continue these slots weekly (with a break for DrupalCon).

Update
After a good start last week, we’ll continue office hours this Tuesady 16th and Wednesday 17th August.

Why office hours?

There are currently a large number of unresolved issues in the core queue, and we want to get more organised dealing with the backlog, and encourage new people to help out.

Current numbers:

How will office hours help?

If you’ve been wanting to get involved in Drupal core development, but aren’t sure where to start, coming to the office hours. You will find experienced contributors who will help you find something to work on.

If you have patches or bug reports against Drupal core, and want to get your patch reviewed or figure out where to take the issue next, this should be a good time of the week to trade reviews on IRC.

Things we will do

Office hours are for both experienced contributors and developers as well as newcomers, expect some of the following:

  • Triaging the core queue – understanding status, priority of issues, closing duplicates etc.
  • Co-writing issue summaries.
  • Co-writing change notifications for needs work issues tagged with “Needs change notification”.
  • Writing SimpleTests for bug reports that don’t have them.
  • Swapping patch reviews.

New contributors should already be prepared to do the following:

  • Have a local environment to review and test core patches.
  • Get familiar with the documentation at http://drupal.org/patch

Mentors/co-ordinators possibly available

We’ll try to make sure at least one person is online during each slot.

Continue reading…

 

State of Drupal 2011 survey

The last time I organized a State of Drupal survey was in 2008. The results of the 2008 survey were instrumental in shaping Drupal 7 as well as directing the work of the Drupal Association on drupal.org.

Now three years later, I created a new survey. The results of this survey will guide thousands of people in the Drupal community over the next two years.

Take the State of Drupal 2011 survey now.

It shouldn’t take more than ten minutes to fill out. Don’t worry if you’re new to Drupal: every voice counts!

I’ll present the results during my DrupalCon keynote in London; the video and the presentation slides will be downloadable after. Please do tell us what you think these days about Drupal: your views will shape Drupal 8 and beyond. Thanks!

Continue reading…

 

Drupal 7.7 released

Drupal 7.5, a maintenance release which fixes security vulnerabilities is now available for download. Drupal 7.6 7.7 also fixes other issues reported through the bug tracking system.

Note: Drupal 7.7 is just Drupal 7.6 with a fixed VERSION string (7.6 was reporting itself as 7.5). No other changes.

Upgrading your existing Drupal 7 sites is strongly recommended. There are no new features in these releases. For more information about the Drupal 7.x release series, consult the Drupal 7.0 release announcement.

Security information

We have a security announcement mailing list, a history of all security advisories, and an RSS feed with the most recent security advisories. We strongly advise Drupal administrators to sign up for the list.

Drupal 7 includes the built-in Update status module, which informs you about important updates to your modules and themes.

Bug reports

Drupal 7.x is being maintained, so given enough bug fixes (not just bug reports), a new maintenance release will be made available the last Wednesday of next month (August 31).

Changelog

Drupal 7.5 only includes fixes for security issues. Drupal 7.6 also includes bugfixes. The full list of changes between the 7.4 and 7.7 releases can be found by reading the 7.6 release notes. A complete list of all bug fixes in the stable 7.x branch can be found in the git commit log.

Security vulnerabilities

Drupal 7.5 was released in response to the discovery of security vulnerabilities. Details can be found in the official security advisory:

To fix the security problem, please upgrade Drupal.

What is included with each release?

Shows a graph and that 7.5 should be used to upgrade quickly, 7.6 contains bug fixes and might need testing.

We make two versions of Drupal core available, so you can choose to only include security fixes (Drupal 7.5) or security fixes and bugfixes (Drupal 7.7). You can choose your preferred version. We are trying to make it easier and quicker to roll out security updates by making security-only releases available as well as ones with bugfixes included. We hope this helps you roll out the fixes as soon as possible. Read more details in the handbook.

Update notes

  • (#634616) AJAX now responds to ‘click’ instead of ‘mousedown’.

Continue reading…

 

Drupal 7.4 released

Drupal 7.3, a maintenance release which fixes security vulnerabilities is now available for download.

Drupal 7.4 also fixes other issues reported through the bug tracking system.

Upgrading your existing Drupal 7 sites is strongly recommended. There are no new features in these releases. For more information about the Drupal 7.x release series, consult the Drupal 7.0 release announcement.

Security information

We have a security announcement mailing list, a history of all security advisories, and an RSS feed with the most recent security advisories. We strongly advise Drupal administrators to sign up for the list.

Drupal 7 includes the built-in Update status module, which informs you about important updates to your modules and themes.

Bug reports

Drupal 7.x is being maintained, so given enough bug fixes (not just bug reports), a new maintenance release will be made available the last Wednesday of next month (July 27).

Changelog

Drupal 7.3 only includes fixes for security issues. Drupal 7.4 also includes bugfixes. The full list of changes between the 7.2 and 7.4 releases can be found by reading the 7.4 release notes. A complete list of all bug fixes in the stable 7.x branch can be found in the git commit log.

Security vulnerabilities

Drupal 7.3 was released in response to the discovery of security vulnerabilities. Details can be found in the official security advisory:

To fix the security problem, please upgrade Drupal.

What is included with each release?

Continue reading…

 

Docs team 2nd Quarter 2011 update

Hello from Jennifer and Ariane, your friendly Drupal Documentation Team co-leads! It’s time for a quarterly update on what’s happening in the Documentation team—we’ve been trying out some new initiatives and working on infrastructure since our last update (April 5, 2011), and we’d like to get you up to date.

April – June events

  • In April and May, Ariane tried out a new concept: picking out a few online Drupal.org documentation projects for the docs team to focus on, in the spirit of an agile “sprint” (not to be confused with a day-long let’s-all-document “sprint”). April’s sprint focused on 5 key Drupal 7 documentation updates, and it was quite successful: many people participated; four of the five documentation goals were completed, and lots of progress was made on the 5th (updating the core module documentation for Drupal 7). May’s sprint had a bit less momentum, but many of the April contributors continued on, and some progress was made.
  • Jennifer also made a developer-doc priority for April and May—to finish the theme and module Drupal 6 to 7 migration guides. This task was completed in June.
  • We named June “Bring a Friend to Docs” month, and outlined an easy procedure to ease new contributors into contributing to documentation. If you missed it in June, you’re still welcome to follow the steps on that page—we can always use more contributors!

Upcoming events

  • Jennifer and Ariane will both be at DrupalCon London (thanks to the Drupal Association for funding Jennifer’s trip!). Keep an eye on the BOF (Birds of a Feather – informal sessions) schedule, and join us for a Documentation sprint on Friday, August 26 (if you can’t make it to London, you can join us in IRC on #drupal-docs, probably about 9 AM to 5 PM London time). Jennifer’s also (hopefully) co-presenting a Core Conversation about improving the Drupal Help system with Kristof Van Tomme, if it gets accepted. Hope to see you there!
  • Ariane’s online documentation sprints will take a vacation for the summer, and are planned to resume after DrupalCon London.

Continue reading…

 

DrupalCon London Session Schedule and Core Conversations


The DrupalCon London Team had the task of narrowing 341 fantastic proposals into a schedule of 60 sessions, balanced across 5 tracks: Site Building and Environment Set-up, Business and Best Practices, Code & Coders, Design, UX & Theming, and Ecosystem. You can check out the schedule now and attendees will be able to build their schedule on the DrupalCon London site by logging in later this week.

This breaks down to 5 tracks with 12 sessions each. The 6th track, Core Conversations, will also have 12 sessions slots available and DrupalCon London will be opening core conversation session proposals between 14 June and 14 July 2011, 23:59 GMT+1. Core Conversations are a place for people actively working on Drupal or Drupal.org to meet and plan the future of Drupal (Drupal 8). We will announce selected Core Conversation sessions on 22 July 2011.

We remind you that we have some excellent pre-conference training courses and workshops scheduled for 22 August 2011 and invite you to register for these. This is a great opportunity for Drupalists at all levels of experience to learn from the experts.

The cost for a full day training varies from only £150 for the Absolute Beginner’s Guide to Drupal to £325 for advanced topics like Building Modules for Drupal 7 and Drupal Powered E-Commerce.

Demand for Drupal talent is high, so why not invest in your future!

Register now to attend DrupalCon London and for pre-conference training.

If you would like to support DrupalCon London and help us spread the word about the conference. Here you can get badges for your website and promote the conference via our Twitter and Facebook widgets.

See you at DrupalCon London 22-26 August 2011!

Stay up-to-date with the latest information about DrupalCon London by going to http://london2011.drupal.org/ or following us on Twitter @drupalcon.

Continue reading…

 

Report from the University of Minnesota Drupal Usability Testing

From May 17 – 19, 2011, in advance of DrupalCamp Twin Cities, several Drupal community members met at the University of Minnesota usability lab in Minneapolis to perform a round of formal usability testing on Drupal 7. This is the fourth major usability testing for Drupal, and the first targeting the new Drupal 7 release.

People who were familiar with building websites (but not with Drupal) were observed while they worked through a number of site building tasks. This report contains a summary of the results.

Summary

The good news is that most of the changes that were put in Drupal 7 tested well. Compared to Drupal 6, Drupal 7 no longer confuses new users with basic conceptual hurdles like where the front-end vs. back-end of their site is and how to create an “About us” page, and for the most part the administrative interface is clear.

The bad news is that now that some of these basics have been dealt with, we’ve uncovered a whole new layer of challenges for first-time Drupal site builders, some of which were pretty surprising. Finding modules, creating and placing blocks, and creating content types were difficult tasks for participants to understand, and it’s these site builder tools we’ll want to improve for Drupal 8.

Who did we test, and how did we test them?

Eight participants (a typical number for this kind of study) evaluated Drupal by working through a series of real world tasks over a 75 minute period, “thinking aloud” while the team observed and took notes from behind a one-way mirror. The participants could phone a “help desk” (staffed by a member of the team) if they ever got stuck and needed a nudge in the right direction, and a number of open-ended questions were asked throughout the test session.

All eight of our participants are people directly in Drupal’s target audience. They are site builders, already using tools such as Dreamweaver and WordPress.

Continue reading…

 

Drupal 7.2 and 6.22 released

Drupal 7.1 and 6.21, maintenance releases which fix security vulnerabilities are now available for download.

Drupal 7.2 and 6.22 also fix other issues reported through the bug tracking system.

Upgrading your existing Drupal 7 and 6 sites is strongly recommended. There are no new features in these releases. For more information about the Drupal 7.x release series, consult the Drupal 7.0 release announcement, more information on the 6.x releases can be found in the Drupal 6.0 release announcement. Drupal 5 is no longer maintained, upgrading to Drupal 6 is recommended.

Security information

We have a security announcement mailing list, a history of all security advisories, and an RSS feed with the most recent security advisories. We strongly advise Drupal administrators to sign up for the list.

Drupal 7 and 6 include the built-in Update status module, which informs you about important updates to your modules and themes.

Bug reports

Both Drupal 7.x and 6.x branches are being maintained, so given enough bug fixes (not just bug reports) more maintenance releases will be made available.

Changelog

Drupal 7.1 only includes fixes for security issues. Drupal 7.2 also includes bugfixes. The full list of changes between the 7.0 and 7.2 releases can be found by reading the 7.2 release notes. A complete list of all bug fixes in the stable 7.x branch can be found in the git commit log.

Drupal 6.21 only includes fixes for security issues. Drupal 6.22 also includes bugfixes. The full list of changes between the 6.20 and 6.22 releases can be found by reading the 6.22 release notes. A complete list of all bug fixes in the stable 6.x branch can be found at git commit log.

Security vulnerabilities

Drupal 7.1 and 6.21 were released in response to the discovery of security vulnerabilities. Details can be found in the official security advisory:

To fix the security problem, please upgrade Drupal.

What is included with each release?

We made two versions of both Drupal 7 and 6 available, so you can choose to only include security fixes (Drupal 7.1 and 6.21 respectively) or security fixes and bugfixes (Drupal 7.2 and 6.22).

Continue reading…