This article focuses on three attempts to compare people (and organizations) in the Drupal community: Certified to Rock, DrupalCores, and the Drupal Marketplace page. It explores how these methods were useful, where they might have been lacking, and what we can learn from related academic research into leaderboards.
In this article, co-authored with Tim Lehnen, CTO of the Drupal Association, we will describe how Drupal's issue credit system works and why we would like to bring it to GitLab and other code collaboration platforms. We hope that other free/libre and open-source projects and organizations that want to understand their return on investment in open source can model their approach on this issue credit system and benefit from the insights we have learned in the Drupal community.
Last week, when I renewed my yoga teaching credentials through the Yoga Alliance, I was required to agree to an "Ethical Commitment" based on values intrinsic to the practice of yoga, such as ahiṃsā (nonviolence), satya (truthfulness), asteya (not stealing), aparigraha (non-possessiveness), and santoṣa (contentment). While it might seem like such an agreement would be limited to my role as a yoga teacher, these same principles inform decisions that I make in all aspects of my life, including how I build my website.
The values and principles of the Drupal community align well with the Ethical Commitment to which all yoga teachers certified by the Yoga Alliance must agree. This article explains why I use Drupal as the ethical base of my online presence.
While some developers rightly focus on how to make websites accessible, this article focuses on the why. Why does the Drupal community hold accessibility in such high esteem? The Drupal community strives to provide a diverse and inclusive space, so building accessible websites clearly supports those goals. This article explores the stated reasons for Drupal's continued commitment to accessibility beyond the obvious truth that making websites accessible is the right thing to do.
As the global pandemic continues to spread — causing widespread sickness and death, restricting in-person human contact, creating additional responsibilities at home or financial hardships, or any of the countless other changes to daily life that have resulted in feelings such as fear, anger, boredom, or uncertainty — this virus has forced some of us to reassess our values and our place in the world. While the majority of us who participate in the Drupal community remain focused squarely on technical issues, others might find now is an especially good time to take a closer look at Drupal's Values and Principles.
As each of us negotiates a world where COVID-19 dominates the headlines and our everyday interactions, this article considers how some of the lessons that the Drupal community—perhaps an idealized Drupal community—has learned might shape our understanding of these times that feel so extraordinary. Drupal does not have a monopoly on any of these concepts, but in stressful times, similes and metaphors can help us interrogate our underlying assumptions and the communities that we have each constructed.
In this article, I use data from the Drupal Git commit history, as well as other sources, to demonstrate how dramatically the Drupal core “code committing” landscape has changed. My analysis below argues that the process of committing code to Drupal core is a far more complex process than some might assume of a project with a BDFL.
When I attended my first DrupalCon in San Francisco I brought three suits. At that point, I had been speaking at (academic) conferences for a decade, and in my experience conferences were places where attendees dressed formally and speakers literally read their papers (here's a real example from a 2005 Women's and Gender Studies Conference where I spoke). I arrived in San Francisco thinking I would spend some time exploring the city while I was there, but I ended up spending nearly all of my extra time in the ChX Coder Lounge learning everything I could about Drupal from kind people in the Drupal community.
Drupal has a great reputation as a CMS with excellent security standards and a 30+ member security team to back it up. For some Drupal sites, we must do more than just keep up-to-date with each and every security release. A Drupal site with private and confidential data brings with it some unique risks. Not only do you want to keep your site accessible to you and the site’s users, but you also cannot afford to have private data stolen. This article provides a checklist to ensure the sensitive data on your site is secure.
The Drupal community can bring people together, discourage hate, and promote democracy. I hope that we can find common ground, build on what we have accomplished, and organize against the forces that seek to divide us against ourselves.