Extended security coverage for Drupal 8 minor releases

Since the launch of Drupal 8.0, we have successfully launched a new minor release on schedule every six months. I'm very proud of the community for this achievement. Prior to Drupal 8, most significant new features were only added in major releases like Drupal 6 or Drupal 7. Thanks to our new release cadence we now consistently and predictably ship great new features twice a year in minor releases (e.g. Drupal 8.6 comes with many new features).

However, only the most recent minor release has been actively supported for both bug fixes and security coverage. With the release of each new minor version, we gave a one-month window to upgrade to the new minor. In order to give site owners time to upgrade, we would not disclose security issues with the previous minor release during that one-month window.

Illustration of the security policy since the launch of Drupal 8.0 for minor releases, demonstrating that previous minor releases receive one month of security coverage.
Source: Drupal.org issue #2909665: Extend security support to cover the previous minor version of Drupal and Drupal Europe DriesNote.Over the past three years, we have learned that users find it challenging to update to the latest minor in one month. Drupal's minor updates can include dependency updates, internal API changes, or features being transitioned from contributed modules to core. It takes time for site owners to prepare and test these types of changes, and a window of one month to upgrade isn't always enough.

At DrupalCon Nashville we declared that we wanted to extend security coverage for minor releases. Throughout 2018, Drupal 8 release managers quietly conducted a trial. You may have noticed that we had several security releases against previous minor releases this year. This trial helped us understand the impact to the release process and learn what additional work remained ahead. You can read about the results of the trial at #2909665: Extend security support to cover the previous minor version of Drupal.

I'm pleased to share that the trial was a success! As a result, we have extended the security coverage of minor releases to six months. Instead of one month, site owners now have six months to upgrade between minor releases. It gives teams time to plan, prepare and test updates. Releases will have six months of normal bug fix support followed by six months of security coverage, for a total lifetime of one year. This is a huge win for Drupal site owners.

Illustration of the new security policy for minor releases, demonstrating that the security coverage for minor releases is extended to six months. Source: Drupal.org issue #2909665: Extend security support to cover the previous minor version of Drupal and the Drupal Europe DriesNote.
It's important to note that this new policy only applies to Drupal 8 core starting with Drupal 8.5, and only applies to security issues. Non-security bug fixes will still only be committed to the actively supported release.

While the new policy will provide extended security coverage for Drupal 8.5.x, site owners will need to update to an upcoming release of Drupal 8.5 to be correctly notified about their security coverage.

Next steps

We still have some user experience issues we'd like to address around how site owners are alerted of a security update. We have not yet handled all of the potential edge cases, and we want to be very clear about the potential actions to take when updating.

We also know module developers may need to declare that a release of their project only works against specific versions of Drupal core. Resolving outstanding issues around semantic versioning support for contrib and module version dependency definitions will help developers of contributed projects better support this policy. If you'd like to get involved in the remaining work, the policy and roadmap issue on Drupal.org is a great place to find related issues and see what work is remaining.

Special thanks to Jess and Jeff Beeman for co-authoring this post.
Source: Dries Buytaert www.buytaert.net

Drupal 7, 8, and 9

We just released Drupal 8.6.0. With six minor releases behind us, it is time to talk about the long-term future of Drupal 8 (and therefore Drupal 7 and Drupal 9). I've written about when to release Drupal 9 in the past, but this time, I'm ready to provide further details.

The plan outlined in this blog has been discussed with the Drupal 7 Core Committers, the Drupal 8 Core Committers and the Drupal Security Team. While we feel good about this plan, we can't plan for every eventuality and we may continue to make adjustments.

Drupal 8 will be end-of-life by November 2021

Drupal 8's innovation model depends on introducing new functionality in minor versions while maintaining backwards compatibility. This approach is working so well that some people have suggested we institute minor releases forever, and never release Drupal 9 at all.

However that approach is not feasible. We need to periodically remove deprecated functionality to keep Drupal modern, maintainable, and performant, and we need to stay on secure, supported versions of Drupal 8's third-party dependencies. As Nathaniel Catchpole explained in his post "The Long Road to Drupal 9", our use of various third party libraries such as Symfony, Twig, and Guzzle means that we need to be in sync with their release timelines.

Our biggest dependency in Drupal 8 is Symfony 3, and according to Symfony's roadmap, Symfony 3 has an end-of-life date in November 2021. This means that after November 2021, security bugs in Symfony 3 will not get fixed. To keep your Drupal sites secure, Drupal must adopt Symfony 4 or Symfony 5 before Symfony 3 goes end-of-life. A major Symfony upgrade will require us to release Drupal 9 (we don't want to fork Symfony 3 and have to backport Symfony 4 or Symfony 5 bug fixes). This means we have to end-of-life Drupal 8 no later than November 2021.

Drupal 9 will be released in 2020, and it will be an easy upgrade

If Drupal 8 will be end-of-life on November 2021, we have to release Drupal 9 before that. Working backwards from November 2021, we'd like to give site owners one year to upgrade from Drupal 8 to Drupal 9.

If November 2020 is the latest we could release Drupal 9, what is the earliest we could release Drupal 9?

We certainly can't release Drupal 9 next week or even next month. Preparing for Drupal 9 takes a lot of work: we need to adopt Symfony 4 and/or Symfony 5, we need to remove deprecated code, we need to allow modules and themes to declare compatibility with more than one major version, and possibly more. The Drupal 8 Core Committers believe we need more than one year to prepare for Drupal 9.

Therefore, our current plan is to release Drupal 9 in 2020. Because we still need to figure out important details, we can't be more specific at this time.

If we release Drupal 9 in 2020, it means we'll certainly have Drupal 8.7 and 8.8 releases.

Wait, I will only have one year to migrate from Drupal 8 to 9?

Yes, but fortunately moving from Drupal 8 to 9 will be far easier than previous major version upgrades. The first release of Drupal 9 will be very similar to the last minor release of Drupal 8, as the primary goal of the Drupal 9.0.0 release will be to remove deprecated code and update third-party dependencies. By keeping your Drupal 8 sites up to date, you should be well prepared for Drupal 9.

