LICENSE: _may be_ licensed to use source code; incorrect license grant
1–10 of 162 posts
Re: LICENSE: _may be_ licensed to use source code; incorrect license grant
#2> at this time we are not entertaining any changes as such.
Always wonder what leads people to write like this. What does "as such" add to the sentence? At least "at this time" is temporally conditional to the future, it has purpose.
Entertaining is posh "thinking about" or "interested in" so had the merit of being one word in place of two but so is "considering"
Are we not entertained?
Re: LICENSE: _may be_ licensed to use source code; incorrect license grant
#3This would lead me to steer away from the project. They clearly like the way it is and that is unclear for everyone apart from maybe them. I am not even sure it benefits them though.
Re: LICENSE: _may be_ licensed to use source code; incorrect license grant
#4You should read the license, it seems somewhat insane to be honest: https://github.com/mattermost/mattermost/blob/master/LICENSE...
Re: LICENSE: _may be_ licensed to use source code; incorrect license grant
#5> at this time we are not entertaining any changes as such. Always wonder what leads people to write like this. What does "as such" add to the sentence? At least "at this time" is temporally conditional to the future, it has purpose. Entertaining is posh "thinking about" or "interested in" so had the merit of being one word in place of two but so is "considering" Are we not entertained?
Well, it means no changes _intended as_ changes [pertaining to the topic at hand]; it implies there may be incidental alterations or differences, eg this issue might be addressed in a blanket legal revamp (whatever that's called) but, at least over this, they aren't pulling over the station wagon to argue with the screaming stakeholders in the back.
It's what we used to call "load-bearing vagueness"
Re: LICENSE: _may be_ licensed to use source code; incorrect license grant
#6I'm already shutting down my private instance of Mattermost, no thank you. I'm thinking of Zulip, at least they aren't pulling this shenanigans.
Re: LICENSE: _may be_ licensed to use source code; incorrect license grant
#7If the binaries are licensed under MIT, can I decompile the binaries, clean up the source code and have a clean version of Mattermost for distribution?
Re: LICENSE: _may be_ licensed to use source code; incorrect license grant
#8> at this time we are not entertaining any changes as such. Always wonder what leads people to write like this. What does "as such" add to the sentence? At least "at this time" is temporally conditional to the future, it has purpose. Entertaining is posh "thinking about" or "interested in" so had the merit of being one word in place of two but so is "considering" Are we not entertained?
It's good English, it has actual meaning (your thinking of "at this time" is only one interpretation, it more likely means "We're not entertaining changes of that kind/nature" )
Re: LICENSE: _may be_ licensed to use source code; incorrect license grant
#9The license seems perfectly clear in that it's multiply-licensed under AGPL, MIT, and corporate licensing based on different use cases. Maybe this guy has reading comprehension issues, but more likely he's just unhappy with the corporate part and wants to stir drama.
Re: LICENSE: _may be_ licensed to use source code; incorrect license grant
#10Isn't this by default unlicensed then? I would avoid it anyway. Absolutely no need for that risk.