Triangle-area Drupalers and cartography enthusiasts: please join us from 1:00 PM to 5:00 PM on April 24 at the American Underground @ Main. Our team will be working on porting Views GeoJSON to Drupal 8.
We’ll be updating this post shortly with some additional information on how to prepare for the code sprint — tips for setting up a Drupal 8 development environment, what tasks we’ll be tackling during the code sprint, and how you can participate remotely if you can’t come here in person.
If you’re interested to join us, please RSVP to firstname.lastname@example.org.
Update: Preparing for the codesprint
As promised above, here are some notes on how to prepare for participating in the code sprint tomorrow. Please do these things before arriving at the sprint so we can get started right at 1 PM.
Set up a local Drupal 8 site
Spend some time getting your local Drupal 8 environment set up. Make sure you can login, that XDebug is working, etc. At the time of this writing, the latest beta is
8.0.0-beta9, we recommend using that instead of the latest commit to the
Clone the Views GeoJSON repo from GitHub, and review the issues
I’ve mirrored the Views GeoJSON repo from Drupal.org over on GitHub. You can clone the repo at https://github.com/savaslabs/views_geojson.
I recommend cloning the repo into your
/modules directory, as symlinking it led to some problems. So, if your local D8 site is at
~/src/d8local, then you would
cd ~/src/d8local/modules; git clone https://github.com/savaslabs/views_geojson.git
After cloning the repo, double check that you can enable it on your local Drupal 8 site. It won’t do anything (yet!) but you should be able to enable it.
Make sure you also fork the repo on GitHub so that you can submit pull requests to it. We’ll be using pull requests to review code before merging it in. At the end of the day, we’ll create a single patch against the
7.x-1.x branch that we’ll submit to the Views GeoJSON issue queue on Drupal.org.
I’ve also created issues in the GitHub repo that we can divvy up tomorrow.
Related Blog Posts
The cost of investing in Drupal 7 - why it’s time for Drupal 8
While there were compelling reasons to build in Drupal 7 in the past, we discuss why, for most, it’s time to move on to Drupal 8.
Related Case Studies
Comments are disabled for this post.