-
-
Notifications
You must be signed in to change notification settings - Fork 15.3k
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
ISSUE_TEMPLATES: remove the package request template #391926
base: master
Are you sure you want to change the base?
Conversation
Signed-off-by: Fernando Rodrigues <alpha@sigmasquadron.net>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, I think the incentives are bad here: it encourages people to add packages they don’t necessarily care about or don’t have the necessary domain knowledge to ensure are working over time. The result will often be broken packages or ones that get abandoned. As there is always going to be more and more software that Nixpkgs hasn’t packaged and achieving consensus that a piece of software is not worth packaging is hard, the number of these issues will basically inevitably grow forever.
I don’t think there’s never an instance where it makes sense to open an issue for software Nixpkgs is missing – e.g. “we don’t package this piece of software that is required for this common piece of hardware to work properly on NixOS” is a reasonable bug report – but we don’t need an entire form template to encourage it, and the Discourse is often going to be a better place for these requests.
I’ll leave time for others to comment, though.
As discussed in the Nixpkgs Contributions Matrix room, several contributors have reached a consensus that such a template only encourages future orphaned packages, and needlessly adds work for actual Nixpkgs contributors while demanding nothing from the issue reporter.
Things done
Add a 👍 reaction to pull requests you find important.