In our free Module Monday: Backup and Migrate tutorial we discussed all the benefits and features the module has to offer. In this tutorial I am going to extend on the functionality of the module because something great has happened in the Drupal world. Pantheon, a Drupal hosting provider, has purchased NodeSquirrel an offsite backup solution created by the makers of the Backup and Migrate module. What is so great about this is Pantheon is allowing free backups up to 5gb. This means there are no more excuses not to have an offsite backup of your Drupal database.
At yesterday's Worldwide Developer Conference keynote, Apple announced its annual updates to iOS, OS X, and the new watchOS. As usual, the Apple rumor blogs correctly predicted most of the important announcements weeks ago, but one important piece of news only leaked a few hours before the keynote: the launch of a new application called "News". Apple's News app press release noted: "News provides beautiful content from the world's greatest sources, personalized for you".
Apple basically cloned Flipboard to create News. Flipboard was once Apple's "App of the Year" in 2010, and it remains one of the most popular reading applications on iOS. This isn't the first time Apple has chosen to compete with its ecosystem of app developers. There is even a term for it, called "Sherlocking".
But forget about Apple's impact on Flipboard for a minute. The release of the News app signifies a more important shift in the evolution of the web, the web content management industry, and the publishing industry.Impact on content management platforms
Why is Apple's News app a big deal for content management platforms? When you can read all the news you are interested in in News, you no longer have to visit websites for it. It's a big deal because there are half a billion active iOS devices and Apple will ship its News app to every single one of them. It will accelerate the fact that websites are becoming less relevant as an end-point destination.
Some of the other new iOS 9 features will add fuel to the fire. For example, Apple's search service Spotlight will also get an upgrade, allowing third-party services to work directly with Apple's search feature. Spotlight can now "deep link" to content inside of a website or application, further eliminating website or applications as end-points. You could search for a restaurant in Yelp directly from your home screen, and go straight to Yelp's result page without having to open the Yelp website or application. Add to that the Apple Watch which doesn't even ship with a web browser, and it's clear that Apple is about to accelerate the post-browser era of the web.
The secret to the News app is the new Apple News Format; rumored to be a RSS-like data feed with support for additional design elements like images, videos, custom fonts, and more. Apple uses these feeds to aggregate content from different news sources, uses machine learning to match the best content to a given user, and provides a clean, consistent look and feel for articles coming from the various news sources. That is the long way of saying that Apple decides what the best content is for you, and what the best format is to deliver it in. It is a profound change, but for most people this will actually be a superior user experience.
The release of Apple News is further proof that data-driven experiences will be the norm and of what I have been calling The Big Reverse of the Web. The fact that for the web to reach its full potential, it will go through a massive re-architecture from a pull-based architecture to a push-based architecture. After the Big Reverse of the Web is complete, content will find you, rather than you having to find content. Apple's News and Flipboard are examples of what such push-based experiences look like; they "push" relevant and interesting content to you rather than you having to "pull" the news from multiple sources yourself.
When content is "pushed" to you by smart aggregators, using a regular web browser doesn't make much sense. You benefit from a different kind of browser for the web. For content management platforms, it redefines the browser and websites as end-points; de-emphasizing the role of presentation while increasing the importance of structured content and metadata. Given Apple's massive install base, the launch of its News app will further accelerate the post-browser era of the web.
I don't know about your content management platform, but Drupal is ready for it. It was designed for a content-first mentality while many competitive content management systems continue to rely on a dated page-centric content model. It was also designed to be a content repository capable of outputting content in multiple formats to multiple end-points.Impact on publishing industry
Forget the impact on Flipboard or on content management platforms, the impact on the publishing world will even be more significant. The risk for publishers is that they are being disintermediated as the distribution channel and that their brands become less useful. It marks a powerful transformation that could de-materialize and de-monetize much of the current web and publishing industry.
Because of Apple's massive installed base, Apple will now own a large part of the distribution channel and it will have an outsized influence on what hundreds of millions of users will read. If we've learned one thing in the short history of the Internet, it is that jumping over middlemen is a well-known recipe for success.
This doesn't mean that online news media have lost. Maybe it can actually save them? Apple could provide publishers large and small with an immense distribution channel by giving them the ability to reach every iOS user. Apple isn't alone with this vision, as Facebook recently rolled out an experiment with select publishers like Buzzfeed and the New York Times called Instant Articles.
In a "push economy" where a publisher's brand is devalued and news is selected by smart aggregators, the best content could win; not just the content that is associated with the most well-known publishing brands with the biggest marketing budgets. Publishers will be incentivized to create more high-quality content -- content that is highly customized to different target audiences, rather than generic content that appeals to large groups of people. Success will likely rely on Apple's ability to use data to match the right content to each user.Conclusion
This isn't necessarily bad. In my opinion, the web isn't dead, it's just getting started. We're well into the post-PC era, and now Apple is helping to move consumers beyond the browser. It's hard to not be cautiously optimistic about the long-term implications of these developments.
The Drupal Maillog module solves two issues:
- Being able to review all emails being sent from a site
- Stopping emails from being sent from a site
The module intercepts all email due to be sent from a Drupal website. Once it has done this, it can be configured to both log the emails so they can be reviewed and still send the emails on.
We enable the Maillog module in all environments (production and the development and stage environments) and then use settings.php to put the configuration for each environment in code.
Below is an example configuration settings for a production environment which needs the emails to be logged and then sent out:-// Maillog settings. $conf['mail_system'] = array( 'default-system' => 'MaillogMailSystem', 'maillog' => 'MaillogMailSystem', ); $conf['maillog_send'] = TRUE; // Do send the email. $conf['maillog_log'] = TRUE; // Do log the emails. $conf['maillog_engine'] = 'DefaultMailSystem'; // Use this as the email engine.
The mail_system conf setting is a core Drupal configuration which tells Drupal which email handlers exist and which should be used as the default handler. Here we can see that MaillogMailSystem is set to be the default and so will be the one which is used to handle all emails from the site.
The maillog_engine conf setting is a maillog module setting which tells maillog which email handler to pass the email onto if maillog_send is set to TRUE.
Here is an example configuration for a development environment where we want to log the emails being sent but do not want to actually send the emails.// Maillog settings. $conf['mail_system'] = array( 'default-system' => 'MaillogMailSystem', 'maillog' => 'MaillogMailSystem', ); $conf['maillog_send'] = FALSE; // Do not send the email. $conf['maillog_log'] = TRUE; // Do log the emails.
Next is an example production environment configuration for a site which uses the Mandrill module to have the Mandrill service send emails instead of the Drupal default. Since we do not want to log emails on this site the Maillog module is redundant but we still want it enabled because it will still be useful in the development environments. By enabling the module in production then it will still be enabled when we drag the database down from production to development where it needs to be enabled.// Maillog settings. $conf['mail_system'] = array( 'default-system' => 'MandrillMailSystem', 'maillog' => 'MaillogMailSystem', 'mandrill' => 'MandrillMailSystem', );
If you have the Drupal Views module enabled and have configured Maillog to log emails then a Maillog section will appear under admin/reports on the site. This lists all the emails the site has sent or would have sent if maillog_send is set to FALSE. Note that this report will only appear after you have cleared cache so is not immediatley available after enabling the module.
The Maillog module is a useful tool for managing and reviewing emails on a Drupal site. By enabling the module in all environments it is always there even if we pulled the database down from production to development. By placing configuration in code we can be precise about the way Maillog behaves in each environment.
Maillog can also help to give assurance that emails will not be sent to real people in the development environments. However, we also suggest using the reroute email module to give additional protection.
This quarter saw a phenomenal turn out for the Drupal Association’s May Global Training Days! 25 training companies from 15 countries participated in hosting Introduction to Drupal sessions. A huge thank you to our community organizers and trainers, you are helping grow Drupal adoption globally!
To see all the action, pictures, and new Drupalers from the May training, check out twitter #DrupalGTD!
Want to host a training for your community? We have two more dates coming up in 2015, so it’s not too late to start give back to your community. If you want to set one up, the upcoming Global Training Days are:
- Friday August 29th - Saturday 30th
- Friday November 14th - Saturday 15th
Drupal has a particular way of doing things, which is sometimes not to the taste of everybody. This can lead to a misplaced feeling that it is weird or difficult. However, the Drupal way comes from years of developed good practice, and is backed by tens of thousands of developers' knowledge and experience.
Automated Drupal core and contrib updates have been discussed in the Drupal community on Drupla.org as well as on external blogs since Drupalgeddon in October 2014. The result? Automated updates are a good idea and would prevent Drupal sites from being hacked, but they also bring some inherent problems, such as:
- Updates applied directly to the live site will ignore the development and quality assurance workflow
- Updates could break the site if manually applied patches are overridden by automatically applied updates
- If updates aren’t done continuously, the code changes are major and risky when applied as security hotfixes
Those are the most important arguments against automated updates from "the inside", meaning where Drupal updates its code base itself. Because many Drupal sites are developed in a professional environment, enterprise sites in particular, these Drupal development shops need to update their sites with integration into their development and deployment infrastructure and workflow. This should happen just as a separate team member will do this during her work hours. As monitoring and applying updates continuously is time-consuming, especially when you have many sites to support, the need to keep a site up-to-date is high – but the priority is not. That’s why many Drupal sites are already outdated when they go live after they have passed the development cycle. We want to help the Drupal ecosystem handle updates more professionally and more easily.
In our latest blog post we described a workflow based on the idea of delivering Drupal updates continuously as a fixed part of the development workflow.
Taking the Drupal community's feedback into consideration, we’ve built a service that updates Drupal sites automatically, respecting both development and deployment workflows as well as module, core and theme patches. We call this new service Drop Guard.
Drop Guard will help Drupal shops, freelancers and site owners to keep their Drupal installation updated and secure – automatically.
Now, Drupal shops that provide support services for their clients can automate a big part of their service and extend their offer to include 24/7 security patch support – without losing sleep over critical security updates.
Drop Guard integrates into the deployment workflow, regardless which tools and hosting environment you use. Currently we support a webhook integration for CI services such as Jenkins, Travis CI, Circle CI or PHP CI; SSH integration; feature branch handling to support GIT branching models such as GIT flow; automated patch detection and application during updates. Drop Guard also has some basic built-in deployment features. For small sites, in a few weeks we’ll be releasing a new feature for "FTP only" workflows without the need to have a GIT-based deployment.
The service is currently available at no cost for interested beta testers. If you want to be one of the first to use Drop Guard to automate and professionalize your Drupal update processes, just register at http://drop-guard.net and we’ll contact you for a personal on-boarding.
Planning to outsource web development and other services, customers should think of Ukraine in the first place. This and many other ideas of Zhenya Rozinskiy, a business consultant, who has been living and working in the United States for nearly 25 years now, can be found in our interview.Read more
Last week’s DrupalCon interview featured friends from Pantheon. If you missed the interview or even our first Roundtable Interview, you can catch the first episode here. The interviews first appeared during our weeklong live broadcast with Periscope and Twitter.... Read more
The organizers of DrupalCamp St. Louis 2015 are excited to announce that the schedule is set for DrupalCamp STL.15; we will have sessions from a variety of presenters on a variety of topics—for both beginners and seasoned veterans alike!
Some of the great sessions lined up include a session on Git basics, the status of Migrate in Drupal 8, content strategy, securing Drupal, improving performance, improving search, Twig, and more! To kick it off, we'll have an awesome keynote from Alina Mackenzie (alimac) about getting involved in the Drupal Community.
Check out the sessions: DrupalCamp St. Louis 2015 Session Schedule.
Register for DrupalCamp STL.15 today, and build your schedule on the site—besides these excellent sessions, you'll get a tasty catered lunch, a comfy t-shirt, and some great memories and networking opportunities on both days of the Camp!
In case you missed it, the call for sessions for DrupalCon Barcelona closes this Monday, 8 June at midnight, Barcelona local time (CET)! If you've submitted your idea already, thank you! If you haven't yet, why not?
Got an idea for a session? Submit your session here: https://events.drupal.org/barcelona2015/submit-session
Some helpful advice to get your session to the top of the list:
S. M. Bjørklund: How to migrate content from drupal 6 to 7 by using Migrate_d2d - Part 4 - field mappings
This is probably the last post in this series. I will try in this article to bring it all together. This will also be the most code heavy article. If you are new to migrate and Drupal-to-Drupal data migration, make sure you read and understand the first articles before preceding.Mapping fields (field mappings)
Migrate have no way of knowing your plans for your Drupal 6 CCK fields or to what fields you are planning to store the data in Drupal 7. Perhaps you do not want or need to migrate all your old data. Source and target field have the same field name and type, but sometime you might want to fix a bad decisions made in the past and reorganize your architecture. Migrate call this field mappings. What ever reason you might have, you will need to share these ideas with Mirate. The basic format is like this:
More details are found in the official documentation at drupal.org.
An example of this is found in article.inc:<?php
This map field_foo (drupal 6) to the cleverly named field field_bar (drupal 7). This is all it take to get a text field like this migrated if you re-run the node migration drush mi Article.
DrupalOnWindows: Making namespaced callbacks work in Drupal 7 (without hacking core and with bound parameters)
What is the best way to prepare for Drupal 8 and make your projects easy (and cheap) to migrate to D8? Start using Drupal 8 programming patterns now as much as D7 allows you to....
I guess that most of you are already doing that - and have done for a few years now - with custom crafted frameworks that, as much as possible, use modern design patterns not stuck in 20 y/o spaguetty code. D7 is spaguetty, your custom modules and code need not to be so.More articles...
- Making namespaced callbacks work in Drupal 7 (without hacking core and with bound parameters)
- Calling .Net Framework and .Net Assemblies from PHP
- Hiding the fact that your site runs Drupal
- PHP 7 nightlies for Windows
- How to use NetPhp
- Benchmarking Drupal 7 on PHP 7-dev
- Benchmarking Drupal 8 on PHP 7-dev
- PDF Generation in PHP
- Setting up Code Syntax Higlighting with Drupal
- Drupal: Fields or Properties (or something else)
TL;DR We need to ship D8. ;)
I was sent this question today from a co-worker:
"We always talk anecdotally about how Drupal adoption slows before a new release and then picks back up. Do we have any data to support that for Drupal 7 or Drupal 6? I’d love to know the impact of Drupal 8 as well – but not sure that’s possible. Any thoughts?"
This is a great question, but since email is where information goes to die ;), I figured I would copy my response into a blog post as well.Show me the data!
Since D8 has been in development so long, we don't have enough data showing on https://www.drupal.org/project/usage/drupal anymore since it prunes it after 3 years. :(
This only goes back to June 2008 which is after D6 came out, so it's not ideal, but we can still glean some useful data out of it.Drupal 6
Here is a screenshot of the data from just prior to Drupal 7's release in January 2011:
- In December 2008 there were 77K installs of D6 (compared to 0 in January since it wasn't out yet :)) (77K% increase). This is when D7 was in active development.
- At the end of 2009 there were 203K installs of D6 (163% increase). This was when D7 was in feature freeze.
- At the end of 2010 there were 323K installs of D6 (59% increase). This was when D7 was just about to ship.
- At the end of 2011 there were 292K installs of D6 (9% decrease). This is when D7 had been out for about a year and several key contributed modules were ported.
- D6 usage has been declining ever since, and is currently at about 135K installs.
Here is the data from 2011 to today:
- At the end of 2010 there were 6.5K installs of D7. This is when D7 was just about to be released.
- At the end of 2011 there were 230K installs of D7 (3438% increase). This is when D7 had been out for about a year and several key contributed modules were ported, and D8 was just beginning development (was mostly D7 bug fixes at this point). Of note, D7 usage eclipsed D6 usage just a few months later (Feb 2012).
- At the end of 2012 there were 522K D7 installs (127% increase). This is when D8 was nearly done with feature development.
- At the end of 2013 there were 728K D7 installs (39% increase). This is after D8 was in code freeze.
- At the end of 2014 there were 869K (19% increase). This is when D8 was in beta.
- As of last week (mid-2015) there were 984K installs (13% increase). D8 is currently still in beta, with ~25 critical issues remaining before release candidates.
There are a few patterns we can discern from this data:
- There is an enormous uptick in Drupal usage every new major release (though it's delayed until it reaches a "stable" state, i.e. after enough contributed modules are ported).
- After that initial year or two of exponential growth, it slows down a lot.
- The closer the next version is to being released, the slower the growth is of the current version. Generally, this is because people will postpone projects and/or use non-Drupal solutions to avoid incurring a major version upgrade.
- Usage of the older stable version starts to decline after the newer major version reaches the "stable" state.
There are a few enormous shifts coming with D8 that should change these patterns significantly:
- Drupal 8 is much more fully-featured out of the box than any of its predecessors, so for many sites there is no need to wait on any contributed modules to begin building. Therefore we reach "stable" state (for sites that can do what they need to with just core) at Day 0, not 6-12 months later.
- A number of key contributed modules that delayed porting of other key contributed modules in D6/D7 (Views, Entity Reference, Date, etc.) were moved into core in D8. So they're available right now—even before release—to build on. And indeed we're seeing other big ecosystem modules (Commerce, Rules, etc.) porting now, while D8 is still in development.
- D8 will end the 3-4 year "big bang" release cycle. Instead, we'll be doing "small bang" releases every 6 months with non-backwards compatibility breaking feature/API improvements. That means we should hopefully stave off adoption decline much longer, and possibly even sustain the "hyper adoption" rate for much longer.
- We will still eventually have a D9 "big bang" release (3-4 years from now) with backwards compatibility breaks, but only after it's amassed enough awesome functionality that couldn't be otherwise backported to D8. This will provide us with another "epochal" marketing event that D8 is giving us today (well, soon) in order to drive adoption even further.
Sorry, that was probably Way Too Much Information™ but hey, the more you know. ;)Tags: drupaldrupal 8acquia
Drupal Media has benefited from Google Summer of Code in the past. Last year one project under Drupal was directly a part of the Media Initiative - Entity Embed module for Drupal 8. I was that lucky student who got this wonderful opportunity to work under the mentorship of Media Initiative leads - Dave Reid (davereid) and Janez Urevc (slashrsm) but that’s a story from the past and you can read more about it in this blog post. In this post I’ll talk about the participation of Drupal Media in GSoC 2015.
3 Projects from Drupal Media, woot!
This year is turning out to be a great one for the Media Initiative in Google Summer of Code. We proposed three projects this year - all for Drupal 8 - and all of those were accepted and we managed to get three outstanding students. We take pride in telling everyone that not only all three students are Core contributors, they have also contributed to one or more Media modules already.
Now I would like to introduce the three students:
- Jayesh Solanki (jayeshsolanki). Jayesh is a GSoC 2014 alumnus and last year he successfully ported Disqus module to Drupal 8. This year, he will be assisting with the development of Entity Browser. Entity browser is a module for Drupal 8 that tries to provide powerful and flexible framework for searching & selecting of entities. If you want to follow the development of this module or project, all the development will be happening in this Github repository. Janez Urevc (slashrsm) will be mentoring this project.
- Prateek Mehta (prateekMehta). Prateek will be working on developing URL embed module for Drupal 8. This project aims to build a framework for CKEditor which would allow an end-user to display an embedded representation of a URL, the content of the URL can be a video, images, rich text or a link. This framework will handle URLs from various third party sites and essentially replace oEmbed module from Drupal 7. For more details, refer to this architecture discussion. Currently, the development is happening in this Github repository but this will change soon when we get a new namespace on Drupal.org (don’t worry, we’ll keep you posted). Dave Reid (davereid) and I will be mentoring this project.
- Yuvraj Singh (root_brute). Yuvraj will be working on develop Embed module for Drupal 8 which will be an API level module. The idea of this project is to abstract the buttons, embed form, and display plugins from Entity Embed module into a generic Embed module that can be used by both Entity Embed, URL Embed, and other embeddables in Drupal 8. For more details, refer to this architecture discussion. If you want to follow the development of this module or project, all the development will be happening in this Github repository. Dave Reid (davereid) and I will be mentoring this project.
We have high hopes from all these three projects and hope that all of these will finish successfully on schedule and I’m very happy to tell you that all the signs are pretty good so far.
Looking forward to an exciting summer of code.Tags: Drupal PlanetGoogle Summer of Codegsoc2015gsoc
Look for links to our Strategic Roadmap highlighting how this work falls into our priorities set by the Drupal Association Board and Drupal.org Working Groups.Organization and User Profile Improvements Explicit Attribution Option for ‘I am A Volunteer’
As a part of our effort to recognize individual contributions to the Drupal ecosystem we’ve slightly adjusted the options available to a user when making an attribution in the issue queues. Instead of simply assuming that a comment made without an attribution to an organization or customer is done by a volunteer - we now allow volunteers to explicitly mark their work as such. Requiring a positive affirmation of the volunteer attribution should improve the accuracy of the data we are gathering about the Drupal ecosystem.
This now means a user can make issue comment attributions in the following ways:
- Without attribution
- As a volunteer
- On behalf of an organization and/or customer
- Both as a volunteer and on behalf of an organization and/or customer.
We are seeing a rate of around 30% of issue comments attributed to an organization, customer or as volunteer work. We hope to see that rate increase steadily.
To date, there have also been over 7,000 issue credits that have been awarded to over 2,300 users and 175 organizations. We are looking forward to displaying these credits on user and organization profiles in the month of June and beginning to find new ways to reward our top contributors.Content Strategy and Visual Design System for Drupal.org
Our collaboration with Forum One on developing content strategy for Drupal.org finished a few weeks ago. While recommendations were published in the issue queues earlier, we decided to use DrupalCon Los Angeles as an opportunity to present the work done and future plans in more detail, and get direct feedback from community members. Check out session slides or video if you want to know more on proposed changes to Drupal.org IA and content strategy.
Right now we are working on a few preparations steps before we can start implementing the changes. The first one of those steps would be a card sort exercise to validate our proposed IA and navigation with Drupal.org users. More blog posts and issues will follow as we move further.Issue Workflow and Git Improvements
The Drupal Association has been preparing a plan for a new issue workflow on Drupal.org - with some very exciting improvements planned to create a workflow that is both familiar to other repository hosts and yet unique to the needs of the Drupal community.
Perhaps the greatest value of the new Git workflow will be the presence of per-issue repositories and pull requests on Drupal.org issues without forking the issue conversations. Drupal.org will use git namespaces to provide every developer working on an issue with their own branch. Developers will be able to pull in the latest changes from HEAD, or changes from other users’ branches. Drupal.org will be able to summarize the commits, take the changeset and run tests, and help maintainers manage the merge process to push changes upstream.
This architecture will make additional features possible as well:
- The patch based workflow will continue to work - behind the scenes Drupal.org will create commits on namespaced branches from these patches so that these code contributions will be first-class citizens with the new git workflow.
- We will be able to provide an inline editor for code in issues - simplifying the workflow for contributions such as code style fixes, documentation, quick typo corrections, etc.
- We can provide the option to compare any two changes in an issue, giving us automated interdiff functionality.
- We can identify merge conflicts across issues - to hopefully prevent conflicts across issues before they become too deeply entangled.
This planning work culminated in a presentation at DrupalCon Los Angeles - where the community provided some great feedback, and dove into help us with some architectural components during the extended sprints.
Implementation of the new Issue Workspaces architecture will certainly take some time - but we’re excited to have a plan to work from as we move forward.Community Initiatives Two Factor Authentication
May saw the initial roll out of Two-Factor Authentication on Drupal.org. Users with elevated privileges on Drupal.org now have the option of enabling TFA, and this may become required for all elevated roles in future.
Next we want to make two factor available to all authenticated users on Drupal.org. However, before we can allow every user to enable two factor it is important that we create a support policy for resetting accounts with TFA enabled, which is still under discussion.DrupalCI
DrupalCon Los Angeles was a great opportunity to meet with the community and talk about the current state of DrupalCI, and it’s upcoming release.
As of the end of May, DrupalCI is very close to being ready for integration on Drupal.org. All of the environments requested for the MVP deployment are functional, and the Drupal Association staff is getting ready to demo the integration with Drupal.org on a development site - at the same time work is continuing on the results site componenet and the test-runner’s results publishing capabilities.
DrupalCI will be rolled out in parallel with the existing PIFT/PIFR infrastructure for at least a few months following initial deployment as a sanity check.Localize.Drupal.org
Click-testing has identified several additional issues going into the end of May, and the Association team continues to work on knocking the issues down as they appear. When the current set of identified issues is resolved, we intend to notify the most active translation groups and ask them to perform a final round of testing on the staging environment.
When any issues from that final round of testing are resolved, we will deploy the D7 version of Localize.drupal.org.Revenue-related projects (funding our work) DrupalCons
DrupalCon Los Angeles was a productive and fun event for the community and the Association staff - in every way a success. At the conference we made several announcements about the upcoming DrupalCons, including 2016 locations.
First, we announced the opening of the call for papers for DrupalCon Barcelona, September 21st-25th. The call for papers for Barcelona closes on June 8th.
We then announced our next two conferences, and launched their websites.
DrupalCon Asia will be held in Mumbai in February of 2016.
And the next DrupalCon North America will be held on May 9th-13th, 2016 in New Orleans!Sustaining Support and Maintenance
The Git servers replacing our existing Git infrastructure are nearly ready for thorough testing and deployment. These servers give us a highly available cluster for git.drupal.org, in addition to increased storage capacity, a newer operating system, and dedicated hardware for Git services on Drupal.org.
Our Fastly CDN deployment for downloads (ftp.drupal.org) was a success, and soon to follow is the same new architecture for updates traffic (updates.drupal.org). This new architecture uses dynamic purging to reduce the number of update requests served by our origin servers. It also decreases the latency between packaging a release and serving the update data from a number of minutes to a few seconds.
As always, we’d like to say thanks to all volunteers who are working with us and to the Drupal Association Supporters, who made it possible for us to work on these projects.
I was happy to talk with two major contributors to Drupal 8 at the same time at Drupal South 2015 in Melbourne Australia. At the time we recorded our conversation in March 2015, Hussain Abbas from Bangalore, India and Jibran Ijaz from Lahore Pakistan had both contributed well over 100 patches to D8. In this podcast we talk about their history in Drupal, open source software as a force for good in society, the benefits of contribution, Drupal as the 1st project of the PHP-FIG era, Drupal 8 for developers, the incredible energy and size of the Australasian Drupal community, and more.