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: * Discussed working through the recent release feedback we've given. This includes: - moving the releases to a new location (incubator) - associated tickets for access - all information being tracked in https://github.com/apache/grails-core/issues/14779 * grails-forge merge into grails-core - We are merged grails-forge into grails core per https://lists.apache.org/thread/lhhrqyscgbczkxk1bhqmsd00n7l79b71 - there are outstanding infrastructure items on this that will be resolved over the course of next week such as the secrets from forge being added to grails-core * sitemesh 2 revert - we discussed https://lists.apache.org/thread/8lynrl0yd6ykn749md1g2wjb8jph3s5l the need to revert sitemesh 2 - there was unanimous support to move forward so a vote thread will be created - Paul is to follow-up based on it being a derivative license of the ASF license. * Discussed the decision to split grails-publish gradle plugin - all related information is in the vote & discussion threads that are ongoing now. * Website Redesign - Martyn, a designer who volunteered to help us with our site, joined us to demo an initial proof of concept. Initial concept is here: https://v0-grails-redesign.vercel.app/ - we discussed the site guidelines that ASF requires: https://incubator.apache.org/guides/sites.html - we discussed the automated checks for the site: https://whimsy.apache.org/pods/public/project/grails - we discussed our trademark: https://tsdr.uspto.gov/#caseNumber=87172851&caseSearchType=US_APPLICATION&caseType=DEFAULT&searchType=statusSearch https://tsdr.uspto.gov/#caseNumber=87173404&caseSearchType=US_APPLICATION&caseType=DEFAULT&searchType=statusSearch specifically, what colors may or may not be allowed & the requirement to put `Grails` on the logo due to the trademark. - requested a light vs dark mode - we brainstormed what's most important including: -- Highest Developer Productivity -- Foundational Framework for Rapid Application Development & Maintenance -- Full stack framework vs just a rest API -- We referenced what we put in our announcements: `Grails is a powerful Groovy-based web application framework for the JVM built on top of Spring Boot that has many plugins to further extend its functionality.` -- We discussed how any front end framework can be used, including: --- GSP --- Any JS frontend with Grails Backend (React, Vue, Angular, etc) -- We referenced https://github.com/rainboyan/grails-htmx -- We referenced https://github.com/matrei/grails-inertia-plugin - the term "Modular Monolith" is often used in Spring Boot - how the importance of being able to maintain the application with 1 person: https://world.hey.com/dhh/the-one-person-framework-711e6318 - discussed the historical industry trends and how they appear to be reversing * An update was given on Grails domains & DNS: - need to update DNS for the 5 container instances (latest, next, snapshot, prev, and prev_snapshot) away from Cloudflare - need to still migrate repo.grails.org (grails.jfrog.org); which uses ~2TB/month and uses cloudflare as it's CDN - need to migration ge.grails.org and find the hostname we could point at - discussed email inbox hosting and decided we can use the Apache private list for any project related contacts. We will follow-up on any private accounts that have not been updated. * Discussed where documentation should live in the longer term. We currently have: - GitHub pages for docs.grails.org & grails-spring-security - grails.apache.org for our static site - legacy documentation as grails subdomains (async, gorm, gsp, views, testing) - longer term, James D advocated for us having a central documentation location for Apache related documentation that's also published to the ASF website. - shorter term, the legacy documentation can be updated if people are up for it, otherwise we can leave it as-is since it's hosted by github pages * We briefly discussed Grails' documentation system and all of the supporting infrastructure. Spring makes use of https://docs.antora.org/antora/latest/ which would give us documentation search and be able to manage our entire website. We left this for a future discussion, but people should check out the tooling and see what they think. * Our website (not documentation) now has https://analytics.apache.org * We discussed our social media accounts. James F has volunteered to continue to maintain them. Including: twitter & youtube in our 1password vault. We are adding Mastadon (@apachegra...@fosstodon.org ) and Bluesky: ( @grails.apache.org ) to go along with what Groovy has done previously. * We migrated our 1password instance so that it's controlled by the Grails PPMC. * We discussed the state of the asset pipeline and how we're waiting on gradle publishing. It was suggested to publish to maven central for the gradle plugin as well to make configuration simpler. -James
