webchick.net

very helpful lioness

drupal

Drupal core committer takes Acquia Certification exam. You won't believe what happens next!

Mon, 03/24/2014 - 13:43 -- webchick

TL;DR I passed. :P Here's a run-down of what the experience was like.

Up-front disclaimer: I work for Acquia. However, I was not involved in the creation of Acquia Certification and had no insight to the test beforehand apart from a single sample question. I'm also writing this on my personal blog, rather than Acquia.com, because these are *my* thoughts/impressions, and haven't been vetted by anyone else. :) Carry on!

Heads up: Maternity leave starting next week

Sun, 04/28/2013 - 18:19 -- webchick

(Sorry for spamming Drupal Planet with this, but a few people on IRC were saying it might be a good idea for people to get a wider heads-up, given the number of Drupal community hats I wear.)

In a week, we're heading down to Minnesota to pick up our new addition to the family, and so starting May 6 I'll be on maternity leave for 3 months, until ~August 1 (thank you, Acquia!!).

Here's an outline of how that may or may not affect you, and who to talk to instead:

Step-by-step: Converting modules from Drupal 7 to Drupal 8

Fri, 02/08/2013 - 01:55 -- webchick

As Gábor pointed out, now's the time to help make Drupal 8 more unified and user/developer friendly. A great way to do that is try porting your modules, now, while there's still time to fix the APIs before code freeze.

Here's the video and slides from my Upgrading your modules to Drupal 8 talk at DrupalCon Sydney 2013, featuring the Pants module.

Slides: PDF | PPT | KEY (the canonical version)

But wait, there's more! ;)

The story of my first DrupalCon

Sun, 02/03/2013 - 22:16 -- webchick

This was originally posted to the "The influence of subtlety" thread on the Drupalchix group back in 2010, but since that was awhile ago now, and since I'm giving a talk on How to Create Ravenously Passionate Contributors at DrupalCon Sydney (and this experience played a huge part) I figured I'd post this to Drupal Planet as well.

Here are some highlights from my first DrupalCon (Vancouver, 2006).

Want to help improve Drupal.org at DrupalCon?

Tue, 08/21/2012 - 17:30 -- webchick

Join Tatiana / tvn, Drupal.org Project Coordinator, for a series of BoFs on major new features for Drupal.org and how you can help!

Wednesday

13:00-14:00 Drupal.org office hours BOF
http://munich2012.drupal.org/content/drupalorg-office-hours

Come meet the Drupal.org team and learn more about how you can help make awesome changes to Drupal.org!

One Drupal 8 Slide Deck To Rule Them All - Please give this at your local event!

Sat, 06/02/2012 - 18:16 -- webchick

Greetings, Drupal Planet!

Here are the slides from my DrupalCamp Vancouver "hook_future_alter()" talk. This outlines the major changes currently in development for Drupal 8, how Drupal 8 will impact end users, site builders, designers, and developers, and how to jump in and help!

Hit-list for top Drupal 7 module stabilization

Fri, 11/11/2011 - 00:27 -- webchick

Back in September, http://drupalcontribstatus.com/ was launched to track the porting status of the top 60 contributed projects to Drupal 7. Since then, we've whittled the list down to just 20 projects remaining, as well as tons of progress on the rest! YEAH!

I contacted each of the maintainer(s) of those remaining projects and have come up with a list of next steps for each. Your help is needed if we want to get that graph up to 100% by year's end. (Just in time for Drupal 7's first birthday! :))

As a general rule, help is needed in the following areas:

  • Issue queue triage (Difficulty: Novice): Going through the issue queues of these modules and doing things like closing duplicate reports, verifying that bug reports are valid, and so on. None of this is particularly difficult work, but time that maintainers have to spend doing it is time they can NOT spend porting their modules to Drupal 7.
  • Reviewing patches (Difficulty: Intermediate): Going through the issues in the queue marked "needs review" and making sure patches still apply, then testing to make sure that they still work, then reporting on the results of your testing are all critical things that really help save maintainers time, and ensure that any actionable issues are escalated to their attention.
  • Experience in various core sub-systems (Difficulty: Intermediate to Advanced): If you know how to write automated tests, are familiar with how the render API works, can answer questions about the new Field API or File API, there are several issues identified that could use YOUR help! Note that you don't necessarily need to be in MAINTAINERS.txt to provide this help, either; if you've already started building Drupal 7 sites and modules, you likely know enough to be helpful!
  • Co-maintainership (Difficulty: Intermediate) Many of these projects are seeking co-maintainers. If you or your business/customers depend on any of these modules, investing solid time in the issue queue to help review and roll patches for issues in need would be of tremendous benefit, and would help position yourself to ask for commit rights so that you can ensure these modules stay solid going forward.
  • JavaScript knowledge! (Difficulty: Intermediate to Advanced) Seriously. We are, generally speaking, a bunch of PHP nerds. If you know JavaScript, you can be helpful on a number of different (and important) fronts.

So, without further ado, here are some specifics on how you can help Drupal 7, and the maintainers whose code you rely on!

Pages

Subscribe to RSS - drupal