-
Notifications
You must be signed in to change notification settings - Fork 9.8k
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
Dealing with so many open PRs #15045
Comments
Yes, my thought exactly. I submitted a PR (#14598) that seems to have been ignored completely. It's frustrating to submit PRs and not even get a one-line response. At the same time, I'm willing to volunteer to review PRs, if that is desired. |
My two cents as non-dev, why not spending a period (a week?) just focusing on PRs ? |
Ironically, this very issue is also dead. |
I was considering starting a "proper" fork which is more aggressive in terms of accepting new extractor pull requests, but I am afraid it might get out of hand quickly. |
Have you thought about doing something like this?
Obviously I'm not a youtube-dl maintainer, just throwing my 2 cents, waiting for my own PR to get reviewed. :D |
What is the purpose of your issue?
So it appears that youtube-dl is, well, struggling with a pull request overload. This issue is to discuss possible solutions for this. I am not trying to start any controversy, just to make everyone aware of the problem.
I believe that in a large part, there are two main sub-issues here:
Not enough maintainers. @dstftw is the only really active maintainer, and he cannot be expected to do almost all of the work.
Plenty of old PRs that should have been closed or merged by now. See [joemonster] Add new extractor #5177 and [walla] Fixed extractor and added site-wide video extraction #5163 for PRs that are surely dead, or TVI/IOL extractor #7080 and [iTunes] Add new extractor #14202 for ones where the submitter has received no response from maintainers for quite a long time.
I have no suggested solutions for this, so I wish to get some discussion going.
The text was updated successfully, but these errors were encountered: