mirror of https://github.com/sbt/sbt.git
Updated Issues gardening (markdown)
parent
1c66252af7
commit
a375c8415a
|
|
@ -2,4 +2,27 @@
|
|||
|
||||
This page is intended to provide guidelines for core developers and some contributors to garden GitHub issues.
|
||||
|
||||
See [Good First Issues](../Good-First-Issues).
|
||||
### "Choice of forum" problem
|
||||
|
||||
Communication work like flow of water -- they start and go where it's convenient, where there is least barrier.
|
||||
Bug reports or discussion could happen in person at work, on Twitter, on Gitter chat rooms, or on GitHub issues.
|
||||
|
||||
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]
|
||||
|
||||
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 them if they are up for reposting the information to GitHub Issues or Discuss, if you think it needs further investigation.
|
||||
|
||||
### Good First Issues
|
||||
|
||||
See [Good First Issues](../Good-First-Issues).
|
||||
|
||||
|
||||
[1]: https://stackoverflow.com/tags/sbt
|
||||
[2]: https://github.com/sbt/sbt/issues
|
||||
[3]: https://discuss.lightbend.com/c/tooling
|
||||
|
|
|
|||
Loading…
Reference in New Issue