We're open sourcing our content management system
By Brent Dixon on March 08, 2007
From our new Open Source CU projects page:
We first started Open Source CU as an idea exchange. Now we think it’s ready to become a code exchange as well.
Over the next few weeks we’ll start releasing our Content Management System as an open source project. This CMS is the tool we developed to allow non-technical staff at a credit union to keep their website updated. We hope that other credit unions can use it to keep their sites fresh and relevant.
We’ll also be looking for other projects that are either currently open source or are willing to become open source. If you have a project that you would like to share, please let us know.
As Trey pointed out in the OSCU post, the CMS is Rails
Jesse Robbins was alo cool enough to post the story on Digg (thanks, Jesse!). To digg it, click here.
...On an entirely different note, our office is completely boxed up. We’re shipping out for the cross-country drive in two days. It’s very surreal.




Mark on March 09
Awesome….I’m interested in the logistics…
Warning: A few nerd questions to follow….
Will you release it as an Engine…like you’ve been using it?
Have you thought through the contribution aspect…where do I sign up to be part of the “Core”?
Can’t you guys just focus on one thing at a time? (Give With Us, CMS, and Moving…it’s making my head hurt!)
I look forward to seeing how this is rolled out. (Another thought….blogging the rollout…barenakedapp style…could be an awesome tool for others looking to opensource their projects)
Matt Dean on March 20
Mark,
Good questions.
First, regarding the engines—yes and no. My understanding is that most of the “engine” functionality is no longer needed with the new version of Rails. The CMS will still be in the form of a plugin, it just won’t need to be started like engines were.
Upgrading to the new Rails is one of the things left to do before putting the code out there. What I’d like to do is introduce the code as a series of posts (like you said, kind of like barenakedapp style). I’m not sure whether I want to create a separate blog for it—I’m thinking we may need to since the content isn’t something our typical reader usually cares about. If we do then we’ll definitely cross-post.
Contribution to the project will be handled through Google Code. We’ll definitely get you added to the core when the time comes.
And yes, my head is hurting too!