Posted on November 16, 2012 // Short URL

Climbing the Drupal Ladder

In this episode Addison Berry talks with Bryan Hirsch (bryanhirsch), Kay VanValkenburgh (kay_v), and Brock Boland (BrockBoland) about the Drupal Ladder, a community project to get more people involved in Drupal core, while also learning valuable skills for their Drupal work. What is it, what's the goal, and the whys and hows about jumping in are covered.

Podcast notes

Introduction to Omega 3.x video series
Drupal Global Training Days
Drupalize.Me "What is Drupal?" workshop (Dec. 14)
Drupal Ladder group discussion
Drupal Ladder distribution
Drupal Ladder IRC channel: #drupal-ladder
Core Mentoring
xjm's core presentation with some stats (from Aug 2011)

If you want to suggest ideas for podcasts, or have questions for us to answer on a podcast, let us know:
Contact us page



Technical Newbs Podcast?

Another great podcast, Addi. Thanks.

I've been developing in Drupal since 5.2 but only within the last couple of years have really gotten involved in contributing and trying to be more involved in the community. I know the docs are resource out there on this are plentiful but I would love to hear some Drupal experts talk about some of the finer points of collaboration and contributing such as how they got started and their current process now.

I don't have much free time, but I want to help with D8 and Drupal is the first collaborative system I've worked in, so removing the grey area around these points could be the push I need to dive in more quickly.

1. What's your process to create a patch? Submit a patch? Test a patch?

2. How/Does this process differ between Contrib and Core?

3. How big can patches get and how do you handle the big ones?

4. Can more than one person work on the same patch? If so, how do you handle conflicts?

5. What, exactly, do each of those statuses mean in the issue queue and who is responsible for changing the status of an issue?

6. What was/is your biggest challenge in collaborating on Drupal projects/issues/bugs/features?

7. How do you decide on a release state for a project (alpha, beta, rc)

...And I'm sure I could think of others. Just thought I would pose that as an eager developer with limited time. Thanks again for keeping these podcasts going.



Good questions!

These are definitely good questions. I'm going to work this up as another podcast. Perhaps a podcast dedicated to talking about blockers, and perceived blockers, for new contributors, and get some answers to those kinds of questions. Thanks for the questions, and the idea for a new podcast!