Re: [I] Review permissions for all actions in ATR (tooling-trusted-releases)

["dave2wave (via GitHub)" <gi...@apache.org>]

dave2wave commented on issue #242:
URL: https://github.com/apache/tooling-trusted-releases/issues/242#issuecomment-3539449683

   Some thoughts about properly defining the Release Manager role.
   
   - RM role
     - Unexpired GPG Public key associated with Committee
     - Current PMC member or committer
     
   - Only PMC members can associate keys to their Committee
     - Any PMC member gives permission to committers to be RMs by adding their key
     - Policy change from current infra policy where all committers are enabled or none
     
   - Other permissions
     - Should only RMs be allowed to move release candidates through the phases
     - Should only RMs be allowed to finish / approve of the final step?
     - No passing a bad tally to make a release unless we are in a debug state or tooling.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For additional commands, e-mail: dev-help@tooling.apache.org