Feed aggregator

Making The Most Of Mobilegeddon

Drupal Fire -

Lullabot (via DrupalFire)

On April 21, 2015, Google rolled out a set of changes to its search algorithm so sweeping it dubbed them "Mobilegeddon." Together, these updates dramatically boosted the impact of a site’s "mobile-friendliness" on its search rankings. Google says the changes will have "significant impact in our search results", though at least for now it only affects search results on mobile devices.

Making The Most Of Mobilegeddon

Lullabot -

On April 21, 2015, Google rolled out a set of changes to its search algorithm so sweeping it dubbed them "Mobilegeddon." Together, these updates dramatically boosted the impact of a site’s "mobile-friendliness" on its search rankings. Google says the changes will have "significant impact in our search results", though at least for now it only affects search results on mobile devices.

Chromatic: Testing Recurly Webhooks with ngrok

Planet Drupal -

In our last post about Recurly, we gave you a primer on setting up the Recurly module in Drupal. However, if you need to thoroughly test your Recurly integration on a local environment, you’ll want to test the webhooks as well. Webhooks in Recurly are interchangeably called "push notifications." From the Recurly documentation:

Recurly can send webhooks to any publicly accessible server. When an event in Recurly triggers a webhook (e.g., an account is opened), Recurly will attempt to send this notification to the endpoint you specify.

We’ve used a service called ngrok to help set this up. Ngrok is a service which allows you to create secure tunnels to your localhost.

You’ll need:

Setting up ngrok
  1. Create an ngrok account: https://ngrok.com/

  2. Download ngrok: you can download and extract it (https://ngrok.com/download) or use a package manager. On Mac OSX, brew cask install ngrok worked for me. This installed it into my applications folder, so I could just use ngrok as the command instead of ./ngrok. See this post for details on brew cask.

  3. Once you can run it per the instructions on the download page, you’ll need to do a one-time setup with your auth token. Here’s where we do things a little differently. We need ngrok to receive our webhooks from Recurly.

  4. Start the ngrok public tunnel with HTTP AUTH and Host header rewrite set to your local development instance name:

./ngrok http -host-header=yourlocalinstance.dev -auth="username:password" -subdomain=your-recurly-subdomain 80

a. yourlocalinstance.dev is the path to your local instance.

b. the username:password is made up by you to authenticate webhooks.

c. your-recurly-subdomain is easiest to find in the address bar when logged into Recurly, you also need this to set up the Recurly module.

  1. You should now see something like this in your shell:
Setting up Drupal
  1. Now we need to get the Drupal side of Recurly set up to receive the webhook notifications. Go to config/services/recurly in your local instance.

  2. Under "Push Notification Settings," you’ll see the Listener URL key. It’ll be something like yourlocalinstance.dev/recurly/listener/USD. Take note of this if you change it from this default.

Connecting ngrok to Recurly
  1. Now that we have ngrok set up, we need to set up the Recurly side to send the webhook notifications to the right place. Log into Recurly, and head to Developer>Webhooks on the left hand side, or configuration/notifications/configure.

  2. Your Webhook URL should be the url you generated in your shell with the ngrok command, with the Listener URL Key you noted in your Drupal settings appended to it.

  3. The HTTP username and password are the username:password combination you used to start ngrok.

You should be all set up now. All webhooks will be sent to Webhook URL, which is using ngrok. ngrok is forwarding those requests to your local instance. Go ahead and make a change to a user’s subscription (or somewhere else you’re using Recurly’s webhooks) and take a look. You should see the requests coming through your shell:

And you can also inspect them in your browser at http://localhost:4040/inspect/http:

That’s it! While ngrok is running, your local instance and Recurly can now communicate through webhooks, so you can test everything as though it were on your production server.

Introducing OpenAerialMap

Drupal Fire -

Development Seed (via DrupalFire)

Today we’re releasing a beta version of OpenAerialMap. OpenAerialMap makes it easy to share and find open satellite and drone imagery. This is critical to the work of the disaster response community. We are launching this tool in close partnership with the Humanitarian OpenStreetMap Team (HOT).

OpenAerialMap is a set of tools for searching, sharing, and using open satellite and drone imagery. This initial release includes the core infrastructure to catalog petabytes of open imagery. It also includes an extremely usable API and an elegant web interface to submit, search and download available imagery.

Search for available imagery.

Select scenes by grid.

Preview imagery and get metadata information.

Rebooting a great concept

The OpenAerialMap concept has bounced between several attempts over half a decade. Previous attempts failed to take off. HOT reinitiated the concept this year with funding from the Humanitarian Innovation Fund. We worked with the HOT and others in the open imagery community to reimagine an approach to OpenAerialMap that we expect to be much more successful.

  • We focused on simple, usable toolset that meets the clear needs of the humanitarian response community. The underlying architecture is flexible enough to be immediately useful to research, resource management, urban planning, and other communities. However, we decided to first build a frictionless interface for the clear needs of the disaster response community.
  • We are extremely focused on community. From day one, we involved other organizations and developers like Azevea, Planet Labs, Cadasta, OpenDroneMap and HOT’s own developers.
  • With these and other groups, we reimagined OpenAerialMap along a network model. Rather than try to house all the open imagery out there, OpenAerialMap is a node and index for a larger network or open imagery - the Open Imagery Network.

A network approach to open imagery

Open Imagery Network (OIN) is a simple framework and license for placing imagery into an open source license. Participants in the OIN adopt a common metadata scheme to describe the imagery they are making available, and standardized ways to broadcast and access that data. This allows us to build tools that search across all open imagery data without requiring one entity to host all of it. We’re working with HOT, Planet Labs, Cadasta, Azavea, OpenDroneMap, and others to develop OIN and to build OpenAerialMap as the first node in that network.

Your feedback

Community input is critical to the development of OpenAerialMap. Let us know what you think about the beta version and send us feedback on Twitter or open an issue on Github. We’ll work to add functionality and features toward an initial release candidate later this summer.

Hook 42: DrupalCon LA - A Few of Our Favorite Things

Planet Drupal -

DrupalCon is a wonderful experience (even if it's in downtown LA!). We come together as a community to learn and share and have a fun time. The Hook 42 team grew a bit from last year and was fortunate to have 8 team members in LA. We had a great time and wanted to share some of our highlights with you.


Downtown LA from rooftop. Photo credit: Kristen Pol.


As usual, there were tons of great keynotes, sessions, BoFs, and sprints. The keynotes and sessions were recorded so check those out.


Having fun at the Dries Q&A. Photo credit: Paul Johnson.

Aimee's Favorite Session/BoF

So many… but basically all things Drupal 8. :) Schnitzel’s application of Drupal 8 in production, Matt Cheney’s review of the D8 CMI in a managed workflow was informative and thought provoking, and of course MortenDK’s Drupal 8 Theming with <3. I did love the Princess Cruises case study since it is a wonderfully complex but elegantly deployed combination of multilingual workflow, services, and content syncing. Their team did an amazing job!

Kristen's Favorite Session/BoF

The "hallway track" was strong at this 'con for me. I only went to two BoFs (one was Aimee's D8 multilingual workshop and the other one was multilingual therapy) and one session (my own multilingual D7 talk). So… I guess my favorite organized non-party thing was helping at the sprints on Friday! :)

Tom's Favorite Session/BoF
  1. Estimation - A science not an art
  2. Building Your (Drupal-based) Business: Or... What Keeps You Up At Night?
K2's Favorite Session/BoF

My favorite session was MortenDK’s Drupal 8 Theming with <3. He’s fun to watch and got me really jazzed to use twig in Drupal 8.

Darryl's Favorite Session/BoF

I really enjoyed Jeff Eaton’s Battle for the Body Field, but I cheated by watching it after I got home. I learned about Entity Embed module, for which I think I’m going to find a lot of use!

Lindsay's Favorite Session/BoF

The winner is … CI for CSS: Creating a Visual Regression Testing Workflow. Wow, that’s a mouthful of a title, but quite an informative session. Lots of great things to know that were presented clearly. Thanks for the great session by Kate Kligman.

Patrick's Favorite Session/BoF

