+1 rename

Walter

> On Aug 24, 2025, at 12:07 PM, James Daugherty <[email protected]> wrote:
> 
> I'm not sure about the historical documentation websites.  All of the
> subdomains for documentation on grails.org have migrated to
> docs.grails.org into a single guide as of 7.0 (there's nested guides
> for Grails Data related projects).  I think the historical non-ASF
> documentation will remain at those links. My proposal was to only move
> the current documentation since it's been merged and can easily be
> modified.  We haven't discussed how to handle the historical
> documentation since we have no easy way of combining it.
> 
> On Sun, Aug 24, 2025 at 12:19 PM Gianluca Sartori <[email protected]> wrote:
>> 
>> +1
>> 
>> Are we going to change the website URL from gorm.grails.org to
>> data.grails.org as well?
>> 
>> 
>> Gianluca Sartori
>> --
>> https://dueuno.com
>> 
>> 
>> On Sun, 24 Aug 2025 at 16:01, James Daugherty
>> <[email protected]> wrote:
>> 
>>> Hi Everyone,
>>> 
>>> In the recent weekly meeting, we discussed how we have repackaged GORM
>>> related projects to be prefixed with 'grails-data-' coordinates, but
>>> we have not made an effort to continue renaming GORM everywhere else.
>>> 
>>> This thread is to discuss people's thoughts on removing references to
>>> GORM completely & only referring to Grails Persistence Libraries as
>>> "Grails Data" going forward.
>>> 
>>> My thoughts:
>>> 1. We renamed it because GORM does not match implementations - not all
>>> implementations are true ORMs anymore.
>>> 2. We have a trademark on Grails and do not have one on GORM.  This
>>> would allow us to enforce our brand.
>>> 3. Go has become significantly more popular and there's a conflicting
>>> project using 'GORM':  https://github.com/go-gorm/gorm  This project
>>> has existed since 2013, and due to previous names being not enforced,
>>> I don't think it's feasible to change at this point.
>>> 
>>> I'm personally a +1 to only using Grails Data going forward and
>>> dropping the GORM name.
>>> 
>>> -James
>>> 

Reply via email to