-
-
Notifications
You must be signed in to change notification settings - Fork 12.7k
Formalise criteria for feature inclusion in formulae #206404
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
Comments
Great idea 👏🏻 My take:
|
Sounds like that would require |
Yes, one or more of these would need to be keg-only.
I'm not sure this will be the case for e.g. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
What were you proposing (and why)?
Formalise a policy on what features can be included in formulae (when is this fine, what dependencies would we want to avoid and why, etc.). This is a tracking issue to facilitate discussion and improve our documentation on what "extra" features we are generally okay with including, and when it is fine to do so – what's the minimum number of requests beyond which we include things, etc.
A clearly documented policy allows us to point users making feature requests to it, and also ensures standards are applied consistently across formulae and by all maintainers.
The text was updated successfully, but these errors were encountered: