doc: add GPG fingerprint for cjihrig

[cjihrig]

R=@Fishrock123 or @rvagg

[thefourtheye]

Is there a way we follow to verify the keys?

[Fishrock123]

cc @nodejs/tsc, as stated at #2189 (comment), Colin is interested in also helping to do releases. :D

[Fishrock123]

@thefourtheye see https://github.com/nodejs/io.js#verifying-binaries

[thefourtheye]

@Fishrock123 Thanks :-)

[rvagg]

tsc-agenda seems the appropriate mechanism to move forward on this, 👍 @Fishrock123

[Starefossen]

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 😄

[Fishrock123]

TSC voted to add Colin as a releaser as per #69

Just need to make sure the GPG key is signed and verifiable.

[rvagg]

@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?

[rvagg]

lgtm

[cjihrig]

@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.

[rvagg]

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!

[rvagg]

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.