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

email: add lts email alias #12

Closed
wants to merge 2 commits into from
Closed

email: add lts email alias #12

wants to merge 2 commits into from

Conversation

jasnell
Copy link
Member

@jasnell jasnell commented Dec 4, 2015

Add lts@iojs.org alias

/cc @nodejs/lts

For now, map the `report@io.js` alias to `tsc@io.js`. We can scope
this down to individuals if/when it becomes necessary. For now,
the TSC handles moderation and CoC violation issues so this seems
appropriate.
@rvagg
Copy link
Member

rvagg commented Dec 5, 2015

what's the purpose of this one?

@jasnell
Copy link
Member Author

jasnell commented Dec 5, 2015

To make it easier to send out meeting reminders/updates, etc. Not for general discussion

@jasnell
Copy link
Member Author

jasnell commented Dec 5, 2015

I'd consider it optional, really. not critical for it to land

@bnoordhuis
Copy link
Member

LGTM. Handy for sending out invites, amirite?

@rvagg
Copy link
Member

rvagg commented Dec 7, 2015

Invites for calendars are usually better when people are added individually but also possible to do on a list.

My concern here is precedent, do we mind if each WG ends up with its own email address? Perhaps not but let's think through possible ramifications.

@jasnell
Copy link
Member Author

jasnell commented Dec 7, 2015

No worries on holding off. I created a small command line tool that
generates a list of emails for nodejs team members that meets my needs for
now!
On Dec 6, 2015 5:49 PM, "Rod Vagg" notifications@github.com wrote:

Invites for calendars are usually better when people are added
individually but also possible to do on a list.

My concern here is precedent, do we mind if each WG ends up with its own
email address? Perhaps not but let's think through possible ramifications.


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

@jasnell
Copy link
Member Author

jasnell commented Jan 7, 2016

We don't actually need this. It's more of a convenience. Going to close and withdraw this.

@jasnell jasnell closed this Jan 7, 2016
@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.

5 participants