This document summarizes the history and activities of the Georgia Tech Drupal Workgroup from 2009 to 2014. It discusses what Drupal is, provides an abbreviated history of the GT Drupal group including key events and leadership transitions, describes the group's website and participation levels, highlights strengths such as online collaboration and training opportunities, and identifies opportunities for the future such as additional training, improved code sharing, and leveraging resources. The document aims to showcase how the Office of Information Technology (OIT) helps make the GT web development community more effective with Drupal.

1. Drupal Workgroup
2014 June 17
OIT PMR groupAtlanta, GA
How OIT helps make
the GT web community
even MORE awesome!

2. 2
What the heck is Drupal?
Hi, I’m
drupal
I make websites …
with help from
the
GT community!

3. 3
History of GT Drupal group (abbreviated)
• 2009 Apr: Workgroup begins
• 2011 Nov: Adelle (@ OIT) facilitates liveliness & consistent mtgs.
• 2012 Jan: 1st
Official Feature (Calendar) by Inst. Comm.
• 2012 Apr: Prof. Educ. Kindly offers git repo for unofficial features.
• 2013 Feb: OIT Web Hosting guru’s presentation on Security
• 2013 Jul: 4 Unofficial Features (Script, Profile, Editor, SubTheme)!
• 2013 Sep: NEW Design (official) by Inst. Comm.
• 2013 Oct: Cutting-edge (beta, unofficial) SubTheme by Sciences.
• 2013 Nov-Dec: Leadership transitions (Benevolent dictatorship =>
Semi-official Committee from diff. Colleges/Units); TWO Build Days;
Update to Official Design coordinated with unofficial Editor feature.
• 2014 Jan: Dan/Chris @OIT help us WebEx meetings (microphone)
• 2014 Jun: Twice as many GT folks attend DrupalCon!! [estimate]

4. 4
Our Website (Drupal.gatech.edu)

5. 5
Total Emails on Listserv (Chart)

6. 6
Active Participants on Listserv (Chart)

7. 7
Strengths of Drupal @ GT
• Online communication/collaboration
– Any GT person can improve site
– Listserv ambiance & culture: fun,
open, helpful & friendly
– WebEx extends mtg. attendance
– Code sharing (git)
• Security gets “easier”
– GT Login vs. Spam
– Zero day patches
– Automate safer settings (GT Profile)
• Training
– Shared How To guides
– Build/Workshop days
– Conferences & Camps

8. 8
Opportunities for Drupal @ GT
• Consultant process ($ + project types)
• Ongoing Training (@ all levels)
– Editors (esp. accessibility!)
– Innovative Developers (symfony, git)
– Consistent Mtgs. & Build Days
• Code sharing (git + how to/process)
• Bottom-up PLUS Top-down
– Leverage scarce resources (~5%
time commitment from distributed)
– Funding + Space (esp. training)
• Larger communities (ADUG + USG)

9. 9
Questions…

10. 9
Questions…