-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reconcile RubyGems with GitHub Team privileges #102
Comments
https://github.com/samvera/maintenance#updating-gem-ownership-permissions features the steps involved in ensuring that RubyGems ownership permissions are updated. |
https://github.com/samvera/maintenance/blob/main/script/grant_revoke_gem_authority.rb#L104 conditions upon the |
Realistically, I suspect that this is going to be blocked by #121 |
#123 advances this to some extent, but I suspect that questions will still need to be posed to the Samvera Community in order to gauge how best to document RubyGems projects which are anomalies. |
As discussed on the RubyGems documentation:
In order to define a policies for publishing Gems securely, I would please propose that the following criteria be met:
contributors
Team on GitHub).gemspec
files).gemspec
files, each linked to past roles within different organizations (there are certainly cases where an individual may move between organizations or change roles while remaining active members of Samvera). In this case, I propose that there be a primary e-mail address reserved for Samvera contributionsgem cert --build [email protected]
The text was updated successfully, but these errors were encountered: