Seems good, I guess. Ahmad has been with the project for quite some time now, is pretty active and works for you company now, right? I think the main criteria for project-wide admin access is trust and availability so these persons can easily be contacted for whatever reasons.
Zbynek I know the least but I have seen him in reviews / PRs and some chat messages. I think you had more contact with him so I trust you. Updating the list of maintainers also means all names not listed here will be removed from the organization / projects? -- J. Colin Alworth schrieb am Montag, 16. Dezember 2024 um 22:14:03 UTC+1: > When I was assigned as an owner of github.com/gwtproject, there was only > one other non-Google member. The teams haven't changed since then - we have > two non-Google maintainers, and three non-Google site maintainers. > > I think we're long past due to update this setup - but as the most-junior > addition to the "owners" group, and as a person who stands to have at least > *some* financial gain from the GWT Project, I have avoided making any > administrative change like this. > > One set of changes I have been involved in - granting access to specific > community members to the extracted modules that they have contributed to. > This limits scope of individual contributors to the project they are > working on, and requires some oversight and coordination. This work is > somewhat stalled as we try to resolve an effective way to compile various > locales into working applications in J2CL, but that's outside the scope of > this message. > > I'd like to propose updating the maintainers lists for GwtProject, after a > short period of discussion here. A maintainer of a repository will have > write access - ability to manage issues and pull requests, ability to push > to branches (except once protected). > > I've discussed this with a few contributors, and would like to propose > updating the list of maintainers as follows (*existing members* in > italics): > > *Project-wide* - responsible for the entire github.com/gwtproject setup, > including admin access to projects: > *Colin Alworth* (past and present contributor/reviewer, manages releases) > *Thomas Broyer* (past contributor, current reviewer, maintains a set of > GWT archetypes and the suggested Maven plugin) > Ahmad Bawaneh (past and present contributor/reviewer, module migration, > release testing) > > *GWT* - Dev tools, JRE emulation, and existing (frozen) user modules: > *Jens Nehlmeier* (past contributor, current reviewer, module migration) > Zbynek Konecny (past and present contributor/reviewer, site maintainer, > release testing) > > *GWT-site/webapp* - gwtproject.org content. Presently separate repos, but > now that -webapp doesn't control deployments we might consider merging them: > *Jens Nehlmeier* > Zbynek Konecny > Frank Hossfeld (site maintainer, release testing) > > > I debated about how to write this message, and ended up deciding on this > format so that we could have a working starting point of past and future > maintainers to consider. I do _not_ have a specific set of "criteria to > meet" for any of these roles, and I would welcome any other nominations, > plus also any "seconds" to advocate for these other other nominations. > > This is a busy time of the year for many, so I will take no action > regarding this until at least Jan 8, and will send at least one reminder if > there is no other discussion before that time. > -- You received this message because you are subscribed to the Google Groups "GWT Contributors" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/5fd8e653-3bdf-47b3-9ba5-fe86203b6074n%40googlegroups.com.
