mapbox / mapbox/mapbox-plugins-android
Meta-issue: Automatically closing reports for bugs that you haven't fixed yet is a terrible policy
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 242
- Forks
- 116
- PR merge metrics
- No merged PRs in 30d
Description
Your 'stale' bot appears to comment on reports that have been inactive for 6 months asking for more details (regardless of how many have been provided), then closes the report (after only 1 hour!). This results in legitimate bugs like #1044 being closed without a fix. I'm sure you're aware that bugs make your product less attractive to potential customers like me, and closing reports without fixing the issue makes you look unprofessional and motivates me to look for an alternative that is better managed.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by reviewing the repository's stale-bot configuration and the referenced report #1044; done would require an agreed policy for requesting details and closing unresolved reports.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100