I greatly enjoyed the “I Survived Drupalgeddon” session by Matt Korostoff. It was a fun personal story of how hackers invaded his site, what happened after they did, and how one can prevent it from happening to their site.

Genevieve's Favorite Session/BoF

My two unrelated favorites were - 1) Designing for Brains: The Psychology of User Experience & 2) How to Run a Drupal Agency.


There were some really fun tshirts and swag in LA. We brought two new designs of our own (California Drupalin' and It Takes a Village), thanks to the very talented artist, Joe To, along with some previous favorites including Drup Oil, Features Reaper (happy version), and Multilingual Drupal to fill out our growing number of awesome doodles. Going to camp or con and want some swag? Ping us to see if we'll be there. ;)


DrupalCon LA monkey hats from Mailchimp were a big hit. Photo credit: Paul Johnson.

Aimee's Favorite Tshirt/Swag

Four Kittens v2! Backdrop DRAGON! Pantheon’s I BUILD THE INTERNET, LA edition! Hangover helper survival kits!

Kristen's Favorite Tshirt/Swag

Monkey hat is super cute and the Backdrop dragon but I think my kids liked the backscratcher the best… makes for a good extra hand.


Mom… I can scratch your back! Photo credit: Kristen Pol.

Tom's Favorite Tshirt/Swag


K2's Favorite Tshirt/Swag

My favorite T-Shirt was the monkey hats from Mailchimp, wa hoo! I just wish I had gotten a picture of Lindsay in it!

Darryl's Favorite Tshirt/Swag

What am I supposed to do with a hockey stick? I did get another Jet Brains PHPStorm yo-yo, which I do play with.

Lindsay's Favorite Tshirt/Swag

Definitely the Backdrop sticker. I mean, seriously, look at this dragon. So cool.


Backdrop's Dragon Drop is pretty darn cute. Image credit: Backdrop Press Kit.

Patrick's Favorite Tshirt/Swag

My favorite shirt was the Golden State Warriors Tshirt that had Pantheon’s logo on the back. Apparently they bought the Golden State Warriors Tshirt right down the street of their SF office and just added their logo to the back!


Not sure if great food is what comes to mind when going to LA like it did for Portland or Austin but we still managed to get in some good eats.


Pantheon partner dinner at the Palm. Image credit: Kristen Pol.

Aimee's Favorite Food

The Original Pantry for the early-risers breakfast with Darryl and the 2 am post-party breakfast for the night owls. Yay for 24 hour comfort food!

Kristen's Favorite Food

Who needs words? This was my dessert at Local Table.


Local Table has pastry chef who makes masterpieces. Image credit: Kristen Pol.

Tom's Favorite Food

Grand Central Market

K2's Favorite Food

My favorite meal was the Hook 42 dinner at what I will refer to as “the home cooked hipster joint in Hollywood.” So much fun to just be us all together - it felt like family.

Darryl's Favorite Food

I had breakfast 3 times at The Original Pantry. It was right on the way, and I was always there a bit ahead of the crowd, so I never had to wait. I think that’s one more time than I ever ate there in the 33 years I lived in LA (well, in The Valley, so, not very convenient).

Lindsay's Favorite Food

That filet mignon at the Pantheon dinner. Like butta.

Patrick's Favorite Food

My favorite food was the Guinness vanilla ice cream float I received at the Hook 42 dinner because it was an efficient way to drink and eat at the same time.

Genevieve's Favorite Food

What K2 said. So tasty.


DrupalCon is all about the people! We love seeing our old friends and meeting new ones. We <3 the community. :)


DrupalCon LA mentors. Photo credit: amber_is_i.

Aimee's Favorite Person

ALL THE PEOPLE! It is wonderful to see the extended family of community members. Schnitzel, Ryan Weal, YesCT, and more! Patrick Storey and Lindsay Gaudinier were two shining examples of a successful second DrupalCon. Patrick was heavily engaged with mentoring and volunteering and Lindsay dove in deeply to the front end technical sessions. Austin + community + practice + LA is a great springboard for success.


Patrick mentoring the new recruits. Last DrupalCon he was a recruit! Photo credit: Kristen Pol.

Kristen's Favorite Person

Tough one! Was nice to finally meet Damien McKenna in person and see his rabbit ears.


Gotta love them ears! Photo credit: Kristen Pol.

Tom's Favorite Person

Were there people there?!?

K2's Favorite Person

I didn’t have a standout favorite, but I can note that I feel like this time I really knew a lot more people and felt like part of the Drupal community. Wave to all!

Darryl's Favorite Person

I had a great time playing “Germanic Ping Pong” with the Amazee Labs folks at their party! (Yes, I know they’re Swiss, but I learned this game in Germany…)

Amazee Labs ping pong party including Germanic ping pong. Video credit: Kristen Pol.

Lindsay's Favorite Person

Ryan Weal. Him, K2 and I hung out in the coders lounge and it was tons of fun.

Patrick's Favorite Person

I’ll say Amy Vaillancourt-Sals. First off, great name! She came to the Mentor Core Sprint where I was mentoring and I showed her how to re-roll a patch. Then a couple hours later I saw her pushing the “return” button on Dries’ computer for the Live Commit! And I was able to think to myself “I knew her before she was famous”.

Genevieve's Favorite Person

It was my first DrupalCon - so everyone was new and interesting!

Social Event

The social event calendar was extra packed for LA. We couldn't get to everything but did what we could. Too many fun things, too little time! ;)


Pantheon Party. Photo credit: Kristen Pol.

Aimee's Favorite Social Event

The Pantheon party. Hands down. Thank you, Pantheon!

Kristen's Favorite Social Event

Ok, this one was tough. You know bubble wrap? Addicting, right? Well… try one of these ping pong ball collectors when you have a room of crazy Drupalers hitting (or dumping!) balls to the floor at an amazing rate. OCD heaven! On a more relaxing note, I had a wonderful soak in a hot tub with K2 instead of going to trivia night (first one I've missed!)... that was a relaxing type of heaven (with lightning to boot).


Kristen Pol on duty at the Amazee Labs ping pong party. Photo credit: Amazee Labs.

Tom's Favorite Social Event


K2's Favorite Social Event

Without a doubt the big outdoor party that Pantheon threw - amazing!

Darryl's Favorite Social Event

The Pantheon party and the Amazee Labs parties were both great!

Lindsay's Favorite Social Event

The outdoor Pantheon party. There was dancing and the nicest porta potties ever.

Patrick's Favorite Social Event

Definitely the L.A. Live Pantheon party. Shut down a street in one of the biggest cities in the world? Sure, why not!

Genevieve's Favorite Social Event

You can never forget Ping Pong!


K2, Patrick & Genevieve at the Amazee Labs ping pong party. Photo credit: Amazee Labs.

Weird/Strange LA Thing

No matter where you go, there's gotta be something weird. Here's some interesting things we came across in Los Angeles.


Not sure really what this is but it was in Kristen & Kristin's airbnb. Photo credit: Kristen Pol.

Aimee's Favorite Weird/Strange LA Thing

On Google Maps, the “Urban Core” was called Skid Row. Every time I searched for directions, the late ‘80s metal music played in my head.

Kristen's Favorite Weird/Strange LA Thing

Our Airbnb was pretty eclectic. There were steampunky things adorning the surfaces and artsy things on the walls and even super heroes hanging from the bathroom ceiling.


This punk was protecting us from a good vantage point in our Airbnb. Photo credit: Kristen Pol.

Tom's Favorite Weird/Strange LA Thing

How could the LA downtown “Urban Core” have fewer cars than San Francisco? It’s LA. Car town.

K2's Favorite Weird/Strange LA Thing

Fruit on the street with chili and salt on it. Yum! Also the crazy amount of shutdown theaters in the area we stayed. Who knew LA had such beautiful architecture downtown.

Darryl's Favorite Weird/Strange LA Thing

The coded magnetic door lock keys to our AirBnB apartment were kind of weird. Insert the key into the lock, wait until the lock mechanism activates, then turn. And you had to turn it to the right to unlock the door.

Lindsay's Favorite Weird/Strange LA Thing

All of the dogs out for walks in the morning! I wanted to pet every single one! [Cue Oprah] You get a dog, and you get a dog, everyone gets a dog!

Patrick's Favorite Weird/Strange LA Thing

Apparently between 9-11pm it’s dog walk o’clock. You will not see any dogs all day, and all of a sudden everyone is walking dogs everywhere downtown.

That’s a wrap!

Thanks to the Drupal Association and all the volunteers for making DC LA a huge success. Please leave a comment with some of your favorite things! And… see you in L.A. again… this time as in Lousiana. :)


In case you didn't see enough photos…


Mentor dinner at Local Table. Photo credit: Kristen Pol.


Darryl hanging out with Schnitzel. Photo credit: Amazee Labs.


Aten+Kalamuna+Four Kitchens bowling party. Photo credit: Kristen Pol.


Pantheon pinball party. Photo credit: Kristen Pol.


Still smarting from pantheon party last night @getpantheon #DrupalConLA #hook42 @hook42inc pic.twitter.com/oUGT3zI61Z

— K2 (@K2Hook42) May 14, 2015 Tuesday, May 26, 2015 Hook 42 Topics:

Modules Unraveled: 136 Details on the NodeSquirrel Acquisition by Pantheon with Drew Gorton and Ronan Downling - Modules Unraveled Podcast

Planet Drupal -

Published: Wed, 05/27/15Download this episodeNodeSquirrel
  • What is NodeSquirrel?
    • Backup and Migrate (over 300,000 sites using it)
    • Only cloud backup-as-a-service for Drupal
    • Backup database and Files
    • Every site should have automatic off-site backups configured.
  • That leads great into the pantheon acquisition, because now everyone can create free off-site backups with NodeSquirrel.
Pantheon Acquisition
  • How did the aqcuisition come about?
    • Drew - BadCamp October 2014. Sitting at a Pantheon party, ended up talking to Zack about running a services firm and product at the same time. The excitement, issues etc. involved with that. And it happened.
  • Did you pitch it to him? Did he pitch it to you?
    • Me.
  • So, what’s in it for them? Why did Pantheon buy NodeSquirrel?
    • They want to build great tools that developers can love and trust and use.
  • What’s new now that it’s been acquired by Pantheon?
    • It’s FREE! (There’s a new free tier)
    • It’s not a trial. It’s always free.
    • It’s not just for Pantheon customers.
    • We have access to Pantheon’s resources to further the development and continue improving support.
    • It’s been a side project from the start, but now that it’s backed by a real product company, we’re officially here for the long-haul. So, if you’ve been holding off because you didn’t want to risk storing your backups with something that might not be there in a year, you can rest assured that we’ll be here.
    • (Ronan) Now I’m able to dedicate more time and effort to the Backup and Migrate module (instead of only using my free time), which helps the community as a whole.
  • What happens to current users?
    • Higher storage limits
    • Might even be able to downgrade and pay less.
    • Won’t lose any features. Still use local backup, etc. (except maybe email)
  • What’s in the future?
    • Drupal 8
    • Wordpress
    • More features for both Backup and Migrate and NodeSquirrel
    • Bringing Pantheon features to NodeSquirrel and NodeSquirrel features to Pantheon (Notes)
Episode Links: Ronan on drupal.orgRonan on TwitterDrew on drupal.orgDrew on TwitterNodeSquirrel on TwitterNodeSquirrelBackup and Migrate ModulePantheonZack’s post about the acquisitionDrew’s post about the acquisitionTags: BackupsNodeSquirrelplanet-drupal

Open Geospatial Happy Hour

Drupal Fire -

Development Seed (via DrupalFire)

The Geospatial World Forum is well under way in Lisbon and we’re impressed with the diversity of people and talks at the event.

On Thursday night, we are organizing an Open Geospatial Happy Hour at Café Fábulas with our friends from Planet Labs. This Happy Hour is a great opportunity to meet people and talk about open data, mapping and satellites in a more informal setting.

You don’t have to be attending the conference to join the happy hour, just let us know if you’re coming. You can RSVP here.

If you are participating in the GFW, make sure to check out our workshop and talk in the exhibition hall on Thursday morning.

Pixelite: How to profile PHP memory with Drupal

Planet Drupal -

Why is this important

How to size the PHP setting max_memory is actually really important for the health of your Drupal application. Size this too small, and you risk getting PHP fatals due to not enough memory allocated. Size this too large, and you are essentially under-utilising your hardware, which in turn can lead to more cost.

How to record every Drupal requests PHP max memory usage

Tim Hillard created this really nice module called Memory profiler, which probably wins some sort of award for being around one of the smallest modules on drupal.org. Essentially this module registers a shutdown function that gets called at the end of every normal Drupal request.

The module is lightweight enough to run on production and only produces an extra syslog line per request.

Analyse the data

The data for memory profiler flows into watchdog, so if you run syslog (which you should), you can use CLI tools to analyse the data.

What does a single request look like $ grep "memory profiler" drupal-watchdog.log | head -n 1 May 26 06:25:21 sitename: https://www.sitename.com|1432621521|memory profiler||https://www.sitename.com/|https://www.sitename.com/home|0||4.75 MB - home request_id="v-fc9573dc-036f-11e5-a8c0-22000af91462"

This comes from your syslog format (which can be changed on a per site basis):

$ drush vget syslog_format syslog_format: '!base_url|!timestamp|!type|!ip|!request_uri|!referer|!uid|!link|!message' Extract the data from syslog

From here you can tokenise the parts you actually care about, in other words the:

  • URL requested (part 5)
  • PHP max memory (part 9)

Using more bash foo

$ grep "memory profiler" drupal-watchdog.log | head -n 1 | awk -F'|' -v OFS=',' '{print $5, $9}' https://www.sitename.com/,4.75 MB - home request_id="v-fc9573dc-036f-11e5-a8c0-22000af91462"

On Acquia Cloud a request ID is added to all requests, we don’t need this. Also having the string ‘MB’ there is superfluous.

$ grep "memory profiler" drupal-watchdog.log | head -n 1 | awk -F'|' -v OFS=',' '{print $5, $9}' | sed 's/ MB.*//' https://www.presto.com.au/,4.75


So in order to create a CSV for analysing in a spreadsheet you could do:

$ echo "request_uri,max_memory" > /tmp/memory.csv && grep "memory profiler" drupal-watchdog.log | awk -F'|' -v OFS=',' '{print $5, $9}' | sed 's/ MB.*//' >> /tmp/memory.csv

And then you can make pretty graphs if you want:

Or if you just want to find the top requests to your application by memory you can do

$ grep "memory profiler" drupal-watchdog.log | awk -F'|' -v OFS=',' '{print $5, $9}' | sed 's/ MB.*//' | sort -t, -k+2 -n -r | head -n 20 Conclusions

Based on your findings in the logs, you should be able to come up with:

  • A better understanding of your request memory profile
  • Better max memory settings for your Drupal application
  • Potentially identify poor performing pages (memory wise) and can look to optimise them

This module will only work if:

  • hook_boot() is called (which might not be the case if you run custom lightweight PHP scripts that do not bootstrap Drupal)
  • The Drupal request is not terminated with a SIGTERM or SIGKILL signal

Let me know if you found this helpful, or if you have any changes to my bash foo. If you have profiled your Drupal application recently, what methods and tools did you use?

DrupalCon News: Talking Business and Strategy in Barcelona

Planet Drupal -

This year, the Business and Strategy track in Barcelona will be about growth and change. The Drupal market is expanding as companies are growing, being founded or merging. Both growth and change present Drupal businesses with various challenges which is why we will focus on how we grow and how we sustain a strong culture in the midst of it, while sharing proven processes and tools.

DrupalCon News: How Session Selection Works

Planet Drupal -

Once you’ve submitted a stellar session proposal, you'll probably wonder what the process for session selection looks like from the other side. We are happy to pull back the veil on this community-led selection process for you to better understand the bells and whistles of session selection.

DrupalCon News: Train with us in Barcelona

Planet Drupal -

