CMS News, Reviews and Resources

Content Management Matters ™

Home > Archives > Web CMS
 Newsletter:



Acquia's Carbon has Launched in Private Beta

By James Mowery
Aug 29. 2008

Acquia Logo

Acquia, the commercialization entity that resulted from the Drupal project, has finally released a private beta of Carbon — its commercial Drupal distribution. They’ve only been talking about the project since the end of April.

Acquia serves as a commercial backbone for supporting clients and businesses who want to utilize the open source project, and it appears that the company is making good on its goal.

Any person who has used Drupal could probably tell the story about how when he or she first saw the project. It looked very complex. It probably was a complex thing to grasp how it worked.

SPONSORSHIP

CMSWire speaks to a specific audience of professionals and opinion makers focused on content management, publishing and collaboration.
Advertise here.

Furthermore, anyone coming from the likes of WordPress would likely be put into a seizure with all the stuff Drupal has going for it. Although, after getting past the initial shell-shock, users tend to quickly realize how vast and impressive the Drupal project really is—the power, the customization and the reliability are all tucked away in a light-weight modular package.

As great as Drupal is, it requires plenty of effort to maintain, support and secure the popular Web CMS.

Acquia, co-founded by Dries Buytaert — the original creator and project lead of Drupal CMS — can step in and provide an extra boost of support and reassurance that isn’t available in the publicly released version. The latest release, called Carbon, is exactly the kind of thing that businesses and enterprises desire.

According to TechCrunch:

The release is essentially a hardened distribution of Drupal, complemented with technical support and network service offerings. Code named Carbon for now, the package includes a select set of community contributed modules alongside the Drupal core. Acquia has taken the task of pre-testing, reviewing, and comparing all community contributed modules to offer a set of the most relevant and reliable contributions. Site administrators are notified of updates to Carbon modules through the network, code named Spokes. The system differentiates between feature, bug fix, and security updates, and informs users of compatibility issues or other dependencies amongst different modules.

Essentially, Acquia is providing users with a service that it can monetize. That service is support, and it is a great business opportunity that is likely to succeed as the increase of demand in open source software grows. If you would like to explore Acquia’s projects and support for the Drupal project, check out their website.

Access to the Beta is currently open to only the first 100 TechCrunch registrants — expect you missed that boat already — or to anyone who requests entry in person at Drupalcon Szeged. But fear not, they are offering new invites every week - so be sure to get on the list to receive yours. Come back and let us know how the beta works.

Was this article useful?

Comments

Exciting times in the Drupal world!

We've also just announced our partnership with Acquia to provide high quality themes with their distribution: http://www.topnotchthemes.com/blog/080828/acquia-partners-with-topnotchthemes-commercially-supported-drupal-distribution

Posted by: on August 29, 2008 7:31 PM

This shift from open source to a trialware/shareware ethos (i.e. you get it for free, but, you pay for support) worries me a lot.

Is it because open source only works up to a point ? or is it that there was an inability to manage and harness the huge drupal community in a smarter way?

Because the majority of the core developers behind Drupal are now working for Acquia full time now, I can see a shift of Drupal users across to Carbon, which is understandable. It is also a pity, because it means Drupal will essentially lose the open source spirit and vitality that has brought Drupal as a project to where it is today.

Why would a contributor to Drupal submit a patch, bug fix, idea for improvement to an existing module, when they can simply copy and modify the existing module, give it a new name and release it as their own...charging for support?

So I tend to disagree with the comments that point to "exciting times in the Drupal World!"....I'm more worried that it is "exciting times for the venture capitalists and shareholders of acquia!"...who own Carbon and all the products Acquia comes up with.

Posted by: PMCKENNA on August 31, 2008 8:13 AM

Hello PMCKenna,

I just wanted to briefly state that it could really go either way.

Unfortunately, people who own trademarks and copyrights to this stuff find ways to monetize it. Do you think that the people behind Wikipedia are not making money from their efforts?

Look at a video game like Spore. They are going to be making money directly off of other people's efforts. Is it fair? I am not sure.

I'll hold my reservations on this, but this trend of profitable businesses building off of open source software is very hot.

Ethics matter too, but that is why the community exists. Unfortunately, no matter how far Acquia pushes it, the community, for the most part, is likely to stick around unless they step way out of bounds.

If you were Dries Buytaert, wouldn't you want to make money off of this project that everyone on the internet was taking advantage of? I don't know the answer, but, again, that is just the way the world works.