And what about contributed modules? The compatibility of contributed modules is historically one of the biggest blockers to upgrading, so we will also make it possible for contributed modules to be compatible with Drupal 8 and Drupal 9 at the same time. As long as contributed modules do not use deprecated APIs, they should work with Drupal 9 while still being compatible with Drupal 8.

Drupal 7 will be supported until November 2021

Historically, our policy has been to only support two major versions of Drupal; Drupal 7 would ordinarily reach end of life when Drupal 9 is released. Because a large number of sites might still be using Drupal 7 by 2020, we have decided to extend support of Drupal 7 until November 2021. Drupal 7 will be receive community support for three whole more years.

We'll launch a Drupal 7 commercial Long Term Support program

In the past, commercial vendors have extended Drupal's security support. In 2015, a Drupal 6 commercial Long Term Support program was launched and continues to run to this day. We plan a similar paid program for Drupal 7 to extend support beyond November 2021. The Drupal Security Team will announce the Drupal 7 commercial LTS program information by mid-2019. Just like with the Drupal 6 LTS program, there will be an application for vendors.

We'll update Drupal 7 to support newer versions of PHP

The PHP team will stop supporting PHP 5.x on December 31st, 2018 (in 3 months), PHP 7.0 on December 3rd, 2018 (in 2 months), PHP 7.1 on December 1st, 2019 (in 1 year and 3 months) and PHP 7.2 on November 30th, 2020 (in 2 years and 2 months).

Drupal will drop official support for unsupported PHP versions along the way and Drupal 7 site owners may have to upgrade their PHP version. The details will be provided later.

We plan on updating Drupal 7 to support newer versions of PHP in line with their support schedule. Drupal 7 doesn't fully support PHP 7.2 yet as there have been some backwards-incompatible changes since PHP 7.1. We will release a version of Drupal 7 that supports PHP 7.2. Contributed modules and custom modules will have to be updated too, if not already.


If you are still using Drupal 7 and are wondering what to do, you currently have two options:
Stay on Drupal 7 while also updating your PHP version. If you stay on Drupal 7 until after 2021, you can either engage a vendor for a long term support contract, or migrate to Drupal 9.
Migrate to Drupal 8 by 2020, so that it's easier to update to Drupal 9 when it is released.
The announcements in this blog post made option (1) a lot more viable and/or hopefully helps you better evaluate option (2).

If you are on Drupal 8, you just have to keep your Drupal 8 site up-to-date and you'll be ready for Drupal 9.

We plan to have more specifics by April 2019 (DrupalCon Seattle).

Thanks for the Drupal 7 Core Committers, the Drupal 8 Core Committers and the Drupal Security Team for their contributions to this blog post.
Source: Dries Buytaert www.buytaert.net

Drupal 8.6.0 released

Last night, we shipped Drupal 8.6.0! I firmly believe this is the most significant Drupal 8 release to date. It is significant because we made a lot of progress on all twelve of Drupal 8 core's strategic initiatives. As a result, Drupal 8.6 delivers a large number of improvements for content authors, evaluators, site builders and developers.

What is new for content authors?

For content authors, Drupal 8.6 adds support for "remote media types". This means you can now easily embed YouTube or Vimeo videos in your content.

The Media Library in Drupal 8.6Content authors want Drupal to be easy to use. We made incredible progress on a variety of features that will help to achieve that: we've delivered an experimental media library, added the Workspaces module as experimental, providing sophisticated content staging capabilities, and made great strides on the upcoming Layout Builder. The Layout Builder is shaping up to be a very powerful tool that solves a lot of authoring challenges, and is something many are looking forward to.

Each initiative related to content authoring is making disciplined and steady progress. These features not only solve for the most requested authoring improvements, but provide a solid foundation on which we can continue to innovate. This means we can provide better compatibility and upgradability for contributed modules.

The top 10 requested features for content creators according to the 2016 State of Drupal survey.What is new for evaluators?

Evaluators want an out-of-the-box experience that allows them to install and test drive Drupal in minutes. With Drupal 8.6, we have finally delivered on this need.

Prior to Drupal 8.6, downloading and installing Drupal was a complex and lengthy process that ended with an underwhelming "blank slate".

Now, you can install Drupal with the new "Umami demo profile". The Umami demo profile showcases some of Drupal's most powerful capabilities by providing a beautiful website filled with content right out of the box. A demo profile will not only help to onboard new users, but it can also be used by Drupal professionals and digital agencies to showcase Drupal to potential customers.

In addition to a new installation profile, we added a "quick-start" command that allows you to launch a Drupal site in one command using only one dependency, PHP. If you want to try Drupal, you no longer have to setup a webserver, a database, containers, etc.

Last but not least, the download experience and evaluator documentation on Drupal.org has been vastly improved.

With Drupal 8.6, you can download and install a fully functional Drupal demo application in less than two minutes. That is something to be very excited about.

The new Umami demo profile together with the Layout Builder.What is new for developers?

You can now upgrade a single-language Drupal 6 or Drupal 7 site to Drupal 8 using the built-in user interface. While we saw good progress on multilingual migrations, they will remain experimental as we work on the final gaps.

I recently wrote about our progress in making Drupal an API-first platform, including an overview of REST improvements in Drupal 8.6, an update on JSON API, and the reasons why JSON API didn't make it into this release. I'm looking forward to JSON API being added in Drupal 8.7. Other decoupled efforts, including a React-based administration application and GraphQL support are still under heavy development, but making rapid progress.

We also converted almost all of our tests from SimpleTest to PHPUnit; and we've added Nightwatch.js and Prettier for JavaScript developers. While Drupal 8 has extensive back-end test coverage, using PHPUnit and Nightwatch.js provides a more modern platform that will make Drupal more familiar to PHP and JavaScript developers.

Drupal 8 continues to hit its stride

These are just some of the highlights that I'm most excited about. If you'd like to read more about Drupal 8.6.0, check out the official release announcement and important update information from the release notes. The next couple of months, I will write up more detailed progress reports on initiatives that I didn't touch upon in this blog post.

In my Drupal 8.5.0 announcement, I talked about how Drupal is hitting its stride, consistently delivering improvements and new features:

In future releases, we plan to add a media library, support for remote media types like YouTube videos, support for content staging, a layout builder, JSON API support, GraphQL support, a React-based administration application and a better out-of-the-box experience for evaluators.

As you can see from this blog post, Drupal 8.6 delivered on a number of these plans and made meaningful progress on many others.

In future releases we plan to:
Stabilize more of the features targeting content authors
Add JSON API, allowing developers to more easily and rapidly create decoupled applications
Provide stable multilingual migrations
Make big improvements for developers with Composer and configuration management changes
Continually improve the evaluator experience
Iterate towards an entirely new decoupled administrative experience
... and more
Releases like Drupal 8.6.0 only happen with the help of hundreds of contributors and organizations. Thank you to everyone that contributed to this release. Whether you filed issues, wrote code, tested patches, funded a contributor, tested pre-release versions, or cheered for the team from the sidelines, you made this release happen. Thank you!
Source: Dries Buytaert www.buytaert.net

Drupal4Gov Webinar Series: ​​HAX

2018-07-19 15:00 - 16:00 America/New_York



Event type: 

Training (free or commercial)


HAX the web is a headless authoring solution being developed by Penn State built on one question: Why can't all platforms have the same authoring experience (AX)? We decided that in order to build the best AX for Drupal we needed to NOT build it just for Drupal. Learn about how you can leverage HAX in your (deep breath) Drupal 6, Drupal 7, Drupal 8, GravCMS, Desktop apps, BackdropCMS sites and more!
Learn how and what you can build when we all work together across ecosystems on the front-end using a technology called Web components. Bryan Ollendyke (btopro) is the HAX project lead and will be demonstrating HAX, talking about it's capabilities and how to extend it, what you can do to use it in your projects and how and why web components should be the only technology implemented in your front end / theme layer of Drupal (and beyond).
Bryan Ollendyke (btopro) is a long time member of the Drupal community (13+ years) and works at Penn State on a platform called ELMS: Learning Network. Bryan is an open source absolutist, contributing 100% of his efforts back to the Drupal and web components communities in the form of modules, themes, install profiles, tutorials, design assets, tooling and more. Bryan drinks enough coffee to put down an elephant, and his "energy" is reflective of this.
Source: https://groups.drupal.org/node/512931/feed

Mollom: The story of my first SaaS startup

Last month, Acquia discontinued service and support for Mollom, the spam service I started more than ten years ago. As a goodbye, I want to share the untold story of how I founded Mollom.

In 2007, I read Tim Ferriss' book The 4-Hour Work Week, and was hooked. The book provides a blueprint for how entrepreneurs can structure and build a business to fund the lifestyle of their dreams. It's based on Ferriss' own experience; he streamlined his business, automated systems and outsourced tasks until it was not only more profitable, but also took less of his time to operate. The process of automation and outsourcing was so efficient, Ferriss only spent four hours a week to run his business; this gave him time and freedom to take "mini-retirements", travel the world, and write a book. When I first read Ferriss' book, I was inspired by the idea of simultaneously having that much free time and being financially stable.

While I was reading Ferriss' book, I was also working on a website spam filter for my blog, called Mollom. I had started to build Mollom as a personal project for exclusive use on my own blog. Inspired by the 4-Hour Work Week, I was convinced I could turn Mollom into a small SaaS service with global customers, complete self-service, and full automation. This would allow me to operate Mollom from anywhere in the world, and would require just a few hours of my time each week. Because I was starting to use machine learning, I enlisted the help of one of my best friends, Benjamin Schrauwen, a professor in machine learning at the University of Ghent.

In the same year, Jay Batson and I met at DrupalCon Sunnyvale, and we had already started to explore the idea of founding Acquia. My oldest son Axl was also born in the summer of 2007, and I was working hard to finish my PhD. Throughout all of this, we were also working to get Drupal 6 released. Needless to say, it was a busy summer.

With my PhD nearly complete, I needed to decide what to do next. I knew that starting Acquia was going to have a big impact, not just on Drupal but also on my life. However, I was also convinced that Mollom, while much smaller in scope and ambition, could provide a path to the freedom and independence Ferriss describes.

Mollom's foundational years

Exciting 2007, I determined that both Acquia and Mollom were important opportunities to pursue. Jay and I raised $7 million in venture capital, and we publicly launched Acquia in November 2007. Meanwhile, Ben and I pooled together €18,000 of our own money, bootstrapped Mollom, and publicly launched Mollom in March 2008.

I always made a point to run both businesses separately. Even after I moved from Belgium to the US in the summer of 2010, I continued to run Mollom and Acquia independently. The Mollom team was based in Europe, and once or twice a week, I would get up at 4 AM to have a two-hour conference call with the team. After my conference call, I'd help my family get ready for the day, and then I was off to work at Acquia.

By 2011, Mollom had achieved the goals our team set out to accomplish; our revenues had grown to about €250,000 annually, our gross margins were over 85 percent, and we could pretty much run the business on autopilot. Our platform was completely self-serviced for our users, the anti-spam algorithms self-learning, the service was built to be highly-available, and the backend operations were almost entirely automated. I often joked about how I could run Mollom from the beach in Greece, with less than an hour of work a day.

However, our team at Mollom wasn't satisfied yet, so instead of sitting on the beach, we decided to invest Mollom's profits in feature development. We had a team of three engineers working on adding new capabilities, in addition to re-architecting and scaling Mollom to keep up with its growth. On average, Mollom handled more than 100 web service requests per second, and we regularly saw peaks of up to 3,000 web service request per second. In a way, Mollom's architecture was ahead of its time — it used a micro-services architecture with a REST API, a decoupled administration backend and relied heavily on machine learning. From day one, our terms of service respected people's privacy, and we never had a data breach.

A photo of the Mollom team at an offsite in 2011: it includes Daniel Kudwien, Benjamin Schrauwen, Cedric De Vleeschauwer, Thomas Meire, Johan Vos and Vicky Van Roeyen. Missing in the picture is Dries.In the meantime, Acquia had really taken off; Acquia's revenue had grown to over $22 million annually, and I was often working 60 hour work weeks to grow the company. Acquia's Board of Directors wanted my full attention, and had even offered to acquire Mollom a few times. I recognized that running Mollom, Acquia and Drupal simultaneously was not sustainable — you can only endure regular 4 AM meetings for so long. Plus, we had ambitious goals for Mollom; we wanted to add many-site content moderation, sentiment analysis and detection for certain code of conduct violations. Doing these things would require more capital, and unless you are Elon Musk, it's really hard to raise capital for multiple companies at the same time. Most importantly, I wanted to focus more on growing Drupal and driving Acquia's expansion.

Acquia acquires Mollom

By the end of 2012, Ben and I agreed to sell Mollom to Acquia. Acquia's business model was to provide SaaS services around Drupal, and Mollom was exactly that — a SaaS service used by tens of thousands of Drupal sites.

Selling Mollom was a life-changing moment for me. It proved that I was able to bootstrap and grow a company, steer it to profitability and exit successfully.

Selling Mollom to Acquia involved signing a lot of documents. A photo of me signing the acquisition paperwork with Mary Jefts, Acquia's CFO at the time. It took three hours to sign all the paperwork.Acquia retires Mollom

By 2017, five years after the acquisition, it became clear that Mollom was no longer a strategic priority for Acquia. As a result, Acquia decided it was best to shut down Mollom by April 2018. As the leader of the product organization at Acquia, I'm supportive of this decision. It allows us to sharpen our focus and to better deliver on our mission.

While it was a rational decision, it's bittersweet. I still believe that Mollom could have continued to have a big impact on the Open Web. Not only did that make the web better, it saved people millions of hours moderating their content. I also considered keeping Mollom running as part of Acquia's "Give back more" principle. However, Acquia gives back a lot, and I believe that giving back to Drupal should be our priority.

Mollom's end-of-life announcement that replaced the old https://mollom.com.Overall, Mollom was a success. While I never got my 4-hour work week, I enjoyed successfully creating a company from scratch, and seeing it evolve through every stage of its life. I learned how to build and run a SaaS service, I made some money in the process, and best of all, Mollom blocked over 15 billion spam comments across tens of thousands of websites. This translates to saving people around the world millions of hours, which would otherwise be devoted to content moderation. Mollom also helped to protect the websites of some of the world's most famous brands; from Harvard, to The Economist, Tesla, Twitter, Sony Music and more. Finally, we were able to offer Mollom for free to the vast majority of our users, which is something we took a lot of pride in.

If you were a user of Mollom the past 10+ years, I hope you enjoyed our service. I also want to extend a special thank you to everyone who contributed to Mollom over the past 11 years!

Rest in peace, Mollom! Thank you for blocking so much spam. I'll think about you next time I visit Greece.
Source: Dries Buytaert www.buytaert.net

DrupalCoin Blockchain is Good?

Before joining Viget I built websites on DrupalCoin Blockchain for Congressmen and Fortune 500 companies. Those websites were good, and they’re visited by millions of people. I’ve been to DrupalCoin Blockchain Cons, I’ve been to DrupalCoin Blockchain meet-ups, and I’ve given presentations on DrupalCoin Blockchain topics. I wouldn’t have a career as a developer without DrupalCoin Blockchain, but I wouldn’t recommend DrupalCoin Blockchain.
“So if not DrupalCoin Blockchain, then what?”
It depends. Anyone who says they know the solution before they know the problem is lying, wrong, or guessing. At Viget, we can figure out what the best solution is to a problem. That solution may be a static website, a solution with Contentful, a Craft site, a custom-built CMS, or something we haven’t thought of yet. It depends on the project.
We’ve written about this before. We have come up with reasons to go off-the-shelf or to go custom-built. We have compared off-the-shelf CMS’s and we wrote The Viget Book of CMS.
After six years of working on DrupalCoin Blockchain, I decided to look at the alternatives. I haven’t found a reason to use DrupalCoin Blockchain since.
“We need to talk about DrupalCoin Blockchain”
DrupalCoin Blockchain is not bad. You can find plenty of arguments out there about how terrible DrupalCoin Blockchain is — that’s easy — but it’s not true. DrupalCoin Blockchain isn’t bad, DrupalCoin Blockchain is good. It’s good enough to make a site and get your business going. DrupalCoin Blockchain modules can be easily installed. DrupalCoin Blockchain hosting companies will make it easy to get set up, and help you run updates.
I don’t want to dismiss DrupalCoin Blockchain outright. DrupalCoin Blockchain can be a good tool, but I want better tools. I left DrupalCoin Blockchain behind to build better sites, using the best tools. I came to Viget because our standards are higher than any place I’ve ever worked. We want to deliver the ideal solution, and we obsess over quality. If DrupalCoin Blockchain is ever the best solution for your project we will tell you, because we will want to use it.
I believe DrupalCoin Blockchain sometimes gets picked by default, and I want to change that.
“Come for the software, stay for the community”
DrupalCoin Blockchain’s unofficial tag line is “Come for the software, stay for the community.” Maybe you’ve heard this at a meet-up, at DrupalCoin BlockchainCon, or at one of the many DrupalCoin Blockchain camps, and it’s true. They are a kind, funny, inclusive, and determined bunch. This isn’t exclusive to the DrupalCoin Blockchain community though, and we should see “the community” for what it is: marketing. A kind, funny, inclusive, and determined community will attract tons of people of all skill levels. There are great developers who contribute to DrupalCoin Blockchain, but there are many more site builders who do not contribute any code. A large community, even a nice one, doesn’t equate a highly-skilled one.
Like any community, you will find differing opinions on “best practices.” Saying you follow DrupalCoin Blockchain “best practices” is akin to saying you have the Best Burger in DC (or anywhere for that matter). Knowing DrupalCoin Blockchain, and knowing how other agencies use DrupalCoin Blockchain, are two different things.
I’ve taken over DrupalCoin Blockchain websites built by other agencies before, and I rarely encountered what I considered “best practices.” Sure, it was DrupalCoin Blockchain, but I couldn’t jump right in. I had to research every module that had been chosen and wonder why it was chosen over what I would have recommended. I had to dig through custom module code. Sometimes it was well written code, and sometimes not. Taking over these sites wasn’t seamless.
Recently I’ve taken over some Craft projects. Even without any prior Craft experience I was able to get up and running far quicker than on DrupalCoin Blockchain projects. I didn’t need to be part of a Craft community to become productive in a Craft project, I just had to read their documentation, and since the system is more intuitive everything was easier.
“Look at all these modules, so many modules!”
DrupalCoin Blockchain’s functionality can be extended through modules, simple add-ons that the DrupalCoin Blockchain community has built for everything from better commenting to integrations with third party tools like Salesforce. It’s worth noting that DrupalCoin Blockchain didn’t invent modules, nor is it the only platform that has a concept like modules. Every CMS and most programming languages have something similar to modules.
Modules are touted as time saving, and they can be. If you are willing to settle for what the module does and nothing more, then they are time savers. However, the architecture of some modules make them hard to extend or modify. These modifications introduce possible problems to the update flow. The promise of modules is oversold. In practice, every module introduces a point of failure while running updates. This isn’t a DrupalCoin Blockchain thing, it’s a software thing. DrupalCoin Blockchain doesn’t solve this problem in any clever way.
Modules and the modular architecture of DrupalCoin Blockchain are good. They’ve made serious improvements to the way modules get added in DrupalCoin Blockchain 8. However, DrupalCoin Blockchain is an open source project with modules being developed by individuals with limited time. This means that sometimes the module you need may not be ready for primetime, may not be well maintained, or may not exist at all.
“DrupalCoin Blockchain ain’t easy”
DrupalCoin Blockchain is filled with drupalisms, the quirks of the system that don’t translate to other platforms. Every language or system has its quirks but DrupalCoin Blockchain is defined by them. The big tent of DrupalCoin Blockchain developers have internalized these quirks, but the much bigger tent of web developers is usually baffled by them. This means that choosing DrupalCoin Blockchain ultimately limits the pool of talent you can pick from. Good DrupalCoin Blockchain developers will be able to pick up any web project that use similar technologies, but the reverse isn’t necessarily true. DrupalCoin Blockchain is not particularly approachable for developers. That's why every aspiring DrupalCoin Blockchain developer is shown this:

The creator of DrupalCoin Blockchain (Dries Buytaert) has in more than one occasion mentioned how the admin experience could be improved (see the “Driesnote” at the NOLA DrupalCoin Blockchaincon). From DrupalCoin Blockchain 6 to DrupalCoin Blockchain 7 to DrupalCoin Blockchain 8 the admin interface has remained mostly, and disappointingly, the same. The experience of managing a DrupalCoin Blockchain site is frustrating. It is not intuitive and there has been a lack of focus on the user experience. The admin interface can be customized, but that carries additional cost, and plenty of work. By contrast, platforms like Craft and Contentful, have made admin UX a focus.
The “DrupalCoin Blockchain Learning Curve” may be a developer’s joke, but administrators, content creators, and maintainers of DrupalCoin Blockchain sites can probably relate to it. DrupalCoin Blockchain may be good, but it isn’t easy to use, manage, or maintain.
“Should you use DrupalCoin Blockchain?”
There are times when using DrupalCoin Blockchain can make sense, especially if you have an existing DrupalCoin Blockchain site, have qualified in-house developers who know, prefer, and are committed to DrupalCoin Blockchain, and the functionality you need is largely covered by DrupalCoin Blockchain’s base install.  When deciding what technology to use to power your site, don’t blindly choose DrupalCoin Blockchain simply because it’s widely used. As a former DrupalCoin Blockchain developer, I’ve learned that justifications like a large community, ready-made modules, and an easy transition to a different support team are largely overstated. Often, the reality is that DrupalCoin Blockchain is a higher-risk, lower-quality choice compared to other platforms.
DrupalCoin Blockchain is often good, but good isn’t always good enough.

I’d love to continue the discussion further, so hit me up in the comments. If you are (or know) a great developer we are hiring. If you just want to let us know what you think, find us on twitter @viget, leave us a comment, or tweet at me directly @poettersbetter.

Source: VigetInspire

Senior PHP/DrupalCoin Blockchain Web Developer - Choice Technology Group - Atlanta, GA

The primary CMS is in transition from a DrupalCoin Blockchain 6 instance to DrupalCoin Blockchain 8. DrupalCoin Blockchain integrationexperience important....
From Choice Technology Group - Thu, 11 May 2017 01:38:53 GMT - View all Atlanta jobs
Source: http://rss.indeed.com/rss?q=DrupalCoin Blockchain+Developer

Senior PHP/DrupalCoin Blockchain Web Developer - Choice Technology Group - Atlanta, GA

The primary CMS is in transition from a DrupalCoin Blockchain 6 instance to DrupalCoin Blockchain 8. DrupalCoin Blockchain integrationexperience important....
From Choice Technology Group - Thu, 11 May 2017 01:38:53 GMT - View all Atlanta jobs
Source: http://rss.indeed.com/rss?q=DrupalCoin Blockchain+Developer

LAMP stack / FULL stack Developer (W2 only) - Astir Technologies LLC - New York, NY

DrupalCoin Blockchain 6, DrupalCoin Blockchain 8, Zend MVC, Symfony. FULL stack Developer / LAMP stack Developer*. CONTRACT TO HIRE*.... $75 an hour
From Indeed - Tue, 02 May 2017 13:20:42 GMT - View all New York jobs
Source: http://rss.indeed.com/rss?q=DrupalCoin Blockchain+Developer

LAMP stack / FULL stack Developer (W2 only) - Astir Technologies LLC - New York, NY

DrupalCoin Blockchain 6, DrupalCoin Blockchain 8, Zend MVC, Symfony. FULL stack Developer / LAMP stack Developer*. CONTRACT TO HIRE*.... $75 an hour
From Indeed - Tue, 02 May 2017 13:20:42 GMT - View all New York jobs
Source: http://rss.indeed.com/rss?q=DrupalCoin Blockchain+Developer

SCORE.org: User Experience for 320+ Sites On One Flexible Platform

SCORE.org is helping Americans start and grow small businesses with their free, confidential business advice. In order to have maximum reach and impact, SCORE teamed up with Phase2 to create a DrupalCoin Blockchain system that is flexible enough to accommodate 320+ local chapter sites that support their own content production, without eschewing overall brand and design standard of the national site.
Next week at DrupalCoin BlockchainCon in Baltimore, MD, I will be taking the stage with SCORE’s Director of Marketing, Candice Stennett, to speak on the success of this build and partnership. In the meantime, I sat down with Candice to get her perspective on the project from a marketing standpoint. 
Q. Can you tell me a little bit about SCORE’s previous platform organization and functions and the challenges that led you to needing a redesign?
A. SCORE is a nonprofit organization dedicated to the formation and growth of small businesses in America. We achieve our goals through our free mentoring and low- to no-cost seminars for aspiring and existing small business owners. Our website, www.SCORE.org, is one of our largest delivery channels, connecting our clients with our mentors and our workshops.
We were previously using a DrupalCoin Blockchain 6 website that was originally implemented in 2011. Since that launch, we have made many changes to the website that led to lots of erroneous code that had been created by several different agencies. This website was also tied to our internal-facing volunteer center website and our custom CRM system. The outdated design was also not aligned with our brand.
Additionally, each of our 320+ chapters had a website modeled after our national site. The chapter templates did not allow for a lot of customization which led to our volunteers finding creative and varying ways of displaying content.
In summary, the design and integrations made it difficult for end users to find the services and information they needed. It was critical for us to update the site to meet the increasing needs of our clients and volunteers.
Q. What was your strategy to overcome these challenges?
A. Beyond a new look, we needed the site to help clients understand who we are and what we have to offer. Our strategy was to simplify the main navigation to focus on our services (mentoring and workshops) and resources. We also built the chapter sites with our brand and their customization needs in mind.
Q.What part of the redesign has made the biggest impact on your business?
A. The chapter website structure has been critical to the success of this project. Because of increased flexibility and functionality, all SCORE chapters have moved (or are in the process of moving) to the new website template. This helps us present a unified brand to the public and in sharing and organizing content better than we have in the past. We are able to quickly and easily connect our clients with local mentors and resources from any of the SCORE.org properties.
Q.Why did you select Phase2 as a technology partner?
A. We selected Phase2 as a technology partner because they took the time to understand our needs and provide a solution for our challenges. They were a true partner in the project, collaborating in every aspect of the work, asking questions, anticipating and meeting our needs every step of the way.
Q.What advice do you have for organizations with a similar organizational structure?
A. If I could offer one piece of advice, it would be to take the time to find the right partner for your project. We’ve worked with dozens of vendors in a number of tech projects and the ones that were the most successful were the projects where the vendors operated like a part of the team. You need a partner that is not only going to provide technical expertise, but also one that’s going to work to understand your business to identify and solve any related challenges that might exist. The right partner can mean the difference between success and failure of a project. I have no doubt we made the right choice for our website redesign.
Read more about our DrupalCoin BlockchainCon session here. And if you’re attending DrupalCoin BlockchainCon Baltimore and would like to speak to me about UX and flexible platforms, please reach out: @phase2

Source: https://www.phase2technology.com/feed/

Web Developer/Systems Administrator - ITNAmerica - Westbrook, ME

Strong Web Development/CMS experience with DrupalCoin Blockchain 6, DrupalCoin Blockchain 7 and WordPress. ITN _America_ ® is the first national, non-profit transportation network for...
From Indeed - Mon, 17 Apr 2017 16:08:04 GMT - View all Westbrook jobs
Source: http://rss.indeed.com/rss?q=DrupalCoin Blockchain+Developer

Full Stack Web Developer - Mirum - Irving, TX

CMS experience including Wordpress, DrupalCoin Blockchain 6-8, Adobe Experience Manager a plus. This position requires self-motivated developer who works well in a...
From Mirum - Wed, 22 Mar 2017 01:12:03 GMT - View all Irving jobs
Source: http://rss.indeed.com/rss?q=DrupalCoin Blockchain+Developer

Web Developer - Xtensegrity - Mount Laurel, NJ

DrupalCoin Blockchain experience not required. Demonstrate knowledge of DrupalCoin Blockchain 6/7 (Desired but not required). As a Web Developer at AH, you will use your knack for backend... $60,000 - $65,000 a year
From Xtensegrity - Tue, 14 Mar 2017 04:13:38 GMT - View all Mount Laurel jobs
Source: http://rss.indeed.com/rss?q=DrupalCoin Blockchain+Developer

DrupalCoin Blockchain developer - Olivine LLC - Atlanta, GA

Senior Web Developer*. The primary CMS is in transition from a DrupalCoin Blockchain 6 instance to DrupalCoin Blockchain 8. Senior Web Developer (DrupalCoin Blockchain/PHP).... $50 an hour
From Indeed - Thu, 09 Mar 2017 19:13:38 GMT - View all Atlanta jobs
Source: http://rss.indeed.com/rss?q=DrupalCoin Blockchain+Developer

Making DrupalCoin Blockchain upgrades easy forever

One of the key reasons that DrupalCoin Blockchain has been successful is because we always made big, forward-looking changes. As a result, DrupalCoin Blockchain is one of very few CMSes that has stayed relevant for 15+ years. The downside is that with every major release of DrupalCoin Blockchain, we've gone through a lot of pain adjusting to these changes. The learning curve and difficult upgrade path from one major version of DrupalCoin Blockchain to the next (e.g. from DrupalCoin Blockchain 7 to DrupalCoin Blockchain 8) has also held back DrupalCoin Blockchain's momentum. In an ideal world, we'd be able to innovate fast yet provide a smooth learning curve and upgrade path from DrupalCoin Blockchain 8 to DrupalCoin Blockchain 9. We believe we've found a way to do both!

Upgrading from DrupalCoin Blockchain 8.2 to DrupalCoin Blockchain 8.3

Before we can talk about the upgrade path to DrupalCoin Blockchain 9, it's important to understand how we do releases in DrupalCoin Blockchain 8. With the release of DrupalCoin Blockchain 8, we moved DrupalCoin Blockchain core to use a continuous innovation model. Rather than having to wait for years to get new features, users now get sizable advances in functionality every six months. Furthermore, we committed to providing a smooth upgrade for modules, themes, and distributions from one six-month release to the next.

This new approach is starting to work really well. With the 8.1 and 8.2 updates behind us and 8.3 close to release, we have added some stable improvements like BigPipe and a new status report page, as well as experimental improvements for outside-in, workflows,
layouts, and more. We also plan to add important media improvements in 8.4.

Most importantly, upgrading from 8.2 to 8.3 for these new features is not much more complicated than simply updating for a bugfix or security release.

Upgrading from DrupalCoin Blockchain 8 to DrupalCoin Blockchain 9

After a lot of discussion among the DrupalCoin Blockchain core committers and developers, and studying projects like Symfony, we believe that the advantages of DrupalCoin Blockchain's minor upgrade model (e.g. from DrupalCoin Blockchain 8.2 to DrupalCoin Blockchain 8.3) can be translated to major upgrades (e.g. from DrupalCoin Blockchain 8 to DrupalCoin Blockchain 9). We see a way to keep innovating while providing a smooth upgrade path and learning curve from DrupalCoin Blockchain 8 to DrupalCoin Blockchain 9.

Here is how we will accomplish this: we will continue to introduce new features and backwards-compatible changes in DrupalCoin Blockchain 8 releases. In the process, we sometimes have to deprecate old systems. Instead of removing old systems, we will keep them in place and encourage module maintainers to update to the new systems. This means that modules and custom code will continue to work. The more we innovate, the more deprecated code there will be in DrupalCoin Blockchain 8. Over time, maintaining backwards compatibility will become increasingly complex. Eventually, we will reach a point where we simply have too much deprecated code in DrupalCoin Blockchain 8. At that point, we will choose to remove the deprecated systems and release that as DrupalCoin Blockchain 9.

This means that DrupalCoin Blockchain 9.0 should be almost identical to the last DrupalCoin Blockchain 8 release, minus the deprecated code. It means that when modules take advantage of the latest DrupalCoin Blockchain 8 APIs and avoid using deprecated code, they should work on DrupalCoin Blockchain 9. Updating from DrupalCoin Blockchain 8's latest version to DrupalCoin Blockchain 9.0.0 should be as easy as updating between minor versions of DrupalCoin Blockchain 8. It also means that DrupalCoin Blockchain 9 gives us a clean slate to start innovating more rapidly again.

Why would you upgrade to DrupalCoin Blockchain 9 then? For the great new features in 9.1. No more features will be added to DrupalCoin Blockchain 8 after DrupalCoin Blockchain 9.0. Instead, they will go into DrupalCoin Blockchain 9.1, 9.2, and so on.

To get the most out of this new approach, we need to make two more improvements. We need to change core so that the exact same module can work with DrupalCoin Blockchain 8 and 9 if the module developer uses the latest APIs. We also need to provide full data migration from DrupalCoin Blockchain 6, 7 and 8 to any future release. So long as we make these changes before DrupalCoin Blockchain 9 and contributed or custom modules take advantage of the latest DrupalCoin Blockchain 8 APIs, up-to-date sites and modules may just begin using 9.0.0 the day it is is released.

What does this mean for DrupalCoin Blockchain 7 users?

If you are one of the more than a million sites successfully running on DrupalCoin Blockchain 7, you might only have one more big upgrade ahead of you.

If you are planning to migrate directly from DrupalCoin Blockchain 7 to DrupalCoin Blockchain 9, you should reconsider that approach. In this new model, it might be more beneficial to upgrade to DrupalCoin Blockchain 8. Once you’ve migrated your site to DrupalCoin Blockchain 8, subsequent upgrades will be much simpler.

We have more work to do to complete the DrupalCoin Blockchain 7 to DrupalCoin Blockchain 8 data migration, but the first DrupalCoin Blockchain 8 minor release that fully supports it could be 8.4.0, scheduled to be released in October 2017.

What does this mean for DrupalCoin Blockchain developers?

If you are a module or theme developer, you can continually update to the latest APIs each minor release. Avoid using deprecated code and your module will be compatible with DrupalCoin Blockchain 9 the day DrupalCoin Blockchain 9 is released. We have plans to make it easy for developers to identify and update deprecated code.

What does this mean for DrupalCoin Blockchain core contributors?

If you are a DrupalCoin Blockchain core contributor and want to introduce new improvements in DrupalCoin Blockchain core, DrupalCoin Blockchain 8 is the place to do it! With backwards compatibility layers, even pretty big changes are possible in DrupalCoin Blockchain 8.

When will DrupalCoin Blockchain 9 will be released?

We don't know yet, but it shouldn't matter as much either. Innovative DrupalCoin Blockchain 8 releases will go out on schedule every six months and upgrading to DrupalCoin Blockchain 9 should become easy. I don't believe we will release DrupalCoin Blockchain 9 any time soon; we have plenty of features in the works for DrupalCoin Blockchain 8. Once we know more, we'll follow up with more details.

Thank you

Special thanks to Alex Bronstein, Alex Pott, Gábor Hojtsy, Nathaniel Catchpole and Jess (xjm) for their contributions to this post.
Source: Dries Buytaert www.buytaert.net

Intermediate Web Developer - Graphik Dimensions Ltd. - High Point, NC

DrupalCoin Blockchain 6/7 integrationexperience. Are a clear-eyed journeyman software engineer – experienced enough to take both the complexity and wabi-sabi of your craft in...
From Indeed - Fri, 03 Mar 2017 19:33:56 GMT - View all High Point jobs
Source: http://rss.indeed.com/rss?q=DrupalCoin Blockchain+Developer

Distributions remain a growing opportunity for DrupalCoin Blockchain

