Guardr Scrum Meeting 2019-08-13

2019-08-13 4pm ET - 4:15pm ET

Join Zoom Meeting
https://zoom.us/j/942721180

One tap mobile
+16465588656,,942721180# US (New York)
+14086380968,,942721180# US (San Jose)

Dial by your location
+1 646 558 8656 US (New York)
+1 408 638 0968 US (San Jose)
Meeting ID: 942 721 180
Find your local number: https://zoom.us/u/asfpS5RHO

If you can't make the call, feel free to update and ask for help in Drupal Slack #contrib-guardr. Details on joining Drupal Slack: https://www.drupal.org/slack.

Meeting Notes

Good call today. Thank you for all who could attend!

Bruce

• Bruce has worked on the notifications issue and the issue to remove non-necessary composer related files in the main Guardr project
• Has a busy week or two coming up but still wants to be involved
• Shrop thanked him for his contributions and ready to help him stay involved as he can
• Bruce asked what testing looks like for Guardr
  • Shrop said we have some tests that can be done manual and automated to show composer install and the profile installs successfully. Could add on automated testing in the future. There is an issue for planning automated testing if anyone wants to work on that.
  • Jay mentioned Guardr Core gets a lot of testing via the Rain project, which uses it as a dependency

Jay

• Jay asked if the branch has been merged in Guardr Core that they have been relying on for the Rain project. Joe confirmed it had
• Jay asked if it is really necessary to have the Github and Guardr profile project if everyone is using the Guardr Core module
  • Shrop said that we have two goals for the project
    • On time easy install of Drupal 8 Guardr
    • Include Guardr Core in an existing project or as a dependency for another install profile
  • For now we can keep things are is and as a community figure out how to gather data to see what if anything should change
  • Guardr is now being setup to mirror other popular distributions which offer similar solutions

Joe

• Joe took a look at needs review items in the Guardr issue queue
• Helped the group by answering questions related to the new setup

shrop

• Reviewed the issue queue and next steps

Rob

• Called in and attended