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 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…
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.
6-9 February 2013
Crowne Plaza Coogee Beach
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!
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
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…
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.
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.
Screeners and study guide
Findings from study
Video recordings (YouTube)
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.
- 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)
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.
- 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.
- 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
- 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.
- 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]
- 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.
- 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
- 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.
- 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]
- 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.
- 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
- 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).
- 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
- 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.
- 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
- 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)
- Replace the / with text such as ‘path is undefined’
#1831142: Path is never empty in option summary.
- 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.
- ‘View page’ is not an active link until the view has been saved
#1831696: View page link goes nowhere, if you have not saved
- 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.
- 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.
- 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
- Moderate Participant did not understand the Preview was updated automatically. They didn’t use it, and just went straight to ‘view page’.
- Show when the last time the preview was updated
#1836470: Participant did not understand the Preview was updated automatically
- Moderate On Views listing, participants have trouble determining what’s active and what’s disabled.
- 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
- 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.
- 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
- 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.
- It should be relabeled to something like Theming: templates (P4)
#1833834: Theme: information label is unclear
- 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.
- Merge the two settings
- Make settings a tab of HTML list.
- 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.
- 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
- 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
We will discuss the issues and explore other alternatives in the Drupal core issue queue. Relevant issues are tagged BADCamp2012UX.
Video recordings (YouTube)
Participant 8 (new user)
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…
Update: Drupal 7.18 is now available.
Drupal 7.17, a maintenance release with numerous bug fixes (no security fixes) is now available for download. See the Drupal 7.17 release notes for a full listing.
Download Drupal 7.17
Upgrading your existing Drup…
We will be taking Drupal.org down for up to 60 minutes starting Saturday, October 27, 20:00 PDT (Oct 28 0300 UTC). This outage is to deploy Apache Solr 6.x-3.x. Search results will be incomplete following the downtime as we catch up indexing. Please fo…
Update: Drupal 7.17 is now available.
Drupal 7.16, a maintenance release which contains fixes for security vulnerabilities, is now available for download. See the Drupal 7.16 release notes for further information.
Download Drupal 7.16
Upgrading your e…
The Marketplace section on Drupal.org has been revamped through major changes. Most of it happened a couple of weeks ago, but some are as recent as this week. This post will give you quick overview of what has changed and what you need to know and do right now to keep your Marketplace listing up-to-date.
If you don’t want to read all the details, jump to What is going on next, that is important for your listing.
So what changed?
When the work was begun the old services pages (part of the handbook) were removed and the new marketplace was titled “Marketplace preview.” That interim title is gone, the old handbooks are gone, and the Marketplace now has 3 sections:
Hosting section stayed completely the same. As for the other two – there are some updates.
Drupal Services now has 2 listings: Featured providers and All providers, with Featured section being the landing page of the Marketplace.
Training section is also now a view of organization nodes similar to the Services section. The fields shown in this view are Title, Training url and Training description, so make sure to fill those if you want to be listed.
The Hosting, Training and Marketplace displays all pull from the same fundamental organization node type.
After much discussion and weighing of different perspectives and goals we now have new Marketplace guidelines in place, which describe what each section means, what you need to do to get listed, what is the process.
Items to note:
- Contributions back to the community is the first and main requirement to be listed in the Marketplace.
- Organization pages need to be updated at least once per year. If you haven’t updated yours for more then 12 month, we will remind you via your company’s issue and wait 2 weeks for you to update the node. If 2 weeks passed and node is still not updated, we will remove it from the listing.
What is going on next?
We keep working on marketplace improvements so changes above won’t be the last. 2 important things happened just this week:
Having a /drupalgive page and feed featured on Drupal Planet is now a strong recommendation for those companies wishing to be listed in the Featured section. For more information on /drupalgive initiative please see http://drupal.org/drupalgive.
Issue: #1783768: Proposal: make /drupalgive feed a requirement for getting featured
“Countries served” vocabulary has been renamed to “Locations”. From now on the purpose of that field is to display only countries where your company has physical offices. The field value was cleared for all companies, everyone is welcome to update their organization pages with the correct Locations.
Issue: #1765610: Change title of “Countries served” vocabulary to “Locations”
We also cleaned up Sectors and Services vocabularies, a lot of duplicate terms are gone, make sure to update those too.
Am I listed?
If you are listed in either Services or Training section you should see 1 or 2 of the following messages on the top of your organization page:
This organization is a Drupal services provider.
This organization is a Featured services provider.
This organization is a Training services provider.
The messages link to the sections of the Marketplace you are listed in.
What if there are no messages for me?
If there are no messages on the top of your organization page it means you are not listed in any section of the Marketplace.
To get listed you need to pass community review process outlined in the Marketplace guidelines.
First step is to request listing. To do so you need to edit your node and check one (or both) of the following:
Request listing in the Drupal services section.
Request listing in the Training section.
Once you save the node an issue will be created automatically in the Webmaster’s queue for each selected checkbox. The issue will indicate that you want to be listed, community members will review your node and comment on the issue. Reviews are performed by volunteers from our community, so please be patient as this process might take some time.
Where I can find an issue for my company?
If you are author of the organization node and you requested a listing – you will see one or both of the following messages on top of your organization page with the links to relevant issues:
Regarding Services listing communicate with webmasters using this issue.
Regarding Training listing communicate with webmasters using this issue.
Links to note:
- We are trying to collect most frequently asked questions and answers in the Marketplace FAQ.
- Issues related to Marketplace improvements have a tag drupal.org marketplace.
- If you have questions or suggestions you can open an issue or come on IRC #drupal-contribute or #drupal-infrastructure channels.
Thanks goes to BarisW for his help with the latest improvements.
We are also very grateful to Drupal Association Volunteers and Supporting Partners, who have made all these improvements possible. The Supporting Partner Program crowd sources funds that pay for the development team’s time and Drupal.Org hosting costs. And volunteers are a key part of our team. They donate huge amounts of time and talent to help us make Drupal.org better.
UPDATE: Voting closed 7 Oct 2012.
Vote now for community elected “At Large” Directors of the Drupal Association!
In 2011 the Drupal Association was restructured and a new board was appointed. Most of the board are selected by a nominating committee who aim to ensure people on the board bring a range of skills and experience to the table. However, to make sure the community is always well represented there are also two directors chosen directly by the Drupal community “At Large”. These community elections are held to fill those two positions.
Voting is open until 23:59 UTC 7 Oct 2012 at https://association.drupal.org/vote2013
Who can vote?
You are eligible to vote if you have an account on drupal.org, logged in during the past 12 months, and created your account before 31 August 2012 when the election was announced.
How to vote?
Meet the candidates
Floh Klare (SirFiChi)
I’m a Sitebuilder. I use Drupal for personal projects. I’m active in the german community and a leader of the German Drupal-Initiative e.V. I can use Drupal for free and want to give something back. I want others to know, that they can do the same.
Todd Tomlinson (toddtomlinson)
36 years in the IT industry, global experience, prior board positions, non-profits, professor/teacher, live/eat/sleep Drupal.
J. Matthew Saunders (MatthewS)
I bring 17 years from the technology world, 13 years in Opensource, 6 years of highly active participation in the Drupal community, 8 years of nonprofit management in a US based Technology focused nonprofit, two VP board positions in nonprofits including policy development, and two university qualifications – one a Masters – focused on organizational management for nonprofits. I’m passionate about Drupal and adore the Drupal Community.
Chris Ward (chrischinchilla)
I got into Drupal several years ago, initially as a developer but more recently as a project manager, evangelist and community builder. I’d be keen on driving several initiatives: Cleaner, more efficient and user friendly documentation. Creating better case studies for Drupal, the whys and the business benefits of using it. Better community building across the wider tech community, i.e. encouraging Drupal experts to talk at relevant more general conferences and events aside from just Drupal related events.
Valery Lourie (valthebald)
Teaching and course-organizing experience, as well as connection to non-English speaking developer communities in Israel and former Soviet Union (Russian is my mother tongue). I think both communities are “under-penetrated” by Drupal today.
Aimee Maree Forsstrom (amaree)
A Community perspective from a non rock-star roots level and experience managing Open Source Conferences and Meet-ups, Passion
Narayan Newton (nnewton)
I got into Drupal while I was a student systems administrator at The Oregon State Open Source Lab, the hosting providers for Drupal.org. I hope to represent the Infrastructure Team. A major responsibility of the DA Board is infrastructure and currently there is no voice on the board for that largely volunteer team. I also hope to provide some sensible review of future technical projects funded and managed by the board.
David Stoline (dstol)
I want to be part of the DA Board because I want to help shape the future and growth of the community. Having worked with the DA in the past, through my organizational experience with CapitalCamp, I bring a different perspective that will help the overall governance of the DA.
Joseph Bachana (joebachana)
I have been working in technology consulting for my entire adult life. Over the years, I learned not only about how to implement Drupal successfully, but what it means to be committed to an open source project. I want to help and use both my expertise and creative thinking as well as what resources I can apply to help the Drupal project be even more successful in the coming years.
Pedro Cambra (pcambra)
I’m a Spanish Drupal Developer very involved with the community since 2008, I’ve helped to organize 6 different events in Spain since then, including the this year’s Drupal Developer Days in Barcelona, my motivations are to represent the Spanish speaking community in the board and help to grow stronger binds between the Drupal Association and the local groups all around the globe, no matter what their current size is. My main objective: having a Drupalcon in South America sooner than later.
- Session 1
- Session 2
- Session 3
- Session 4
Jeremy Thorson (jthorson)
I’m an active Drupal hobbyist, and the guy who keeps the testbots running. What I bring to the board is i) passion, drive, and demonstrated initiative, ii) a balanced approach to conflicts and challenges, iii) relevant background and non-profit board experience, and iv) a wide breadth of perspectives, representing multiple roles in the community. See my blog post for specific details!
- Session 3
- Session 4
Simon Hobbs (sime)
I’m Simon Hobbs (sime). I’m a Drupal consultant and trainer from Melbourne, Australia. I am a former business owner of a Drupal services company and have been active in the Australian Drupal community. I believe in a stable, conservative Drupal Association with a realistic scope. My personal focus would be on training, how to continue and strengthen the DA’s global training initiative.
Morten Birch Heide-Jørgensen (mortendk)
I run a small Drupal design & theme shop in Denmark: geek Röyale. We as a board need to shift focus back to the community, reevaluate how the organization operates, clearly define why the organization exists, and for whom it exists, and do better as leaders to support and grow Drupal worldwide.
Steven De Costa (starl3n)
I’ll bring a strategic marketing framework to the Board – but don’t confuse this with posters and tweets I want to help the DA define its position within a broader economic view of the IT services industry and leverage the flow of value to benefit the Drupal project. 1st up: I’ll aim to bring new funds via Govt memberships and a grants funding initiative.
- Session 1
- Session 4
Bert Boerland (bertboerland)
Bert has been active as a user, handbook writer, tester and evangelist since the Drupal’s early days op on drop.org and has a long standing track record in the Drupal community. He donated the Drupal.org domain to the community. This is ambitious, adding transparency, communicating the value of the DA when it comes to drupal.org, facilitating the diversity of local camps and making sure the DA is for everybody worldwide. I know however that I can help the DA here and am dedicated to do so.
Jeffrey A. ‘jam’ McGuire (horncologne)
If you’re contributing to Drupal, we’re on the same side – however and wherever it is that you contribute. I would bring multilingual-, multicultural-, non-US-centric perspective; experience from international community – and business worlds; as well as communication – and marketing skills to the board.
- Nomination statement
- Session 1 answers
- Session 2 answers
- Session 3 answers
Forest Mars (forestmars)
New York based hypermedia architect working with Drupal for over 5 years in business, media, and the non-profit sector. I’d like to see contact fine-tuned between the board and the community-at-large, a task that requires not only impeccable communication, but also a nuanced understanding of the complex mix of divergent goals and even tensions which make up the project and surrounding community. Such an understanding naturally gives rise to the desire to contribute exactly what’s needed to bring our stated goals to fruition, reflected in attendance – if not yet participation – at our newly open and, incredibly exciting, DA board meetings.
Voting is open until 23:59UTC 7 Oct 2012 at https://association.drupal.org/vote2013
We will be taking drupal.org down for 30 minutes Tuesday, September 18, 17:00 PDT (Sept 19 0000 UTC). This outage is to update site code and re-hash user passwords, increasing their security. When the site returns, users may find that they cannot login…
The new Case studies section on Drupal.org has been built and launched. You may not have noticed, since the look of the homepage hasn’t changed, but the case studies have a new home with a new look. This has been a multi-layered effort involving the Drupal Association web team and several community volunteers.
Now we need some great new case study content. We’re looking to feature Drupal sites that have one or more of these qualities:
- Visually appealing custom theme
- Stand out for performance optimization, interaction, customization, accessiblity or third-party integration
- Positive and inspiring examples for business owners, site builders and developers to learn from
You can help by writing a case study on your own impressive project, or volunteer your time as a reviewer of case studies.
Why write a case study?
Here’s a few reasons:
- Promote a great Drupal site; show the world what Drupal can do
- Recognize your team members for their hard work
- Recognize maintainers of the contributed modules that you’ve used
- Excellent case studies can be promoted to the Featured section and appear on the front page of Drupal.org!
To get started, go to http://drupal.org/case-studies. From here you can see the types of sites that have been promoted, check out the case study guidelines, and submit your own case study.
Help us maintain case studies
The Case studies section (as is most Drupal.org content) maintenance is handled by volunteers. You don’t need to be a programmer or have special knowledge to help out with case studies, just have good judgement and English language/grammar skills.
Regular tasks include:
- Write case studies for your own projects or for others
- Find Drupal sites that deserve to be featured on Drupal.org
- Review requests to be promoted to Featured, suggesting improvements as needed, e.g.
- copy improvements
- taxonomy terms
- review Community case studies for adherence to case study guidelines, as well as for spam posts and comments
Guidelines for writing a case study: http://drupal.org/node/1588136
Guidelines for case study promotion review: http://drupal.org/node/1617960
Requests for promotion to Featured section have a tag case study promotion, just open issue queue and start reviewing!
If you have questions or need some guidance – come to #drupal-marketing IRC channel on Freenode.
Case study sprint at DrupalCamp Brighton
If you happen to be at the DrupalCamp Brighton this weekend, join case study sprint on Sunday.
We will be taking git.drupal.org down (ssh, http and git:// protocol access) for 30 minutes starting at 10AM PDT (1700 UTC) September 14th. This maintainence window is for updating our git daemon to support updated security features. Please follow the …
Why Drupal was chosen:
Migrating from a raw HTML site, which had to be updated manually, Drupal 7 offers high-end publishing tools to quickly a…
Update: Drupal 7.16 is now available.
Drupal 7.15, a maintenance release with numerous bug fixes (no security fixes) is now available for download. See the Drupal 7.15 release notes for a full listing.
Download Drupal 7.15
Upgrading your existing Drup…
Hello from Jennifer, your outgoing Drupal Documentation Team leader! As I step down as leader of the Documentation team, I wanted to make one last quarterly status update post for the Documentation Team.
People in the Drupal project are currently exploring Drupal community governance, and among the questions they’ll be thinking about are the leadership and structure of the Documentation Team — so expect an announcement sometime soon! In the meantime, I’m not going to be hosting Documentation Office Hours, but if someone else wants to schedule an Office Hours, go ahead and post an event to the Documentation groups.drupal.org page.
Milestones, Accomplishments, and Projects in progress
- Lots of content was updated on Drupal.org this quarter. Of particular note:
- The Accessibility team worked on updating documentation at a sprint in Montreal, including the Creating accessible themes section, and the best practices on accessibility for site builders page.
- The Multilingual team updated both in-code API documentation and on-line Community documentation for Drupal’s multi-lingual system.
- The Mobile team organized and created a Mobile guide.
- I’m sure there are other notable updates that I didn’t mention specifically — 921 different contributors made more than 5000 revisions to documentation pages on Drupal.org this quarter — thanks to everyone who made an edit or created new documentation!
- There’s a new Community Documentation Moderator group! These dedicated individuals will be overseeing the Community Documentation, and doing tasks that the general Drupal community members do not have the permissions to do (deleting comments, making edits on locked pages, creating URL aliases and redirects, etc.). I’d like to especially thank Boris/batigolix for joining the Moderator group and dealing with so many Documentation project issues in the past few weeks — I’m sure he’d appreciate some help though, so please join him! (Responsibilities and instructions for how to get started: http://drupal.org/node/1588928)
- The API documentation cleanup sprint from last quarter has continued into this quarter, and a lot of progress has been made! The goal is to bring the Drupal 7 and 8 core API documentation much more in line with our documentation standards. To join in, visit the issue page. There is also a related sprint for general PHP coding standards at http://drupal.org/node/1518116
- Work on the proposed Curated/Official Docs and Help system has picked up! We have an issue to track progress on building the system, and Google Summer of Code participant Gergely Tamás Kurucz (temaruk) is working on a major component this summer. WorldFallz has also just volunteered to work on the workflow piece of the project, so hopefully around the end of the summer, we’ll be able to deploy the first phase of the system, and start writing “official/curated” documentation. But we will still need some programming help — check the tracking issue for more details.
- The “Books about Drupal” section is being revised to have a new content type and a View, instead of being a set of flat HTML pages. Lowell/LoMo has been working on that, and we hope to get it finished and deployed on Drupal.org in the next few weeks. Issue: http://drupal.org/node/1487988
- Many members of the Drupal documentation team collaborated last quarter on proposing an update to the sidebar navigation for the Community Documentation. We reached consensus that we would like to have +/- expand/contract ability on the sidebar, so that people searching for documentation could more easily drill down into the book structure to find pages of interest. But we need some help: evaluating existing modules to see if they will work for us, and if not, building a module that will. If you’d like to help, the issue is: http://drupal.org/node/1508832
- The API module (the module behind http://api.drupal.org, the programmer API documentation reference site) has been ported to Drupal 7. I did the primary port, and several people contributed by testing it out and/or posting patches for bugs they found. api.drupal.org should be running Drupal 7 sometime soon! The next new features planned for the site are to get more contributed modules visible, make it work correctly with PHP namespaces (which are extensively being used in Drupal 8), and replace the hard-to-maintain Form API reference with an automatically-generated page (and in-code comments). If you’d like to help with these efforts, check the API module issue queue.
If you’re interested in helping with Drupal documentation: