Blue Drop Shop: Drupal Camp Session Recordings: A Year in Review

Planet Drupal - Sat, 2016/05/14 - 5:46pm

It has been nearly a year since I’ve updated the status of my camp recording kits. Since DCSTL15, two other camps took me up on my proposal to sponsor my travel and hotel in exchange for me recording and posting their sessions: TCDrupal and BADCamp. And, of course, as a MidCamp organizer, that counts too. And with each those camps, I’ve iterated and learned from invaluable successes and failures.

First off, here is a link to the current kit.

With everything, each kit is still under $450. In addition, zip ties to hold the VGA to HDMI dongle tight and some gaffers tape to secure everything to the podium are needed.

Recap

At Twin Cities, I learned that, while I try, I cannot reasonably start and stop every recording in every room, especially at camps with five concurrent sessions spread over multiple floors and buildings. The amount of volunteer participation at TCDrupal is incredibly impressive. I had loads of help at my disposal, but only a few moments to outline how the kits work, so I spent a lot of time troubleshooting from room to room.

BADCamp is another camp that sprawls over a campus and is a bit looser on the room monitor support. So this time, I came armed with printed instructions at each podium for hooking up to the kit (link). I added some basic troubleshooting and my phone number. I missed about half the session starts, but speakers were mostly able to follow the instructions and run things without me. That was a huge win. Unfortunately, remembering to also start/stop the audio record was hit or miss.

By the time MidCamp rolled around, I simplified the instructions further and also set the backup audio record to just run all day, removing the failure point of missed audio. The big red button is easy and enticing. The little button on the audio recorder remote...not so much. MidCamp, with two days of four concurrent sessions was my first 100% captured camp since St. Louis.

Pain Points

There are four recurring issues with this setup:

  • VGA-only laptops
  • Recurring audio problems
  • File segmenting
  • Random projector problems

Hopefully, the time of laptops that only have VGA out is coming to an end. I've tried several different VGA-to-HDMI converters with basically no luck. And to spend hundreds of dollars or more for a fool-proof converter when modern laptops have better video output is a hard pill to swallow. I don't foresee this being a long-term problem.

The audio issues are baffling. In some cases, no audio at all is recorded with the screen capture, while other times it is sped up and choppy, hence the importance of the backup audio files from the voice recorder. But this means post-processing time which delays uploads. I intend to contact Hauppauge support, but honestly don't expect to get very far as I am using their device as it was not intended. Lastly, the capture device has a touch panel for adjusting gain and muting the audio. It is a little to easy to accidentally mute the audio.

Minor annoyance: occasionally, the recordings will split into two or more files, meaning I have to stitch them together in post.

At MidCamp for the past two years (both held at different locations on UIC campus), some of the projectors would intermittently go dark during presentations. While this has no impact on the recording, it is extremely unsettling for the presenter and annoying for the attendees. I recall this happening in some cases at Twin Cities, but not at BADCamp. So this one currently has me stumped with no good plan of resolution at this time.

Next Steps

For obvious reasons, I can't record all the sessions at all the camps. And already I have firm plans to record Twin Cities in June, St. Louis in September, and BADCamp in October. Talking to folks at Drupalcon, I also now have soft commitments with Drupal GovCon in July and Drupal Camp New Jersey in January. And other camps have reached out, but I have conflicts.

I managed to pack up a complete kit into a 10" Pelican case. This means that if I can start training some proxies and write up some detailed instructions and troubleshooting, then this solution can scale. Maybe folks won’t have experience with the post-production, but I can help with that remotely, if needed. The beauty of these kits is that with timely starts and stops and good audio, the MP4 file on the thumb drive can be uploaded as soon as it is collected.

The good news is that the more camps I can record, the more data I can collect and the more I can refine the process to make it scalable.

Stay tuned!

Tags:
Categories:

Drupal Association News: Hello, World! (Goodbye, Drupal Association)

Planet Drupal - Sat, 2016/05/14 - 2:06pm

My first day on the job, I got on an airplane and flew to Australia to attend DrupalCon Sydney. As first days on the job go, that’s gotta be up there as one of the best. It definitely set the tone for life in the Drupal community - it’s been an exciting adventure every single day. I’ve traveled around the world, worked with incredibly smart people, and learned four or five Git commands (thanks Cathy!).

So it’s not without some sadness that I share that my last day on this job will be June 3. Why am I leaving? Simply put, because I can. Drupal 8 is out and thriving. The Association is doing more and doing it better than it ever has. Now is the time for me to take a step back, eat some cake, and then find something new to jump into (after a nap, and probably some more cake).

Luckily, the Drupal community has an amazing individual ready to step in to lead the Association. I’m proud beyond words to see Megan Sanicki take on these challenges and work with you all as the next Executive Director of the Association. I know she will continue to build an Association that operates from its values for and with the Drupal community. We’ve been working together on this transition for a little while now, and I can’t wait to see what she does.

I just want to share a couple of thanks before I go. First, I’m deeply proud of the team that we have built at the Drupal Association. The Drupal Association staff are the rainbow unicorns of teams. They are honest about their opinions, but kind in their delivery. They are fierce in their loyalty to the community, and even more so in their loyalty to each other. They genuinely care about every interaction, and even when things go sideways, you can trust that their intentions were nothing but good. I learned from them. Every. Single. Day. I owe them a heck of a lot more than this thank you, but I wanted to get it out in the world. They are the best. Treat them well.

Secondly, I want to thank the dozens of community members who have gone out of their way to support me in this role. I’ll be following up personally with as many of you as I can, but I wanted to call out a few of you in particular. Angie taught me that introverts can learn to like hugs. George and Tiffany taught me to take my time and find the exact right words. Paul taught me that you can’t have too many passion projects. Donna taught me that it’s not summer everywhere. Cathy taught me Git (well, four or five commands that I can remember). There is so much generosity in Drupal.

The Association board and Megan will be working hard over the next few weeks on this transition to make sure that we continue to grow our support of the community, keep producing amazing DrupalCons, and ensure that Drupal remains the best darn CMS out there. I’ll be over here rooting for all of you. You’ll find me next to the cake.

Categories:

Radium on Drupal: Deploying Drupal Sites with Docker Compose

Planet Drupal - Sat, 2016/05/14 - 12:51pm
Deploying a Drupal site (or any website) could sometimes be cumbersome, in particular if you have multiple websites running on one server. The amount of time wasted in configuring the server could be considerable. Docker is one of the tools that can save us from the "configuration hell". Thanks to pre-built images, I no longer have to worry about dependencies since they can be all included in one image. Also, unlike virtual machine, Docker is fast and take only a few seconds to start. Another benefit is that now you can have the same environment on your local machine and on the server -- just use the same image. In this post I will quickly walk through the steps of using Docker Compose to deploy Drupal.
Categories:

ActiveLAMP: Encapsulation, Inheritance, Polymorphism with Drupal Entities - SandCamp 2016

Planet Drupal - Sat, 2016/05/14 - 5:01am

One of the best things to happen with the Drupal 7 release was the introduction of Entities. Drupal Entities have been around forever, but it seems like a lot of developers still refer back to using Nodes when creating content that requires more functionality than what Nodes give you out of the box. In this video, I talk about why it’s a good idea to create your own Entities when the content you’re adding requires extended functionality. I talk about the “what” and the “why” of Entities, not necessarily “how” to create an Entity. There are a bunch of resources already out there on the Internet for that. I talk about using the Entity API module, and defining your own Class for your custom Entities. This presentation was given at SandCamp 2016.

Read more...
Categories:

DrupalCon News: Let us know what you thought about the Con

Planet Drupal - Fri, 2016/05/13 - 11:49pm

Thank you so much for attending DrupalCon New Orleans.  We had an amazing time and hope that you did too.  

After each Con, we ask that you please let us know how it went so we can see what we can improve for next time.  Please

Fill Out the Survey

We also understand that you may be interested in receiving a Certificate of Attendance.  If so, please fill out the request form and we will get back to you shortly.

Categories:

tanay.co.in: Announcing www.d8cards.com - A simple Drupal 8 ladder for small study groups

