Martin Anderson-Clutz – mandclu.com mandclu Fran Garcia-Linares – fjgarlin
Tim Lehnen – drupal.org/association/staff hestenet Nic Laflin – nLighteneddevelopment.com nicxvan
Martin Anderson-Clutz – mandclu.com mandclu
Hayden Baillio – hgbaillio
Topics
- Understanding the Contribution Record System
- Recent Changes and Migration Challenges
- Assigning and Displaying Contribution Credits
- Future Enhancements and Broader Contributions
- Collaborating on Commit Message Format
- GitLab Migration and Contribution Records
- Integration Challenges with GitLab
- Testing and Feedback on New System
- Future Plans and Community Involvement
- API Endpoints and Data Querying
- Gamification and Broader Adoption
Resources
Guests
This episode is sponsored by Amazee.ai
Hosts
Today we are talking about the New Contribution Records System, how it’s changed, and what you may need to do differently with guests Fran Garcia-Linares & Tim Lehnen. We’ll also cover Config Notify as our module of the week.
MOTW
Correspondent
For show notes visit:
https://www.talkingDrupal.com/522
- Brief description:
- Have you ever needed to maintain a site where a site owner had access to update site configuration, and wanted to be notified whenever they did so? There’s a module for that
- Module name/project name:
- Brief history
- How old: created in Feb 2020 by Fran Garcia-Linares (fjgarlin), one of today’s guests
- Versions available: 8.x-1.11, which supports Drupal 8.8 and newer
- Maintainership
- Actively maintained
- Security coverage
- Number of open issues: 2 open issues, neither of which are bugs
- Usage stats:
- Module features and usage
- Just like it sounds, this module lets you trigger notifications when the configuration deviates from the config management code in production.
- You can choose for the notifications to be sent immediately, or via cron, with an option for a daily digest. The notifications can be sent by email, or via Slack, using the slack module (if enabled).
- This should be an easy-to-implement solution if you support a site where users may be updating the site configuration in production. A different approach was discussed back in episode #236 Top Down Configuration
