Node: [Meta] Using new GitHub Team Discussions

Created on 20 Nov 2017  路  12Comments  路  Source: nodejs/node

@GitHub has released a fantastic new Team Discussions Feature. This is something we can use to have discussions that do not pollute the issue or PR tracker, organized by teams. For @nodejs/collaborators , we can use the https://github.com/orgs/nodejs/teams/collaborators discussions.

meta

Most helpful comment

Seems reasonable, but what's the reason for it to be non-public?

I don't want to publicly disclose my geographical location or travel plans publicly on the internet, mostly. I'm all for engaging the community - but I'm a lot more comfortable coordinating with core and then reaching out to the community if appropriate.

This is especially relevant in cases core team members are involved in "reddit controversy" or are being harassed.

All 12 comments

This could be a solution for https://github.com/nodejs/node/issues/16963.
We will have to be careful in how we use this feature because team discussions are only visible to members of the org.

if github provides an api around this feature perhaps someone can throw together a site for viewing the discussions had there (readonly), or maybe github can be persuaded into adding a "let non collabs view this" option

API coming soon:
image
Until then IMHO if we use this we should manually mirror content to a public medium.

https://github.com/blog/2471-introducing-team-discussions

Looks like by default the discussions are public

Ah nope....it's public to org members, not everyone

But it seems like it's limited to org members
image
~I'll simply try this out.~ using @benjamingr's https://github.com/orgs/nodejs/teams/collaborators/discussions/1

Non members, could you 馃憥 if you can't see that?

It's called "Team discussions" after all, so maybe GitHub does not plan to make it public to everyone? Would someone like to reach out to them or should we wait whether they will come up with such an option?

I'd rather not encourage a private communications channel - although it would be a good place to discuss internal concerns (like CI lockdown due to security issues for example - where we might not want to make it advertised although it is already public).

What about using it for messages along the lines "I'm in country X(/city Y) visiting and I'd like to meet the local community if anyone is up for it"?

As in, coordinating meeting other collaborators in a non-public way. If someone ever comes here (Israel) I'd love it if they gave a talk to the local community (or came to a code-and-learn, or just to have a beer/coffee/whatever)

As in, coordinating meeting other collaborators in a non-public way.

Seems reasonable, but what's the reason for it to be non-public?

Seems reasonable, but what's the reason for it to be non-public?

I don't want to publicly disclose my geographical location or travel plans publicly on the internet, mostly. I'm all for engaging the community - but I'm a lot more comfortable coordinating with core and then reaching out to the community if appropriate.

This is especially relevant in cases core team members are involved in "reddit controversy" or are being harassed.

Doesn't seem like there is anything left to, ah, discuss so I'll go ahead and close this out.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

ctavan picture ctavan  路  87Comments

mikeal picture mikeal  路  197Comments

TazmanianDI picture TazmanianDI  路  127Comments

yury-s picture yury-s  路  89Comments

substack picture substack  路  878Comments