Drupal at Multnomah County
Building a Drupal Ecosystem for 

Public and Internal Websites

!
!
!
!
Presented by 

Joshua M...
The story so far
•

Key launches:

1. Public website (multco.us)
2. Intranet (commons.multco.us)

3. Apps platform (*.apps...
The story so far
•

Key launches:

1. Public website (multco.us)

2. Intranet (commons.multco.us)
3. Apps platform (*.apps...
The story so far
•

Key launches:

1. Public website (multco.us)

2. Intranet (commons.multco.us)

3. Apps platform (*.app...
Apps Platform
•

Aegir Multisite installation


•

Distributed development


•

Low cost of entry for an internal applicat...
The story so far
•

Key launches:

1. Public website (multco.us)

2. Intranet (commons.multco.us)

3. Apps platform (*.app...
The story so far
•

Key launches:

1. Public website (multco.us)

2. Intranet (commons.multco.us)

3. Apps platform (*.app...
The story so far
•

Key launches:

1. Public website (multco.us)

2. Intranet (commons.multco.us)

3. Apps platform (*.app...
Draft
What does it take?
What does it take, in an environment with no open source software or
expertise, to launch and support 1...
Executive Buy-in
•

It’s easier now… the White House
project made this conversation easier
to have with your CIO.

!

•

S...
Executive Buy-in
•

It’s easier now… the White House
project made this conversation easier
to have with your CIO.

!

•

S...
Innovate through pilot projects
Innovate through pilot projects

1. Ask for a pilot
Innovate through pilot projects

1. Ask for a pilot
2. Pick something that is winnable
Innovate through pilot projects

1. Ask for a pilot
2. Pick something that is winnable

3. Knock it out of the park
Innovate through pilot projects

1. Ask for a pilot
2. Pick something that is winnable

3. Knock it out of the park
4. Rep...
Hiring and/or building internal talent
Hiring and/or building internal talent
Should you hire or to train up your existing staff?
Hiring and/or building internal talent
Should you hire or to train up your existing staff?

Do both!
Hiring and/or building internal talent
Should you hire or to train up your existing staff?

Do both!
•

Find Drupal partner...
Code deployment
•

Get as much of your build as possible into code. 


•

Get your code in source control—preferably Git.
...
Git workflow
Pull from master to multiple dev branches. When code is pushed (committed) to master, it goes to our QAT/
inte...
Change management
Change management
γνῶθι σεαυτόν (Greek for “know thyself”)
Change management
γνῶθι σεαυτόν (Greek for “know thyself”)
•

Your customers need to know what you plan to do—even if you ...
Drupal at Multnomah County // Questions

Questions?
Story of Multnomah County: Migrating from Vignette and Building a Drupal Ecosystem
Story of Multnomah County: Migrating from Vignette and Building a Drupal Ecosystem
Story of Multnomah County: Migrating from Vignette and Building a Drupal Ecosystem
Story of Multnomah County: Migrating from Vignette and Building a Drupal Ecosystem
Upcoming SlideShare
Loading in …5
×

Story of Multnomah County: Migrating from Vignette and Building a Drupal Ecosystem

876 views

Published on

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
876
On SlideShare
0
From Embeds
0
Number of Embeds
11
Actions
Shares
0
Downloads
3
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Story of Multnomah County: Migrating from Vignette and Building a Drupal Ecosystem

  1. 1. Drupal at Multnomah County Building a Drupal Ecosystem for 
 Public and Internal Websites ! ! ! ! Presented by 
 Joshua Mitchell
 IT Enterprise/Web Application 
 Services Manager
  2. 2. The story so far • Key launches: 1. Public website (multco.us) 2. Intranet (commons.multco.us) 3. Apps platform (*.apps.multco.us) 4. Library (multcolib.org 5. Animal Services (multcopets.org) ! Now it’s time for upgrades
  3. 3. The story so far • Key launches: 1. Public website (multco.us) 2. Intranet (commons.multco.us) 3. Apps platform (*.apps.multco.us) 4. Library (multcolib.org) 5. Animal Services (multcopets.org) Now it’s time for upgrades
  4. 4. The story so far • Key launches: 1. Public website (multco.us) 2. Intranet (commons.multco.us) 3. Apps platform (*.apps.multco.us) 4. Library (multcolib.org) 5. Animal Services (multcopets.org) Now it’s time for upgrades
  5. 5. Apps Platform • Aegir Multisite installation • Distributed development • Low cost of entry for an internal application • Includes a couple external applications
  6. 6. The story so far • Key launches: 1. Public website (multco.us) 2. Intranet (commons.multco.us) 3. Apps platform (*.apps.multco.us) 4. Library (multcolib.org) 5. Animal Services (multcopets.org) Now it’s time for upgrades
  7. 7. The story so far • Key launches: 1. Public website (multco.us) 2. Intranet (commons.multco.us) 3. Apps platform (*.apps.multco.us) 4. Library (multcolib.org) 5. Animal Services (multcopets.org) Now it’s time for upgrades
  8. 8. The story so far • Key launches: 1. Public website (multco.us) 2. Intranet (commons.multco.us) 3. Apps platform (*.apps.multco.us) 4. Library (multcolib.org) 5. Animal Services (multcopets.org) Now it’s time for upgrades
  9. 9. Draft
  10. 10. What does it take? What does it take, in an environment with no open source software or expertise, to launch and support 15 Drupal production Drupal sites in 3.5 years? • Executive buy in • Rapid innovation through piloting • Hiring and/or building internal talent • Code deployment and change management
  11. 11. Executive Buy-in • It’s easier now… the White House project made this conversation easier to have with your CIO. ! • Show the lower cost of licensing • Highlight the big wins by other organizations • Talk up the rapid innovation that is triggered by contributed modules
  12. 12. Executive Buy-in • It’s easier now… the White House project made this conversation easier to have with your CIO. ! • Show the lower cost of licensing • Highlight the big wins by other organizations • Talk up the rapid innovation that is triggered by contributed modules
  13. 13. Innovate through pilot projects
  14. 14. Innovate through pilot projects 1. Ask for a pilot
  15. 15. Innovate through pilot projects 1. Ask for a pilot 2. Pick something that is winnable
  16. 16. Innovate through pilot projects 1. Ask for a pilot 2. Pick something that is winnable 3. Knock it out of the park
  17. 17. Innovate through pilot projects 1. Ask for a pilot 2. Pick something that is winnable 3. Knock it out of the park 4. Repeat
  18. 18. Hiring and/or building internal talent
  19. 19. Hiring and/or building internal talent Should you hire or to train up your existing staff?
  20. 20. Hiring and/or building internal talent Should you hire or to train up your existing staff? Do both!
  21. 21. Hiring and/or building internal talent Should you hire or to train up your existing staff? Do both! • Find Drupal partners to help with training • Send your staff to DrupalCon (or BAD Camp, PNWDS, etc) • If you cannot hire for Drupal, hire for open source passion and willingness to learn Drupal. • Highlight the benefits of working for your organization (pay is not the only draw)
  22. 22. Code deployment • Get as much of your build as possible into code. • Get your code in source control—preferably Git. • Figure out your deployment process. (Database down, code up) • Development (local or Dev server) • Integration or QAT (and test heavily) • UAT (and test heavily) • Production • Automate your code pushes. • Assign build masters to facilitate communication.
  23. 23. Git workflow Pull from master to multiple dev branches. When code is pushed (committed) to master, it goes to our QAT/ integration server. We then deploy code to UAT and then Production. Master Dev Feature 1 Feature 2
  24. 24. Change management
  25. 25. Change management γνῶθι σεαυτόν (Greek for “know thyself”)
  26. 26. Change management γνῶθι σεαυτόν (Greek for “know thyself”) • Your customers need to know what you plan to do—even if you don’t think it will result in an outage. • Take pride in high availability. • Plan your patch cycles. • When is a security update necessary versus a nice to have? • • Review security updates for core within 72 hours. Decide update philosophy. • Build to the cutting edge and update to the oldest viable system.
  27. 27. Drupal at Multnomah County // Questions Questions?

×