I agree that it would be reasonable to set emeritus as those who has not contributed for the past 12 (or 18) months and I think the git history should be the basis of that.
Den ons. 26. nov. 2025 kl. 15.01 skrev James Daugherty < [email protected]>: > Jeff pointed out that `git shortlog -esn --all` shows them all. I > assume we should include those 4 as founders, but as for the > historical developer list, should we only include those in the pom > authorship already + apache members? > > On Wed, Nov 26, 2025 at 8:50 AM James Daugherty <[email protected]> > wrote: > > > > 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 > -- Best regards Søren Berg Glasius Apache Groovy™ and Apache Grails® PMC --- Press ESC once to quit - twice to save the changes.
