Today we are talking about The Drupal Bounty Program, How it supports innovation, and how you can get involved with guest Alex Moreno. We’ll also cover WebProfiler as our module of the week.

For show notes visit: www.talkingDrupal.com/445

• What is the Drupal Bounty program
• How and when did it start
• What issues and tasks are included
• Has the bounty program been successful
• Why was this program extended
• Do you see any drawbacks
• Can anyone participate
• How are issues for the second round being selected
• What do you see the future of the bounty program looking like
• Could this become like other bounty programs with cash
• Do you think the bounty program will help maintainers get sponsorship

• Introducing The Bounty Program
• Bounty Program Extension
• Bjorn
• Talking Drupal #425 - Modernizing Drupal 10 Theme Development

Alejandro Moreno - alexmoreno.net alexmoreno

Nic Laflin - nLighteneddevelopment.com nicxvan John Picozzi - epam.com johnpicozzi Matt Glaman - mglaman.dev mglaman

Martin Anderson-Clutz - mandclu

• Brief description:
  • Have you ever wanted to get detailed performance data for the pages on your Drupal sites? There’s a module for that.
• Module name/project name:
  • WebProfiler
• Brief history
  • How old: created in Jan 2014 by Luca Lusso of Italy who was a guest on the show in episode #425
  • Versions available: 10.1.5 which works with Drupal >=10.1.2
• Maintainership
  • Actively maintained, latest release on Feb 1
  • Security coverage
  • Test coverage
  • Not much in the way of documentation, but the module is largely a wrapper for the Symfony WebProfiler bundle, which has its own section in the Symfony documentation
  • Number of open issues: 36 open issues, 13 of which are bugs
• Usage stats:
  • 477 sites
• Module features and usage
  • Once installed the module adds a toolbar to the bottom of your site, within which it will show a variety of data for every page:
  • Route and Controller
  • Memory usage
  • Time to load (with some additional setup)
  • Number of AJAX requests
  • Number of queries run and the total query time
  • Number of blocks visible
  • How many forms are on the profile
  • Lots of other detailed information available through links
  • Reports are saved into the database, so you can dig through additional details such as:
  • Request information like access metadata, cookies, session info, and server parameters, in addition to the request and response headers
  • All of the queries that ran, how long each took, and even a quick way to create an EXPLAIN statement to get deeper insight from your database engine
  • You can also view all the services available, and with a single click open the class file in the IDE of your choice
  • A handy alternative to other performance monitoring tools like XHProf (either as Drupal module, or installed directly into your development environment), or commercial tools like Blackfire or New Relic
  • Discussion
  • Luca’s book Modernizing Drupal 10 Theme Development actually provides a great deep dive into this module