-
-
Notifications
You must be signed in to change notification settings - Fork 171
Demo KeyBox at next WG Meeting #806
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
Comments
this sounds promising, we've the times where we've had to revoke and replace the global keys we use have been pretty painful (Ansible has helped somewhat) and giving temporary access to collaborators usually involves forgetting that they were given access and leaving their keys in place |
@rvagg, this is the exact issue that I was experiencing with AdoptOpenJDK before I started using KeyBox |
Lets plan to have on the agenda for the next meeting which is Aug 22nd at 4 EST. Next week ! |
@gdams agreement on this was that waiting till next meeting (3 weeks, 12th September) is fine, but if we don't hit that target it might be worth arranging a one off meeting to demo this. If you're going to be busy by the 12th, we should maybe look at organising something (probably on a Tuesday evening). |
Demo happened, closing |
@mhdawson I think at the meeting we said we should keep this open for other feedback, and for progress on getting it running. Obviously it can just be a new issue, either way. |
Uh oh!
There was an error while loading. Please reload this page.
I would like to demo KeyBox at the next Build WG meeting.
The main selling points to me:
My plan would be to set up a KeyBox server on a small linux machine and configure this for the community to manage all of their machines. I have been successfully using this system for managing key access to the AdoptOpenJDK build farm and think that it's a suitable candidate for the Node.js Community to also use.
Please note that I am in no way affiliated with KeyBox, I just love how great it is!
The text was updated successfully, but these errors were encountered: