Skip to content

Seek to disambiguate maintainer/developer/issue-reporter #3

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
davep wants to merge 3 commits into
base: main
Choose a base branch
from
Open

Seek to disambiguate maintainer/developer/issue-reporter #3

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
b39f0bf
Note that a duplicate issue might come from anyone willing to report
davep Aug 5, 2023
8e6b9d5
Note that an issue might come from anyone willing to report
davep Aug 5, 2023
7aec384
Try and stick to maintainer as the name for "the person running the r…
davep Aug 5, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/duplicate.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,6 @@

Typically applied to an issue that is a duplicate of another.

It's not uncommon for multiple issues by different developers to reference the same problem.
It's not uncommon for multiple issues by different authors to reference the same problem.
Maintainers will prefer to track work on a single issue, and will mark others as a duplicate.
It is good practice by the maintainer to link from the duplicate issues to the original issue.
2 changes: 1 addition & 1 deletion docs/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@
This site adds additional context to GitHub Issue labels.

The intention here is to be descriptive regarding the Open Source development process, not *prescriptive*.
In other words it is an attempt to document how developer generally apply these labels, and not attempt to impose some kind of standard.
In other words it is an attempt to document how maintainers generally apply these labels, and not attempt to impose some kind of standard.


!!! note
Expand Down
2 changes: 1 addition & 1 deletion docs/wontfix.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ This label may also be used if the maintainer considers the issue to not be a pr
Perhaps the likelihood of the issue occurring is just too remote, or requires exotic conditions to replicate.
It could also be that the maintainer is simply unable to fix the issue because it is out of their hands, and the root cause is in software they don't control.

## What can developers do?
## What can issue reporters do?

It's possible that the maintainer hasn't fully appreciated the issue in question.
Perhaps it seems a remote theoretical possibility to them, but is more likely than they appreciate.
Expand Down