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

Add inclusivity@ for inclusivity WG #13

Closed

Conversation

beaugunderson
Copy link
Contributor

Per @jasnell's suggestion to open a PR that adds the alias. :)

cc: @ashleygwilliams, @sup

Closes #9.

@Fishrock123
Copy link
Contributor

LGTM, @nodejs/tsc?

This stuff works automagically right?

@Starefossen
Copy link
Member

@Fishrock123 If I recall correctly Rod has to run a script before changes go live. Would be nice to have this fully automated though!

@jbergstroem
Copy link
Member

Yes I reckon we need to push this against the mailgun api.

@rvagg perhaps add the credentials to our infra group?

@rvagg
Copy link
Member

rvagg commented Jan 3, 2016

Lest anyone think I'm holding on to this for myself, the API key is accessible to anyone with access to the NF Rackspace account so it can be updated by any of the build/infra team. For clarification and detailed instructions on how to use it with this repo I've just updated the build/infra/admin_logins.md document in the secrets repo.

@jbergstroem
Copy link
Member

@rvagg: Ah. I can look at pushing it later today.

@rvagg
Copy link
Member

rvagg commented Jan 3, 2016

@jbergstroem nothing to push, this is not merged yet

@jbergstroem
Copy link
Member

@rvagg sorry; poor language. What I meant was that I can look at the scripts that pushes to get familiarised.

@ashleygwilliams
Copy link

hello! looks like this came up in the TSC meeting yesterday. could you give us an update @Fishrock123 @jasnell?

@jasnell
Copy link
Member

jasnell commented Jan 8, 2016

Ah, yes, there does not seem to be any objection so we'll get this landed.
After that it's a matter of running some script that actually creates the
alias. I think @rvagg does that part. I'll land it today.
On Jan 8, 2016 6:26 AM, "ashley williams" notifications@github.com wrote:

hello! looks like this came up in the TSC meeting yesterday. could you
give us an update @Fishrock123 https://github.com/Fishrock123 @jasnell
https://github.com/jasnell?


Reply to this email directly or view it on GitHub
#13 (comment).

@ashleygwilliams
Copy link

awesome! thanks for the quick reply @jasnell :) i'll share with the group at our meeting today

@jasnell
Copy link
Member

jasnell commented Jan 8, 2016

Landed in ea9a396

@jasnell jasnell closed this Jan 8, 2016
@ashleygwilliams
Copy link

🎉 yay!

@Fishrock123
Copy link
Contributor

Rod is away this week, maybe @jbergstroem can do it.

@rvagg
Copy link
Member

rvagg commented Jan 12, 2016

1 route(s) to add
0 route(s) to remove
Adding inclusivity -> ashley666ashley@gmail.com, julie.pagano@gmail.com, beau@beaugunderson.com, nathan@nathan7.eu, bryan@theoreticalideations.com, forrest@npmjs.com, jona@jona.io, thechargingvolcano@gmail.com, rtrott@gmail.com, node@sykosomatic.org...
``

This is active for @iojs.org now, I'll have to contact the LF helpdesk to make an @nodejs.org alias, I'll let you know when they've completed their bit.

@ashleygwilliams
Copy link

awesome ya'll! thanks so much for keeping this moving :)

@rvagg
Copy link
Member

rvagg commented Jan 12, 2016

@nodejs/build FYI the process here on @nodejs.org aliases is that you have to contact the LF helpdesk and/or @mikeal who I think has admin access to the Google Apps account for @nodejs.org now. In the past they have been fairly responsive to simple requests like this.

@beaugunderson beaugunderson deleted the add-inclusivity-alias branch January 12, 2016 07:37
@rvagg
Copy link
Member

rvagg commented Jan 12, 2016

alias was added to @nodejs.org and a test email was sent, hopefully y'all got that and can confirm it's working.

@Trott Trott removed the tsc-agenda label Sep 2, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants