Upgrade Your Drupal Skills

We trained 1,000+ Drupal Developers over the last decade.

See Advanced Courses NAH, I know Enough
Sep 26 2016
Sep 26

The Drupal open source project only exists because of code contributions by tens of thousands of developers and Drupal focused companies around the world. In his recent post, project founder Dries Buytaert blogged that “The Drupal community has a shared responsibility to build Drupal and that those who get more from Drupal should consider giving more”.

Australia’s contribution to Drupal code is significantly underrepresented, with PreviousNext the only Australian company in the Top 100 contributors listed on Drupal.org’s global marketplace. DrupalSouth represents the best opportunity for a wider pool of Australian Drupal developers to change this status by participating in DrupalSouth's official Code Sprint, being held on Wednesday, 26th October.

Sponsored by PreviousNext, some of Drupal 8’s most prolific code contributors will be on hand to help you make your dent in the Drupal universe on Wednesday October 26.


So we can make sure we have enough capacity to understand what level of experience you have, we require you to pre-register your attendance via the registration form.

Venue & Schedule

The Code Sprint will be held on Level 2 in DrupalSouth’s conference venue. Directions will be available in the foyer on the day.

The Code Sprint will be held on Wednesday October 26 and officially start at 10am, finishing no later than 5:30pm.

What is a Sprint?

A sprint is an opportunity to get together with other like-minded people and work together on something that interests you. It can be Drupal core issue, a contrib module you want to port, writing documentation, writing tests. Whatever scratches your itch!

Sprints are not just for developers. Bug reporters, QA testers, and documentation editors are all able to contribute. If you want to get involved, then you are welcome to join in.


While co-sprinters at Drupal events are usually always happy to help, the sprint is not a Drupal training event.

There will be a mix of experience levels, and if you are new to Drupal, there will be people at the event who can get you started. The best way to get involved is to find a group of people who all want to work on the same thing, and to help each other.


We recommend following the Drupalcon guide on getting set up before the sprint. https://events.drupal.org/neworleans2016/mentored-core-sprint#setup
You will need to bring your own laptop, snacks, drinks etc.

What will we be Sprinting on?

The PreviousNext team are involved in a number of core and contrib projects for Drupal 8, including:

  • Default Content
  • Media Entity Browser
  • LDAP
  • Contact Storage
  • Title

Feel free to suggest other projects you’re keen to work on when you register.

DrupalSouth Code Sprint
Jun 11 2015
Jun 11

DrupalCamp STL 15 Hero

On June 20 - 21, people from all over the Midwest who use, design, develop and support Drupal will convene in downtown St. Louis for the second annual DrupalCamp STL. Meet us in St. Louis and help us forge new skills and friendships while furthering the Drupal project.

Registration is only $25, and if you register ASAP you'll get a soft, comfy T-shirt, a nice catered lunch, and an excellent lineup of sessions on Saturday, and sprints all day Sunday!

Check out the schedule for the day, which includes a keynote by Alina Mackenzie on getting involved in the Drupal Community.

Join us in the Learning Lounge on Saturday, and for Sprints on Sunday, to increase your Drupal knowledge, meet some other Drupal community members, and help make Drupal better!

Sep 17 2014
Sep 17

DrupalCon code sprint photo

Have you always wanted to get involved with Drupal core development but don’t know where to begin? Have a Drupal 6 site that you’re looking to upgrade to Drupal 8? The Drupal 8 Migrate in Core initiative aims to provide a robust and extensible migration path from Drupal 6 and Drupal 7 to Drupal 8. A lot of work has already been done, but we’re looking to increase our throughput by training up some testers and developers to contribute to the cause.

To that end, we’ve planned two in-person events and an ongoing virtual event where you can get some facetime with other contributors to get you up-to-speed on the current progress and how you can help. Development experience isn’t required! It takes all types of contributors to complete a project of this scope. We have opportunities for manual testing, documentation writing, UX, theming, patch testing, and patch creating. If you need more of a challenge, I’m sure that chx, benjy, and mikeryan can find something for you to sink your teeth into!

