Slack channel

[GeoffreyBooth]

There’s a Slack channel we can use: https://node-js.slack.com/messages/CEVD3CX33/ (node-js.slack.com workspace, #esm channel). Everyone is welcome to join. It’s the same Slack workspace that main Node is using, per https://github.com/nodejs/node/blob/master/README.md#support, in the public #esm channel.

We’ll need to figure out a way to archive the discussion, but I think this could be a good resource in addition to GitHub comments.

[devsnek]

given that we don't have proper message history in slack i would feel not good discussing things there. can we point people to irc or something instead?

[ljharb]

irc doesn’t necessarily have that either; i think it’s fine to just be sure to capture consensus and issues on github as they come up.

[devsnek]

@ljharb we have the history of #Node.js and #node-dev on irc going back several years, whereas slack is literally holding message history hostage for money.

http://logs.libuv.org/node-dev/2014-12-03
http://logs.nodejs.org/node.js/2012-03-05

[ljharb]

probably best not to have this debate; people are going to talk in all sorts of unlogged places (and already do); logging simply isn’t a requirement.

[devsnek]

@ljharb i'm opposed to The team is using the node-js.slack.com channel #esm for discussion., not the existence of discussion there.

[ljharb]

ah, that’s a different matter then. Perhaps one place you can find members of the team is the #esm channel on the node slack; another is #node.js and #node-dev on freenode irc or similar?

[MylesBorins]

If we don't have a way to more permanently save logs in a public and transparent way I am not comfortable with us stating this is an official team discussion. Here is an example of the logs for #node-dev on freenode http://logs.libuv.org/node-dev/latest

It is also worth noting that the nodejs slackers is not a foundation run environment. Do we have the ability to moderate this channel ourselves or do we rely on external intervention?

[ljharb]

@MylesBorins yes, we do - multiple foundation members, myself included, are admins there, which is why it's listed here.

I don't agree at all that "logging" is a requirement, as there are many unlogged places conversations are had. The important thing is to capture relevant data at some point - that doesn't mean we have to capture everything.

[MylesBorins]

@ljharb many unlogged conversations happen, but these are not mentioned as "the official place" to chat. Doing so in a way that isn't archived is not imho transparent

[jkrems]

The reason for me to actively support moving discussions to slack is because the alternative was keeping our various Hangouts and Twitter convos instead. Which are even less accessible than slack. Slack has the advantage of allowing quick huddles while always keeping the public / visible channels in view and encourage people to switch back to them.

[devsnek]

It can definitely be a place, just not the place.

[MylesBorins]

+1 to what @devsnek said. People can continue to have any conversations they want in as many platforms as they want. The challenge to me is more "is this the official place where we centralize work". The notes and records we have in github issues, irc logs, meetings notes, videos... are all important artifacts for people to figure out how we came to our decisions.

[ljharb]

@MylesBorins what about the suggested wording here?

[MylesBorins]

@ljharb I would be ok with that... I still would like to see the channel archived

[ljharb]

At the moment it's just a generic discussion channel; plenty of conversations about ESM in node happen in unlogged places outside the modules group, including other channels in that slack, and other non-logged channels on freenode.

[GeoffreyBooth]

Updated with a link to IRC, and a mention of the issues and PRs of our two working repos. @MylesBorins @ljharb @devsnek

[devsnek]

should be #node-dev since this is discussing development of core, not support.