> "Fedora adopts issues.redhat.com for bug tracking" - which would be a > possibility, but doesn't seem like a certainty - the result will be To be clear, it is not an explicit goal for Fedora to adopt issues.redhat.com. That's up to the Fedora project, much as adoption of gitlab was. > that we go from having a shared bug tracker, with the benefits of > shared maintenance and being able to easily clone or reference bugs > between Fedora and RHEL, to each maintaining our own bug tracker and > not having those benefits. Personally, I don't think we're taking advantage of perceived benefits at all. They are effectively separate. > Of course, there would be sensitivities in developing such a process - > it could look a lot like Red Hat telling Fedora how to do stuff, which > I think isn't exactly the relationship we want to have. But at the same > time I'm not sure "Red Hat or Fedora just deciding unilaterally to stop > using this thing they'd previously both used" is always the best choice > either. The Fedora decision is up to Fedora. RHEL is driven by product constraints and will evaluate based on those needs. Where we can align, we should. For a recent example of a decision to align more, look at the CKI project. Both Fedora and RHEL benefit greatly from maintaining the kernel in the CKI manner, and this is the closest the Fedora and RHEL kernels have ever been. josh _______________________________________________ epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to epel-devel-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/epel-devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