Planet Drupal - Fri, 2016/05/13 - 8:56pm

At my workplace, we had earlier formed a study group to try out some very simple Drupal 8 stuff.

 

As we progressed, we had built a bunch of activity cards that we used for the group.

 

They are now available @ www.d8cards.com.

 

Check them out. Each activity card has a tutorial and an exercise that you could try out. There are 21 cards covering varied Drupal 8 Topics.

Categories:

Mediacurrent: Friday 5: 5 Tips to Integrate 3rd Party APIs

Planet Drupal - Fri, 2016/05/13 - 5:59pm

TGIF! We hope you've had a great week.

We're hot off the heels of DrupalCon but couldn't disappoint and skip this week. We give you, Episode 8! This Friday, Senior Drupal Developer David Younker joins us to discuss 5 Tips to Integrate 3rd Party APIs.

He provides some great tips for integrating 3rd party APIs and feeds in Drupal 7 sites. Watch the video below to learn more about Using Aggregator, Using Feeds, Custom Solutions, API Keys, and OAuth.

Categories:

Red Route: There's more than one way to Drupalise a cat

Planet Drupal - Fri, 2016/05/13 - 2:28pm

One of the components in the design is something I'm calling tiles - as always, naming things is one of the hardest parts.

The component includes an image with a transparent overlay, showing the title. On hover and focus, some extra information becomes visible. For instance, for a gallery, the address will be shown, and for an exhibition, the artists and tags will be shown. Here's a Codepen which gives you an idea:

See the Pen Tiles... by malcomio (@malcomio) on CodePen.

Different versions of this component are used in quite a few places. On an exhibition page, it applies to a teaser view of the gallery linked via a node reference field. In various views, it applies to the views fields. To get the markup right for the views fields, I needed to create a custom template. But I didn't want to create the same template for each view that needed to use the tile pattern - that would be a nightmare to maintain.

Having read about Twig template extends I was tempted to try them for this use case - it seems like an interesting new feature, so why not try it out?

I created an initial template called views-view-fields--tiles.html.twig, and then set the view template to use it. For instance, I wanted to apply this markup for the exhibitions_new view, so I created a template called views-view-fields--exhibitions-new.html.twig, which contained just one line:

{% extends "themes/gall/templates/views/views-view-fields--tiles.html.twig" %}

It seemed to work OK, but didn't seem like the right approach. For one thing, it would leave me with a theme cluttered with loads of one-line templates, which would get pretty annoying pretty quickly. For another, it felt like a gratuitous use of a solution - a hammer looking for some nails to bash.

The solution I went with in the end was much more familiar from previous Drupal versions, although it uses the new hook_theme_suggestions_HOOK_alter hook:

