Hearty congratulations to Magento, winner of the best new project award at this year's SourceForge Community Choice awards, as well as all the other winners. It was good fun having Habari nominated.

You should never ever modify core files in WP. If you find you have to, file a ticket for a new hook or filter so your modifications can be a plugin — it makes things so much easier.
[read more]
Chris J. Davis has started working on some image editing software focussing on imagery for the Web. The working title of the project is Simpleshop, because the impetus is the huge number of unused Photoshop features when you only use it for Web images. Knowing Chris, Simpleshop will be a complete misnomer before long and the application will definitely be doing it's own thing rather than simply being a cut-down version of the other 'shop. Chris will open source the project when he has a working prototype.
Owen Winkler has responded to Jacob Santos' post outlining why he wouldn't move to Habari with a point-by-point attempt to change Jacob's mind. Owen was a long-time developer of WordPress and a founding member of the Habari team and so has much experience of both communities. I've only been involved with Habari for a short time, after paddling around the edges of WordPress for a little while, so my perspective is much more as an outsider. Jacob complains about the complex file and directory structure of Habari. I've hacked the core, worked on themes and plugins, from scratch and extending ...
[read more]
Donal asks me, "Why will [Habari] be better than WordPress?" Habari may or may not be better than WordPress, but I'm not sure that's really the right question to ask in my case. While Habari is a lot younger than WordPress, it's been developed from the start with a solid vision by people with a lot of experience with blogging software. That's all good, but it's still not why I became involved. Okay, maybe obsessed, but that's who I am. No, it's because Habari has an open, welcoming and vibrant community, and I feel like I can make a real ...
[read more]
[Making OSS UIs work]
Do 1. Get a Benevolent Dictator 2. Make the Program Usable In Its Default State 3. Design Around Tasks 4. Write a Plug-In Architecture 5. User Testing, User Testing, User Testing!! Do Not 1. Develop Without A Vision 2. Join the Clone Wars 3. Leave the UI Design Up To The End User 4. Make the Interface a Thin Veneer over the Underlying Implementation 5. Treat UI Design as Babysitting Idiots