Last month at DrupalCon Portland, I was honoured to receive the Aaron Winborn Award, named after one of Drupal’s most kindhearted and prolific contributors, who we lost far too soon to ALS back in 2015. (If you were not lucky enough to know Aaron, you can read more about him through many others’ words in his Community Spotlight)
What the what?!
Sad Drupal is Sad. :'(
Well, might as well get right down to it... I've made the incredibly difficult decision to leave Acquia, and my employment there officially ended last week. :'(
Some important notes about this:
- This is in no way a negative reflection on Acquia. I have worked with SO many amazing people there in the past 10 years(!), and have endless gratitude for all of the challenges, opportunities, learning, and laughs. The leadership team has a solid strategy, and the effort everyone there puts into achieving it every day is inspiring.
- This is in no way a negative reflection on Drupal. In my time here, I've seen Drupal through its youthful toddler years, to its surly teenage years, and now Drupal's all grown up, with a nice, stable apartment downtown. :) Drupal is and remains an amazingly powerful, flexible solution for building every single type of application one can dream of, with an incredibly strong and vibrant community behind it.
- What this is about is about an opportunity that came up to take lessons learned from Drupal and apply them more broadly to (hopefully) make an even bigger impact (more on that below).
- Also, I'm not leaving the Drupal community (more on that below too), and will stay on as Core Committer/Product Manager, albeit with less time than I used to have to dedicate to it, for rather obvious reasons. (This is ultimately a good thing, as it'll direct that time towards more strategic/impactful endeavours.)
These days, my life is all migrations, all the time, which means I often need to run Drupal 7 and Drupal 9 sites side-by-side simultaneously to compare the results.
The latest version of Drush, Drush 10, only works on Drupal versions 8.4+. To use Drush on Drupal 7 sites, you need an older version, Drush 8. And both of them use the command
There are various Drupal-knowledgeable local development environments, such as Acquia Dev Desktop, Lando, DDEV, and Drupal VM that handle this complexity for you, which is super handy. However, the rest of my team uses a "from scratch" local development environment on Mac OS X, so I needed to figure out how to do this by hand.
I made a Twitter inquiry if there was an existing tutorial on how to do this, and since I couldn't find one, here it is. :) Hopefully this helps others, as well! (Thanks to those who responded, pointing me in the right direction!)
Wow, it's been awhile since I blogged, apparently. :P This is not a proper blog, but rather a random smattering of notes I'd rather not lose. Maybe it's helpful to others as well!
Today, my daughter's teacher sent around some resources to facilitate home schooling over the next while. Here are the steps I went through to take my iPad (which I won at gay bingo in a unicorn onesie back in the day lol) to my kiddo's iPad.
We'll be spending the day removing deprecated code from Drupal 8 contributed modules to get them ready for Drupal 9.
Here's how you can participate! (Whether in-person or remotely!)
- Pull up the getting started info at https://tiny.cc/d9readiness and get set up with the drupal-check tool to check your code for deprecations.
- Join the #d9readiness channel on Drupal Slack.
- Check the list of issues tagged Drupal 9 compatibility + Seattle2019 (or use your own module!)
- Fix 'em and upload a patch! There are tips and tricks on the most common ones at https://github.com/mglaman/drupal-check/wiki/Deprecation-Error-Solutions, and the list of change records have the full details for any given change.
If you're a module developer who would like to "opt in" to having your module reviewed / patched by a new contributor at the sprint, please create (or find an existing) issue with the Drupal 9 compatibility + Seattle2019 tags!
Want to see the progress? Here's a contrib kanban overview!
For DrupalCamp Belarus in mid-May, I'll be giving a talk entitled "Tales of Drupal Past: Origin Stories of Drupal Contributors." My goal is to feature folks from the Drupal community and share their stories of coming into Drupal, with the goal to help inform and inspire others about our community, coming from a wide range of diverse perspectives/backgrounds.
How about... YOU? What were you doing before Drupal? How'd you get your start? What are you doing now? How has Drupal changed/impacted your life?
I would really appreciate any responses, whether in the comments here, on your own blogs, and/or on social media (with the #DrupalOriginStories tag, please). (Especially if you're based in Eastern Europe, I would love to hear from you!)
I can share mine, as a start... (Feel free to make yours shorter than this, however! :))
Greetings, folks! As we head into feature freeze for Drupal 8.6 (the week of July 18), here's a run-down of the various initiatives, and a hit-list of what they're trying to accomplish in the next two weeks. Patch reviews, testing, design, docs, and many more skills are very welcomed!
A couple of caveats here:
1) This is my own personal best understanding of where this stuff is all at, based on reading issue comments, attending meetings, overhearing things from other people who attended meetings, catching the odd Slack snippet of conversation, carrier piegon, etc. And therefore may not be 100% accurate, or even 80% accurate — there's a lot going on! (please clarify in the comments if you see any errors/omissions)
2) Just because something is listed here, there is absolutely no guarantee that it gets reviewed + (truly) RTBCed + committed in time for feature freeze and makes it into 8.6. As you can see, there are lots of issues in the list below, and we're all doing our best to stay on top of them. Worst-case, there's always 8.7. :)
3) This post gets into nitty-gritty "technical audience" details; if you're interested in a more broad overview of initiatives and their aims for 8.6 and beyond, there's the strategic initiatives overview on Drupal.org. I was also recently on a Lullbabot podcast to that effect.
OK, here we go! These are listed in alphabetical order.
In recent weeks, I've seen a whole lot of FUD regarding the Drupal Community Working Group, and what it is they do or don't do. While I no longer serve in the CWG (I stepped down from all "extra-curricular" Drupal activities back in 2015 to focus on my family), most of the portrayals I've read are misinformed at best and completely inaccurate at worst. So, as an ex-member, who was uninvolved in recent events and therefore can perhaps speak more freely(?), I’d like to try and clear up a few misconceptions I've seen.
I have a friend looking for subsidized housing in and around Vancouver. BC Housing keeps listings at http://www.bchousing.org/Options/Subsidized_Housing/Listings but the data is all shackled up in PDF files as simple lists. There's no easy way to visualize where these properties are located within the city, and no easy way to search/filter for places that, for example, allow pets.
My Twitter timeline has been blowing up with news about Greece's decision to turn down a referendum that would accept debt relief coupled with severe austerity measures. I could find article after article after article explaining why voting "no" on this referendum was a terrible idea. However, since 61% of a country can rarely agree on their favourite kind of ice cream, let alone something with this level of economic magnitude, I was curious to learn what the "other side" of the story was.
So I posted the following to Twitter: