Overall, I’m positive about the distribution aspect of this proposal. Discovering community drivers is currently difficult, and a centralized catalog could definitely improve that, even if Samsung doesn’t actively participate.
My concern is about the long-term maintenance model rather than the repository itself.
Today, most drivers evolve in the developer’s own repository. As soon as a developer starts adding new features, fixing bugs, or experimenting with new capabilities, the community repository will inevitably begin to diverge.
Keeping those repositories synchronized is relatively easy at first, but over time it becomes increasingly difficult. Every merge requires review, testing, and validation across different hubs, firmware versions, and physical devices. Since developers and testers are spread across different regions and own different hardware, this quickly becomes a significant amount of work.
I can easily imagine a situation where the community repository falls behind the original one, or developers stop contributing because maintaining two repositories isn’t worth the extra effort.
So my main question isn’t whether a community repository is a good idea—it is. It’s who owns the responsibility for keeping it up to date, deciding what is considered “stable,” retesting drivers after platform or firmware changes, and preventing the community version from gradually becoming outdated.