Skip to main content

Open Source Bridge - How Two Fools Made Themselves Indispensible From Their Basement Office

Chris Chiacchierini, Mason Bondi - Oregon College of Oriental Medicine
  • 50 staff, 250 students
  • university originally chose proprietary commercial cms for $15K
    • used for marketing site
    • only one of 5 people in the world using it
  • attended open source conference and learned about open source cmses
    • "holy shit, we just got snowed"
    • chose Joomla! for ease of use
  • didn't want to give up on open source cmses
    • went to library, asked if they'd be interested in putting up a site using oss cms
    • did this all under the radar, wanted to wait until it was too late to go back before anyone knew
  • through this a lot of institutional knowledge is being built, and since people had freedom they were starting to get more creative
    • class materials being put online
    • financial information about student loans
  • lots of people and departments were using the open source cms
  • once it was opened up to the students, it really started to take off
  • two parallel forces going
  • got call while he was on vacation -- marketing site got hacked
    • could now go to executive council with security concerns and propose switching over to the open source cms
    • was getting hacked every couple of days
  • executive council asked how much it would cost
    • couldn't believe cost would be $0
  • 4-5 departments already using the open source CMS loved it
  • what about the rest of the community?
    • every single office at the university has a stake
    • lots of departments only updated static information once a year
      • weren't interested in doing anything with the CMS, or are too busy
    • e.g. grades--wanted to put grades online
      • would be vastly more efficient than mailing, but hard to make people change
  • a project management cycle that works
    • opportunity -> needs analysis -> cost benefit analysis (proof of concept) -> project plan proposal -> approval -> design, build test -> implementation & training -> review
    • most often the people with the money aren't the ones who have the technological know-how so there's a lot of politics involved
    • a lot of the project management cycle is done in stealth mode
    • technical people tend to want to take the ball and run with it and tell everyone to get out of the way, but this doesn't work without a sponsor
    • need to get a sponsor at the executive level
      • often best to get the person who has the power to pull the rug out from under you to be the sponsor--they get part of the credit
    • need to sell the idea to a sponsor in the opportunity phase
    • still selling hard in the needs analysis phase
      • can do some of this in stealth--pick people you like and trust to get a little bit of insight into what the needs are
    • after this, set up a needs analysis meeting to ask for feedback--make it clear this is the one chance people have to offer feedback
      • better than going office to office--gets everyone in the same room
      • people see what the impact is outside of their own department
      • also lets people gripe if they want to
    • in cost/benefit phase have to make sure the proof of concept is in place
      • can't only look at cost as cost of the software--also involved is implementation, training, cost of support, etc.
    • project plan proposal--where people who gave feedback see what will actually be implemented
      • even though it won't be exactly what each person wanted, they'll see the bigger picture
    • approval -- doesn't only mean budget, but once something's approved there's no turning back
      • if you're not sure you can follow through, stop before approval
      • after approval you HAVE to deliver
    • implementation & training
      • second tier thing they implemented was putting course materials online using moodle (course management software)
      • no way could get everyone involved and get all the instructors to get all their materials online
        • students weren't excited at first either, but once they used it they won't go back
      • had a goal of rolling out three classes per quarter as a pilot
        • chose instructors that taught enough classes that most of the students would be involved
        • none of the courses are exclusively online but there are pieces of the course you can only get online
      • followed faculty around for three weeks, constant contact, asked for feedback from both instructors and students
        • important to get everyone comfortable
      • what they wanted to happen started to happen--students didn't want to deal with printed materials anymore
        • students started talking to faculty members whose courses weren't online
      • building things out slowly builds inertia, but always keep the costs in mind
      • as far as timing goes, as long as you can keep showing progress, specific deadlines aren't that important
      • if possible getting isolated focused time with people is ideal for getting things ramped up
        • can avoid ongoing and future training, also gets people thinking more creatively
    • review
      • constant cycle
      • some formal review, some informal
      • important to make incremental changes so the solution continues to meet the needs
  • before the cms project started, the IT guys were seen as a necessity
    • now people are looking at the IT department as something that can help with solutions
    • creating a lot of work for the department
  • through a successful project you can gain "street cred"
    • create a working relationship with other departments

Comments

Brandon Moser said…
My friend @jhadow did the same thing with his Radiology dept at Univ of Vermont. He also used Joomla and it has been really successful.
Matthew Woodward said…
Funny how often this happens. ;-) Was a great presentation.

Popular posts from this blog

Installing and Configuring NextPVR as a Replacement for Windows Media Center

If you follow me on Google+ you'll know I had a recent rant about Windows Media Center, which after running fine for about a year suddenly decided as of January 29 it was done downloading the program guide and by extension was therefore done recording any TV shows.

I'll spare you more ranting and simply say that none of the suggestions I got (which I appreciate!) worked, and rather than spending more time figuring out why, I decided to try something different.

NextPVR is an awesome free (as in beer, not as in freedom unfortunately ...) PVR application for Windows that with a little bit of tweaking handily replaced Windows Media Center. It can even download guide data, which is apparently something WMC no longer feels like doing.

Background I wound up going down this road in a rather circuitous way. My initial goal for the weekend project was to get Raspbmc running on one of my Raspberry Pis. The latest version of XBMC has PVR functionality so I was anxious to try that out as a …

Setting Up Django On a Raspberry Pi

This past weekend I finally got a chance to set up one of my two Raspberry Pis to use as a Django server so I thought I'd share the steps I went through both to save someone else attempting to do this some time as well as get any feedback in case there are different/better ways to do any of this.

I'm running this from my house (URL forthcoming once I get the real Django app finalized and put on the Raspberry Pi) using dyndns.org. I don't cover that aspect of things in this post but I'm happy to write that up as well if people are interested.

General Comments and Assumptions

Using latest Raspbian “wheezy” distro as of 1/19/2013 (http://www.raspberrypi.org/downloads)We’lll be using Nginx (http://nginx.org) as the web server/proxy and Gunicorn (http://gunicorn.org) as the WSGI serverI used http://www.apreche.net/complete-single-server-django-stack-tutorial/ heavily as I was creating this, so many thanks to the author of that tutorial. If you’re looking for more details on …

The Definitive Guide to CouchDB Authentication and Security

With a bold title like that I suppose I should clarify a bit. I finally got frustrated enough with all the disparate and seemingly incomplete information on this topic to want to gather everything I know about this topic into a single place, both so I have it for my own reference but also in the hopes that it will help others.Since CouchDB is just an HTTP resource and can be secured at that level along the same lines as you'd secure any HTTP resource, I should also point out that I will not be covering things like putting a proxy in front of CouchDB, using SSL with CouchDB, or anything along those lines. This post is strictly limited to how authentication and security work within CouchDB itself.CouchDB security is powerful and granular but frankly it's also a bit quirky and counterintuitive. What I'm outlining here is my understanding of all of this after taking several runs at it, reading everything I could find on the Internet (yes, the whole Internet!), and a great deal…