I opened https://github.com/apache/grails-gradle-publish/pull/21 to support titles in the grails publish plugin. Once this is merged, I'll put together a PR for us to further discuss based on this thread.
-James On 2025/11/28 14:33:46 Mattias Reichel wrote: > This would be nice to have in the poms, but I think it might be a lot > of work if we keep these lists separate per project. > Groovy, it seems, has the same aggregated, manually edited list[1], in > all module poms. > > [1] > https://github.com/apache/groovy/blob/5acebda191d346b531ceaa7ee0b08cd03fe04651/build-logic/src/main/groovy/org.apache.groovy-published-library.gradle#L82 > > > Den ons 26 nov. 2025 kl 14:50 skrev James Daugherty <[email protected]>: > > > > Hi Everyone, > > > > The recent bom property issue reminded me we still have not followed > > up on harmonizing our author list in our pom files. Currently, we do > > not list all of the developers under authors for each project. > > > > Groovy's pom > > (https://central.sonatype.com/artifact/org.apache.groovy/groovy) > > enumerates all authors and assigns a role to indicate if they're still > > active / founder / legacy. > > > > Groovy uses the following roles: > > 1. Founder > > 2. Developer > > 3. Developer Emeritus > > > > Going by https://www.infoq.com/news/2025/11/grails-7-released/, the > > following would be founders: > > 1. Graeme Rocher > > 2. Guillaume LaForge > > 3. Steven Devijver > > 4. Dierk König > > > > But I don't see #2 & #3 in the commit history. I assume we should > > only include those in the commit history? > > > > As for developer vs developer emeritus, I think we should consider > > anyone who hasn't contributed in the last 12 months as developer > > emeritus. Everyone else would just be listed as a developer. > > > > What are people's thoughts on this proposal? > > > > -James >