Want to help us make DrupalCon Barcelona the best event it can be? Get training! We’re currently accepting training proposals for DrupalCon Barcelona, so if you want to share your Drupal knowledge and get a little cash doing it, submit your great training idea to our team.

Oil-Climate Index Launches

Drupal Fire -

Development Seed (via DrupalFire)

Nearly 100 million barrels of oil flow through the global oil supply chain every day. But not all oils are created equal. When you consider the full oil processing lifecycle, some types of oil are responsible for nearly twice as much greenhouse gas as others. This is important information for oil procurement and energy policy. Smarter oil selection can lead to significant reduction in greenhouse gases without even touching overall oil consumption. We worked with the Carnegie Endowment to launch the Oil Climate Index website to help consumers and policymakers make smarter decisions on oil.

Extracting Oil Data

Oil emission data has traditionally been extremely hard to find. The source data for most oil fields is often secret and some of the models needed to calculate total greenhouse gas emissions have been proprietary. The Carnegie Endowment made a major contribution to understanding the climate impacts of fossil fuels with the Oil-Climate Index. The Oil Climate Index is the first study using entirely open-source models for evaluating greenhouse gas emission. These models were developed in a collaboration by Carnegie Endowment’s Energy and Climate Program, Stanford University, and the University of Calgary. In addition, the Oil Climate Index also collected model input data for 30 popular and emerging oils.

The data is extremely complex and nuanced. Depending on what you want you want to do with an oil, making diesel vs jet fuel, different oils may be better. An improvement in an extraction or refinement process may have a significant climate benefit for one oil but not for another. To make this data useful to scientists, investors, policy makers, and interested citizens we built a flexible data exploration tool. The tool makes reasonable assumptions to allow immediate comparison, but also allows users to explore how specific factors change the overall climate impact of each oil. Most importantly, all of the data and the modeling methodologies are open and available for download.

Designing for complexity

We limited graphing options to the most meaningful properties to provide flexibility without unnecessary complexity. To visualize the Oil-Climate Index, we weren’t just showing static data, we were visualizing results of complex models. Processing all the data in the browser is impractical. Instead, we picked several model input parameters that are most meaningful and calculated their data up front. We built processing tools behind the site to recalculate this data as Carnegie extracts data on new oils.

For more information on the Oil-Climate Index hit us on Twitter, ask @DxGordon, or check out these resources:
- http://carnegieendowment.org/2015/05/05/avoiding-oil-climate-collision/i876
- http://carnegieendowment.org/2015/03/11/know-your-oil-creating-global-oil-climate-index/i3oy
- http://www.koomey.com/post/119950474783

Drupal Association News: Please help us welcome Mark and Gener

Planet Drupal -

The Drupal Association is thrilled to announce the start of two new employees. Many of you may have met Mark and Gener at DrupalCon Los Angeles, but for those of you who were unable to make it, or who didn’t run into them, here’s the info about our newest additions to the team.

Mark Brandstetter, Account Manager for Technology and Hosting, Revenue Team

Mark Brandstetter is helping to take over Don Page's role as one of the new Account Manager's for technology and hosting based out of the Portland office. Mark is originally from the Midwest, but most recently spent 5 years living in Brooklyn, New York. Previously, Mark worked at Yelp and AdRoll, and his background in digital marketing and strategy will prove helpful to the team! In his free time, Mark enjoys cooking, hiking and hopes to one day join his his fellow Portland-Druplers at the DA in owning his very own urban chicken(s). Fingers crossed!!

Gener Umali, Drupal.org Advertising, Revenue Team

Gener Umali will be focused on Drupal.org Advertising, with an emphasis on thoughtfully creating connections between the right people and products. Prior to joining the Drupal Association, Gener worked as a Director of Advertising Sales. In a ten-year advertising career ranging from startups to big-names like CNET, Gener has worked with Mac and Linux Developers, but has never encountered a group as passionate as Drupal developers. He is humbled and inspired by their dedication. In his free time, Gener enjoys tinkering with cars, motorcycles, or anything with a motor. He enjoys travel, and has been to more than thirty countries. He also enjoys snowboarding, skiing, fitness, photography, and collecting old mechanical watches.

