doc: add GPG fingerprint for cjihrig #2217
Conversation
|
Is there a way we follow to verify the keys? |
|
cc @nodejs/tsc, as stated at #2189 (comment), Colin is interested in also helping to do releases. :D |
|
@Fishrock123 Thanks :-) |
Fishrock123
added
the
meta
|
tsc-agenda seems the appropriate mechanism to move forward on this, 👍 @Fishrock123 |
|
The key needs to be added to the Docker Images as well; I'll take care of that as soon as it has been approved by the TSC 😄 |
|
TSC voted to add Colin as a releaser as per #69 Just need to make sure the GPG key is signed and verifiable. |
|
@cjihrig is one of these keys suitable for using as your public key for the webserver? https://github.com/cjihrig.keys If not, could you either add one there or send me one signed with your GPG key so I have a way of verifying it? |
|
lgtm |
|
@rvagg you can use the first key in my GitHub list. I also updated my keybase.io key to be the same one used in this PR, after Steven's comment on the call today. |
|
Done, you should be able to use all the tooling to promote and sign releases as soon as this PR is merged. I suggest that you propose and cut the next release with your new powers! |
|
Derp, I also meant to point you to https://github.com/nodejs/io.js/blob/master/doc/releases.md in case you weren't already aware of it. |
PR-URL: #2217 Reviewed-By: Rod Vagg <rod@vagg.org>
PR-URL: nodejs#81 Related: nodejs/node#2217 Signed-off-by: Hans Kristian Flaatten <hans.kristian.flaatten@turistforeningen.no>
R=@Fishrock123 or @rvagg