Discussions are here!

[blackjack4494]

Go HERE!

I recently applied for a Github beta feature called (Github) Discussions.

You can imagine it like a forum, reddit(, stackoverflow). It's a way to discuss about the project besides the code.
Here the official wording of Github

Software communities don’t just write code together. They brainstorm feature ideas, help new users get their bearings, and collaborate on best ways to use the software. Until now, GitHub only offered issues and pull requests as places to have these conversations. But issues and pull requests both have a linear format—well suited for merging code, but not for creating a community knowledge base. Conversations need their own place—that’s what GitHub Discussions is for.

Discussions live in your project repository, so they’re accessible where your community is already working together. Their threaded format makes it easy to start, respond to, and organize unstructured conversations. Questions can be marked as answered, so over time a community’s knowledge base grows naturally. And because discussions aren’t closed the way issues are, they can easily serve as a place for maintaining FAQs and other collaborative documentation. We recognize that community discussion is as much a part of development as coding, so discussion contributions appear in users’ contribution graphs.

[Surkal]

I would like to propose a pull request. But when I fork the project, it doesn't work and redirects me to my existing "youtube-dl" fork.
How do I do it?

[blackjack4494]

I would like to propose a pull request. But when I fork the project, it doesn't work and redirects me to my existing "youtube-dl" fork.
How do I do it?

@Surkal
Have a look here
#161

[Ashish0804]

Can we have a weekly or bi-weekly release cycle?

[blackjack4494]

Can we have a weekly or bi-weekly release cycle?

That's what discussions are for. Go here