Scheduled Updates

• What is the Scheduled Updates module?
• How does it differ from the Scheduler module?
• What are some of the use cases? What types of updates can be scheduled?
• Is it ready to be used?

Block Visibility Groups

• What is Block Visibility Groups?
• How does it differ from Context and Panels?
• Do you intend it to be a replacement for context?
• When would you use it instead Panels
• What are some example use cases?
• How does it work with other D8 block-related modules?
• Is it ready to be used?

Commerce 2.x for Drupal 8

• What has been the biggest success of Commerce on D7?
  • By starting from scratch on D7 technologies we created a solution that is intuitive to Drupal developers and easier to extend. And with 60k installs, we’ve set a record for ecommerce on Drupal in general.
• And what do you think have been its biggest weaknesses?
  • Not prioritizing UX from the start. Took us a year after the 1.0 release to create Inline Entity Form and recreate the admin screens as a part of the Kickstart. At that point many people already had the impression that Commerce was hard to use.
  • Not providing enough direction to developers. Flexibility is important, as is having unopinionated code. But developers also need to have a clear and obvious path forward. Having an opinionated layer on top, with sane defaults, can save a lot of development time and prevent frustration.
  • Not prioritizing certain features, leaving them to contrib instead. Modules that make up the checkout ux (checkout progress, checkout redirect, addressbook), discounts. Of course, all generals are smart after the battle.
• How has that influenced the development of Commerce 2.x?
  • With Commerce 2.x we once again started from scratch, evaluating all feedback received in the 1.x cycle. We decided to address all three of these major points.
  • Better UX means paying more attention to the product and order admin experience, as well as providing better checkout out of the box.
  • Better APIs means doing more work for the developer, especially around pricing and taxes.
  • And finally, we’re growing the core functionality. We’re expecting a dozen contrib modules to be no longer needed, as we address edge cases and add functionality.
• What are some of the biggest new features of Commerce 2.x?
  • Multi-store will allow people to bill customers from different branches (US and FR offices, for example), or create marketplaces like Etsy.
  • Improved support for international markets means better address forms, better currency management, and significantly better tax support, the kind that will reduce the need for people to use cloud-based tax solutions, at least in Europe.
  • Support for multiple order types, each with its own checkout and workflows will allow developers to create tailored experiences for different kinds of products, such as events, ebooks, t-shirts.
  • An integrated discounts UI means more power to the store admin.
  • And this is just the beginning. Under the hood there are many small features and improvements, over both 1.x and Kickstart.
• What has Commerce done to integrate better with the PHP and Drupal communities?
  • We’ve created several independent ecommerce libraries, attacking currency formatting, address management and taxes. These libraries are now being adopted by the wider PHP community, bringing us additional contributors.
  • On the Drupal side we’ve joined forces with the Profile2 team, creating the D8 Profile module that we’ll use for customer profiles. We’re also depending on Inline Entity Form, which is now shared with the Media team. We’re also moving some of our generic entity code into a new Entity API module, maintained together with Daniel Wehner and other community members.
  • Finally, we have been champions of Composer, the replacement for Drush Make, and required for any module that depends on external libraries.

The Future of Commerce 2.x

• Commerce 2.x is now in alpha2. What’s included? What’s next?
  • Alpha2 includes stores and products, as well as initial order and cart implementations.
  • It also has functional currency management and formatting, address and profile management.
  • Alpha3, to be released in the next two weeks, is focusing on completing the order and cart implementations, and adding the initial checkout implementation.
  • Post-alpha3 our focus will be on discounts, taxes, and finally, payments.
  • The best way to learn more about this is to read the drupalcommerce.org blog, where I post “Commerce 2.x stories” detailing work done so far. We have several new posts planned for february.
• When can we expect Commerce 2.x to be production ready?
  • Our current goal is to release a production ready beta by end of march. We should also have Search API and Rules by then. Leading up to DrupalCon New Orleans we’ll be helping the community implement shipping and licensing and port payment modules. At the same time, we’ll be focusing on reaching RC status.
• What’s the status of commerce contrib? Like PayPal, Authorize.net, etc.
• How can the community help?
  • Each new alpha welcomes more manual testing and feedback.
  • We also have office hours every wednesday at 3PM GMT+1 on #drupal-commerce where people can discuss code and help out on individual issues.
• Do you feel that requiring Commerce to be installed via Composer will impact adoption?
  • The average developer is already familiar with Composer and will benefit greatly from it, just like D7 developers benefited from Drush Make. Getting Drupal, Commerce, and all dependencies is a single Composer command, as is keeping it all up to date.
  • People unwilling to run Composer on their servers can run it locally and commit the result.
  • I’m also hoping we’ll be able to offer distribution-like tarballs on either drupal.org or drupalcommerce.org as we get closer to a release candidate.

Questions from Twitter

• howdytom ‏@howdytom
  Commerce Kickstart provides a great toolset with basic configuration. Is there a plan to do a Commerce Kickstart for Drupal 8? If not, will Commerce provide more out of the box solutions for a full featured shop?
  • Commerce Kickstart had several parts.
  • The first one was about providing better admin and checkout UX, as well as discounts. That’s now handled by Commerce out of the box.
  • The second was about providing a demo store with a developed set of frontend pages. That’s going to stay in contrib and will greatly benefit from the flexibility introduced by Drupal 8 and CMI.
  • It’s too early to plan a distribution yet. Drupal 8 has almost no contrib, and drupal.org doesn’t support using Composer to build distributions yet.
  • However, we are using Composer to provide single-command site templates, the kind that gives you Drupal core, Commerce and other modules. This will allow us to provide good starting points for different use cases, similar in nature to Commerce Kickstart 1.x.
  • Once 2017 comes around, we’ll investigate next steps.
• Jimmy Henderickx ‏@StryKaizer
  In commerce d8, will it be possible to alter a product name dynamicly (either by hook or other solution)?
• Czövek András ‏@czovekandras
  Any plans making iframe payment methods 1st class citizens? Thinking of running checkout form callbacks.
• Marc van Gend ‏@marcvangend
  How did D8 architecture change the way you code your modules?

Honeypot

• What is the Honeypot module?
• What prompted you to contribute the Honeypot module? Why was it originally created?
  Flocknote (two employers ago) user registration
  A bunch of my blogs / comments
• What methods or techniques does honeypot use to detect bots?
  A literal ‘honeypot’
  Time delay
• What types of foms can it protect?
• What’s different about Honeypot vs. other spam prevention modules like CAPTCHA and Mollom?
  Avoid punishing the user (explain)

Drupal 8 and Future of Honeypot

• How did the port of Honeypot to Drupal 8 go?
• Have you started developing new sites in Drupal 8? And if so, how’s that going?
• How have spammers adapted to tools like Honeypot, and how do you try to keep ahead of them?” “More spam getting through Honeypot lately” (https://www.drupal.org/node/2646380)

Community Issues

• You’re also involved a bit in other open source communities for projects like Ansible. How does the Drupal community compare? What are some things you would like to see improved?
• Is there anything you’ve done to make sure you can continue to maintain this open source project among many others both on drupal.org and github, and not get burned out?

Drupal 6 End of Live

• What does Drupal 6 EOL mean?
• When is Drupal 6’s End-Of-Life (EOL)?
  • February 24th
• Why is support for Drupal 6 being dropped by the Drupal project in the first place? (ie. why does our community even do this?)
  • What makes Drupal 6’s End-of-Life (EOL) different than previous ones (ie. Drupal 5)?
• What, specifically, will happen after February 24th?
  • All D6 modules will be marked as “unsupported” on Drupal.org - which will mean the ‘update’ module will start telling you that ALL your modules are out-of-date
  • Also, the status information that the ‘update’ module uses could go away at any time - so, you’ll no longer be able to rely on that in general (myDropWizard or another vendor MAY create a replacement for the ‘update’ module…)
  • The Drupal security team will no longer be making Security Advisories (or coordinating security releases)
  • In general, most module maintainers will no longer pay attention to Drupal 6 issues and will stop making new releases
• What should people with Drupal 6 sites do?
  • Archive the site, or
  • Plan upgrade, and
  • If you can’t upgrade by February 24th, buy Drupal 6 Long-Term Support from one of the “official” vendors:
    • https://www.drupal.org/node/2646980
• What makes the “official” vendors special (vs. any other vendor)?
  • Get confidential information from Drupal security team
  • Agree to follow security team processes and release all security patches publicly
  • Were vetted by the Drupal security team
• How will the Drupal 6 LTS work?
  • Same process as security team - but work done by vendors rather than security team
  • Will publish patches on the D6LTS project:
    • https://www.drupal.org/project/d6lts
  • Likely, but not 100% decided:
    • Announce new patches on the D6LTS issue queue
    • Make new Pressflow 6 releases with the Drupal core patches
• So, can the community get this without working with a vendor?
  • Yes!
  • But each vendor only supporting those modules their customers depend on
  • And what about security issues that hackers find first?
• What does myDropWizard.com do? And how is your offer different than the other vendors?
  • “myDropWizard.com provides 24/7 support and maintenance from Drupal experts for a fixed monthly fee. We keep your site online, up-to-date and secure!”
  • Our Drupal 6 Long-Term Support offer:
    • http://www.mydropwizard.com/drupal-6-lts
    • making security fixes
    • fixing bugs
    • performing one-off maintenance and support tasks on request
    • getting your site back online in the case of an outage, and
    • remediation if your site gets hacked.
  • Basically, keep your site online and secure until you’re ready to upgrade - and we can help with a D7 or D8 upgrade as well
• Technical questions about how we do what we do?
• Your offering includes a whole bunch of stuff! Why don’t you have a “security updates only” offering?

Composer

• What is composer?
  • Dependency Manager for PHP
• How does it relate to Drush Make?
  • Surprisingly similar
  • “Getting off the island”
• What can you do with composer on a Drupal site?
  • download dependencies, drupal modules, themes, profiles, drush, external libraries etc
• How do you download contrib modules?
  • https://packagist.drupal-composer.org/
• How do you download contrib themes?
  • ^^
• Can you specify where to download project? ie: modules/contrib and modules/custom?
  • composer/installers & davidbarratt/custom-installer
• Where do you store custom modules/themes?
  • Two methods: Committing to your repo or creating separate repos
  • Reference repo in you composer.json
  • Toran Proxy
  • davidbarratt/custom-installer
• How can you specify and download a library to go with a module?
  • module should specify it in composer.json
  • if not submit a patch, and add to your composer.json for now
• Patches
  • cweagans/composer-patches

Use Cases

• drupal/drupal vs drupal/core
  • http://cgit.drupalcode.org/drupal/tree/composer.json
  • If you want to use the project-repo/web
  • composer create-project drupal/drupal
• Composer template for Drupal Projects
  • https://github.com/drupal-composer/drupal-project
• Build sites from scratch with composer install
• Update drupal/modules/themes/etc. with composer update

Project

• Drupal8 theming - why we did it
• Plan for the unknown (responsive 2.0 how can we make D8 move forward & not break everything.
• Seven theme & usability improvements in Drupal 8
  • Were you involved with Seven in Drupal 7?
  • What are your thoughts on alternate admin themes like Adminimal?
• CSS architecture in Drupal 8
  • Why BEM?
• Classy & Stable theme
  • Why you should always use a base-theme

Use Cases

• How do the changes affect people who want to create custom themes and base themes?

Questions from Twitter

• Eric J. Gruber
  Everything, really.
• Dragan Eror
  How to remove query string from the end of CSS link, so I can enable browser's live reload? #MUP150 #drupal8
• Eric J. Gruber
  What are some common hooks have changed from D7 to D8 that we need to be aware of?
• Tamás Hajas
  Example about how can the new Stable theme help the work of frontenders. #MUP150
• Tamás Hajas
  Status and future of core themes. #MUP150
• why isnt seven called 8 ;)

Project

• For people who might not know, what is a Drupal distribution?

  • Out of the box, vanilla Drupal doesn’t do much - you have to install modules and mold it into what you want
  • A distribution is Drupal prepackaged with contrib modules and themes, pre-configured for a specific use case (OOB, X+Y)

• What is Panopoly?

  • A “starter site” distribution (replacement for vanilla Drupal)
  • A “base distribution” on which to build other distributions
  • A set of Features modules that can be used outside of Panopoly

• Why would someone want to use Panopoly instead of vanilla Drupal?

  • Improved blank slate
  • Includes some the most popular modules and configuration that almost everyone is using anyway
  • Hide Drupal-isms from site managers and users
  • WYSIWYG, Media, responsive layouts, edit in place, live previews, improved search, UX improvements, a11y improvements
  • Include a bunch of stuff backported from D8: toolbar, responsive bartik, etc
  • Unified content/layout management system built on Panels eco-system
  • Rather than learning all that community knowledge over, re-use a well thought out, tested approach to doing Drupal

• Some people love Panels, but others hate it. Why would someone who isn’t a “Panels lover” want to use Panopoly?

  • Best of Panels eco-system
  • You build with Views, Entities/Fields, custom code, whatever - the Panels bits tie those things together and allow users to customize them
  • We hide the nastiest bits (page_manager UI) from users and site managers

• Why would someone want to create their own distro?

  • Boilerplate, build once / deploy lots, maintenance of lots of sites
  • Even small organizations can benefit

• What advantages do you get by build your distro on Panopoly?

  • Like “base theme” shared work (like WYSIWYG, responsive, etc) and defined approach
  • Focus only on the unique stuff in your distro (by fitting into Panopoly’s architecture)

• Why would someone want to use one of Panopoly’s Features modules outside of Panopoly?

  • [Quick background on Feature]
  • Dozen or so features
  • If like just a piece of Panopoly (ex. panopoly_wysiwyg) you could steal it!
  • Lots of thought into buttons to enable, filtering for control/security, additional features like Media/Linkit

• Updating distributions can be hard. What does Panopoly do to help with this?

  • [explain why hard]
  • Docs
  • CI
  • distro_update

• Security updates in particular can be hard, because you have to wait for the distro to make its own update. How does Panopoly handle them?

  • [mention how handled in the past / security team]

• What are the plans for Panopoly in Drupal 8?

Drupal 8 from a site-builder’s perspective

• What makes Drupal 8 different from Drupal 7 and other previous versions?
• What about Drupal 8 are you most excited about?
  • CMI
• What contributed module(s) are you most excited to see for D8?
  • Rules
  • CMI extensions
  • Configuration Tools
  • Web Profiler

Drupal 8 from a developer’s perspective

• What makes Drupal 8 different from Drupal 7 and other previous versions?
• What about Drupal 8 are you most excited about?
• What’s making developing contributed modules better from your perspective?

StackStarter and TryDrupal8.com

• What is StackStarter?
• What is TryDrupal8.com?