As I wrote in my last blog post, I'd like to try doing regular sprint days for Drupal 8 migration. These will be a bit more informal than than a conference sprint - basically, a day when anyone interested in helping move the migration system from its experimental status to a fully supported subsystem of Drupal core can show up in #drupal-migrate, or just pick a relevant issue and start working on it. Our theme for at least the first of these sprints is migrate-critical issues - these are issues for the migration system which would be marked critical if the system were full supported, and thus our highest priority to address. Some issues need code written, some need tests written, some could use code review and/or manual testing, and some need discussion around the best approaches - there are multiple ways to help out.
If you're interested in contributing to the sprint, on Monday May 23:
- Check the triaged list of issues - if you find one you'd like to work on, add your drupal.org username under "Who's working on it". The fact that someone is doing work on a given issue doesn't mean you can't help too - virtually any issue without a stable patch could use input and suggestions, and any issue with a patch could use review and manual testing.
- Join #drupal-migrate on IRC. Get help selecting an issue to work on, coordinate with others on a given issue, ask general migration questions (or answer them!), ...
- If writing or testing code for a given issue, pay attention to which Drupal core version the issue is filed against (generally it'll be 8.1.x for bug fixes, and 8.2.x for new work) and be sure you pull the correct core branch to work against.
I expect to be available in #drupal-migrate for most of the time from around 9am to (at least) 6pm U.S. Central time (minus a lunch break). You can expect to find other people with migration expertise there at most times, of course.