/** * Implements hook_theme_suggestions_HOOK_alter(). */ function gall_theme_suggestions_views_view_fields_alter(array &$suggestions, array $variables) { // Set up views to use the tiles template. $tiles_views = array( 'exhibitions', 'exhibitions_a_z', 'exhibitions_new', 'exhibitions_this_gallery', 'galleries_a_z', 'galleries_new', ); $view_id = $variables['view']->id(); if (in_array($view_id, $tiles_views)) { $suggestions[] = 'views_view_fields__tiles'; } }

For someone familiar with previous versions of Drupal, it's another thing which is similar but different. More to learn, and some things to unlearn, but we're not starting from scratch, and we can have more options in our toolkit.

Tags:  Drupal Drupal 8 The Gallery Guide All tags
Categories:

nielsdefeyter.nl: Watch Drupalcon Now Orleans sessions on Youtube

Planet Drupal - Fri, 2016/05/13 - 1:47am
As always the Drupal Association puts videe-recording of most sessions on DrupalCon Youtube. That is also true for the now ongoing DrupalCon New Orleans 2016. An excellent option for learning and understanding Drupal . (and following the event!) Recored video-sessions on YouTube Link DrupalCon New...
Categories:

Dries Buytaert: State of Drupal presentation (May 2016)

Planet Drupal - Thu, 2016/05/12 - 8:25pm

DrupalCon New Orleans comes at an important time in the history of Drupal. Now that Drupal 8 has launched, we have a lot of work to do to accelerate Drupal 8's adoption as well as plan what is next.

In my keynote presentation, I shared my thoughts on where we should focus our efforts in order for Drupal to continue its path to become the leading platform for assembling the world's best digital experiences.

Based on recent survey data, I proposed key initiatives for Drupal, as well as shared my vision for building cross-channel customer experiences that span various devices, including conversational technologies like Amazon Echo.

You can watch a recording of my keynote (starting at 3:43) or download a copy of my slides (162 MB).

Take a look, and as always feel free to leave your opinions in the comments!

Categories:

ThinkDrop Consulting: Onward with OpenDevShop Inc

Planet Drupal - Thu, 2016/05/12 - 6:27pm

Today I am awaking to the last "official" day of DrupalCon New Orleans with a huge new wind at my back.

It felt like an appropriate time to post what is likely my last blog post as ThinkDrop Consulting LLC.

My partners and I have been in a whirlwind tour of the convention, spreading the news of our product, and our new company: OpenDevShop Inc. In order to focus entirely on development and hosting tools, I am closing up ThinkDrop Consulting.

We've been building the OpenDevShop platform since late 2011 for my clients and myself, and in January of this year, we incorporated.

Our mission: to make hosting, testing, and scaling websites as easy as possible; to make infrastructure management as easy to deal with as content; and to foster a community around these types of tools.

OpenDevShop Inc is a member of the newly formed Aegir Coop. The cooperative is a group of companies and individuals who have organized together to support and develop the Aegir ecosystem.

We are working hard to not only grow this business but to grow the Aegir community, both users but especially contributors. We have a lot of work to do if Aegir is going to live up to modern expectations of infrastructure management and deployment tools.

Today we have two Birds of a Feather sessions back to back at DrupalCon: one for OpenDevShop and one for the Aegir Coop.

The energy behind the Drupal Community has never been higher. Let's follow in their footsteps and bring together everyone that cares about better Infrastructure Management and DevOps.

Come join the Aegir & OpenDevShop communities in room 292 (AshDay) from 1pm - 3pm, and maybe later if they let us stay.

Please check out our new company website, opendevshop.com.

We will see you around the community!

Tags: devshopPlanet Drupal
Categories:

LevelTen Interactive: Learn with LevelTen: DrupalCon Session Twitter Recap

Planet Drupal - Thu, 2016/05/12 - 4:50pm

The LevelTen team used the hashtag #learnwithl10 to document the various sessions they attended and what they learned on Tuesday and Wednesday of DrupalCon New Orleans.

...Read more
Categories:

DrupalEasy: DrupalEasy Podcast: New Orleans Day 1

Planet Drupal - Thu, 2016/05/12 - 4:50pm

Direct .mp3 file download.

Hosts Ryan Price, Mike Anello, Ted Bowman and Kelley Curry are joined by guests Mike Herchel (of the Lullabot Podcast) and Steve Edwards (formerly of the Acquia Podcast) to discuss the events on Day 1 of DrupalCon. We start with the Prenote and Driesnote, and then discuss sessions each person was interested in throughout the day.

Check in later this week for more episodes from DrupalCon New Orleans 2016.

Follow us on Twitter Intro Music

House of Drupalcon from #Prenote

By Adam Juran, Campbell Vertessi and Jeremy "JAM" Macguire

Subscribe

Subscribe to our podcast on iTunesGoogle Play or Miro. Listen to our podcast onStitcher.

If you'd like to leave us a voicemail, call 321-396-2340. Please keep in mind that we might play your voicemail during one of our future podcasts. Feel free to call in with suggestions, rants, questions, or corrections. If you'd rather just send us an email, please use our contact page.

Categories:

OSTraining: Drupal 8 CookieConsent EU Law module

Planet Drupal - Thu, 2016/05/12 - 1:53pm

One of are OSTraining members asked how to add cookie notification to a drupal 8 site.

The CookieConsent is a module provides a solution to deal with the EU Cookie Law.

And is particularly useful if you want to use the SuperCookie module

Categories:

Wunderkraut blog: Dropcat - the configuration files

Planet Drupal - Thu, 2016/05/12 - 1:26pm

In a series of blog posts I am going to present our new tool for doing drupal deploys. It is developed internally in the ops-team in Wunderkraut Sweden , and we did that because of when we started doing Drupal 8 deploys we tried to rethink how we mostly have done Drupal deploys before, because we had some issues what we already had. This is part 2.

The idea with dropcat is that you use it with options, or/and with configuration files. I would recommend to use it with config files, and with minor settings as options. 

You could use just use a default settings file, that should be dropcat.yml, or as in most cases you have one config file for each environment you have – dev, stage, prod etc.

You could use an environment variable to set which environment to use, this variable is called DROPCAT_ENV.  To use prod environment you could set that variable in the terminal to prod with:
export DROPCAT_ENV=prod

Normally we set this environment variable in our jenkins build, but you could also set it as an parameter with dropcat like:
dropcat backup --env=prod

That will use the dropcat.prod.yml file

By default dropcat uses dropcat.yml if youi don't set an environment. 

Thing will be more in the next blog posts, but first we now look into a minimal config file, in our root dir we could hav a dropcat.yml file with this config:

app_name: mysite local: environment: tmp_path: /tmp seperator: _ drush_folder: /home/myuser/.drush remote: environment: server: mytarget.server.com ssh_user: myuser ssh_port: 22 identity_file: /home/myuser/.ssh/id_rsa web_root: /var/www/webroot temp_folder: /tmp alias: mysite_latest_stage site: environment: drush_alias: mysitestage backup_path: /backup original_path: /srv/www/shared/mysite_stage/files symlink: /srv/www/mysite_latest_stage/web/sites/default/files url: http://mysite.com name: mysitestage mysql: environment: host: mymysql.host.com database: my_db user: my_db_user password: my_db_password port: 3306

The settings is grouped in a way that should explain what they are used for – local.environment is from where we deploy, remote.environment is to where we deploy. site.environment is for drush and symlinks (we use for the files folder), mysql.environment, is for… yeah you guessed correctly – mysql/mariadb. 

appname

This is the application name, used for creating a tar-file with that name (with some more information, like build date and build number).

local

These are the settings from where we deploy, it could be localy, it could be a build server as jenkins. 

tmp_path

Where we temporary store stuff.

Seperator

Used for i name of foler to deploy as seperator like myapp_DATE


drush_folder

Where drush-settings from you deploy from, normaly in your home folder (for jenkins normaly: /var/lib/jenkins/.drush), and this is also to which path the drush alias is saved on dropcat prepare.

Remoteserver

The server you deploy you code too.

ssh_user

User to use with ssh to your remote server

ssh_port

Port used to use ssh to your server

identity_file

Which private ssh-key to use to login to your remote server

web_root

Path to which your site is going to be deployed to.

temp_folder

Temp folder on remote server, used for unpacking tar file.

alias

Symlink alias for you site


Sitedrush_alias

Name of you drush alias, used from 'local' server. Drush alias is created as a part of dropcat prepare.

backup_path

Backup path on ”local” server. Used by dropcat backup

original_path

Existing path to point a symlink to – we use for the files folder

symlink

Symlink path that points to original_path

url

URL for you site, used in drush alias

name

Name of site in drush alias.


Mysqlhost

name of db host

database

Database to use

user

Database user

password

password for db user to host

port

Port to use with mysql

We are still on a very abstract level, next time we will go through that is needed in an normal jenkins-build.

Categories:

Wunderkraut blog: Dropcat - the configuration files

Planet Drupal - Thu, 2016/05/12 - 1:26pm

In a series of blog posts I am going to present our new tool for doing drupal deploys. It is developed internally in the ops-team in Wunderkraut Sweden , and we did that because of when we started doing Drupal 8 deploys we tried to rethink how we mostly have done Drupal deploys before, because we had some issues what we already had. This is part 2.

The idea with dropcat is that you use it with options, or/and with configuration files. I would recommend to use it with config files, and with minor settings as options. 

You could use just use a default settings file, that should be dropcat.yml, or as in most cases you have one config file for each environment you have – dev, stage, prod etc.

You could use an environment variable to set which environment to use, this variable is called DROPCAT_ENV.  To use prod environment you could set that variable in the terminal to prod with:
export DROPCAT_ENV=prod

Normally we set this environment variable in our jenkins build, but you could also set it as an parameter with dropcat like:
dropcat backup –env=prod

That will use the dropcat.prod.yml file

By default dropcat uses dropcat.yml if youi don't set an environment. 

Thing will be more in the next blog posts, but first we now look into a minimal config file, in our root dir we could hav a dropcat.yml file with this config:

app_name: mysite local: environment: tmp_path: /tmp seperator: _ drush_folder: /home/myuser/.drush remote: environment: server: mytarget.server.com ssh_user: myuser ssh_port: 22 identity_file: /home/myuser/.ssh/id_rsa web_root: /var/www/webroot temp_folder: /tmp alias: mysite_latest_stage site: environment: drush_alias: mysitestage backup_path: /backup original_path: /srv/www/shared/mysite_stage/files symlink: /srv/www/mysite_latest_stage/web/sites/default/files url: http://mysite.com name: mysitestage mysql: environment: host: mymysql.host.com database: my_db user: my_db_user password: my_db_password port: 3306

The settings is grouped in a way that should explain what they are used for – local.environment is from where we deploy, remote.environment is to where we deploy. site.environment is for drush and symlinks (we use for the files folder), mysql.environment, is for… yeah you guessed correctly – mysql/mariadb. 

appname

This is the application name, used for creating a tar-file with that name (with some more information, like build date and build number).

local

These are the settings from where we deploy, it could be localy, it could be a build server as jenkins. 

tmp_path

Where we temporary store stuff.

Seperator

Used for i name of foler to deploy as seperator like myapp_DATE


drush_folder

Where drush-settings from you deploy from, normaly in your home folder (for jenkins normaly: /var/lib/jenkins/.drush), and this is also to which path the drush alias is saved on dropcat prepare.

Remoteserver

The server you deploy you code too.

ssh_user

User to use with ssh to your remote server

ssh_port

Port used to use ssh to your server

identity_file

Which private ssh-key to use to login to your remote server

web_root

Path to which your site is going to be deployed to.

temp_folder

Temp folder on remote server, used for unpacking tar file.

alias

Symlink alias for you site


Sitedrush_alias

Name of you drush alias, used from 'local' server. Drush alias is created as a part of dropcat prepare.

backup_path

Backup path on ”local” server. Used by dropcat backup

original_path

Existing path to point a symlink to – we use for the files folder

symlink

Symlink path that points to original_path

url

URL for you site, used in drush alias

name

Name of site in drush alias.


Mysqlhost

name of db host

database

Database to use

user

Database user

password

password for db user to host

port

Port to use with mysql

We are still on a very abstract level, next time we will go through that is needed in an normal jenkins-build.

Categories:

d7One: How to print orders in Commerce

Planet Drupal - Wed, 2016/05/11 - 6:53pm

In this tutorial or guide, I will share the best solutions I found for two basic Drupal Commerce use-cases and delve into their respective setup.

Commerce Kickstart 2 (CK2) is a great distribution for setting up an online store; it packs a lot of goodies out-of-the-box. But it can't have them all. Printing an order to PDF is not included. So one has to do some R&D for that.

Categories:

Valuebound: Your First Step to Git

Planet Drupal - Wed, 2016/05/11 - 2:39pm

Hey! So you are here in this page trying to find/learn something about git! Have you used a source code management system to synchronize your local code remotely before? Do you know that Git is the most powerful SCM. I was convinced and yes it is!

I have actually started SCM with svn( Apache Subversion). In fact started with TortoiseSVN, a GUI tool for Windows. Here there are no commands, no need to remember, so, nothing to worry, Just right click on your web root folder and choose whichever option you need! Sounds easy?

If you want to go with SVN, you can refer these links.
http://www.tutorialspoint.com/svn/svn_basic_concepts.htm
http://…

Categories:

Virtuoso Performance: DrupalCon NOLA Tuesday call to action - migration sprints

Planet Drupal - Wed, 2016/05/11 - 3:33am
DrupalCon NOLA Tuesday call to action - migration sprints

Again, in the interests of timeliness I'll stick to a simple chronological wrapup of the day. And in the interests of of-course-everyone-cares-what-Mike-eats, I will continue subjecting you to my culinary adventures - breakfast at the Clover Grill in the midst of tourist land (Bourbon Street). Good, basic diner food - eggs over easy with bacon and hash browns, the primary goal here was to make it quick and get to the convention center in time for the prenote (which I have somehow never managed to rouse myself in time for at previous DrupalCons).

And, as always (by reputation), the prenote was an extravaganza hosted by jam. So much energy on the stage, so many songwriters calling their lawyers... Highlights were Gábor unveiling a sweet, soulful voice, and the epic Code of Conduct song (performed 1.5 times, so no excuses for not getting it down).

That brings us to - ta-da! - DriesNote. As always, a lot of information presented succintly - I'm sure others will cover many of his points, so I'll focus on my special interest - migration. In Dries' annual survey, site builders identified migration tools as their biggest need for Drupal 8, and he called out the Friday migration sprint.

Sprint all the migrates!

So... let's see how much progress we can make on core migration issues this week! Important things to note:

  1. You don't have to wait for Friday. The Sprint Lounge (rooms 275-277) is open every day. And, while as usual I checked off many, many sessions I'd like to attend, after sitting in a couple today where (through no fault of the presenters) I was mainly thinking about migration, I'm going to try to spend significant time every day (right up through Sunday morning) sprinting.
  2. You don't have to be in New Orleans! You can help remotely - drop into the #drupal-migrate IRC channel, or just pick issues from the core queue and dive in on your own.
  3. You don't have to know the migration framework - there are various ways you can help out (see below).

We already have 10 people officially signed up for migration sprinting (between the core and multilingual lists), so (particularly with more people joining) we can afford to split into multiple sprint teams:

  • Backwards-compability breakers - try to address any issues that may affect backwards-compability, so migration implementors will be able to count on a stable API from 8.2.x forward. This was my priority coming in, and you'll find triaged issues on the Sprint triage tab of the Migration sprint spreadsheet.
  • I18n issues - penyaskito is already leading a migration sprint in this area - it overlaps with the BC-breakers on the epic Migrate D6 i18n nodes issue.
  • Migrate criticals - note that this overlaps some with the BC-breakers (the BC-breaker list has its migrate-criticals listed first), so look for issues not already covered there.
  • UI issues - Abhishek Anand, who did some of the work on the UI in contrib, will lead efforts to clean up remaining issues in core. He'll be in the sprint room Wednesday morning, as well as most of the day Friday, and you can also coordinate with him outside of those times (or if you're not here).
  • We have a lot of issues at the Needs review stage - let's see how many we can get to RTBC, or give constructive feedback, so we can move forward on stuff like node and user references.
Specifically, how can I help?
  • If you're at DrupalCon NOLA, come to the sprint room (275-277) any time Wednesday-Friday - I'll try to get there early and reserve a table just for migration. There are a couple of sessions I definitely want to catch, but I should be there for most non-lunch time, and there should generally be others there (especially Friday) when I'm not.
  • If you're remote, you can announce your presence in #drupal-migrate on IRC. Or just pick an issue to work on.

Either way, please put your name under "Who's working on it" in the spreadsheet so we don't duplicate effort (multiple people can be involved in one patch, but should coordinate).

Ways to help on a specific issue:

  • Write a patch (or discuss approaches to a patch) where there is none yet.
  • Review an existing "needs review" patch.
  • Manually test a "needs review" patch - set up a patched D8 environment and try running your site through the migration process (we'll give some help on setup here).
  • Add tests to a patch tagged "Needs tests".
  • Help solve any outstanding issues on a "needs work" patch.
  • Any other ideas you might have...

 

 

mikeryan Tue, 05/10/2016 - 20:33 Tags
Categories: