people

Sometimes situations take time to resolve. This situation is complicated and the goal is to treat everyone respectfully. We're beginning to see things play out now. I want to offer some of my recent thoughts. By no means are they right or fully informed, but I wanted to share (please don't shoot the messenger).A subtle reminderThis situation has reminded me that: We are dealing with actual people We are all human Let’s break each down a bit more to set proper context. We are dealing with actual peoplePeople drive our community. Behind the keyboard is a person. No technical contribution would

For a moment, may some of the hurt and fearful in the Drupal community take a moment to pause and reflect. Take a deep breath and slow down from the continuous retweeting, reddit posts, or the most recent Drupal Confessions. (By the way, does anyone else think "Drupal Confessions" sounds like a Saturday Night Live skit or a bad emo song?) Let me begin by reminding you that some of the strongest voices are the farthest from those potentially marginalized by the Crell situation. These loud voices are drowning out the voices of those they claim to also stand up for. It's like a bad train wreck

In my previous two blog posts [one] [two], I shared my concerns and open questions over the recent events surrounding Crell and discussed my initial efforts to become informed even when full transparency does not and likely will not exist. I have formed the opinion that those seeking answers and specifics may never get the level of detail they desire, both for legal and privacy reasons. I continue to engage with others in conversation out of respect for those processing these events and out of my desire to form a well-rounded and bias-free stance. With the complexities involved, there is no

As I mentioned in my previous post, I was struggling to make sense of this situation. Was Crell treated fairly? Was he being discriminated for his beliefs? How is this possible in the confines of a community that supports diversity and inclusion? I spent parts of my day participating in discussions with team members, engaging community members, researching relevant topics, and reading responses of others that had their own questions and concerns. We are all still processing this and I ask you to please respect the diverse opinions from members in the community. In my post yesterday, I made it

When I was checking Twitter last night, a prominent community member posted a "TMI" message with a link to a blog post. This was totally off-character for a man regularly promoting thought leadership in technical capacities (why I was following him on Twitter). I was quite curious and I was immediately appalled by what I read. The post can be found here: https://www.garfieldtech.com/blog/tmi-outing This created widespread outrage on Twitter, Reddit, and much more. Inevitably it was followed up by a blog post from Dries: http://buytaert.net/tag/living-our-values While totally uninformed and

Off the top of my head, I can name several "first"-based approaches. Do any of these ring a bell? Mobile first, content first, API first, user first, design first, experience first, modeling first, security first. For far too long, experts in these various realms have caught the attention of communities by coining these terms. They speak to the vulnerable: people who have ultimately been burned by not applying the best practices of whatever is being sold. But, that is an altogether different problem than what is ultimately being sold. What is being sold is the need to put something first. This

I'm a huge advocate for finding ways to encourage more Drupal participants. Due to the complexity, it's unreasonable to expect people to initially pick up programming-heavy issues. This is the motivation behind the "novice" label, providing a means for identifying potentially low-complex tasks new contributors could safely pick up. The end result is usually one or more commits which are credited to you and/or your organization on Drupal.org. Commit BiasFor those looking to bolster their Drupal expertise, organizations will often look at who has "given back" to Drupal as a means of vetting. The

WhyI am ashamed to admit, for the longest time I used Drupal (heck, even complained about it) but contributed absolutely nothing back. It occurred to me that, not only did I learn technical and marketable skills thanks to Drupal, my Drupal experience directly corresponded to opportunities that supported my livelihood and viability for me and my family. And, all of this occurred without one line of code from me contributed back. A long while back, I decided to make an effort to solve a core issue. At that point, I had stronger SVN experience than Git. I had approximately eight years of

When you are building a tool, how do you measure the success of your efforts? There are data driven approaches around adoption, like number of times your tool has been downloaded or installed. Similarly, success could be defined as how effectively you solved the problem. This could be measured by the number of issues filed, the (hopefully) lack of vulnerabilities, or the number of feature requests created. But, in any measure, success is actually defined by other people. And, as an engineer, it's such a difficult task to put yourself in their shoes. How do you deal with that? Theory People are

Drupal 8 has been widely praised for improving the developer experience (DX). The "best of breed" adoption of tools (see: Symfony, Guzzle, PHPUnit, Composer, etc) clearly positions Drupal to mature and evolve beyond that which one community is able to do alone. But, there are many different considerations of DX that need explored. And, what lift is required for the community to grasp this new version? And, what is the impact? DX ConsiderationsProbably the number one thing that is praised with Drupal 8 is the technical modernization. Drupal is already challenging to learn effectively. But, if