Posted by: James Mowery on August 31, 2008 12:45 PM

@ James Mowery

I've nothing against Dries, the venture capitalists and investors behind acquia earning money from Drupal, it's the approach I have difficulties with.

Dries and Acquia could just as easily have launched an installation profile of Drupal for enterprise applications and provided commercial support for that.

Installation profiles were introduced by the Drupal community to make the commercialisation of Drupal easier - i.e. installation profiles offer a huge opportunity for companies to provide commercially supported distributions of Drupal. Installation Profiles also helps avoid forks and breakaway projects that may dilute the Drupal project and create confusion.

Instead, we have a 'new' version of Drupal with a new name and a new brand identity. That is not only confusing and very unsettling for the Drupal community (in particular the development community), but, it is also nudges the Drupal community culture away from the open source ethos, which is the very ethos that brought Drupal to where it is today.

It's not difficult to see a lot of Drupal users, particularly Drupal develoeprs switch from Drupal to Carbon, which the press releases describe as "a hardened distribution of Drupal", without paying for the commercial support or network services Acquia plan to provide.

That user migration dilutes the most important part of the Drupal community...i.e. the Drupal developers. It' s plausible that they will continue to take extra time out to take their carbon modules and release them at Drupal.org for free, but, somehow I don't think that will happen in the same open and free way it has for the last few years at drupal.org.

Wouldn't most serious developers prefer to work with 'a hardened version of Drupal'? that's available for free?

Posted by: PMCKENNA on September 1, 2008 7:32 AM

I also doubt that community will stay unified for a long time. I just stumbled upon Drupal. This is a great product.

I came across this post. http://communitythugs.wordpress.com/2008/08/28/drupal-dries-acquia-and-community-contributions/

Looking at few comments on this post and the URL above, I think Drupal founder Dries is already getting flames for misleading the community.

I don't care that much for now but if I am to contribute code and Acquia repackaging making money out of it and not releasing 100% of the improvements back, I'd be very concerned in the first place itself.

If I understand correctly, Dries still owns the Trademark which is another problem.

Aziz

Posted by: Aziz Aslam on September 20, 2008 5:04 AM

Hi Philip and Aziz.

>>Acquia repackaging making money out of it and not releasing 100% of the
>>improvements back

>>It' s plausible that they will continue to take extra time out to take
>>their carbon modules and release them at Drupal.org for free, but,
>>somehow I don't think that will happen in the same open and free way
>>it has for the last few years at drupal.org.

As our announcements on Tuesday made abundantly clear, Acquia Drupal is free to download, GPL-licensed, and all Acquia patches go directly back to the Drupal project for consideration by the appropriate maintainers.

>>installation profiles offer a huge opportunity for companies to provide
>>commercially supported distributions of Drupal.

We looked at this approach, but it doesn't yet provide the simplicity that customers are looking for. Installation profiles still require the user to hunt down module and module version individually, which is a pain. We actually use installation profile functionality within our distribution for some things, but in the end we had to create a fully standalone distribution to deliver the user experience that people want. By keeping all our code in sync with Drupal.org, we avoid the fork issue altogether.

>>Instead, we have a 'new' version of Drupal with a new name and a >>new brand identity.

We have a convenient bundle of Drupal software with the same brand name plus the name of the company that put the bundle together. It is just like Red Hat Linux or Ubuntu Linux, etc. This approach has been an enormous benefit to Linux, and we hope it will be an enormous benefit to Drupal as well.

>>which the press releases describe as "a hardened distribution of Drupal"

Only one press release included that phrase. It was a marketing mistake. I take full responsibility. You won't see it again. Sorry.

>>it is also nudges the Drupal community culture away from the open
>>source ethos

If it nudges the community culture anywhere, it is toward sustainable growth and prosperity for everyone involved in the project. Helping more people to succeed with Drupal, making the Drupal technology better for everyone (no stupid toll booths or walls on the technology), and helping organize and rally the community to accomplish more are good things in which Acquia invests every single day. Our track record speaks for itself, and will continue do so.

>>Dries still owns the Trademark

Dries owns the trademark. Acquia does not. Dries has published guidelines for using the mark. We follow the guidelines. You can too.

Posted by: Jeff Whatcott on October 2, 2008 9:25 AM

Add a Comment

Email:
Web Site:
Comments:
Security Code:
  Remember me?
  


Advertise on CMSWire





Add to Technorati Favorites

Alltop, all the top stories