Skip to content
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

Future: Consider adding risk if many "downstream-only" patches #25

Open
david-a-wheeler opened this issue Jul 22, 2015 · 0 comments
Open

Comments

@david-a-wheeler
Copy link
Collaborator

Consider the number of downstream-only patches. E.G., if a deb or rpm includes more than 5 patches which have not been accepted upstream, the package receives a point. Distros carry patches for unique packaging requirements and when the upstream project is non-responsive. One or two patches may adjust for unique requirements, but beyond that (especially if they last a long time) they may suggest a non-responsive project. The patches are often less reviewed than the original project and so may add risk to the project all by themselves. This parameter may have some overlap with the Contributor Count parameter already included (if there are few contributors, downstream patches may be the only effective way to fix something).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant