Add issue #30839 to issue template checklist #26309

Open
opened 2026-02-21 13:05:01 -05:00 by deekerman · 2 comments
Owner

Originally created by @Semnodime on GitHub (May 3, 2023).

Checklist

  • I'm reporting a feature request
  • I've verified that I'm running youtube-dl version 2021.12.17
  • I've searched the bugtracker for similar feature requests including closed ones

Description

Include issue #30839 in new issue template checklist.
I discovered it while verifying that I'd not duplicate an existing (eventually closed) issue.
As I know where the 'new issue' button is, I didn't pay attention to the existing issues and overlooked the pinned one, despite it's convenience.

Originally created by @Semnodime on GitHub (May 3, 2023). ## Checklist - [x] I'm reporting a feature request - [x] I've verified that I'm running youtube-dl version **2021.12.17** - [x] I've searched the bugtracker for similar feature requests including closed ones ## Description Include issue #30839 in new issue template checklist. I discovered it while verifying that I'd not duplicate an existing (eventually closed) issue. As I know where the 'new issue' button is, I didn't pay attention to the existing issues and overlooked the pinned one, despite it's convenience.
Author
Owner

@dirkf commented on GitHub (May 3, 2023):

The site tells you to read #30839 before starting to open an issue. You're meant to have read it through before you even see an issue template. But even if someone weirdly ignores #30839, the issue search should reveal if the problem is a known one and avoid a duplicate issue.

@dirkf commented on GitHub (May 3, 2023): The site tells you to read #30839 **before** starting to open an issue. You're meant to have read it through before you even see an issue template. But even if someone weirdly ignores #30839, the issue search should reveal if the problem is a known one and avoid a duplicate issue.
Author
Owner

@Semnodime commented on GitHub (May 3, 2023):

@dirkf I understand that your intent was to let users know that there is relevant info best read before creating a new issue.

When I view the README front page and click the issues tab to report an issue, I already focus on the top right corner of my screen to click the button which appears after a small, well-known delay caused by my ISP. So the pinned issue didn't make it into my field of view at all, and adding it into the checklist of the template is a one-time effort in comparison to the time people might spend searching for existing issues if they happen to not see it for whichever reason.

Also, we live in a world where not every sign that tells you to do something is in the best interest of the reader, so instead of letting people know that they MUST read something (with a kinda yelling vibe of frustration), maybe let them know why it is in their interest to do so.
I understand that popular projects are sometimes bombarded with careless, incompetent, and at times even evil people, but keep in mind that most people who bring value know how to properly post an issue with the necessary information and commanding all people to also influence those who disrespect the rules won't help, as they won't read or listen anyway.

I am thankful for the formatting in #30839, as it saves time.
I am thankful for the effort of creating and maintaining youtube-dl.
Hope this helps.

@Semnodime commented on GitHub (May 3, 2023): @dirkf I understand that your intent was to let users know that there is relevant info best read before creating a new issue. When I view the README front page and click the issues tab to report an issue, I already focus on the top right corner of my screen to click the button which appears after a small, well-known delay caused by my ISP. So the pinned issue didn't make it into my field of view at all, and adding it into the checklist of the template is a one-time effort in comparison to the time people might spend searching for existing issues if they happen to not see it for whichever reason. Also, we live in a world where not every sign that tells you to do something is in the best interest of the reader, so instead of letting people know that they *MUST* read something (with a kinda yelling vibe of frustration), maybe let them know why it is in their interest to do so. I understand that popular projects are sometimes bombarded with careless, incompetent, and at times even evil people, but keep in mind that most people who bring value know how to properly post an issue with the necessary information and commanding all people to also influence those who disrespect the rules won't help, as they won't read or listen anyway. I am thankful for the formatting in #30839, as it saves time. I am thankful for the effort of creating and maintaining youtube-dl. Hope this helps.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/youtube-dl#26309
No description provided.