Migration contribution catch-up plan

Well, what with an increase in client work and a move halfway across the country (Somerville Mass to Murphysboro Illinois), I'm afraid I've fallen further behind on the issue queues for migrate, migrate_d2d, and wordpress_migrate. It's been a bit of struggle to triage the queues, so to somewhat automate the which-issue-to-work-on-next process, I'm reducing it to an algorithm (each step of which will be applied to migrate, migrate_d2d, and wordpress_migrate in that order).
  1. Bug reports with patches (needs review, rtbc), oldest to newest
  2. Other bug reports, oldest to newest
  3. Other issues with patches (needs review, rtbc), oldest to newest
  4. Triage of support requests to make sure no bugs are lurking there
At that point, I plan on cutting release candidates for all three modules. Hopefully at that point I'll be able to start doing a better job of responding to new issues as they come in. Hard to say when I'll have a chance to review and respond to older support and feature requests, though, it'll depend on my workload (but of course I'm not the only one in the community capable of helping out with support requests - hint hint). Thank you. Edit: Let's keep track of where I am... I'll also note that not all issues will necessarily get committed/closed, there will be some triage as I go along and not everything will make the cut for Migrate 2.6 and the corresponding migrate_d2d/wordpress_migrate releases.
  1. Bug reports with patches, migrate

Drupal 6 to Drupal 8 migration completed! (mostly)

Just had to share this major milestone - 10 minutes ago (as I type this, not as I publish it) I performed the first complete* migration of my Drupal 6 site into my Drupal 8 development environment (running the ui_poc branch of the IMP sandbox, plus a few patches to be submitted/committed). * "Complete" meaning all user accounts, nodes, comments, and files (including image references within nodes) were migrated - plenty of details yet to be worked out. Here's a shot from the D8 homepage: Yes, clearly there's a timezone issue to deal with in importing the dates...

Updates on Migrate and my site

I've been quiet for a while, so some updates. First off, this site. As part of the IMP initiative to add the Migrate framework to core in Drupal 8, supporting the upgrade process from 6 and 7, I plan on spinning up a Drupal 8 version of this (currently Drupal 6) site and start running migrations from my live site into it. I will also try to increase my frequency of posts here to help provide some more content for that migration - while my more formal and substantive Drupal-related posts will continue to appear on acquia.com, I'll be adding more personal posts (vacation photos! Everyone loves those!) and maybe some lower-bandwidth Drupal commentary (in particular updates on the migration effort for mikeryan.name). Speaking of IMP (and vacation photos) - I was off on a 2-week vacation with my wife in mid-March, and naturally have been catching up on customer projects since returning, so haven't contributed for a few weeks. chx and team have continued to make great progress, in particular getting a massive update of the sandbox work on the underlying API committed to core. I should be more active in the IMP effort in the coming months.

Soft launch - Colloquy customization

It's been a good long time, but I will be ramping up the activity here shortly as I work on IMP (Migrate in Drupal 8 core). I'm spending more time in #drupal-contribute and decided to finally go back to Colloquy as my client. The first thing I wanted was to shut up the enter room/leave room/change nick messages, but it's not something customizable through the UI - didn't take long to find it in the FAQ, a little CSS goes a long way. The next thing was to make the scrollback mark more prominent. It took a little digging, but I found the foundational CSS for Colloquy at Colloquy.app/Contents/Resources/default.css. Here's what I added to My Variant.css to get a mark I couldn't miss:
hr#mark {
	width: 95%;
        height: 2px;
	border-color: #ff0000;
        background: #ff0000;

Drupalcon summary

This may be slightly out of order, since I've still got a ways to go in blogging my notes on the specific sessions I attended at Drupalcon, but I want to get my overall thoughts and impressions out as quickly as possible.

First, expanding on my comment on Drupal.org - I'm re-entering the Drupal community after some time away, and it feels so right... There are some acknowledgements I need to make:

First and foremost, my significant other SIGNIFICANT Other, Sarah Richards, has been supportive above-and-beyond of the time I've spent Drupaling on top of my day job (and of the constant whining over how little time I have left to do all the other things I want to do). I hope her patience continues, because I have a lot of catching up to do in the Drupal world. And I hope some non-profit working on progressive change out there can use an anthropologist with project management experience (contact me if you can...).

Drupalcon Day 1 continued

I made a stab at live blogging with the usability session, but I think it will work better for me just to jot down the random points that particularly strike me at the time, and fill in more thoughts later. Hopefully most if not all sessions will be on video, so there's no need to be a scribe...


I'm pleased to announce that I am joining Moshe Weitzman in Cyrve. Our specialty is content migration and transformation - the grunge work of fitting old information into new holes.

Past projects of mine

XML -> Mobile-compliant XHTML

I produced a mobile-compatible website for delivering 2008 U.S. Presidential election results to hand-held devices. This involved modifying the Drupal FeedAPI module (at that time still in beta) to read custom fields in addition to standard RSS fields (patch submitted).

As a follow-up project, in two days I created a system to take XML feeds of raw election data and produce mobile-compatible XHTML pages to present the results, for live updates on Super Tuesday. This system included a templating system so the client could easily style it to their own needs (they reported it took half an hour with my delivered system to complete the theming and customization), and has remained in operation through subsequent primary elections.

Boston Drupal Meetup

Excellent meetup last night. The stuff I actually thought to jot down:

My Lightning Talk was on my collaborative knowledge base project at the day job. The Node Auto Term (NAT) module was pointed out as an potential substitute for the book module.

David mentioned an issue he has having with Automatic Nodetitle (the string "0" turning into a null) - it uses the Token module, which I've just signed up to co-maintain along with pathauto, so I want to take a quick look at that (if I can squeeze another ten minutes out of the next couple of weeks...).