Seek to disambiguate maintainer/developer/issue-reporter #3
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Some of the wording seems to imagine that the person reporting an issue is a "developer" -- this can often not be the case; plenty of repositories contain code for applications that aren't aimed at developers, and the users of those applications are still encouraged to report problems via GitHub. I suspect this site will be even more useful to such projects.
I've also modified one instance of developer being used to mean maintainer.
The X/Y problem article seems to lean heavily into "folk reporting are developers"; I've left that alone as I guess it's more common to be the case there; but perhaps it's worth us rethinking the wording there so it's also helpful to maintainers of repositories where the target user base isn't other developers.