Reading the Drupal Ladder

Events happening in the community are now at Drupal community events on www.drupal.org.
kwattro's picture

Hello,

We organize next saturday a learn sprint in belgium at the BrainDUG meeting.

I've read the ladder till the "Write tests" chapter and I have some suggestions / remarks for helping organizers .

  1. Getting started in the issue queue

I think this chapter go too fast comparing on the two next ones, people have to directly submit an issue. If think regarding the name of the chapter, it could be the place to explain how is organized the Drupal issue list, what are the meaning of the different status, prios, ... Explain what is shown when we choose an issue page.

This can require the creation of two new chapters "report an issue" and "confirm issues/bugs reports" .

  1. Test patches

The 4 git commands have a better place in the end of the "install git" chapter. People that come in the "test patches" chapter, reading the chapter name they become hot and gonna say, yeah we gonna see a patch, see code, doing something cool ( testing patches ! ) but the first step they have to do is again configuring git. Deception !

On the point 9 of the "test patches" chapter, it mention "you would now post a comment saying you have applied and tested the patch". I think it would be better to guide the learners to do it, with screenshots of the process. Why not creating real bugs on the Learn distribution ?

  1. Writing patches

Point .10 : "now wait for the testbot to test you patch..."

Imho a little explanation of the testbot and the possible return values could be useful, some people are visual, so seeing screenshots with comparison red/green returns from the bot will please these people.

  1. Join an issue team

People feel, WOW, we gonna integrate a team to solve issues together. They think they will discover supra-cool team names like "awesome-boston-drupalians" and they open the spreadsheet, damned, looks empty, unreadable, no team names only user names 1 & 2 .

To be honest I thank it first, and I'm still a bit in doubt about the real purpose of the teams chapters.

-> Teams means pairs ?
-> Does a local UG have to create their own spreadsheet ? If well it could be nice to present a blank template ?

Mmh I think I've done, this is only my personal advice before a learn sprint .

Now two more questions :

-> As the learndrupal.org is not yet multilingual, can I start a new ladder for french speaking people on the learndrupal.org site ?
-> When will v1.0 be released, I intend to maybe give a talk about learndrupal.org at the DrupalCamp in Belgium on 26 may but I think the site is not reflecting the eagerness of the volounteers working on it and it can not call the wanted effect to the audience.

Regards,

Christophe

Comments

Good post and suggestions

techgirlgeek's picture

I'm not sure who updates the current lessons, I've just been encouraging people to comment on lessons directly and hoping some of the suggestions get incorporated soon.

As for creating a new French ladder, I don't think there would be a problem with it. AFAIK, we are encouraged to build our own ladders as we see fit.

Re: teams, I think that is teams of 1 or 2 people. That probably needs more explanation/clarification.

Re: spreadsheet, We've created our own google doc for Colorado. You can copy the blank one, headers, etc. to create your own.

Hope this helps a little.
Welcome to the fun,
Karyn
(techgirlgeek)

Thanks for your reply

kwattro's picture

Thanks for your reply techgirlgeek.

Cheers,

Drupal Ladder

Group organizers

Group categories

Group notifications

This group offers an RSS feed. Or subscribe to these personalized, sitewide feeds: