Node-restify: thoughts on a having a slack to coordinate between maintainers?

[trentm]

@yunong @micahr @DonutEspresso @retrohacker (and others) Thoughts on having a Slack to coordinate restify maint? I'm fine if the answer is lukewarm. I don't want to make work for people. I certainly wouldn't want to create an impression that anyone needs to be responsive on it.

[retrohacker]

@trentm hey! I was actually just thinking about this again today :smile:

My main reservation on this is that back-channels can fragment project history. I'd like to explore opening ad-hoc locked issues (if locking is even necessary) for maintainers to talk things through on in a public place before we add another medium.

The last time we spoke about this was when we decided to remove our IRC link: https://github.com/restify/node-restify/issues/1055#issuecomment-297616586

[SamuelMarks]

FYI: IRC link is still at https://www.npmjs.com/package/restify

Related to updating README there, @trentm can you release 5.0.0 on npm also? 😀

[retrohacker]

@SamuelMarks thanks for pointing this out!

The 4.x README.md doesn't have the irc update.

5.0.0 was released but, when we later released 4.3.1, npm pointed the "latest" tag to the most recently released version (4.3.1) as opposed to the highest value semver. We just updated the latest tag to point back to 5.0.0. npm install restify is giving me 5.0.0 again :smile: would appreciate it if someone could verify its working on their end also!

[trentm]

@retrohacker Oh, sorry about the latest link, I didn't even think of that! https://github.com/restify/node-restify/issues/1392 added to deal with that for future 4.x releases.

[SamuelMarks]

Only just saw this, yeah confirmed 5.0.0 is working. Upgraded my projects around a week ago, no issues.

Thanks

[retrohacker]

Seems like nobody felt strongly about this, closing for now.

If anyone feels passionately about having another communication channel for the project feel free to comment and we can re-open.

[misterdjules]

I wasn't aware of this GH issue (thanks @trentm for pointing it out!), and I just created a restifyjs.slack.com workspace. I'm no expert in managing Slack communities, and I'm not even sure that currently anyone can join without being invited.

I created it because we were having discussions about https://github.com/restify/clients/pull/174, and it felt like hashing things out in a real-time communication system would help reach consensus.

If we feel that a Slack workspace is detrimental to the project, I'm fine with closing it. I agree with @retrohacker's earlier point that " back-channels can fragment project history". I hadn't thought about that, I think it's a very good point.

On the other hand, I'm also open to giving it a try and see whether this concern turns out to be valid.

[SamuelMarks]

Allow people to invite themselves with: https://github.com/outsideris/slack-invite-automation

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[misterdjules]

Closing as it seems the restifyjs Slack workspace has already been useful since we created it. @SamuelMarks I created a separate GH issue to explore the possibility of allowing any user to join the workspace using the solution you suggested.