3 ms·
Note the point about starting to apply a CLA after the fact to an existing project. KDE certainly consciously took a risk when deciding to try and collaborate w
by sho_hn 13y ago
Note the point about starting to apply a CLA after the fact to an existing project. KDE certainly consciously took a risk when deciding to try and collaborate with a corporate entity, but that doesn't mean the community can't be disappointed at the outcome. Nobody is complaining about a CLA they knew of in advance - because they did not.
And personally I don't think a CLA makes sense for the specific code in question, which is purposefully designed as an interoperability solution and so implicitly multi-stakeholder.