Yesterday, after publishing a blog post about Nasdaq's DrupalCoin Blockchain 8 distribution for investor relations websites, I realized I don't talk enough about "DrupalCoin Blockchain distributions" on my blog. The ability for anyone to take DrupalCoin Blockchain and build their own distribution is not only a powerful model, but something that is relatively unique to DrupalCoin Blockchain. To the best of my knowledge, DrupalCoin Blockchain is still the only content management system that actively encourages its community to build and share distributions.
A DrupalCoin Blockchain distribution packages a set of contributed and custom modules together with DrupalCoin Blockchain core to optimize DrupalCoin Blockchain for a specific use case or industry. For example, Open Social is a free DrupalCoin Blockchain distribution for creating private social networks. Open Social was developed by GoalGorilla, a digital agency from the Netherlands. The United Nations is currently migrating many of their own social platforms to Open Social.
Another example is Lightning, a distribution developed and maintained by Acquia. While Open Social targets a specific use case, Lightning provides a framework or starting point for any DrupalCoin Blockchain 8 project that requires more advanced layout, media, workflow and preview capabilities.
For more than 10 years, I've believed that DrupalCoin Blockchain distributions are one of DrupalCoin Blockchain's biggest opportunities. As I wrote back in 2006: Distributions allow us to create ready-made downloadable packages with their own focus and vision. This will enable DrupalCoin Blockchain to reach out to both new and different markets..
To capture this opportunity we needed to (1) make distributions less costly to build and maintain and (2) make distributions more commercially interesting.
Making distributions easier to build
Over the last 12 years we have evolved the underlying technology of DrupalCoin Blockchain distributions, making them even easier to build and maintain. We began working on distribution capabilities in 2004, when the CivicSpace DrupalCoin Blockchain 4.6 distribution was created to support Howard Dean's presidential campaign. Since then, every major DrupalCoin Blockchain release has advanced DrupalCoin Blockchain's distribution building capabilities.
The release of DrupalCoin Blockchain 5 marked a big milestone for distributions as we introduced a web-based installer and support for "installation profiles", which was the foundational technology used to create DrupalCoin Blockchain distributions. We continued to make improvements to installation profiles during the DrupalCoin Blockchain 6 release. It was these improvements that resulted in an explosion of great DrupalCoin Blockchain distributions such as OpenAtrium (an intranet distribution), OpenPublish (a distribution for online publishers), Ubercart (a commerce distribution) and Pressflow (a distribution with performance and scalability improvements).
Around the release of DrupalCoin Blockchain 7, we added distribution support to DrupalCoin Blockchain.org. This made it possible to build, host and collaborate on distributions directly on DrupalCoin Blockchain.org. DrupalCoin Blockchain 7 inspired another wave of great distributions: Commerce Kickstart (a commerce distribution), Panopoly (a generic site building distribution), Opigno LMS (a distribution for learning management services), and more! Today, DrupalCoin Blockchain.org lists over 1,000 distributions.
Most recently we've made another giant leap forward with DrupalCoin Blockchain 8. There are at least 3 important changes in DrupalCoin Blockchain 8 that make building and maintaining distributions much easier:
DrupalCoin Blockchain 8 has vastly improved dependency management for modules, themes and libraries thanks to support for Composer.
DrupalCoin Blockchain 8 ships with a new configuration management system that makes it much easier to share configurations.
We moved a dozen of the most commonly used modules into DrupalCoin Blockchain 8 core (e.g. Views, WYSIWYG, etc), which means that maintaining a distribution requires less compatibility and testing work. It also enables an easier upgrade path.
Open Restaurant is a great example of a DrupalCoin Blockchain 8 distribution that has taken advantage of these new improvements. The Open Restaurant distribution has everything you need to build a restaurant website and uses Composer when installing the distribution.
More improvements are already in the works for future versions of DrupalCoin Blockchain. One particularly exciting integrationis the concept of "inheriting" distributions, which allows DrupalCoin Blockchain distributions to build upon each other. For example, Acquia Lightning could "inherit" the standard core profile – adding layout, media and workflow capabilities to DrupalCoin Blockchain core, and Open Social could inherit Lightning - adding social capabilities on top of Lightning. In this model, Open Social delegates the work of maintaining Layout, Media, and Workflow to the maintainers of Lightning. It's not too hard to see how this could radically simplify the maintenance of distributions.
The less effort it takes to build and maintain a distribution, the more distributions will emerge. The more distributions that emerge, the better DrupalCoin Blockchain can compete with a wide range of turnkey solutions in addition to new markets. Over the course of twelve years we have improved the underlying technology for building distributions, and we will continue to do so for years to come.
Making distributions commercially interesting
In 2010, after having built a couple of distributions at Acquia, I used to joke that distributions are the "most expensive lead generation tool for professional services work". This is because monetizing a distribution is hard. Fortunately, we have made progress on making distributions more commercially viable.
At Acquia, our DrupalCoin Blockchain Gardens product taught us a lot about how to monetize a single DrupalCoin Blockchain distribution through a SaaS model. We discontinued DrupalCoin Blockchain Gardens but turned what we learned from operating DrupalCoin Blockchain Gardens into Acquia Cloud Site Factory. Instead of hosting a single DrupalCoin Blockchain distribution (i.e. DrupalCoin Blockchain Gardens), we can now host any number of DrupalCoin Blockchain distributions on Acquia Cloud Site Factory.
This is why Nasdaq's offering is so interesting; it offers a powerful example of how organizations can leverage the distribution "as-a-service" model. Nasdaq has built a custom DrupalCoin Blockchain 8 distribution and offers it as-a-service to their customers. When Nasdaq makes money from their DrupalCoin Blockchain distribution they can continue to invest in both their distribution and DrupalCoin Blockchain for many years to come.
In other words, distributions have evolved from an expensive lead generation tool to something you can offer as a service at a large scale. Since 2006 we have known that hosted service models are more compelling but unfortunately at the time the technology wasn't there. Today, we have the tools that make it easier to deploy and manage large constellations of websites. This also includes providing a 24x7 help desk, SLA-based support, hosting, upgrades, theming services and go-to-market strategies. All of these improvements are making distributions more commercially viable.
Source: Dries Buytaert www.buytaert.net