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

Replace JS gitter with Discussions #600

Merged
merged 3 commits into from
Jan 21, 2021
Merged

Replace JS gitter with Discussions #600

merged 3 commits into from
Jan 21, 2021

Conversation

dyladan
Copy link
Member

@dyladan dyladan commented Jan 13, 2021

Following the example of Java (#587), The JS community has made the decision to move from Gitter to Discussions.

/cc @obecny

@yurishkuro
Copy link
Member

Those are not really equivalent media, but if the OTEL JS community simply does not have a need for real time chat, I think it's fine to remove it. I am not sure it's worth listing Discussions in the summary though, they are just a tool within GitHub like Issues, people should know how to use those already (it may be helpful to setup issues template to direct people to discussions for questions, e.g. https://github.com/jaegertracing/jaeger/issues/new/choose)

@Oberon00
Copy link
Member

I think Github Discussions (like PRs, issues) do have realtime features though? Like if someone comments while you have it open, the new comment will appear without you needing to refresh.

@dyladan
Copy link
Member Author

dyladan commented Jan 14, 2021

Those are not really equivalent media, but if the OTEL JS community simply does not have a need for real time chat, I think it's fine to remove it.

Most of the discussion in gitter has already been in question/answer format. The JS SIG itself rarely if ever uses it to discuss among ourselves. Moving these questions to GitHub makes them more easily searchable and useful over a longer period of time. It also prevents questions from getting lost to the chat history.

I am not sure it's worth listing Discussions in the summary though, they are just a tool within GitHub like Issues, people should know how to use those already (it may be helpful to setup issues template to direct people to discussions for questions, e.g. jaegertracing/jaeger/issues/new/choose)

I am just following the example of Java #587

@SergeyKanzhelev
Copy link
Member

whatever @open-telemetry/javascript-maintainers decide. Also fix the README.md in Javascript repository than to indicate that discussions are preferred like Java did

@SergeyKanzhelev
Copy link
Member

Maintainers want this change. So happy to merge this.

Please make sure to update the readme in SIG repositories to point to discussions instead of Gitter

@SergeyKanzhelev SergeyKanzhelev merged commit bf0d5e1 into master Jan 21, 2021
@SergeyKanzhelev SergeyKanzhelev deleted the js-discussions branch January 21, 2021 19:12
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

Successfully merging this pull request may close these issues.

6 participants