On Fri, Oct 25, 2019, 21:42 Randy Barlow <bowlofeggs@xxxxxxxxxxxxxxxxx> wrote:
On Fri, 2019-10-25 at 14:53 -0400, Neal Gompa wrote:
> It's not a bad feature to have in fedpkg, but it fundamentally does
> not help *other people* discover what we have in the distribution.
Yeah I've discussed this a bit with some people, and I agree. Fedora
*users* might use the packages app to find out the same info that
packagers want to find out.
However, I think that even though users and packagers are coming to
this app for the same purpose, only one of those purposes maps to the
CPE team's mission statement: the packager's. If you are a packager,
you *need* to know what versions are where at a glance, especially when
dealing with something high priority like a CVE.
That's not to say that the end-user story isn't a valuable use case,
but our team is overburdened and we need to drop most of what we do
right now, and we have to be specific about what our purpose is. This
means dropping some valuable use cases.
https://pkgs.org/ might be a good replacement for that. Does anybody have used or is using this website ? Any feedback on it ?
Of course, this is also my own opinion, and I welcome disagreement.
_______________________________________________
infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________ infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
