On 09/05/2023 21:16, Jon Turney via Cygwin-apps wrote:
[...]
I've cleaned-up a lot of the inconsistencies around the abilities of
"trusted" maintainers.
They can already modify the package maintainer database to handle ITPs,
package orphaning, adoption and removal.
One of the reasons I moved the cygwin package maintainer 'database' (the
file cygwin-pkg-maint) into a separate repository [1], was so that it
could be separately access-controlled via gitolite.
This has now been done, so individuals on the "trusted maintainer" list
can now also modify it via the shared 'cygwin' login. (The access
privileges of that login are determined by gitolite depending on the
specific ssh key presented)
This opens up the possibility of adding more "trusted maintainers" in
future, without them having to also posses a sourceware login.
[1] https://cygwin.com/pipermail/cygwin-apps/2024-November/043931.html
They should now be permitted to upload, git push, deploy, vault, etc.
all packages (orphaned or not), as if they were the package maintainer.
