-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 I go to a dist-git repo and find a bug when browsing the source code. I can open a PR to fix it, but what if I don't know how to fix it? I open an issue, right? Except, there's no issue tracker for dist-git pagure repos. That's what bugzilla is for. Now I need to go to bugzilla, find the component, fill out a bug, yada yada. I understand the need for bugzilla and that it's not going away anytime soon, but could we possibly integrate dist-git pagure issue tracking and bugzilla in a way that makes the whole process more seamless for this workflow. We could even use the bugzilla API and display things differently in pagure if we wanted. These are just suggestions. I feel like this can be improved. Dusty -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEPb6zG5c6sV89tRYPMwLb1zlS5nEFAlpVWZoACgkQMwLb1zlS 5nFejxAAl9SCy5mshEsPGk/qK9rDQLYMPP094r8rJt9vBYvxA+6jvR+3PcnRoe0M +CtGndYHS28RJjZTzxL9dHTDX4pzZwOZUY1IDTIyKEZHrh9NuEDgAUYVobzeGFTP 3b5kDqx/PBD8K6oGlJ6FMZ7TMqYcJsU4cHZ0Qx76R1LlFvMIU1eXX7FJysdHbVKd J/+t9OotvmZJml7RIG4cYcLyjJG7WTqSRAZNByKbK9mrXQTVAhVX5sauWsqeTotQ sbOO+vDfccrzQwPCjZR8iqSi75wHcKsI+VAByfZ4iVLOubNdou8QmhAUcHJuM0kA YdzknBXI0Yh2aoqsFFHAmwfks0fjlG7OvNnOvYcFp9XhL02s0bMr8sblTSdYBjnZ iwKbTzGjzlB0F3ZA5YiWSrUA5nigZCnycZ0ShD4FCdmsYcT9Iw3cgGBiEniYaSOk WIs8Lp0FQDvixY3D8maw/ZJ7KwZSZ+uuIpKnnHrW3GHZtrGxajNXQY7RIIw9DZt0 PXwPgfQYfINfOB8NuqMg5dZgzIeIusT/nN/xrlo8pL2QPMl79S6ZG35cFjQAmgck x6M994d1nke10c4K3oZQtsN3XgJvZ8cV9iPJZSGhekvBaD+e6ZnIksilXx52FBdN 7imp0i8UtI0+6/JRS8qx3zc1llQU4qAdgZTOIwz3C81fe2u1594= =xzlu -----END PGP SIGNATURE----- _______________________________________________ infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx
