Re: Re: relicensing gpl widgets
Moderator: Moderators
Re: Re: relicensing gpl widgets
The curious observer may wonder: why would the person who held the BA github hostage for 3 years go to such lengths to try to override the gpl license? Why does it matter if everyone gets to add + onto the end of every license? The answer of course is to try to make it seem that the door is open for mods to start relicensing widgets where it gives them "competitive advantages," for example changing all v2 licenses to the less strict v3.
This is a sign of widget licenses being weaponised against the community. For example, review the commit where all gpl licenses were removed by BAR.
https://github.com/beyond-all-reason/B ... 44f66eb82d
Re: Re: relicensing gpl widgets
I dont want to respond but anyway..... the next commit that was reverted:
https://github.com/beyond-all-reason/Be ... e314e9f475
https://github.com/beyond-all-reason/Be ... e314e9f475
Re: Re: relicensing gpl widgets
Ares wrote: ↑09 Sep 2022, 09:31 Observant readers might ask why would the person who held the BA github hostage for 3 years be making strangely specific gpl licensing posts and then lock them so no one can reply?
The answer is to retroactively and forthrightly claim to have publicly permitted relicensing of widgets from other mods under the false flag of an unrelated ZK request.
Notice how he also gave the example of a gplv3 to gplv2 relicense to try and divert from his real objective of trying to let people relicense from gplv2 to gplv3. A classic example of Bluestone misdirection like when BA was banned for "security reasons".
The curious observer may wonder: why would someone go to such lengths to try to allow gplv2 be swapped to gplv3? Why does it matter if everyone gets to add + onto the end of every license? The answer of course is to try to make it seem that the door is open for mods to start relicensing widgets where it gives them "competitive advantages".
This is a sign of widget licenses being weaponised against the community. For example, review the commit where all gpl licenses were removed by BAR.
https://github.com/beyond-all-reason/B ... 44f66eb82d
Bluestone did not hold BA github hostage.
BA was not banned, stop spreading this lie. Old engine support was reduced to small team games so that games would actually start using newer engines, which is the fuel that engine developers needed to keep going forward.
Notice how the commit you reference in your post was reverted the next day:
https://github.com/beyond-all-reason/Be ... e314e9f475
At this point, all I can say is please seek out professional help, I am worried to see your victim complex consuming you entirely.
Re: Re: relicensing gpl widgets
If you want developers using new engines prove it by releasing 3do2s3o.lua publicly rather than playing favourites based on personal grudges. Community engine tools should be public, not be used to privately gatekeep mods.
This tool has been given to ZK yet refused to BA. The discrimination needs to stop. https://github.com/ZeroK-RTS/Zero-K/com ... f2c59398ab
For all non-biased parties: read the following threads and make up your own mind if BA was banned.
viewtopic.php?f=1&t=39392
viewtopic.php?f=1&t=39689
Last edited by Ares on 17 Dec 2022, 23:43, edited 1 time in total.
- Silentwings
- Posts: 3720
- Joined: 25 Oct 2008, 00:23
Re: Re: relicensing gpl widgets
I wondered if some loltastic thread like this would happen
Re: Re: relicensing gpl widgets
It only took 3 days for the prediction to come true.
Re: Re: relicensing gpl widgets
What is your problem exactly? Tidying up code to use the proper licence that SpringRTS requires?