Please help us give a warm welcome to Mark and Gener. They’ll be working hard to generate funding for the project we all love, and are already proving to be fantastic additions to the Drupal Association team.

Welcome, Mark and Gener!

Drupal Watchdog: Version Control Workflow Strategies

Planet Drupal -


As a longtime lover of source control, I've been known to have a few opinions on how to use it. I've generally taken the approach that the tool I use needs to work for me, not against me. Unfortunately with the flexibility of a distributed version control system, such as Git, the right answer isn't always obvious. Taking the time to impose some arbitrary constraints on your workflow will make your daily tasks more predictable, and therefore easier to complete. One of the biggest wins you can make is using a standardized branching pattern for your work. If your team hasn't already "unvented" its own best practices, this article will help you choose an effective workflow for your team.

The different workflows really break down into two simple categories: the first is best described as a scheduled release pattern; the second as continuous deployment. Of course there are a spectrum of options in between, but let's look at the polar opposites for now.

The first option, the scheduled release, is typically used for products which have launch dates and different versions available at any one point in time. For example, Drupal uses a major.minor syntax for its releases. In some scheduled releases, you will also have a smaller “hotfix” release which adds a third set of numbers to the released version. From a branch perspective, this means you have a number of parallel development branches at work. Each time you begin new work, you need to carefully consider your starting point. This branching pattern was popularized by the 2010 blog post describing what is now referred to as the Gitflow Branching Model.

Drupal Easy: DrupalEasy Podcast 155: Feel 66% Better (Ben Jeavons - Drupal.org Two-Factor Authentication)

Planet Drupal -

Download podcast 155

Ben Jeavons, coltrane on Drupal.org, member of the Drupal security team, joins Ted Bowman, Ryan Price, and Mike Anello on the first post-DrupalCon Los Angeles podcast. Ben gets us up-to-speed on two-factor authentication and the modules he helped write as well as their implementation on Drupal.org. We also wrap up our coverage of DrupalCon Los Angeles, practice using Ted's new nickname, and assign homework to listeners.

read more

Cheeky Monkey Media: 4 Easy steps to configure Drupal to send html emails

Planet Drupal -

Do you know drupal can be config to send out html mails, which you can add images, colours to email in order to enhance your users experience.

We are going to use mail system and mime mail in this tutorial. I will try to keep things simple.

Step 1: Install required modules and update configuration
  1. https://www.drupal.org/project/mailsystem
  2. https://www.drupal.org/project/mimemail

Here is a tutorial of how to install modules for drupal...

Isovera Ideas & Insights: Content is Still the King -- Thoughts from DrupalCon-LA

Planet Drupal -

DrupalCon is always an exciting time of year for all of us in the Drupal community. This year was even more exciting as Drupal 8 is right on the horizon. Our developers flew out to Los Angles for this year's event, giving us an opportunity to share ideas with our peers (RJ coordinated a great discussion on headless Drupal), attend different sessions, and continue to stay-up-to-date on the latest trends.

2bits: Presentation: Backdrop: A Drupal Fork

Planet Drupal -

Last week, Nathan Vexler of the University of Waterloo, and Khalid Baheyeldin of 2bits.com presented at the Waterloo Region Drupal Users Group on Backdrop. Backdrop is a fork of Drupal, based mostly on Drupal 7.x, and mostly compatible with its API. It also has some features from Drupal 8.x. It aims to provide an alternative that reduces the cost of ownership by minimizing the learning curve for developers.

read more

Presentation: Backdrop: A Drupal Fork

Drupal Fire -

2bits (via DrupalFire)

Last week, Nathan Vexler of the University of Waterloo, and Khalid Baheyeldin of 2bits.com presented at the Waterloo Region Drupal Users Group on Backdrop.
Backdrop is a fork of Drupal, based mostly on Drupal 7.x, and mostly compatible with its API. It also has some features from Drupal 8.x. It aims to provide an alternative that reduces the cost of ownership by minimizing the learning curve for developers.

read more


Subscribe to Cruiskeen Consulting LLC aggregator