The Industry Standard for Developer Communities: Commons

We're seeing a groundswell of technology brands migrate to the open source alternative - Drupal Commons for their Developer Communities. Technology companies are expert buyers of technology... and they're deploying Drupal and Acquia Commons for some very public applications.

Many of the largest community sites in the Technology sector are powered by Drupal today, including:

Twitter https://dev.twitter.com/
ebay/PayPal: https://www.x.com/
LinkedIn: https://developer.linkedin.com/
Symantec: http://symantec.com/connect
Novell: http://novell.com/communities
Nvidia: http://developer.nvidia.com/
Red Hat: http://opensource.com/
Intel: http://appdeveloper.intel.com/en-us

Selecting a platform for all your customers or developers to collaborate on is not a quick decision. These communities are critical to achieving business goals; they enable partner ecosystems to exponentially grow and customer support issues to be solved in seconds. The chosen platform must be highly secure (tech companies are a prime target for hackers), exceedingly scalable (several of the above communities have nearly 1m subscribers each), very customizable (to reflect corporate branding) and ultimately very user friendly (to encourage a high level of participation and engagement from a very tech savvy audience).

At least three of these companies are very high profile migrations to Drupal away from Jive Software. Typical reasons to select Drupal and Acquia Commons include more innovation, more integration, more customization/branding, with no license fees and no costs per user/page view etc.

If you'd like to learn more about building Developer Communities in the Technology sector then please join the webinar I am hosting on September 28th, details will follow... shortly after we're also hosting a webinar on best practices for Jive to Drupal migration.

Oh and if you know of any good examples of Drupal communities in the technology sector or migrations from Jive to Drupal then please let me know.

Tags: 

Add new comment

Plain text

  • No HTML tags allowed.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Lines and paragraphs break automatically.

Filtered HTML

  • Use [acphone_sales], [acphone_sales_text], [acphone_support], [acphone_international], [acphone_devcloud], [acphone_extra1] and [acphone_extra2] as placeholders for Acquia phone numbers. Add class "acquia-phones-link" to wrapper element to make number a link.
  • To post pieces of code, surround them with <code>...</code> tags. For PHP code, you can use <?php ... ?>, which will also colour it based on syntax.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Allowed HTML tags: <a> <em> <strong> <cite> <blockquote> <code> <ul> <ol> <li> <h4> <h5> <h2> <img>
  • Lines and paragraphs break automatically.
By submitting this form, you accept the Mollom privacy policy.