We recognize that events and conversations earlier this year surfaced many concerns and needs within the community. One in particular is related to Larry Garfield’s role within Drupal. After several conversations with Larry, and careful consideration, we can now provide an update to this situation, our decisions, and Larry’s role moving forward.

We thank you for your patience while we spent many hours meeting with Larry and outside experts to resolve this matter. We recognize that actions were taken quickly before, which resulted in poor communication, and we wanted to avoid this happening again. We made sure to provide the proper time and attention these conversations needed before releasing this follow-up post.

We know our poor communication in the past led to frustration with us and pain for others. For that, we are sorry. We want to learn from this and improve. We listened to the community’s request to provide more streamlined, clear, and easy-to-follow communication. So, this post includes a statement from Dries Buytaert, as Project Lead, followed by a statement from Megan Sanicki, Executive Director of the Drupal Association.

[...]

Larry's subsequent blog posts harmed the community and had a material impact on the Drupal Association, including membership cancellations from those who believed we doxed, bullied, and discriminated against Larry as well as significant staff disruption. Due to the harm caused, the Drupal Association is removing Larry Garfield from leadership roles that we are responsible for, effective today.

[...]

As long as Larry does not harm or disrupt the project, he will continue to be a member of the community as an individual contributor. However, we reserve the right to remove Larry's individual contributor roles if that is not the case. Also, we recognize that situations can change over time, so the Drupal Association will revisit these decisions in two years.

I recognize that my communication to Larry and with the community did not provide transparency into this situation and I apologize for the pain and confusion that caused. Our advisors told us not to share these details in order to protect all parties pending evaluation from authorities. Also, when Larry shared these details during the appeal process, he asked us to keep them confidential. It is my hope that this statement provides the clarity that many have been requesting.

• WordPress, Joomla, Drupal, More: Keeping Up With Open Source CMS

  Due to its organic nature, the world of open source software is in constant flux, which makes it difficult to keep tabs on.

  To keep you in the loop, I’m kicking off a monthly roundup of open source CMS news, starting today.

  Here are your latest open source CMS highlights.

• 4 open source peer-to-peer marketplaces

  What happens if your startup can't afford one of these proprietary solutions or you need customized features? You go look for an open source alternative that could open the space for new solutions and modules. Here are four peer-to-peer marketplaces that are working to become the Wordpress or Prestashop of their kind.

• The Wix Mobile App, a WordPress Joint

  Anyone who knows me knows that I like to try new things — phones, gadgets, apps. Last week I downloaded the new Wix (closed, proprietary, non-open-sourced, non-GPL) mobile app. I’m always interested to see how others tackle the challenge of building and editing websites from a mobile device.

  I started playing around with the editor, and felt… déjà vu. It was familiar. Like I had used it before.

  Turns out I had. Because it’s WordPress.

• WordPress and Wix Are Fighting About Open Source Software

  So WordPress and Wix are fighting one another – and I'm not talking about them competing for customers. Instead, the two website building heavyweights are having a brawl via the blogosphere.

• Attackers use patched exploits to hit Joomla! sites

• Joomla websites attacked en masse using recently patched exploits

  Attackers are aggressively attacking Joomla-based websites by exploiting two critical vulnerabilities patched last week.

  The flaws allow the creation of accounts with elevated privileges on websites built with the popular Joomla content management system, even if account registration is disabled. They were patched in Joomla 3.6.4, released Tuesday.

• Georgia state government earns national recognition for web accessibility

  Georgia's enterprise web platform runs on Drupal 7, which includes many accessibility features in its baseline code and structure. That makes it easier for any new site to build in accessibility from day one. This comes with the caveat that not all modules are accessible, and plenty can be coded and designed without accessibility in mind, meaning that just using Drupal does not make a site accessible to users with disabilities. That said, even in its original implementation with Drupal 7 in 2012, Georgia's web publishing platform was built to meet federal accessibility standards (Section 508, for those of you interested in the details).

  From there, when the product team wanted to improve the platform's underlying code to meet the more modern WCAG 2.0 AA accessibility guidelines, they were working from a flexible and scalable base.

Dries Buytaert announced today that Nasdaq Corporate Solutions has selected Drupal 8 and will work with Acquia to create its Investor Relations Website Platform. In the words of Angela Byron, a.k.a "Webchick", "This is a big freakin' deal."

Direct: Nasdaq using Drupal 8 for new Investor Relations websites