In recent days there's been a bunch of insightful and thought provoking reflection within the Drupal community (as well as a share of bullshit). I've benefited from hearing perspectives that remind me of my biases and privileged placement as a cis white male.
As controversy swirls around the Drupal project leadership, community members are asking searching questions about the role of corporate influence in the project.
Change can often be a hard thing for groups—even progressive groups. Getting a staff team to willingly adopt new software or a new website can be challenging. Especially for staff who always feel a shortage of time in getting the important work done.
A current project we're working on at Chocolate Lily involves upgrading a Drupal 6 site to use the Drupal 7 Open Outreach distribution. It's the first time we've used a Drupal distribution for an existing Drupal site instead of a new one.
What is Drupal good for? Drupal is often used for creating complex organizational websites that might take weeks or months to develop from initial plans to launch. But what if you need a site, like, tomorrow?
Any way you do it, upgrading an organizational website to a new major version of Drupal - for example, from Drupal 5 or 6 to Drupal 7 - is a significant task.