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: update irc channels to point to #node.js and #node-dev #2743

Closed
wants to merge 3 commits into from

Conversation

nelsonpecora
Copy link
Contributor

Minor typo fix.

@ChALkeR ChALkeR added the doc Issues and PRs related to the documentations. label Sep 8, 2015
@ChALkeR
Copy link
Member

ChALkeR commented Sep 8, 2015

@nelsonpecora
Copy link
Contributor Author

Didn't even see that one! I'll update it.

@nelsonpecora
Copy link
Contributor Author

Searched through and found another irc channel reference in CONTRIBUTING.md. I think that's all of them.

@Fishrock123
Copy link
Contributor

Yes and no. We should point to both. Maybe.

#io.js is still the channel we use for actual development, and it will continue to be. It will probably be renamed at some point.

@evanlucas
Copy link
Contributor

Yea, I do like having the #io.js channel around still

@Fishrock123
Copy link
Contributor

Basically, #node.js is great for questions, but we need a development channel that isn't flooded. :S

Currently #io.js is that. I'll take care of doing a rename soon(tm).

@jbergstroem
Copy link
Member

+1 to #node.js-dev or similar

@jbergstroem
Copy link
Member

While at it, does anyone keep track of who has ownership flags of these channels? It'd be good to make sure that they are people active on irc and is part of the nodejs foundation and or tc and or wg.

@Fishrock123
Copy link
Contributor

I'm not sure who owns #node.js, but I own #io.js and #node-dev.

@ChALkeR
Copy link
Member

ChALkeR commented Sep 9, 2015

@Fishrock123 I think that would be @isaacs.
@jbergstroem Try /msg chanserv access #Node.js list (and the same for #io.js and #node-dev channels) =).

@nelsonpecora
Copy link
Contributor Author

Ah, these are all good points. I'd say 👍 to something like #node.js-dev (or #node-dev) as well.

Maybe point to #node.js in the root readme, then #node-dev in the contributing section (and in dev documentation)?

@jbergstroem
Copy link
Member

@Fishrock123 could you perhaps have a chat to @isaacs and see if you can get a owner flag? I'm an old IRC beard as well but probably not active enough to fulfil the duties required.

@Fishrock123
Copy link
Contributor

@jbergstroem I see no point in altering #node.js as it is, for the most part. I guess I can ask one of the mods so I can get access to the topic and stuff.

@silverwind
Copy link
Contributor

So about this PR. Maybe both should be listed?

@jasnell
Copy link
Member

jasnell commented Nov 13, 2015

At this point, it's likely just to leave the IRC channels alone as they are. -1 to this change.

@MylesBorins
Copy link
Contributor

@jasnell if we are going to keep the dev channel as io.js perhaps we can make reference to both #node.js and #io.js and explain the difference as to avoid confusion

@jasnell
Copy link
Member

jasnell commented Nov 13, 2015

@thealphanerd 👍

@jbergstroem
Copy link
Member

How about creating something like #node-dev and redirect #io.js there?

@evanlucas
Copy link
Contributor

#node-dev actually already exists, it just isn't really used.

@nelsonpecora
Copy link
Contributor Author

Per @jasnell and the conversation in this ticket, it seems like the channels are ok as they are. Closing this. 😃

@ChALkeR
Copy link
Member

ChALkeR commented Nov 17, 2015

@evanlucas

#node-dev actually already exists, it just isn't really used.

That's historic, a redirect from #io.js to #node-dev would solve that.

@jasnell

At this point, it's likely just to leave the IRC channels alone as they are. -1 to this change.

The current channel names confuse newcomers.

@jasnell
Copy link
Member

jasnell commented Nov 17, 2015

Yes, I agree but I think it's likely to be more confusing to change them... but that's just my personal opinion

@ChALkeR
Copy link
Member

ChALkeR commented Nov 17, 2015

@jasnell How would it, if #io.js would automatically redirect everyone to #node-dev?

@jasnell
Copy link
Member

jasnell commented Nov 17, 2015

