Issue description

Hello @rainboyan .

I've been following your work on Twitter and I think it is great that you have an interest in growing and evolving the Grails framework codebase.

On Twitter, and in some commits within your forked repo, you have been referring to this project as "Grails 2022".

The Grails framework is an open source project released under the Apache 2 license which affords you the right to fork, modify, and redistribute the source code with your modifications.

While the Grails framework is available under an open source software license, that license does not include the right or license to use Grails trademarks, which includes the word "Grails".

For more information, please see the Grails Foundation's Trademark Policy. In particular, this line:

§ You may not use one or more Grails trademarks, or anything similar, in the name or logo of forked software projects.

What I would prefer, is that we work together to bring some of your ideas into the Grails framework. To that end, I'd like to re-extend the invitation that I sent you privately for you to meet with the Grails Foundation's core development team to talk through some of your ideas and to explore and kick-off opportunities for you to contribute many of them directly to the Grails codebase.

If you would prefer to work on your own and release your own framework forked from the Grails codebase, please rename your project so that it follows the Trademark Policy of the Grails Foundation and can't be confused as being supported, backed, or otherwise affiliated with the Grails Foundation.

If you do choose to fork the framework, presuming you continue to release your modifications as open source, we will watch your progress and may incorporate some of your additions in to the Grails framework.