This is a very uncomfortable time for Drupal. It seems there has been a great deal of concern and discomfort lurking just below the surface for a while, and recent events surrounding me have brought them all to the forefront at once. It's going to take some time to unravel it all. Hopefully it can be a learning process for many.

For the moment, though, there's one particular point I want to address, and particular people I want to address it to: Don't be an asshole, not even in my defense.

I did briefly speak with Dries in private recently about recent events. I cannot discuss details of our conversation, but there is one point he mentioned that I feel warrants an immediate response.

Since my last post Dries and Megan have issued a new joint statement on the ongoing mystery regarding my removal from DrupalCon and the gossip campaign against me. To date, I have focused my public posts mainly on my experiences, my beliefs, and the prejudice with which I have been treated by select members of the Drupal community and by select (if powerful) members of Drupal's leadership. However, I feel the latest joint post from Dries and Megan last Friday deserves a more direct response.

Some commenters noted that it doesn't add anything or reveal any additional information. I disagree. It makes implications and innuendo that are sufficiently untrue that I fear, if they have not crossed the line into libel, they certainly teeter on the precipice.

It's been an eventful couple of days, that's for sure... Eventful enough that I feel it's necessary to clarify a few points.

First off, I want to express my sincere thanks to everyone that has reached out, in public or in private, to express their support in this situation. I genuinely appreciate it, even if I haven't had a chance to respond to everyone directly. Thank you all.

I'm especially gratified to hear from those people, particularly women, with whom I have worked most closely over the years in Drupal. Even people I've not talked to in a while, whether we got along or not, have voiced that I’m anything but a misogynist, and to state anything to the contrary is simply wrong.

Recently, I've become aware of a whisper campaign going around the Drupal world, discussing details about my personal life. I do not know where it started or who all has been part of it. However, it's become apparent that it's not going to settle down, and has now had a major, direct impact on me and my professional career. Only a few people have bothered to speak to me directly, but there's been enough back-chatter that I feel I have no choice but to clarify some private details about me, in public, and address the actions of some fellow members of the Drupal community.

Yep, this is one of those "self-outing" posts. I'm sorry that they still need to exist.

Most of the time I try to stick to technical topics on this blog, rather than political. However, as this past week has shown we do not have the luxury of being a-political. We have a political system where rampant institutional corruption has been suddenly overshadowed by a new administration that has a complete and total disregard for the rule of law, American citizens, people in need (domestic or foreign), the future of our planet, and the basic facts of reality itself.

This does not bode well for us as a people.

Recently I've had reason to start several new projects with Git. That's nothing exciting (except for me), but it means I've been making a lot of first-commits, and often rebasing my early commit history before making it public. That, however, runs into an interesting problem: You can't easily rebase the first commit.

Sometimes that doesn't matter. Lately, though, I've repeatedly found myself wanting to change that first commit, often to remove a file that I included in the initial commit inadvertently.

Fortunately, Git offers a couple of ways around this situation. My personal favorite is to simply start the history with a null commit. Git normally won't let you make a commit if there's nothing to do, but you can easily disable that check. My new Git projects now tend to start like so:

The team over at thePHP.cc recently published an ebook entitled PHP 7 Explained, "Everything you need to know about the next generation."

A few weeks back, I received an email from them stating "As a token of our appreciation for your involvement in the PHP community we would like to gift you a copy of our eBook." Yay, free stuff! Since I'd gotten it free, and it's of timely use to the PHP world, I decided to publish a formal review.

Disclaimer: I was not asked to write a review, although the authors did ask for feedback. The only compensation I receive for this review is the book itself, which was sent without the expectation of a review. Also to the authors, yes feel free to quote portions of this review on the books site as long as it's credited.

OK, well, it took a while, but I've finally gotten my blog off of Drupal 6. :-) Welcome to the new and improved Garfieldtech.com! My blog is unsurprisingly rather bland, as it's, well, a blog. That made updating to Drupal 8.2 using the Drupal migrate module reasonably easy. It wasn't hiccup free, and a few not-yet-updated modules got lost along the way, but it wasn't an epic struggle, either. There were only two major hiccups:

There has been much discussion in the last few years of "web apps". Most of the discussion centers around whether "web apps" that do not degrade gracefully, use progressive enhancement, have bookmarkable pages, use semantic tags, and so forth are "Doing It Wrong(tm)", or if JavaScript is sufficiently prevalent that a JavaScript-dependent site/app is reasonable.

What I fear is all too often missing from these discussions is that there isn't one type of "web app". Just because two "things" use HTTP doesn't mean they're conceptually even remotely the same thing.

After my last post, a number of people asked if I was leaving Drupal all together. Perish the thought. :-) However, after a decade at Palantir.net and the five-year Wagnerian Saga that was the Drupal 8 development cycle (complete with singing), I have been asking myself "What next?"

Well, what do I like to do? I like to build. I like to teach. I like to make things better. I like to work with smart people, as colleagues, as community partners, and as customers. I want to be able to have an impact in making something better for other people.

To that end, I am pleased to announce that today is my first day as Director of Runtimes, Integrations, Engines, and Services for Platform.sh.