* Adam Williamson: > On Wed, 2020-04-01 at 06:11 -0500, Bruno Wolff III wrote: >> On Wed, Apr 01, 2020 at 12:39:21 +0200, >> Florian Weimer <fweimer@xxxxxxxxxx> wrote: >> > * Bruno Wolff, III: >> > >> > > RHEL is a special case, as CENTOS provides a free drop in replacement >> > > and switching from CENTOS to Fedora shouldn't be much work. Is there >> > > other proprietary software at the OS level or above, that is used for >> > > Fedora infrastructure? >> > >> > The Bugzilla fork running on bugzilla.redhat.com? >> > >> > <https://bugzilla.redhat.com/show_bug.cgi?id=478886> >> >> That was an interesting read. It sounds like corners were cut under the >> assumption that there would be no desire to share the code. Specifically >> code and config were mixed together and the config can't be released. > > There's been an ongoing project in RH for the last few years to get > RHBZ closer to upstream. It's *much* closer now than it was a few years > ago. I haven't looked at the internal fork for a year or so, but last > time I did it wasn't a long way away from upstream. Yes, it's really close, and I still hope it will happen eventually. It will be a bit sad to see this counterexample go, though. > So yeah, this is a valid entry in the list, but again it's a very > 'grandfathered' one, and one it would be practically very difficult to > do much about (trying to unpick Fedora from RHBZ has been talked about > more than once but is logistically a very difficult job). The close integration between Fedora and Red Hat Enterprise Linux bugs has been quite helpful to us, too. I also don't think CPE is eager to run their own Bugzilla. Thanks, Florian _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to 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/devel@xxxxxxxxxxxxxxxxxxxxxxx
