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.
Dries Buytaert and I examined commit data to help understand who develops Drupal, how much of that work is sponsored, and where that sponsorship comes from. We illustrate that the Drupal community is far ahead in understanding how to sustain and scale the project, and show that the Drupal project is a healthy project with a diverse community of contributors. Nevertheless, in Drupal's spirit of always striving to do better, we also highlight areas where the Drupal community can and should do better.
Last night I had the pleasure of attending the first joint meeting of Minnesota Go and Rust users, and arrived home inspired -- not just by Go and Rust, but also about Drupal and its community.
Over the past couple of years, the Drupal community has been hard at work trying to confront a variety of challenges concerning Drupal core development, especially issues like burnout and funding.
I hope that you see a lot of reminders to vote this week. Of course, I am referring to the vote for the Drupal Association (DA) Board of Directors. I have already seen a number of blog posts and tweets that link to the candidate profiles, the first and second "meet the candidate" sessions, and the URL where you cast your vote.
DrupalCon Portland is over and many of us left feeling excited about Drupal 8. There will be a lot of changes from Drupal 7 to Drupal 8, and if you are wondering about what is new, one of the best ways to learn is to get involved with Drupal 8 development right now. Until recently, I had tried a couple of times to get involved with Drupal core, but became frustrated when I couldn't find an issue appropriate for me or I worked on a patch that got stuck in "needs review." While there are many ways to help out with Drupal core development, I would like to highlight three areas where I think you will have success -- the first is an ongoing effort for new contributors, the second is for frontend developers, and the third is for backend developers.