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

An official place to discuss between early-adopters/users? #753

Closed
thbar opened this issue Dec 2, 2023 · 3 comments
Closed

An official place to discuss between early-adopters/users? #753

thbar opened this issue Dec 2, 2023 · 3 comments

Comments

@thbar
Copy link
Contributor

thbar commented Dec 2, 2023

Hello,

Related:

I'm dabbling more and more with Explorer, often converting small bits of non-Explorer code to Explorer once it's relevant or useful or I want to move into LiveBook and show more stuff.

I often have small questions popping up, that are not necessarily obvious to figure out after reading the documentation (although over time it will get easier).

I am pretty sure there are other early-adopters that would be happy to bounce small questions.

My question is: how can we make sure those exchanges are captured & not lost etc?

I am not sure what the right answer is - could be:

  • a Slack channel on the ElixirLang slack
  • a tag on the ElixirForum
  • GitHub discussions on this repository

In the past I had good success with a StackOverflow tag (as a maintainer it made it easy to point people to a specific response, or let them handle things directly), see https://stackoverflow.com/questions/tagged/kiba-etl.

I am pretty sure Explorer is going to see more and more interesting use-cases, and I want to make sure the knowledge is spread as much as possible!

Thoughts? Thank you!

@josevalim
Copy link
Member

ElixirForum is the place to go: https://elixirforum.com/c/elixir-framework-forums/nx-forum/105

There is also the #machine-learning channel on the Erlang Ecosystem Foundation Slack. You can request your an invite by creating a free account :)

@thbar
Copy link
Contributor Author

thbar commented Dec 2, 2023

@josevalim thank you!

Would you welcome a PR adding this information at the top of the readme maybe?

@josevalim
Copy link
Member

@thbar sounds good to me!

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

2 participants