dauer commented on code in PR #390: URL: https://github.com/apache/grails-static-website/pull/390#discussion_r2397556286
########## posts/2025-10-07-apache-grails-graduation-top-level-project.md: ########## @@ -0,0 +1,106 @@ +--- +title: Apache Grails Graduates to Top-Level Project at The Apache Software Foundation +date: October 7, 2025 +description: The Grails Community is pleased to announce the graduation to Top-Level Project at The Apache Software Foundation. +author: James Fredley +image: grails-blog-index-1.png +--- + +# [%title] + +[%author] + +[%date] + +The Apache Grails team is excited to announce that Apache Grails has officially graduated from incubation under the Apache Groovy project to become a Top-Level Project (TLP) at The Apache Software Foundation (ASF). This achievement reflects the dedication of our community and underscores the strength of the ASF's open source ecosystems. + +Apache Grails is a powerful Groovy-based web application framework for the Java Virtual Machine (JVM) built on top of Spring Boot. It enables rapid application development through convention-over-configuration and Don't Repeat Yourself (DRY) principles, making it ideal for productively building full-stack applications with simplicity. Similar to Ruby on Rails, Grails has a nearly 20-year history of evolution and refinement, built on Java Enterprise foundations like Spring Framework, Jakarta EE, and Hibernate. + +"Becoming an ASF Top-Level Project signals the beginning of a new chapter for Apache Grails," said James Fredley, Apache Grails PMC Chair. "With ASF’s support and a thriving contributor community, we look forward to broadening adoption and advancing the project’s capabilities." + +We invite the community to join us in this new chapter—contribute, provide feedback, and help shape the future of Apache Grails! + +## Why use Grails? +- Rapid application development with high developer productivity +- Full-stack web framework with everything included +- DRY & Convention-Over-Configuration: Less boilerplate, sensible defaults +- Gentle learning curve with Groovy for productivity +- "Framework of frameworks" built on Spring Boot, Spring Framework, Jakarta EE, and Hibernate for enterprise foundations + +## History and Migration Journey +Work on the Grails framework began in July 2005, with the 0.1 release on March 29, 2006, and the 1.0 release announced on February 18, 2008. Over the years, ownership transitioned from G2One (2005-2008) to SpringSource (2008-2015), Object Computing (2015-2021), and the Grails Foundation/Unity Foundation (2021-2025), before joining the ASF in 2025. For much of its history, Grails was primarily led by single organizations. + +The migration to the ASF was an 18-month process starting in late Spring 2024. Motivations included shifting from single-organization dependency to a volunteer-driven model for sustainability, fostering community growth and revitalization with new energy from volunteers, aligning with open-source best practices like the Apache Way (consensus and transparency), enhancing governance through a Project Management Committee (PMC), mailing lists, and voting, and promoting vendor neutrality to encourage broader collaboration. + +Key steps involved forming a volunteer team, assessing project readiness, submitting an incubation proposal, modernizing the codebase (including mono-repo merge, build system updates, dependency upgrades, and Maven coordinates), and issuing releases under the ASF. Releases included Milestone 4 (June 2025, the first ASF release), Milestone 5 (July 2025), Release Candidate 1 (August 2025), Release Candidate 2 (September 2025), with the 7.0.0 General Availability expected in October 2025. + +The project passed the ASF board vote on September 24, 2025, officially graduating to TLP status. + +We extend our thanks to all contributors who made these advancements possible. Special mentions go to recent contributors across various Grails repositories. + +Takeaways from the migration process include establishing early relationships with the ASF Infrastructure team via Slack and JIRA, leveraging incubation mentors for success, planning the end state for codebase and repositories upfront to avoid duplicated efforts, addressing challenges in migrating automated Gradle and GitHub Actions workflows (now serving as a model for Gradle-based projects), and consolidating repositories from an initial 100 down to 18 (with 9 active). + +## Thank you! +A huge thank you to our amazing community for supporting the Grails Framework over the past 20 years! We’re excited for +the future and grateful for the opportunity to continue innovating and pushing Grails forward together. + +## Contributors +We would like to extend our heartfelt thanks to all the contributors who made Grails 7 possible. \ +Special thanks to: + +* [James Daugherty](https://github.com/jdaugherty) +* [James Fredley](https://github.com/jamesfredley) +* [Mattias Reichel](https://github.com/matrei) +* [Scott Murphy](https://github.com/codeconsole) +* [Brian Koehmstedt](https://github.com/bkoehm) +* [Søren Berg Glasius](https://github.com/sbglasius) +* [Paul King](https://github.com/paulk-asert) +* [Puneet Behl](https://github.com/puneetbehl) +* [Jonas Pammer](https://github.com/JonasPammer) +* [Gianluca Sartori](https://github.com/gsartori) +* [David Estes](https://github.com/davydotcom) +* [Michael Yan](https://github.com/rainboyan) +* [Jude Vargas](https://github.com/JudeRV) +* [Thomas Rasmussen](https://github.com/dauer) +* [Laura Estremera](https://github.com/irllyliketoast) +* [Hallie Uczen](https://github.com/shadowchaser000) +* [Jérôme Prinet](https://github.com/jprinet) +* [Stephen Lynch](https://github.com/lynchie14) +* [Andrew Herring](https://github.com/dreewh) +* [Yasuharu Nakano](https://github.com/nobeans) +* [Aaron Mondelblatt](https://github.com/amondel2) +* [Arjang Chinichian](https://github.com/arjangch) +* [Felix Scheinost](https://github.com/felixscheinost) +* [Carl Marcum](https://github.com/cbmarcum) +* [Eugene Kamenev](https://github.com/eugene-kamenev) +* [yucai](https://github.com/huangyucaigit) +* [gandharvas](https://github.com/gandharvas) +* [zyro](https://github.com/zyro23) + +Recent Contributors by Project: + +* [grails-core](https://github.com/apache/grails-core/graphs/contributors[%6MonthsBackForGitHub]) +* [grails-spring-security](https://github.com/apache/grails-spring-security/graphs/contributors[%6MonthsBackForGitHub]) +* [grails-static-website](https://github.com/apache/grails-static-website/graphs/contributors[%6MonthsBackForGitHub]) +* [grails-forge-ui](https://github.com/apache/grails-forge-ui/graphs/contributors[%6MonthsBackForGitHub]) +* [grails-quartz](https://github.com/apache/grails-quartz/graphs/contributors[%6MonthsBackForGitHub]) +* [grails-gradle-publish](https://github.com/apache/incubator-grails-gradle-publish/graphs/contributors[%6MonthsBackForGitHub]) +* [grails-redis](https://github.com/apache/grails-redis/graphs/contributors[%6MonthsBackForGitHub]) +* [grails-github-actions](https://github.com/apache/grails-github-actions/graphs/contributors[%6MonthsBackForGitHub]) + +[Combined Commit List](https://github.com/search?q=repo%3Aapache%2Fgrails-core+repo%3Aapache%2Fgrails-spring-security+repo%3Aapache%2Fgrails-static-website+repo%3Aapache%2Fgrails-forge-ui+repo%3Aapache%2Fgrails-quartz+repo%3Aapache%2Fincubator-grails-gradle-publish+repo%3Agrails-redis+repo%3Agrails-github-actions+is%3Apublic&type=commits&s=committer-date&o=desc) + +Their dedication and hard work have significantly contributed to the release of Grails [%version]. Review Comment: Should it say "Grails [%version]" or just "Grails 7" - I could be missing where the `%version` is set... -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
