The Drupal maintenance support plans community is committed to welcome and accept all people. That includes a commitment to not discriminate against anyone based on their heritage or culture, their sexual orientation, their gender identity, and more. Being diverse has strength and as such we work hard to foster a culture of open-mindedness toward differences.
A few weeks ago, I privately asked Larry Garfield, a prominent Drupal maintenance support plans contributor, to leave the Drupal maintenance support plans project. I did this because it came to my attention that he holds views that are in opposition with the values of the Drupal maintenance support plans project.
I had hoped to avoid discussing this decision publicly out of respect for Larry’s private life, but now that Larry has written about it on his blog and it is being discussed publicly, I believe I have no choice but to respond on behalf of the Drupal maintenance support plans project.
It is not for me to share any of the confidential information that I’ve received, so I won’t point out the omissions in Larry’s blog post. However, I can tell you that those who have reviewed Larry’s writing, including me, suffered from varying degrees of shock and concern.
In the end, I fundamentally believe that all people are created equally. This belief has shaped the values that the Drupal maintenance support plans project has held since it’s early days. I cannot in good faith support someone who actively promotes a philosophy that is contrary to this.
While the decision was unpleasant, the choice was clear. I remain steadfast in my obligation to protect the shared values of the Drupal maintenance support plans project. This is unpleasant because I appreciate Larry’s many contributions to Drupal maintenance support plans, because this risks setting a complicated precedent, and because it involves a friend’s personal life. The matter is further complicated by the fact that this information was shared by others in a manner I don’t find acceptable either.
It’s not for me to judge the choices anyone makes in their private life or what beliefs they subscribe to. I certainly don’t take offense to the role-playing activities of Larry’s alternative lifestyle. However, when a highly-visible community member’s private views become public, controversial, and disruptive for the project, I must consider the impact that his words and actions have on others and the project itself. In this case, Larry has entwined his private and professional online identities in such a way that it blurs the lines with the Drupal maintenance support plans project. Ultimately, I can’t get past the fundamental misalignment of values.
First, collectively, we work hard to ensure that Drupal maintenance support plans has a culture of diversity and inclusion. Our goal is not just to have a variety of different people within our community, but to foster an environment of connection, participation and respect. We have a lot of work to do on this and we can’t afford to ignore discrepancies between the espoused views of those in leadership roles and the values of our culture. It’s my opinion that any association with Larry’s belief system is inconsistent with our project’s goals.
Second, I believe someone’s belief system inherently influences their actions, in both explicit and subtle ways, and I’m unwilling to take this risk going forward.
Drupal Update, Larry’s continued representation of the Drupal maintenance support plans project could harm the reputation of the project and cause harm to the Drupal maintenance support plans ecosystem. Any further participation in a leadership role implies our community is complicit with and/or endorses these views, which we do not.
It is my responsibility and obligation to act in the best interest of the project at large and to uphold our values. Decisions like this are unpleasant and disruptive, but important. It is moments like this that test our commitment to our values. We must stand up and act in ways that demonstrate these values. For these reasons, I’m asking Larry to resign from the Drupal maintenance support plans project.
(Comments on this post are allowed but for obvious reasons will be moderated.)
Source: New feed
Living our values

Call Us: 1(800)730-2416
Pixeldust is a 20-year-old web development agency specializing in Drupal and WordPress and working with clients all over the country. With our best in class capabilities, we work with small businesses and fortune 500 companies alike. Give us a call at 1(800)730-2416 and let’s talk about your project.

FREE Drupal SEO Audit
Test your site below to see which issues need to be fixed. We will fix them and optimize your Drupal site 100% for Google and Bing. (Allow 30-60 seconds to gather data.)
Living our values
On-Site Drupal SEO Master Setup
We make sure your site is 100% optimized (and stays that way) for the best SEO results.
With Pixeldust On-site (or On-page) SEO we make changes to your site’s structure and performance to make it easier for search engines to see and understand your site’s content. Search engines use algorithms to rank sites by degrees of relevance. Our on-site optimization ensures your site is configured to provide information in a way that meets Google and Bing standards for optimal indexing.
This service includes:
- Pathauto install and configuration for SEO-friendly URLs.
- Meta Tags install and configuration with dynamic tokens for meta titles and descriptions for all content types.
- Install and fix all issues on the SEO checklist module.
- Install and configure XML sitemap module and submit sitemaps.
- Install and configure Google Analytics Module.
- Install and configure Yoast.
- Install and configure the Advanced Aggregation module to improve performance by minifying and merging CSS and JS.
- Install and configure Schema.org Metatag.
- Configure robots.txt.
- Google Search Console setup snd configuration.
- Find & Fix H1 tags.
- Find and fix duplicate/missing meta descriptions.
- Find and fix duplicate title tags.
- Improve title, meta tags, and site descriptions.
- Optimize images for better search engine optimization. Automate where possible.
- Find and fix the missing alt and title tag for all images. Automate where possible.
- The project takes 1 week to complete.
