Talking Drupal #411 - D.o Issue Etiquette

Today we are talking about D.o Issue Etiquette with Tim Lehnen.

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

Topics

• Episode 361 Credit
• Most recent changes
• AI
• How should project maintainers respond
• How should the community respond
• Consequences
• Who developed the policy
• Who is responsible for enforcement
• How do these policies help maintainers
• Anything missing
• Future updates

Resources

• Talking Drupal #361 - Drupal Credit System
• Issue Etiquette
• Abuse of the Credit System
• Unhelpful comments
• Site moderator queue
• CWG issues
• Introduction to Contribution Best Practices for Organizations
• Slack Channel #contribution-recognition-feedback
• Drupal Association Membership

Guests

Tim Lehnen - @hestenet

Hosts

Nic Laflin - www.nLighteneddevelopment.com @nicxvan
John Picozzi - www.epam.com @johnpicozzi
Tim Plunkett - @timplunkett

MOTW

Correspondent

Martin Anderson-Clutz - @mandclu

• Brief description:
  • Have you ever wanted a simple way to view and store information about the overall health of your Drupal website? There’s a module for that!
• Module name/project name:
  • Site
• How old:
  • Project originally created in Sep 2007, current project looking like it took over the namespacex in June 2023
• Versions available:
  • 1.10.0-alpha11 works with D8 and above
• Maintainership
  • Currently very actively maintained, last release was in the past couple of weeks
• Does not have issue enabled, project page says to open issues against ox project, which currently has no open issues
• Usage stats:
  • 3 sites
• Maintainer(s):
  • Jon Pugh, a founding member of the Aegir project, among many others
• Module features and usage
  • The Site module stores information about the health of your site in a fieldable, revisionable entity
  • Provides a detailed history of the state of your site, including changes to configuration with a log of who changed what, where
  • Will include data on Drupal and PHP version, Git information, and more
  • Health can be based on the core Status report, the Site Audit module report, or a custom SiteState plugin
  • Can display an overall status indicator in the toolbar, so as a site owner or maintainer you don’t have to go to the Site Status page to see it
  • That page will display more detailed information, including the “reason” for the current status, the site’s history, and more
  • Integrates with the Site Manager module (also by Jon Pugh) which provides a UI for monitoring and managing a portfolio of Drupal sites
  • You can try out Site and Site Manager as part of the Operations project (machine name ox) as a Lando-based local setup of four sites, of which one provides a dashboard for the other three