I’m very pleased to announce that JBoss DNA has a new name: “ModeShape”. Yes, it’s the same project, with the same software (albeit rebranded), and certainly the same fantastic community. Just a new name and a new home.
Why are we rebranding? After all, isn’t “JBoss DNA” a good name? We thought so. But while having “JBoss” in the name comes with a lot of benefit, there are some disadvantages. For a lot of people, “JBoss” means “Application Server“, and though we hope to play a role with AS in the future, right now our JCR implementation is completely independent of JBoss AS. For other people, “JBoss” means products (a la subscriptions and support), and ours is an open-source project that, at this point in time, is not included in any of the current JBoss platforms. So, if we lose the “JBoss” part of “JBoss DNA”, we’re left with “DNA”, and unfortunately that’s just not sufficient for a project name from a trademark or legal perspective.
So, we’ve chosen to rebrand our project as “ModeShape”. We have a great new logo:
and some other great new resources:
- new project site
- new Twitter account (follow us!)
- new blog
- new mailing lists and chat room
- new SVN repository (with all the history from JBoss DNA)
- new JIRA project (with all the old DNA issues)
- new forums (with all the old DNA threads)
- new swag and desktop wallpapers
We’re also releasing ModeShape 1.0.0.Beta1, but more on that in the next post.
We’re excited to officially have our new brand. Props to James Cobb and Cheyenne Weaver for our new logo, graphics and other branding help. And, as is so often the case, thanks to our fantastic community for their hard and quick work completing the rebranding.
BTW, where did name originate? It’s actually a slight modification of a term used in structural dynamics to help describe and understand how a structure responds dynamically to some force or input, where the response is mathematically a combination of each of its natural mode shapes. And it seemed to fit a project with goals of making it possible to understand the shape and structure of information and content. (Okay, maybe that’s a stretch. But you get the idea.)