Skip to content
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

doc: add GPG fingerprint for cjihrig #2217

Merged
merged 1 commit into from
Jul 24, 2015
Merged

doc: add GPG fingerprint for cjihrig #2217

merged 1 commit into from
Jul 24, 2015

Conversation

cjihrig
Copy link
Contributor

@cjihrig cjihrig commented Jul 21, 2015

@thefourtheye
Copy link
Contributor

Is there a way we follow to verify the keys?

@Fishrock123
Copy link
Contributor

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

@Fishrock123
Copy link
Contributor

@thefourtheye
Copy link
Contributor

@Fishrock123 Thanks :-)

@Fishrock123 Fishrock123 added the meta Issues and PRs related to the general management of the project. label Jul 21, 2015
@rvagg
Copy link
Member

rvagg commented Jul 22, 2015

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

@Starefossen
Copy link
Member

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
Copy link
Contributor

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

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

@rvagg
Copy link
Member

rvagg commented Jul 23, 2015

@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
Copy link
Member

rvagg commented Jul 23, 2015

lgtm

@cjihrig
Copy link
Contributor Author

cjihrig commented Jul 23, 2015

@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
Copy link
Member

rvagg commented Jul 23, 2015

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
Copy link
Member

rvagg commented Jul 23, 2015

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>
@cjihrig cjihrig merged commit a3c1b97 into nodejs:master Jul 24, 2015
Starefossen pushed a commit to Starefossen/docker-iojs that referenced this pull request Jul 27, 2015
PR-URL: nodejs#81
Related: nodejs/node#2217
Signed-off-by: Hans Kristian Flaatten <hans.kristian.flaatten@turistforeningen.no>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
meta Issues and PRs related to the general management of the project.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants