Gianluca, Answer according to ChatGPT, they tried to block at first.. [image: Screenshot 2025-06-06 at 8.24.36 AM.png]
I think the answer will be a "yes, and..". We will definitely need the structured documentation as you noted, but we also need to position as much troubleshooting discourse to be indexable as possible; the LLM's are making unstructured text more valuable than ever. -Andrew On Fri, Jun 6, 2025 at 6:23 AM Gianluca Sartori <g.sart...@gmail.com> wrote: > Hi Andrew, > > I am not sure if ChatGPT and the like are happier with issue tracking or > Q&A data rather than structured documentation. > > I have used stack overflow a lot for the same reason I now use ChatGPT: to > quickly find solutions or options instead of reading the books :). > > Looking at the sources ChatGPT provides with its answers I don’t recall > having seen StackOverflow, but this is just my experience. > > I am not aware of how they assign a “relevance score” to their sources. > > I don't know, my gut tells me that a complete and structured documentation > would be better these days. > > Having recent news/talks/posts on Groovy & Grails will help for sure the > “relevance” and the perception of the technology. We all know it’s a > psychological thing but most of the marketing/communication is based on > that. > > Along with the Grails 7 release we need to find a way to better communicate > Grails, maybe with documented use cases and company names. So when people > ask ChatGPT about Grails that’s what it’s going to tell them :) > > Cheers, > Gianluca Sartori > -- > https://dueuno.com > > > On Fri, 6 Jun 2025 at 04:53, Andrew Garcia <and...@goodshuffle.com > .invalid> > wrote: > > > I believe I recall hearing that the content of the mailing list is > > crawlable bots yes? In this case that’s a strong value add to the > community > > as I believe it’s on our best interest that as much of the > troubleshooting > > conversations, and answers, are indexable by services like ChatGPT and > > Claude. Ai conversations at the go-to source for everyone/engineers of > the > > future and if we isolate all of the rich conversation away from the eyes > of > > those platforms we’re only hurting ourselves. > > > > I’m a fan of the expediency and organization of slack, but if it’s not > > replicated online and indexable we’re missing the future. > > > > -Andrew > > > > > > Sent from my iPhone > > > > > On Jun 5, 2025, at 10:07 PM, James Daugherty < > jdaughe...@jdresources.net.invalid> > > wrote: > > > > > > Hi Everyone, > > > > > > In this past week's developer meeting, we discussed the decline of > > > stackoverflow ( > > > https://blog.pragmaticengineer.com/stack-overflow-is-almost-dead/). > The > > > ASF provides us a users mailing list and we would like to transition > > grails > > > questions to the mailing list. We intend to keep slack as an > alternative > > > means of communication and log github discussions to the users mailing > > list > > > too. > > > > > > Is there any disagreement to this proposal? The idea is we'll remove > > > references to stack overflow on our website & suggest people ask > > questions > > > on the users mailing list, github discussions, or slack instead. > > > > > > -James > > > -- *Andrew Garcia* | Co-Founder & CEO and...@goodshuffle.com *Goodshuffle Pro* <https://pro.goodshuffle.com/?utm_source=goodshuffle&utm_medium=email&utm_campaign=employeesignature&fbid=emailsignaturehomepage> | Read our reviews on Capterra <https://www.capterra.com/p/167364/Goodshuffle-Pro/reviews/> <https://www.facebook.com/Goodshuffle/> <https://www.instagram.com/goodshuffle/> <https://www.linkedin.com/company/goodshuffle/posts/?feedView=all> <https://www.youtube.com/c/GoodshufflePro> <https://pro.goodshuffle.com/dispatch-lp?utm_source=goodshuffle&utm_medium=referral&utm_campaign=Feature_Release>
