Yes! 
Thatās where Iāve started, but beyond thatā¦ A remix has a connected to Fedora, but I would like Fedora to be connected to the initiative, because I believe that everything that Fedora builds up, builds up Fedora.
Sure, but sigs that also make a remix are definitely part of fedora.
For example folks in the mobility sig try and reduce the delta between
what they need to work on moble hardware and whats in fedora, but being
a remix allows them to use a non fedora kernel which they must do until
thereās upstream support for their hardware.
I would like Fedora to provide the platforms and frameworks that machine learning (/AI) developers need, because developers will recommend the systems that they use.
Sure, understood.
I would like Fedora to build channels that direct developers to a space where they can collaborate, and channels that direct changes back upstream into Fedora, whenever possible. Upstreaming successful changes into Fedora should be an explicit goal, as it is an explicit goal for Fedora to upstream changes we make to components.
A sig doing a remix does this though.
I would like Fedora to take part in community building, helping developers find interested users, and helping users find interesting projects, because I believe that the communities we promote will promote the project in return.
Sure.
A few more questions:
This LTS kernelā¦ is that really needed? Or is there a way to maintain
a patchset against the fedora kernel for this? Could that be less work (
I am sure it would be less disruptive for testing/quality/etc).
Iād love to hear some feedback on this from Fedora kernel maintainersā¦
I worry that doing this would open the door to a bunch of custom kernels
for different cases where the support is not upstreamā¦
1 Like
+1, I think what the mobility group has been doing with Pocketblue is really cool and should be a good starting point for that effort.