concrete5.3 has been made possible by long hours, a great community of developers, and the kind license grants of these folks:
This developer wrote the Python based engine we use to compare versions. It's the only script we've been able to find that actually does diff with an awareness of how HTML tags work. If you stop and think about it, you'll realize that's a HUGE challenge and this guy solved it with a few pages of code. You should hire him to think about very complicated problems if he's willing. He allowed us to bundle his GPL based script into concrete5 under the LGPL licesne.
This designer does a lot of amazing work, is based in Chicago, and is gonna be someone you read about in magazines and books one day (if he isn't already!) We're using his file type icons in the new file manager because they're dead sexy, and work at a large scale. He's allowed us rights to redistribute them with concrete5 and we really dig that!
Thanks to both of these guys, it's awesome to be able to find something amazing on the web and use it. We'll keep doing our best to make sure the whole package is greater than the sum of it's parts!
So my lawyer called me up the other day with interesting news.. "Your trademark application for concrete5(tm) is going well, you're gonna be able to turn that TM into a little R with a circle any day, just get that c5 crap off of your website."
Thanks to the Usagi Project for putting this video together.
Some very cool people in Japan have taken the lead with concrete5 there and will be demoing it at on Open Source conference this month. If you happen to be in Japan, or have a lot of disposable income and are looking for an excuse to jump on a plane and head there on short notice…. here ya go!
Usagi Project will attend Tokyo OSC with concrete5 Japanese version.
Tokyo Open Source Conference 2009/Spring
Japan Electronics College Building No.7
Shinjuky, Tokyo, 169-8522
RSVP the seminar at
Also you can just show up at our demo booth during the event.
Feb 20 (Fri) 10:00am -5:30pm
Feb 21 (Sat) 10:00am -4:30pm
Date & time for first meeting
Feb 20 (Fri) – 21 (Sat) (Seminar starts on Feb 21 11am)
5.2 has been officially released, no more "release candidate."
We've landed two large projects that will improve concrete5 in dramatic ways. First, we're helping a very excellent creative agency build a big site for a major organization, and it involves a complete overhaul of the file system and asset manager. This is wonderful stuff. This means no more single directory with timestamp prefixes on files, but rather a well thought out system with versions, permissions, meta data – all sorts of nice stuff.
Second, we're building a major ecommerce implementation for a fun children's book publisher that integrates concrete5 with Magento Commerce. Both are very powerful applications for what they do, and should behave well as one product in the future.
We're also releasing some more add-ons to the marketplace, starting with the ad block today and with the calendar block right around the corner. The forums are going to be heading out to our beta team & user groups shortly – progress is being made on all fronts.
All of this means we're quite busy, bringing on more help, and generally loving where we are with concrete5! We have to scale back our already limited involvement in the day-to-day postings of the forum. Andrew and I are going to try to get through all un-answered threads once a week if we can, but you're going to have to continue to rely on the community experts that have already started to answer most stuff in there. If you would like an "official" view on something in a timely fashion, I would strongly encourage you to evaluate the worth of concrete5 to your business and join our Partnership Programs, where we promise your issue attention within 48 hours, typically 8.
So I hope you're all having a great start of '09 so far – it's clearly going to be a very exciting year.
This update is STRONGLY recommended for anyone who is testing out concrete 5.2. This update fixes a number of caching bugs, some of which can result in data loss and a less than optimal experience.