If you can’t wait to get started, please check out how you can properly configure your system in order to contribute. Even if you just want to do some manual testing, you’ll want to check this out. Once your system is ready to go, then find me in IRC (#drupal-migrate) or find us at an upcoming event.

DrupalCon Amsterdam

Ryan Weal will be the team leader on the ground at DrupalCon Amsterdam. He’ll be camped out at the official sprint locations on the extended sprint days as well as the day prior and after the ‘con (September 27, 28, 29 and October 3, 4, 5). Friday, October 3 is traditionally the largest sprint day of them all, so if you have any experience with contributing to Drupal core, let Ryan know and he’ll likely put you to work helping out new contributors.

Christian López Espínola (penyaskito) will also be attending the Amsterdam sprints in-person, focusing on Migrate in Core multilingual issues. If you’ve got a Drupal 6 or 7 multilingual site that you’re thinking about migrating to Drupal 8, now is a great time to get ahead-of-the-curve.

If you’re planning on attending and participating in the sprints, please be sure to sign up on the Sprint Attendance doc (find the “Migration testing” section). A number of the main contributors will be participating virtually, so we hope to make some good progress during this sprint.

DrupalCamp Atlanta

On Saturday, October 4, at DrupalCamp Atlanta, I’ll be leading another sprint that aims to kickstart new contributors into on-going roles in the Migrate in Core project. I’m planning on working with volunteers to get them up-to-speed with the overall migration system, and matching their skills up with current tasks including manual testing as well as testing and creating patches. I’ll also be presenting a session at the camp on the current status of Migrate in Core in Drupal 8 that should provide a good primer for those thinking about helping out.

Virtual Drupal 8 Migrate in Core Office Hours

I’m living proof that best intentions often go awry. Over the past several years, I’ve flirted with core contributions, but it wasn’t until I found a few nice folks to show me the ropes for the first few weeks that I was hooked. My goal is to repeat the process I went through for as many people as possible (hopefully with much fewer pain-points though!)

With that in mind, I’m happy to announce that starting Wednesday, September 24, I’ll be hosting virtual office hours for new Migrate in Core contributors. If you’re interested, please use the contact form or hit me up @ultimike to let me know and I’ll get you all the details. I’m planning on running it from 7-9pm EDT. Immediately following, at 9pm EDT on Wednesday evenings is the weekly Migrate in Core Google+ Hangout where we do a quick overview of the current state of the project.

Let’s Get This Done!

I’m planning on writing a series of blog posts to help new contributors compress the amount of time it takes them to have a good understanding of how the migration system works under-the-hood. Look for the first post next week.

The Migrate in Core project is destined to radically increase the adoption rate of Drupal 8, especially for Drupal 6 sites that are getting a bit long in the tooth. By getting some experience with it early, you’ll be in a great position to help existing and future clients in making the move to Drupal 8.

Photo by Mike Gifford

Trackback URL for this post:


Nov 06 2013
Nov 06

Executive summary

We want an accessibility testing green board for Drupal. Currently, the testing platform and tests are under development and progress is solid, thanks in major part to Kevin Miller (kevee). The tests register 257 failures currently, although some might be false positives and duplicates. We need developers, testers and reviewers to get us to robust test coverage and zero failed tests against Drupal 8 by 2014.

We’re calling this effort Green by 2014.

Please tag all issues with accessibility and Green by 2014.

Current efforts to improve accessibility in Drupal 8

The Drupal 8 development cycle has included concerted effort to improve the accessibility of administration features and content. But we’re not satisfied by uneven improvements. We want Drupal 8 to be the most accessible content management system in the world.

The accessibility module describes itself as “a common framework for checking accessibility of a webpage". It provides facilities to check content and code against standard accessibility guidelines.

This module and its tests are still under active development. We need developers to assist us in bringing these efforts to conclusion within the Drupal 8 development timeframe so that we can declare with conviction and evidence that Drupal 8 meets Section 508 and WCAG AA standards.

Update the Accessibility module code to be compatible with the latest D8 HEAD APIs

Drupal 8 HEAD, although largely stable, still undergoes occasional pattern and API changes. Given this reality, we need to spend time updating the Accessibility module’s 8.x branch to keep up with these changes. Our effort to get to a automated testing green board must start with updating the Accessibility module so that testers can run it locally.

We need individuals who are familiar with Drupal 8 module development in order to advance development of the accessibility module. These folks will:

  1. If you can, propose patches to resolve them.
  2. Patch reviewers. Please follow issues that you can contribute to!
  3. Please tag your issues with Green by 2014.

Making Drupal more accessible

The Accessibility module helps us identify where Drupal’s access support falls below that of Section 508 and WCAG standards.

This testing tool runs many tens of tests across numerous pages of a Drupal installation. You can either run the tool locally through the Accessibility module or view the daily run at Drupal Accessibility Status (beta).

The tool is not perfect yet, though. Some tests return false positives, meaning that an identified issue is not really an issue. In this case, we need to adjust the test to remove the false positive. For legitimate test failures, we must log an issue against Drupal core and propose a patch to fix the issue.

Logging accessibility issues against Drupal core

In cases of an actual accessibility issue, we must first create an issue to describe it and then address that issue with a patch. The Accessibility module reports issues in a table layout. The test name, theme hook, theme item (function or template) and and output markup are provided. I’ve given one example here in a list format.

  • Test: Text has appropriate contrast
  • Theme hook: page
  • Theme item: core/themes/bartik/templates/page.html.twig
  • Element:

mgifford gives us a great example of a focused issue that arose from the automated tests and anandps provides a patch to review.

In this issue, mgifford gives us a reference to the failed test, the specific code that’s failing and a possible path for a solution.

Text has appropriate contrast
page: core/themes/bartik/templates/page.html.twig

<div class=\section clearfix\></div>
<div id=\name-and-slogan\></div>

Does have color contrast problems according to this new Chrome Color Contrast plugin.

In your issues, you are not expected to provide a solution. Simply logging the issues gives us a great start to addressing it.

Drupal already has great issue documenting guidelines in how to create a good issue report. Please follow those guidelines when creating a report.

Please tag your issues with accessibility and Green by 2014.

False positives

The automated testing tool might report an error that occurs becuase of a poorly written test, not because we have an issue with Drupal core code. This is a false positive failure. Most likely the parameters of the test need to be adjusted. You should always first consider, when addressing a test failure, if the test might be at fault if you find in your investigation that the Drupal output passes your manual testing.

False positives must be fixed in the QUAIL project directly on Github. To address them, take the following steps (as far as you are able).

  1. Tag the issue false positive and Green by 2014.
  2. If you can, propose a patch to resolve it.

Documenting our coverage

It’s well and good to have great test coverage, but we need to communicate that coverage to the outside world. Specifically if we are to make claims of conformance, we must be very sure that our tests convey conformance.

That requires us to correlate our existing tests to sections of the specification and explain how the test satisfies that section. The current state of correlations is documented in the Test guideline alignment.

Send a pull request to update any of the documentation in the QUAIL github repo.

Verification tools

You might try the following browser tools, among numerous others, when verifying accessibility tests.

Please help out!

We intend to make Drupal 8 the most accessible content authoring and management tool ever. And we intend to make that claim verifiable in part through robust and wide automated testing coverage. We need your skills, dedication and compassion to make it a reality!

Dec 20 2012
Dec 20

No votes yet

This weekend I participated in the Brevard Code Sprint for the MediaFront Module. I must admit, being new to Drupal, it did cross my mind that I’d be more of a hinderance than a help. I couldn’t have been more mistaken! The dozen folks from the Drupal community were great to work with. To start us off, Travis Tidwell (travist), the MediaFront module maintainer, walked us through a demonstration of the module and Mike Anello (ultimike), of the code sprint sponsor DrupalEasy, facilitated the group in choosing assignments to work on. As he asked for volunteers to work on some novice code issues, I figured “No better time to learn, than when surrounded with help!” so I dove right in. With the help of some great new friends, at the end of the day I had created my first patch and was well on my way to my first commit!

We discussed some problems that the module was having and created the issue to Hide the full-screen button when they have controller only mode enabled. Since a picture is worth a thousand words, I’ll just show ya... it looked like this:

controller bar with fullscreen

In working on fixing the problem we came up with a fix, but then realized the fix corrected the problem but left the look of the item needing reformatted because it just made a big space where the button was ... another chance to learn! I got some new GIT experience creating the patch, which fixed the problem and made the item look good. Making that contribution, encouraged me to look for other coding issues that I would never had even thought about attempting before going to this code sprint. I know you’re wondering so I’ll show you the fix:

If you are new to Drupal and trying to learn it on your own, I can’t encourage you enough to seek out these code sprints, DrupalCamps or DrupalCon community events no matter what your experience level. Everyone was so willing to answer any question I had or point me in the right direction to get over my hurdle. At times there were two of us side-by side working on one screen figuring out the best way to tackle an issue and there were times they let me do it on my own to learn at my own pace. In that one day I feel so much more confident in my Drupal understanding and much more comfortable asking for help. I’ve started some new relationships and strengthened some other ones.

Trackback URL for this post:


Jun 04 2012
Jun 04

After a full day of sessions and learning about Drupal, Saturday June 23rd from 10 am to 5 pm will be the third Get Involved with Core Sprint. (Previous sprints were held at DrupalCon Denver and DrupalCamp Twin Cities). The sprint will be hosted at Zivtech (the same location as the previous night's after-party).

If you want to contribute to Drupal core but aren't sure where to start, this is your chance to get in-person training and mentoring from friendly, experienced core contributors. If you've already started to work on core, this is your chance to meet other contributors, hang out in person, and work on manageable tasks in the Drupal core queue. The goal is to help you help with core.

Time & Location:

We'll start sprinting at 10 am (feel free to show up anytime after 9:30) and continue until 5 pm.

The Philadelphia Building
1315 Walnut St, Suite 1500
Philadelphia PA 19107
Map: http://goo.gl/maps/HSBs

What to expect

We'll kick things off at 10am with an introduction and some training, and then start sprinting on core issues. Feel free to either drop by and work on just a couple tasks, or to stay and sprint with us all day! We will help match people with issues that are right for their skill levels and areas of interest.

What to bring

  1. An interest in Drupal contribution
  2. A laptop


You can save time at the sprint by configuring your development environment in advance with the following:

  1. A local web server. We suggest the Acquia Dev Desktop for an easy point-and-click installer on Mac and Windows. Alternately, see the following videos for help setting up your development environment:
  2. A code-friendly text editor. (Sublime Text 2 is a free and cross-platform editor.)

If you run into any problems trying to install anything above, don't worry! We will help you configure your environment during the sprint.

Already a battle-hardened contributor?

There's plenty you can do to help! We could use assistance from people that already know the ropes. Have Drupal 8 running? Know how to apply a patch with Git? Great! You're already one step ahead of three other people. If you want to help we would love your assistance and can pair you up with others that need help learning how to apply a patch, locating documentation, or doing their first patch review. Just let us know what you're interested in doing.

Sprint mentors

May 25 2012
May 25

Come join Zivtech and the rest of the Philadelphia Drupal community on June 22-23, for two action packed days of good programing, great beer/food/code, and even better people!

Drupaldelphia-being held at Alter Hall at theTemple University Fox School of Business- is the annual Philadelphia Drupal Camp, and June 22 will mark its fifth year! We're expecting 300 people and 25 sessions covering all sorts of awesome Drupal topics. Session submissions are still open- but they close June 8, so submit a session soon!!! We're also looking for sponsors- shoot Andrew Wilson ([email protected]) an e-mail if you're interested. All Drupaldelphia tickets come with lunch, as well as an awesome t-shirt, designed by Zivtech's Sean Wolfe.

After Drupaldelphia, we hope you'll join us at our amazing new office for the Drupaldelphia After / Zivtech Office Opening Party Jawn. We'll be starting around 5pm, will have tons of great food and drinks, and will be talking tech and shooting the breeze from our 15th floor suite. Please RSVP so we can leave your name with security and order enough food.

Recently, we were extremely excited to read the news about Views moving into Drupal core (including our own tim.plunkett taking a leadership role in the effort), and we are just as excited to announce Earl Miles as keynote speaker at Drupaldelphia this year! In addition to the keynote, on Saturday, June 23 Earl, Tim, xjm, and a bunch of other awesome people are organizing a Drupal core code sprint at the Zivtech office. If you're interested in being awesome, and learning how to contribute to Drupal core, then this code sprint is for you! Keep an eye out for more information in the next week!

We hope to see you in Philly! We love our city and want you to love it too, so plan your trip and we'll look forward to welcoming you to Philadelphia!

May 14 2012
May 14

There's a new initiative in the wind to upgrade our own Drupal.org site to version 7, and look out, its flying on its own!

Yes, it's been a long time desire ever since Drupal 7 launched, but the momentum and prowess of our amazing community is finally magnetizing into action around the Upgrading Drupal.org to Drupal 7 initiative! It started with a fantastic planning and coding sprint in Portland, OR last month. (see the video) We are now full speed ahead in virtual space and IRC and the issue queues.

It will still take several months of concerted effort by a dedicated team of volunteers to make this transition a successful, safe, and powerful one. Our goal is to launch the new D7 site before the upcoming DrupalCon Munich, and if all goes well and we continue to see an influx of interested helpers (see below on how to help), we'll make that goal!

Our goal is to launch the new D7 site before the upcoming DrupalCon Munich, and if all goes well and we continue to see an influx of interested helpers (see below on how to help), we'll make that goal!

The upgrade to D7 is mostly a 1-to-1 port of existing functionality and we must be careful not to over-engineer, but since Drupal 7 provides so much more in terms of entities, fields, database, and performance improvements, during this upgrade we will gain:

    • Underlying plumbing to support additional functionality after the upgrade, such as better Git sandbox and issue queue integration, as well as project ratings, stats, and reviews.
    • A re-engineered issue queue and project releases system which will be a more broadly useful solution to sites other than Drupal.org, and with less custom code it will be easier to maintain and contribute to this new system in terms of community collaborative needs.
    • A mobile-friendly, HTML5 version of the Drupal.org theme.
    • Increased security for user passwords.
    • A suite of automated behavoir-driven tests to help ensure that Drupal.org stays functional throughout the upgrade process, and during future improvements.
    • Automated performance testing for Drupal.org’s web properties in order to isolate and resolve performance regressions.
    • Numerous "under the hood" improvements to Drupal.org's infrastructure to make it more self-sustainable, easier to maintain, and performant.
    • Dozens of upstream performance and bug fix contributions to Drupal core and other dependent modules which help the community with their upgrade paths.

And of course as we move ahead to D7 we are being careful not to lose all of the improvements that have been instilled into our site by previous initiatives and the sweat equity of hundreds of expert volunteers. We’ll also be eating our own dog food by making sure that our core and contrib upgrade paths via update.php work as advertised.

Let's not let the momentum die. Will you help us by either volunteering or convincing your company to sponsor-teer you?  There may even be one more all-hands sprint coming up in Portland for any contributors who can make it.

How To Help

Stop by our Drupal.org Office Hours every Monday from 11am - 12pm Pacific (18:00 - 19:00 UTC) in the #drupal-infrastructure IRC channel and ask for ‘Senpai’ or ‘tvn’. You can also follow @drupal_org on Twitter to volunteer your services!

Oct 19 2011
Oct 19

Technological leadership

Active in product innovation and open source software services, we build lasting value for our customers and the Drupal community.

Empowering relationships

Caring about clients and the outcome of their projects, we get involved and make meaningful relationships that give our customers maximum independence.

Community engagement

Dedicated to fostering the Drupal open source community, we catalyze event and development initiatives, resulting in real change and growth.

Sep 30 2011
Sep 30

This September, to kick off Drupal Camp Montreal 2011, the Montreal Drupal community held our first large-scale Drupal code sprint. The sprint was held from September 14-16 at Notman House and carried on at the camp until September 18th. The sprint was spearheaded by Gábor Hojtsy who is leading the Drupal 8 Multilingual intiative. Francesco Placella, who has contributed to Drupal 7’s field translation API as well as the Entity Translation module, was also a key contributor.

In Quebec, support for multilingual websites is extremely important as most projects include some type of multilingual user interface and content. Holding a code sprint for the multilingual initiative was a perfect opportunity for our community to contribute to Drupal. Overall, there were over 15 contributors who attended the code sprint including developers, UX designers, site builders, and new-comers to Drupal. Our whole team participated in the sprint and three of our developers attended all five days of the sprint.

The code sprint covered a lot of ground, including documentation, UX improvements, and patches to Drupal core and the Entity Translation module. UX improvements were proposed for installing new languages and configuring languages in Drupal. Core development was done to improve how various Drupal APIs handle language. Since most Drupal developers don't have experience with multilingual, this is key to improving Drupal's overall multilingual support. For an overview of all the progress made, read Gábor’s summary of the sprint or watch his presentation from the camp on the Drupal 8 Multilingual initiative. Here’s a summary of our contributions:


Logan Smyth worked on creating new functions for managing multilingual field items (http://drupal.org/node/1260640), adding support for Javascript versions of t and formatPlural (http://drupal.org/node/488496), moving the language domain and prefix settings to the language negotiation configuration page (http://drupal.org/node/1280530), and creating a new API for managing Locale source and target strings (http://drupal.org/node/361597).

Tavish Armstrong worked on language handling in the form API (http://drupal.org/node/1280996), the API for deleting languages (http://drupal.org/node/1260528), and compatibility between Node Clone and Entity Translation (http://drupal.org/node/1230858).

Thomas Getgood, our newest developer, worked on a patch to enable bulk field language updates when switching field translatability for the Entity Translation module (http://drupal.org/node/1279372).


Suzanne Kennedy, our front-end developer, worked on multilingual documentation with Sylvain Aube of Whisky Echo Bravo. Together, they cleaned up the existing documentation and added pages on Entity Translation (http://drupal.org/node/1280632). They also pushed to make the Drupal multilingual documentation guide a top-level handbook on drupal.org, which it now is. You can learn more about the Entity Translation module and how it compares to Content Translation from Suzanne’s presentation at DrupalCamp Montreal.

Thank You!

The sprint was a huge success, and a great milestone for the Montreal Drupal community. In addition to learning more about the multilingual intiative and how languages are handled in Drupal 7 and 8, we learnt a lot about contributing to Drupal, issue queue management using IRC, and how to write tests. Thanks to Francesco and Gábor for making the trip to Montreal from across the Atlantic! Thanks to Notman House for providing the venue for the first three days of the sprint, and McGill for hosting the camp and sprint over the weekend. The Drupal Association also provided us a community cultivation grant, which paid for Francesco's flight from Italy and Acquia flew in Gábor Hojtsy from Hungary as part of their sponsorship of the camp.

We’re looking forward to helping organize another sprint in Montreal in the near future!

Jan 25 2011
Jan 25

Technological leadership

Active in product innovation and open source software services, we build lasting value for our customers and the Drupal community.

Empowering relationships

Caring about clients and the outcome of their projects, we get involved and make meaningful relationships that give our customers maximum independence.

Community engagement

Dedicated to fostering the Drupal open source community, we catalyze event and development initiatives, resulting in real change and growth.

Sep 14 2010
Sep 14

A few weeks ago, I embarked on my first overseas trip to go to Copenhagen for this year's European DrupalCon. It was my 4th DrupalCon to date, but I've been wanting to attend one of the European ones for a while, as they have a reputation for having a different vibe than the North American ones (and of course so I could finally see some of Europe!)

The Core Dev Summit (+ Code Sprint Day)

Like the last conference in San Francisco, it was prefaced with the Core Developer Summit, which is a full day of presentations, discussions, and code sprinting on the core Drupal platform. The Core Dev Summit is the single day (twice a year at this point), where a good number of the people who work on Drupal core come together to take a step back and discuss in-depth any ideas or concerns. This often leads into some dedicated sprinting on core related issues (as well as some of the most crucial contributed modules).

I attended mainly for two purposes: to keep on top of what all the core developers are up to and get some face time with them (since I usually only talk to them online), and to make sure there was some representation from the Drupal Docs team there.

I've been working on the online Drupal documentation a lot lately, helping to prepare the it for the Drupal 7 launch, and ended up leading an impromptu docs sprint when several people volunteered to work on the handbook for the second half of the day. It was great to get some help from both people who were new to docs as well as a couple fairly hardcore long time developers. Big thanks go to Djun Kim (aka. puregin) for working on the handbook page for the new-to-Drupal-7 File module, and to Ken Rickard (aka. agentrickard) for working on the new-to-Drupal-core Field and Field UI handbook pages. It was fantastic having help from some great developers writing these, and Ken actually found a pretty big permissions bug while writing the page.

...when you write documentation, you are forced to take a bit of code and really understand it. You [read] through it, make sure it does what you're saying it does, and test it. Guess what happens when you dig into code that deeply? You find bugs!

And because it's so encouraging (and true), I have to add this other bit he posted:

If you are interested in getting involved in core, working the docs queue is the single best way to do it. You find bugs other people miss, the patches are generally easy to get committed, you get used to the issue queue and creating patches, and best of all the patches are enormously valuable. Get to it!

(Off-but-on-topic, Angie Byron, aka. webchick, just put up a great post on contributing documentation on the Lullabot blog today, go read!)

Neil Drumm (aka. drumm) who works on the API docs and is currently helping manage the Drupal.org redesign was there as well, so I got to review some of the docs.drupal.org in-progress redesign with him. The redesign team has been doing a fantastic job, and I'm really looking forward to the relaunch and some of the freedom that will be afforded by having a separate subdomain for documentation.

I was also really pleased to get the opportunity to participate in a discussion about the CVS application process, which was has been a hot topic recently. Sam Boyer (sdboyer), who is working on the Drupal git migration, led a discussion to get feedback from many long time core contributors. Mainly, we talked about what is still broken in the process, what needs to change, and what small but effective changes could be made during the git migration to help improve matters. Main suggestions focused around ideas about how to manage namespace and numbers of modules, how to mentor new applicants, and the need to recruit more reviewers.

The post-conference Code and Docs Sprint Day was also extremely productive even though I was feeling a bit off and had to lead the docs sprint from back at the apartment! We did a kickoff over Skype then worked over IRC the rest of the day, and powered through a TON more of the core module handbook docs and some work on the install and upgrade guides. I really missed not being able to work in-person with everyone, but still want to thank all who turned up and cranked out some awesome docs work, namely: Steve Kessler (DenverDataMan), Alex Pott (alexpott), Barry Madore (bmadore), Marika Lundqvist (marikalu), Miro Scarfiotti (smiro2000), Paul Krischer (SqyD), Carolyn Kaminski (Carolyn), Khalid Jebbari (DjebbZ), and last but not least Boris Doesborg (batigolix) who I am really sad not to have met in person, as he worked a bunch with me on the D7 Help initiative over the winter. Next time! You all rock, hope to see you around the docs queue and IRC till the next con. 

The rest of DrupalCon...

I had to agree with what I'd heard about the European cons, as I did feel a lot more of a community vibe (probably due to the smaller size, being the same size as my first DrupalCon in Boston in 2008), and did not see a lot of the corporate aspects that have become part of the North American cons of late. Those are, of course, part of Drupal's growth, but they do change the atmosphere.

The sessions I went to were all really fantastic. I think my three favourites had to be:

  1. The Managing a Drupal Consulting Firm panel (video) - Todd Nienkerk and Aaron Stanush (Four Kitchens), Thomas Barregren (NodeOne), Vesa Palmu (Mearra), Matt Cheney (Chapter Three), Liza Kindred (Lullabot), Eric Gundersen (Development Seed), and Tiffany Farriss (Palantir) sharing stories and tips for how to be a successful and happy Drupal consulting firm. Great ideas, and bonus high comedic value!
  2. Jeff Miccolis' (jmiccolisFor Every Site a .make File - great review of .make files and associated development practices (couldn't find the video, if anyone knows where it is, comment please!)

And though I didn't attend it, Amitai Burstein's session on Group, which is the Drupal 7 iteration of Organic Groups (video) was the crowd favourite, and highly recommended as one to watch online.

What else can I say? It was a fantastic week with a bunch of fantastic people. As @timbertrand put it:

"Dear Proprietary Social SW Vendor -
this is only a taste of our development team"

See you next time!

Dec 09 2008
Dec 09

Following on the Data Architecture Design Sprint during a cold and snowy Chicago week in February, two Drupalcon presentations, a lot of writing, and even more debating, I am really looking forward to next week's Fields in Core code sprint. Our goal is to re-organize Drupal's content APIs and data storage around Fields instead of Nodes; think of it as "CCK in core, except for the admin UI." When the dust settles, everything will continue work just as it does now, but we will have a framework in place to allow Drupal and the community to get maximum leverage from what it is best at: Adding Value to Content.

We are assembling a team of six experienced Drupal developers at the Acquia offices in Andover MA: Yves Chedemois, Károly Négyesi, Karen Stevenson, David Strauss, Moshe Weitzman, and myself, and Dries Buytaert will be on site and participating as well. We will be tracking our progress at the Fields in Core group and expect to have plenty of tasks for virtual attendees to help with.

I'd like to particularly call attention to the fact that Yves, Karen, and Moshe are donating their personal time for this sprint. Also, NowPublic, Four Kitchens, and Acquia are donating their employees' time. Since four of the attendees need to fly in and stay in hotels, we're trying to raise $7,000 to cover the costs and maybe a nice dinner out for everyone as well. That works out to $25 per hour that these developers will be working on your favorite CMS. So, please consider making a donation. :-)

About Drupal Sun

Drupal Sun is an Evolving Web project. It allows you to:

  • Do full-text search on all the articles in Drupal Planet (thanks to Apache Solr)
  • Facet based on tags, author, or feed
  • Flip through articles quickly (with j/k or arrow keys) to find what you're interested in
  • View the entire article text inline, or in the context of the site where it was created

See the blog post at Evolving Web

Evolving Web