4 ms·
In what case would the license change impact anything? You want to make proprietary changes to the X server?
by yjftsjthsd-h 3y ago
In what case would the license change impact anything? You want to make proprietary changes to the X server?
- sudobash1 3y agoIt could be significant in embedded devices due to the anti-tivoization requirements of the GPLv3.
- mikecoles 3y agoThis sounds beneficial rather than otherwise.
- asveikau 3y agoI feel like the historical culture of X development is permissive licenses and proprietary Unix vendors developing closed solutions on top. It was deliberately like that. So this feels like a departure.
- wmf 3y agoThe Unix Wars were a waste of time and money for everyone involved. By the time they realized it they were already dead. There's no reason to bring back that business model.
- badsectoracula 3y agoWhile that is the case and still is today, i remember Keith Packard (a prominent X developer) making various remarks over the year in his presentations on the negative side of having all these companies making their own private forks without contributing code back.
- snvzz 3y agoThis is precisely what Tinyx is doing: A "private" fork in a license that would make it impossible to contribute code back to Xorg.
- badsectoracula 3y agoThat is only if Xorg doesn't switch to GPLv3. Though of course in that case (i.e. Xorg not switching) someone can fork Xorg, relicense it to GPLv3 and merge the TinyX code - so everyone gets their cake. In practice however i doubt anyone would bother with any of the above (including Xorg wanting to merge any TinyX contributions).
- anthk 3y agoI remember propietary accelerated X releases. That set X.org back almost for a decade.