Skip to content

README: "open your issue against" #34

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.

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
Chealer opened this issue Sep 7, 2023 · 5 comments
Open

README: "open your issue against" #34

Chealer opened this issue Sep 7, 2023 · 5 comments

Comments

@Chealer
Copy link

Chealer commented Sep 7, 2023

The README's Reporting issues section ends with the following paragraph:

If you face an issue and know which particular GitHub repository is most related, you can open your issue against that repository. If unsure, you can open an issue here.

An issue can be introduced. solved or discovered, but not "opened" (as opposed to a ticket).

This should read something like:

If you face an issue and know which particular GitHub repository is most related, you can report your issue against that repository. If unsure, you can file an issue report here.

By the way

  1. The list may be misleading, as there is also a repository for the website.
  2. The section should be retitled "Tracking issues"/"Issue tracking", or just "Issues" (since hopefully the issue will already be reported).
  3. The "Issues" link(s) from the Jump in section should be moved to this section.

@wimjongman
Copy link
Member

Thanks for pointing this out. I guess that when we say issue we mean issue report. One could argue that the term issue has become equivalent to the term ticket, which we used to use. Strictly speaking, you can also not open a ticket.

Please go ahead and change the content so that it is better.

@Chealer
Copy link
Author

Chealer commented Sep 11, 2023

Hi @wimjongman

Thanks for pointing this out.

An honour

I guess that when we say issue we mean issue report.

In some instances, clearly.

One could argue that the term issue has become equivalent to the term ticket, which we used to use. Strictly speaking, you can also not open a ticket.

Hum. Do you agree that a ticket can be closed?

Please go ahead and change the content so that it is better.

I think the formulation I suggested (without the emphasis) would be fine.

@wimjongman
Copy link
Member

Hum. Do you agree that a ticket can be closed?

Yes, if you say that a Ticket now means a bug report. A ticket used to be something that you bought to get on a train or something ;). Semantics... 🗡️

@Chealer
Copy link
Author

Chealer commented Sep 12, 2023

"Ticket"

Hum. Do you agree that a ticket can be closed?

Yes, if you say that a Ticket now means a bug report.

I wouldn't go that far as "ticket" didn't lose its original sense. But "ticket" can mean "issue report", or something very close to that (which I would basically describe as a recorded change request).

A ticket used to be something that you bought to get on a train or something ;). Semantics... 🗡️

Indeed, but the word complexified a long time ago. You will find plenty usages of "(IT/support/helpdesk) ticketing system" online even from their creators, and out of 3 dictionaries I consulted:

  • Wiktionary acknowledges "A service request, used to track complaints or requests that an issue be handled. (Generally technical support related)."
  • Cambridge dictionary acknowledges "a request sent online or by phone for help with a problem with a website, computer system, etc.: "
  • The only one which doesn't list that sense does list at least 1 non-physical sense.

And none of these indicate the sense as discouraged.

I am convinced that "ticket" can be used as a quasi-synonymous for "issue report", but I do not recommend it over "issue report".

@wimjongman
Copy link
Member

Yes, I agree.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants