This blog was originally intended as a comment on Maxime's medium post. It got long, and I am loath to create content for mega-sites. As such, I responded with a post of my own, which is exactly what Maxime did to Robert Douglass' original Facebook post... I guess we all have our competing standards ;-)
If you've engaged me on topics outside the world of Drupal, it becomes apparent pretty quickly that I have some rather esoteric interests. Everything from molten salt reactors to Star Wars is pretty much on the table. Unfortunately, working either for clients or on Drupal itself take up the majority of my time that's not already dedicated to my family, so it is rare that I go out and actually participate in things in which I have an interest. For my 30th birthday, my amazing wife got me my first Skydiving jump.
Drupal 8 has been out for over a year at this point. I worked extensively on helping to improve portions of core during the Drupal 8 cycle, but maintaining your own site is radically different from trying to develop the platform that site(s) will reside upon. Upgrading my blog is especially exciting for me because I was still on Drupal 6. Getting to jump directly from Drupal 6 to Drupal 8 is a pretty big win and the fact that Drupal 8 supports this out of the box was amazing. Now granted this is just my blog, it's not even 100 nodes, but still...
It is with a mixture of bitter and sweet that I am officially announcing that I'm leaving Commerce Guys for a new position elsewhere. I have really enjoyed the last 3 (nearly 4) years at Commerce Guys. They have been an amazing place to grow both as a person and as a programmer. During my time there I've had the opportunity to work on numerous big projects and interesting technical challenges.
To say I've spent a lot of time working on Drupal 8 over the last 21 months would be a bit of an understatement. The Plugin System & the Blocks & Layouts Initiative have consumed much of my professional and personal time over that period, and we've worked on a lot of really awesome and interesting stuff. That being said, the vast vast majority of that work was still really "Drupal" and certain aspects of the underlying architecture that we were building on I didn't have the time to learn in detail.
In early February a gathering of developers came together in Acquia’s offices to decide the fate of the Drupal 8 initiative known as WSCCI (Web Services and Core Context Initiative).
You may have noticed the nice little g+ icon on the site, I've started using a Google+ Page to deliver and organize information about the Contextual Administration module I maintain. This is an interesting new use scenario for me, and I wanted to share what I'm doing and why.
For the past 2 seasons of camps and cons, I've been proposing some material that has taken a lot of its cues from page_manager and ctools. This has been a really hard road to follow because of the complexity inherent in these tools, and as a consequence, only the camps have really given me any real traction on my sessions. This has been encouraging in the sense that my camp sessions have been very well attended and have gone extraordinarily well, and discouraging in the sense that Drupalcon attendees have missed out on these sessions.
Page Manager (and family... i.e. Panels) is starting to get some more traction within our community. New users are finding it, using it, and asking awesome questions about it every day. I've done my part both from a development side as well as a teaching front to try to help that along as much as I can, and I'm very pleased with the fact that the community is beginning to find these tools and really appreciate what they can do. With that being said, I want to pedal some of my own page_manager based wares on those of you who might listen.
Recently, there has a been a LOT of discussion about the future of drupal core and some of its rather "legacy" modules. This is a good conversation to be having, however I think we are spending our efforts in the wrong place, or perhaps better, I think we have or priorities misaligned.