Open Curriculum: Definitions – Scenarios – Roadmap – Skill sets – Open certification – References - Roles
Join the upcoming IRC meeting! Follow discussions here on g.d.o, on IRC at #drupal-skillmap, or on Twitter with the tag #drupalskillmap!
To help develop an open curriculum, the first stage is to lay a common ground for discussion. One step in the common ground is to identify some of the key roles in Drupal Development.
See the notes from the related discussion on 10 May 2010, Learning Drupal chat on IRC. Attendees: Ryan Price (DrupalEasy); Barry Madore (Advantage Labs); Richard Patee (Victoria School of Business and Technology); Emma Jane Hogbin, Author; Gus Austin (Open Learning); Doug Vann, Trainer; Lynn Bender (Drupal Austin User Group); Eric_sea.
List of roles
Note regarding context: we recognize on many projects a person might take on some or even all of these roles. We're using the redesign of Drupal.org as the context for the associated roles. It's a larger project, therefore with greater differentiation in the roles. Therefore, helping to guide the discussion.
Note regarding tasks: the descriptions in the roles mentioned here are not exhaustive. We're mainly focusing on the names of the roles. The descriptions are for clarification.
The next step is to undertake a more detailed task analysis, with the community. So no worries, we'll get to it. The first thing we need to do is ensure we're on the same page with roles.
* System Architect
This person sets up and maintains the system and infrastructure on which Drupal is deployed. They can manage the migration of data and content. They also install and maintain access to the site and version control. An example: http://groups.drupal.org/node/66638
This person can code custom modules according to coding standards and best practices. They can test the quality and security of the code they write.
An example: http://groups.drupal.org/node/66643
* Themer, Front-end developer
* Site Builder
This person installs and configures modules to create site features. They will be knowledgeable about theming and development, but will mostly use Drupal through the administrative interface.
* Content Editor & Manager
This person manages content and users on a Drupal site. They may not know many of the advanced functionality of the Drupal Administrative interface.
* Design, UX
* Project Manager/Planner
This person negotiates project plans with clients based on the understanding of the capabilities of Drupal. They understand best practices and can communicate client needs in the language of Drupal to the team.
* Drupal Marketer
This person is knowledgeable about Drupal's capabilities and applications and can communicate them to clients and other audiences in ways best suited and understood by the client or audience.