luke
/
sbt
mirror of https://github.com/sbt/sbt.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Updated "Choice of forum" problem (markdown)

kenji yoshida 2024-11-07 18:48:28 +09:00
parent 26d0780a44
commit 7b823a0d83
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
"Choice-of-forum"-problem.md

@ -4,14 +4,14 @@ Bug reports or discussion could happen in person at work, on Twitter, on Gitter
Maintainers, on the other hand, want specific information on specific places. For sbt:
- Questions on [Stackoverflow][1]
- Issue report on [GitHub Issues][2]
- Feature and contribution discussion on [Lightbend Discuss][3]
- Feature and contribution discussion on [GitHub Discussions][3]
Often, we get into a meta discussion of "ok. but not this forum." Let's call this "Choice of forum" problem.
Basically, by the time the problem is happening, it's counter-productive to engage in the Choice of forum discussion. (Exception may be if someone tries to contact you personally without invitation) But let's say if there's a lively discussion going on in Twitter/Gitter, the best you can do would be to gather as much as information there instead of trying to move the forum elsewhere.
Once the discussion has settled, you can then gather up the info, and re-post them yourself; or ask the original reporter if they are up for reposting the information to GitHub Issues or Discuss, if you think it needs further investigation.
Once the discussion has settled, you can then gather up the info, and re-post them yourself; or ask the original reporter if they are up for reposting the information to GitHub Issues or Discussions, if you think it needs further investigation.
[1]: https://stackoverflow.com/tags/sbt
[2]: https://github.com/sbt/sbt/issues
[3]: https://discuss.lightbend.com/c/tooling
[3]: https://github.com/sbt/sbt/discussions