mongoose: Too Many Issues with Mongoose
Do you want to request a feature or report a bug? Feature
What is the current behavior? Issues are opened without following format or posting reproduction scripts. Issues also contain support items that are best served elsewhere, like StackOverflow, forums, or chat, where documentation and proper usage can be referenced.
If the current behavior is a bug, please provide the steps to reproduce.
- I am a young Mongoose user.
- I do not know how to do something in Mongoose or am unaware about its functionality.
- I need support and therefore post an “issue” on this repo.
- My request is neither a feature nor a bug, yet I still need help from the community!
What is the expected behavior? I should really post on StackOverflow or some other channel (suggest opening a Slack channel?) for usage/documentation help.
For contributors, suggest adding in a **Repro script here (or something)** section instructing the user to post a detailed repro script for bugs, and a PR for features, respectively. If not provided, the issue should be closed until the poster can provide enough information to warrant the issue.
Please mention your node.js, mongoose and MongoDB version. node v8.1.4, mongoose v4.11.9, MongoDB v3.4.7
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Reactions: 2
- Comments: 15
Regarding issues without repro scripts, actionable details, etc. we have a GitHub format for that. In order to be friendly to beginners we try to nudge them into providing more information and mark the issue with ‘Needs Clarification’, and then close those out if there’s no response after a certain period of time. We already have a slack channel.
As for issues that have been open for a long time, sometimes there’s a good idea that we just haven’t prioritized yet, so we keep it open. The oldest currently open issue AFAIK is #1102 and its a worthwhile task, just other issues have been higher priority.