drupal workgroup: how oit helps make the gt web community even more awesome!

Post on 29-Nov-2014

122 Views

Category:

Education

3 Downloads

Preview:

Click to see full reader

DESCRIPTION

 

TRANSCRIPT

Drupal Workgroup

2014 June 17

OIT PMR groupAtlanta, GA

How OIT helps make

the GT web community

even MORE awesome!

2

What the heck is Drupal?What the heck is Drupal?

Hi, I’m drupal

I make websites …

with help from the

GT community!

3

History of GT Drupal group (abbreviated)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

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

5

Total Emails on Listserv (Chart)Total Emails on Listserv (Chart)

6

Active Participants on Listserv (Chart)Active Participants on Listserv (Chart)

7

Strengths of Drupal @ GTStrengths 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

Opportunities for Drupal @ GTOpportunities 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

Questions…Questions…

top related