[consulting] Drupal Certification and Requirements

[Liam McDermott]

paola.dimaio at gmail.com wrote:
>> If someone wants to be certified using my process just send me an
>> email. I'll be happy to do it ;)
>>
> I ll take you up on that. Will send you developers for 'validation', hehe
> thanks!
> PDM
As well as being a funny remark (if a little snarky), this is a good 
point. A couple of questions for PDM:

  1. Is this roughly the process you use for finding job candidates?
  2. Does it work well?
  3. Would it really help if someone did it for you?

Pretty much agree with Greg's ideas on using community contributions as 
a metric. The only problem with this approach is making sure a candidate 
has completed tasks (patched bugs, written modules, documentation etc.) 
that cover Drupal concepts and its API.

Catching cheats (if the tasks were standard) would mostly consist of a 
Google search, agreed that this wouldn't catch all of them though. 
Perhaps the best route is somewhere in-between standard tasks and 
contributions; some selection on the bug form to include it as a 
'certification task', and a list of Drupal concepts involved in 
completing it. Then a View where examinees can select tasks to pick-up 
and complete.

Certification could be a little like Google Summer of Code or GHOP, but 
with shiny awards.

Kind Regards,
Liam.