TASEmulators / TASEmulators/BizHawk
Hostile Bug Report Responses are Hurting the Project
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 2.8k
- Forks
- 468
- PR merge metrics
- No merged PRs in 30d
Description
Natt's responses to the recent NES mapper issue have led to me having to field a very frustrating complaint about his behaviour. I shouldn't have to do this. Over the years I personally have become de-sensitized to it, as I'm sure may other contributors have, but you should know that ordinary users and other general observers have not. In particular, fiskbit's work has directly benefited NESHawk in ways that I am incapable of doing on my own, so you are even alienating people who you don't even know are important contributors.
To at least hopefully bring attention to this issue, I am withdrawing from this project and will no longer be contributing.
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
The issue names no files, tests, or entry points; start by reviewing the reported responses and the referenced NES mapper discussion. Done is not defined beyond addressing the conduct concern, so an agreed project-level response or concrete scope would be needed before implementation can begin.
Written by the indexing model from the issue text.
Assessment
- Domain
- developer-experience
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 10/100