On Fri, Mar 13, 2020 at 10:00 AM Josh Boyer <jwboyer@xxxxxxxxxxxxxxxxx> wrote: > > On Fri, Mar 13, 2020 at 9:49 AM Neal Gompa <ngompa13@xxxxxxxxx> wrote: > > > > I am not slamming the kernel maintainers. They're doing excellent > > work, and many of the efforts as part of the CKI project are to be > > lauded. I am also not saying cloud resources in themselves are a > > problem, but it's not like you're running on a git server hosted in > > Fedora's AWS/Azure/GCP account. > > > > My principal concern has always been that projects under the Fedora > > banner (or something like it) should be under infrastructure that the > > Fedora Project controls. > > Ah. I see, well that makes sense, yes. > > > Honestly, I don't care if it's RHOSP, Fedora's AWS/Azure/GCP, or a > > server in a Red Hat office or datacenter. What I care about is that > > when push comes to shove, we're not screwed by an external force in an > > unexpected fashion in a way where we have no recovery plan. > > CKI didn't evolve as a Fedora specific thing. It certainly benefits > Fedora, and I think we should welcome such activities without being > worried entirely about control. The tipping point in my mind is > whether we *depend* on something for Fedora's success. Those kinds of > projects should probably be folded into Fedora control. CKI is > massively valuable, but if it disappeared tomorrow Fedora would still > continue on. > I think that will depend on how much we will grow to rely on the CKI stuff to make "good" kernels. Ideally, it'll become critical to doing so, and thus it will make sense to fold it under the Fedora banner. -- 真実はいつも一つ!/ Always, there's only one truth! _______________________________________________ kernel mailing list -- kernel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to kernel-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/kernel@xxxxxxxxxxxxxxxxxxxxxxx