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

Communication channel for public and private discussions for the WG #140

Closed
lirantal opened this issue Mar 1, 2018 · 17 comments
Closed
Assignees

Comments

@lirantal
Copy link
Member

lirantal commented Mar 1, 2018

@vdeturckheim and I have been changing some thoughts about the need for a more approachable communication channel for the team, and can potentially facilitate general open discussion by the community as well.

The problem today is that the internal (github) discussion system is not a friendly way of communication and carries with it a very "formal" atmosphere. Opening github issues is definitely easier but it is also quite an official approach. We find ourselves having some discussions through the Hacker1 platform but it's not ideal in terms of a "help channel", and you might not know who to mention, not everyone on the WG are also triage members, etc.

@vdeturckheim suggested slack where we can have private rooms for WG members, and public for general community discussions.

@vdeturckheim
Copy link
Member

We could use it to welcome newcomers who wish to get advice on how to join the WG and learn to know them (in the past weeks a few people approched me with such questions).

Also, the ecosystem triage team could benefit from a place to interact with people who think about submitting reports an are not certain how to do it (right now, people are mostly pinging us through twitter DM).

@bl4de
Copy link

bl4de commented Mar 1, 2018

Absolutely something what you must have :)

@MarcinHoppe
Copy link
Contributor

👍 for Slack. irc may also be an interesting open alternative.

@lirantal
Copy link
Member Author

lirantal commented Mar 3, 2018

if we do IRC I get to drive by memory lane with bitchx + eggdrops on a remote shell ;)

@gergelyke
Copy link
Contributor

I am happy to take this on! How about creating a slack org, with a public general channel where anyone can join and a private room where the triage team can discuss issues?

@ChALkeR
Copy link
Member

ChALkeR commented Mar 5, 2018

Slack is not a secure mean of communication.
I am not aware of any viable secure alternatives, though, and we already trust hackerone, so whatever.

@lirantal
Copy link
Member Author

lirantal commented Mar 5, 2018

@ChALkeR Slack may not be secure but we only need it for more streamlined communication channels. Even if we discuss some internal processes in the "private" channels we should definitely not be discussing there details of vulnerabilities - these should stay on the hackerone platform.

@gergelyke @vdeturckheim if there's no rejection on this, maybe we can start spinning this up and see how it goes, and discuss it further on the agenda meeting which is 3 weeks away. WDYT?

@gergelyke
Copy link
Contributor

@lirantal 👍 I can go ahead and register an org - how does nodejs-security-wg sound?

@vdeturckheim
Copy link
Member

lgtm

I don't know what is the current state of the art regarding public signup to slack tbh.

@gergelyke
Copy link
Contributor

in the past, it worked great for me: https://github.com/rauchg/slackin

@vdeturckheim
Copy link
Member

lgtm :D

@lirantal
Copy link
Member Author

lirantal commented Mar 5, 2018

Let's go :)

@MarcinHoppe
Copy link
Contributor

Where would this be announced for non-WG members of community to join?

@vdeturckheim
Copy link
Member

REAMDE link should be good when ready

@lirantal
Copy link
Member Author

lirantal commented Mar 5, 2018

Yep, we should push a badge there as well. I assume @gergelyke will do that.

@vdeturckheim
Copy link
Member

I believe we can close as our Slack is up.

@MarcinHoppe
Copy link
Contributor

👍 for closing.

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

No branches or pull requests

7 participants