@ChALkeR ... does freenode support channel redirection? I know some IRC servers do but I'm not familiar enough with freenode. If so, is redirection transparent to the user and is there a timelimit for the redirection being active (I believe some servers use a 60 or 90 day timeout)

@MylesBorins
Copy link
Contributor

I just asked in #freenode and they do indeed support it

i was directed to this link and told to look at channel mode: +f

"You need to be opped up in both channels when applying it or the target channel needs to be +F"

@jasnell
Copy link
Member

jasnell commented Nov 17, 2015

Ok. So long as the redirection can be done seamlessly with minimal impact to users, I have no objection :-)

@jbergstroem
Copy link
Member

@mikeal I'd argue the same if we manually had to shuffle people over, but since freenode supports redirects it should be a breeze. I like the fact that #node-dev is more descriptive than #io.js in terms of explaining the intended topic. #io.js is in a sense a split path between all users of io.js and devs.

@nelsonpecora
Copy link
Contributor Author

Rebased to fix a merge conflict, then changed CONTRIBUTING.md to point to #node-dev (Though the readme and cli/repl info both point to the more general #node.js channel).

@nelsonpecora nelsonpecora changed the title doc: update irc channel name doc: update irc channels to point to #node.js and #node-dev Dec 1, 2015
@Fishrock123
Copy link
Contributor

@yoshokatana Could you change it to that it links to both? #Node.js should be for general help, Node.js questions, etc, and #node-dev is for the development of node core specifically.

@nelsonpecora
Copy link
Contributor Author

Yup! @Fishrock123 should both channels also be listed in the readme and repl? It might be useful.

@MylesBorins
Copy link
Contributor

@Fishrock123 are we moving forward with this?

@Fishrock123
Copy link
Contributor

@thealphanerd Yes. Later today. There has been a notice in IRC since friday. I need to figure out with @piscisaureus if the IRC log bot will actually work with this though.

@Fishrock123 Fishrock123 self-assigned this Dec 14, 2015
@Fishrock123
Copy link
Contributor

Done. #io.js is now +if (forward joins to #node-dev, invite only to get into the actual channel).

@Fishrock123
Copy link
Contributor

LGTM

Fishrock123 pushed a commit that referenced this pull request Dec 15, 2015
IRC (general questions): irc.freenode.net #node.js
IRC (node core development): irc.freenode.net #node-dev

PR-URL: #2743
Reviewed-By: Jeremiah Senkpiel <[email protected]>
@Fishrock123
Copy link
Contributor

Landed in 3b30613 @yoshokatana Thanks for the patience!

cjihrig pushed a commit that referenced this pull request Dec 15, 2015
IRC (general questions): irc.freenode.net #node.js
IRC (node core development): irc.freenode.net #node-dev

PR-URL: #2743
Reviewed-By: Jeremiah Senkpiel <[email protected]>
@nelsonpecora
Copy link
Contributor Author

😄

@rvagg rvagg mentioned this pull request Dec 17, 2015
MylesBorins pushed a commit that referenced this pull request Dec 29, 2015
IRC (general questions): irc.freenode.net #node.js
IRC (node core development): irc.freenode.net #node-dev

PR-URL: #2743
Reviewed-By: Jeremiah Senkpiel <[email protected]>
MylesBorins pushed a commit that referenced this pull request Jan 19, 2016
IRC (general questions): irc.freenode.net #node.js
IRC (node core development): irc.freenode.net #node-dev

PR-URL: #2743
Reviewed-By: Jeremiah Senkpiel <[email protected]>
@MylesBorins MylesBorins mentioned this pull request Jan 19, 2016
scovetta pushed a commit to scovetta/node that referenced this pull request Apr 2, 2016
IRC (general questions): irc.freenode.net #node.js
IRC (node core development): irc.freenode.net #node-dev

PR-URL: nodejs#2743
Reviewed-By: Jeremiah Senkpiel <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
doc Issues and PRs related to the documentations.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

9 participants