It seems to me that both registered logos have the GRAILS wording. Having been involved in many brand registrations in my life I would suggest registering just the logo (three cups in the circle) with no "GRAILS" text in it. The value of a registered mark is in the shape of it. Instead, for the last 20 years, the best way to protect a text is by owning a domain registered to a date.
My 2 cents Gianluca Sartori -- https://dueuno.com On Thu, 17 Sept 2026 at 00:27, James Fredley <[email protected]> wrote: > Hi all, > > Notes from today's Grails PMC call. > > 1. Micronaut merge / unanswered question > > PR https://github.com/apache/grails-core/pull/16320 was merged without > the question on the related change being answered. That question was for > the other repo. James commented on the relevant commit at the time: > > > https://github.com/apache/grails-micronaut/commit/4b86b739bdcdd2628fbf182805c23a1047cd670e#r200084970 > > > 2. grails.org and grails.io > > Both domains are now in the ASF Namecheap account. DNS is pointed at the > Cloudflare free account managed by the PMC. Planned domain and DNS work > is complete. > > 3. Grails trademarks > > USPTO records: > > - > > 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 > > Question on the call: do we want both marks (with and without the word > "Grails"), or only the three-cups mark without the word? Current > practice is the three cups without "Grails" as the favicon on the sites: > > https://grails.apache.org/favicon.png > > James will email Mark, leaning toward yes on the three-cups-only mark > for that reason. > > 4. Dinner Monday night in Glasgow > > Two options under discussion: > > - Mharsanta: > https://www.google.com/search?q=Mharsanta+-+Scottish+Restaurant+%26+Bar > - Chez Mal Glasgow: https://www.google.com/search?q=Chez+Mal+Glasgow > > Please chime in if you have a preference. > > 5. Grails 8.0.0-RC1 > > Items in play: > > - Multipart uploads: https://github.com/apache/grails-core/pull/16040 > - Give read-only transactions the same meaning on Mongo as on Hibernate: > https://github.com/apache/grails-core/pull/16214 > - Enhance supported lock modes in GORM across Hibernate 5. Evaluate > whether this can be pulled forward: > https://github.com/apache/grails-core/pull/16344 > > Community Over Code is 12 October. 8.0.0 GA needs to be out before then. > > 6. Grails 8.1.0 and 8.2.0 > > - 8.1.0 can be based on Spring Boot 4.1.x, only if needed. > - 8.2.0 is planned against Spring Boot 4.2.x (expected December 2026). > > 7. Grails 9.0.0-M1 > > Target shortly after 8.0.0 GA. > > 8. Convert Grails Forge to Grails 8 and fold it into the root build > > Question was whether to merge for 8.0, 8.1, or 9. Decision on the call: > move to 8.1.x. > > Full PR: https://github.com/apache/grails-core/pull/16337 > > The Community Over Code hackathon will still focus on a single > application generator and CLI, even if Forge lands on 8.1.x. We will > still need the web/API generator regardless of how that work lands. > > Hackathon write-up: > > > https://github.com/apache/comdev-events-site/blob/main/source/events/2026/community-over-code/groovy-grails.md > > Goal stated there: one Grails application generator instead of two > (Forge vs Profiles), plus an agreed CLI command structure. > > Please reply on-list with corrections or anything I missed. > > Thanks, > James >
