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
Notes: 1. The Github Project board for Apache Grails has been fixed and we will start reviewing current ticket status in these weekly meetings. The board can be found here: https://github.com/orgs/apache/projects/487/views/2 We will start planning future changes around the items assigned to this board. 2. We discussed the Apache Grails website (https://grails.apache.org) and the next steps. James F reviewed the following tickets that will implement this work: https://github.com/apache/grails-static-website/issues/349 https://github.com/apache/grails-static-website/issues/350 3. The Apache Board requires all projects to report to them on a regular basis. Since Grails is being sponsored by the Groovy project, Groovy is responsible for our reporting while we're in incubation. Paul is assembling our report in the coming week and will be sending emails to the dev list for any corrections / feedback. 4. The work towards reproducible builds has continued. grails-core: Based on the previous mailing list discussions & the people at the meeting, we've decided to go ahead and merge the latest updates. We decided to change the documentation generation to use groovy 4.0.27-SNAPSHOT, while the bom will continue to refer to 4.0.26 until we can isolate the remaining 14 jar differences. Paul is continuing his work on the 14 jar differences, and hopes to have time this week to investigate. grails-forge It was discovered that there are barriers to having reproducible builds for grails-forge. See https://lists.apache.org/thread/sd0vntrsdlmqn8nnnwpjzbh4fl80sybg for this discussion & proposal. 5. Per the reproducible build thread, we have gone back to ASF Security asking if our proposed workaround for the remaining 14 jars is acceptable. We are pursuing this discussion in parallel to Paul's work to avoid any delays in the first milestone release under the Apache coordinates. 6. Over the past week, James D & James F made substantial changes to grails-wrapper, grails-wrapper-impl, grails-shell-cli, & profiles. As of the current code line, we no longer are creating start scripts manually nor are we copying files around via manual processes. Moreover, we have moved away from manual assembly of the grails distribution and have adopted the built in gradle plugin for application/distribution. The best news is because of this work, we have a fully functioning shell from end-to-end. You can now use the grails-shell-cli to create a grails project, then inside of that project execute grailsw (initially the grails-wrapper project) to pull the shell dependencies (grails-wrapper-impl project) and finally execute the pulled shell. There are some outstanding documentation issues left (like defining GRAILS_HOME to the distribution extraction location), but this work helps us get closer to an Apache coordinate release. This work also included updating to the latest maven resolver libraries, and as such we have removed the legacy sonatype plexus packages. We have updated to the latest version that we can, but javax is still included in those packages. We have not excluded them from the shell since the maven code still expects it. Once maven 4.0 is released, we'll revisit these dependencies. 7. Various IntelliJ issues were covered for both Grails & Groovy. At a high level, we're tracking all of these changes under https://github.com/apache/grails-core/issues/13910 Please note that we have a "blocker" ticket (https://youtrack.jetbrains.com/issue/IDEA-366647) because it affects contributions to grails-core (you have to disable the grails plugin and most people aren't aware of this). Thank you to everyone who has upvoted the IDEA ticket. If you have an IntelliJ license, please take time to upvote this ticket for higher priority. We also covered various IntelliJ issues specific to Grails 7. The coordinate change & the forge URLs specifically. The forge URL needs updated to be the cname instead of https://grailsforge-latest-cjmq3uyfcq-uc.a.run.app James F intends to reach out to Jetbrains to see about adding Grails 7 with Apache Coordinate support. 8. We reviewed the current status of the project listed at https://whimsy.apache.org/roster/ppmc/grails This status included the following items: 1. IP Clearance 2. Software Grant 3. ASF Headers on source code 4. Binary license issues. Items 1-3 have been updated and cleared. #4 is still in progress since the header work needs to be reviewed. We have added ASF headers on all of the core grails application dependencies as of Tuesday May 7. We still have some outstanding plugins that need headers added. Mattias volunteered to add the headers to those projects (security / redis / quartz / etc). 9. The grails-build account is used to publish to Maven Central. With the retirement of OOSRH, we need to migrate this account to start publishing snapshots Maven Central. We are working with OCI to get privileges to migrate it. 10. James D gave a brief status on the Hibernate 6 branch merge. We intend to merge the Hibernate 6 branch into grails-core, but it will only include the projects changed by Walter, which currently are the core & doc projects from hibernate. The proof of concept will be assembled by James D next week and a vote thread will be put out after Walter confirms this will work for continued development. 11. Google has discontinued their past container registry and replaced it with a new one. It is used to host images for start.grails.org. OCI has generously offered to continue to let us use their GCP hosting until we can determine what to do long term. James F is working with OCI to fix the infrastructure for the new container registry. We discussed longer term where to put this code. We know the micronaut apps are tiny in size, require minimal memory, and do not have a lot of throughput. No definitive answer was given, but we want to follow-up with ASF infrastructure on what they could provide. We may need financial contributions to cover this. The Friends of Grails collective was proposed to help fund this. There are no decisions at this time, other than to fix the current way. -James
