| | 1 | [https://docs.google.com/spreadsheet/ccc?key=0An7ZaZdq6UfJdEQ4eXhnenVGbEZPdURCWXhENElQUEE#gid=0 Google doc to manage tasks for Developer] |
| | 2 | |
| | 3 | [https://tech.transitionnetwork.org/trac/ticket/667 Handover ticket to track time] |
| | 4 | |
| | 5 | Skills and experience required for new developer |
| | 6 | |
| | 7 | Essential |
| | 8 | * Strong developer experience of both Drupal 6 and 7, with a track record of maintaining, updating and providing technical support for established Drupal sites. |
| | 9 | * Well acquainted with the Drupal APIs and ecosystem -- must have written own modules. |
| | 10 | * Understanding of Drupal coding best practices. |
| | 11 | * Worked with - and coded for - the usual Drupal biggies: Views, Panels, Features, Rules. |
| | 12 | * Strong PHP and JavaScript/jQuery skills. |
| | 13 | * Must know how to use Drush and Git to a good level. |
| | 14 | * Exposure to developing for the CTools APIs and functions, especially plugin system and Panels. |
| | 15 | * Strong debugging/problem solving skills. |
| | 16 | * Personable, flexible and open minded. |
| | 17 | Beneficial |
| | 18 | * Experience of Aegir hosting system, especially Barracuda variant. |
| | 19 | * A background in theme building, and using theme() functions. |
| | 20 | * Understanding of Linux hosting environments and server tools. |
| | 21 | * Use of MySQL databases, and query building. |
| | 22 | * An understanding of when a new module is needed, vs configuration changes, vs coding. |
| | 23 | * Experience of being workload being managed remotely (Email, Skype, Hangouts) and via issue trackers. |
