We meet every week via a google meeting. The times alternate each week to encourage attendance from multiple time zones. Each week we will provide a summary here to facilitate historical preservation & further discussion. If you would like to join this meeting, you can do so here: https://meet.google.com/her-tjpt-xmf
* We discussed the old grails build user and how it's still used to build the GPC & grails-plugins org. We need to transfer its email address to either priv...@grails.apache.org or add that email to the existing email group. Due to the difficulty we've had forwarding email in the group, we are contemplating handing over the domain to the ASF to have them fix it. The other proposal is to stop the existing emails and just change to priv...@grails.apache.org. - After discussion, we believe that stopping the usage of the old google emails is probably best and the most expedient / right solution long term. James D will update the Github Build Account & James F will look into the Maven Central side. * We discussed the need to merge code while awaiting for a vote, such as the 7.0.0-M4. If CI runs, it will publish and then we'll have a snapshot of a release version - very bad. We are going to propose we instead "tag" the release on its tag and then as part of the final vote / approval process, we'll merge the tag back into the branch. This has the added benefit that people can make changes while we're undergoing a vote & it will eliminate orphaned commits. James D to start a discussion thread to confirm agreement. * We discussed the 7.0.0-M4 release and how we had to cancel the initial vote. This was due to the dynamic command lookup feature of the shell (that intellij uses) not working. James D has fixed this issue and called a new vote. * There is currently an SVN staging issue (credentials are not working in the Github workflow), so files from the Github CI have to be copied manually. We've opened a ticket with infrastructure and are awaiting their help. * Multiple IntelliJ tickets were resolved this past week. Including: - the grails-core lockup when enabling the grails plugin - support for the ASF repackaging - support for the commands (this was why we redid the M4) * We discussed the grails-spring-security project and how the same reproducible / release changes need to be made to it. Worse, we've seen a number of test failures due to the 3.5 upgrade that need to be resolved. Mattias has been working on this, but he's rather busy right now and has asked for assistance. We are dividing up the work where possible. Once we have the tests running, we'll call for a vote for the plugin. * We discussed the decline of stackoverflow and the difficulty of finding previously answered questions in slack. https://blog.pragmaticengineer.com/stack-overflow-is-almost-dead/ is some documentation related to this. We want to migrate questions to the users ASF mailing list. Everyone seemed to initially agree, but James D will follow-up with a discussion thread to confirm agreement. * We discussed the adoption of asf.yaml and how it doesn't reset the branch protection rules. Since it doesn't reset the rules, James F agreed to work on defining an asf.yaml to help redirect Github discussions to the users mail listing. * Søren is working on updating the website per ASF policy. Paul staged an initial version to grails.apache.org that we will continue to improve. James F is working on the automation side. The goal is to have the website publishable so we can announce the M4. -James
