71–80 of 424 posts
Earlier quoted context omitted.
> He thinks he owns literal hex codes Pantone would like a word.
Pantone is a lot more than hex codes, it's a whole system of material science for colors.
Nobody is gonna pay for a VSCode theme.
That's untrue. I've created https://monokai.pro , to my knowledge the first commercial theme. It's been going strong for years now. People are willing to pay for nice things. Especially if it takes longer to create it yourself. A theme is more than a list of colors. Monokai Pro contains custom designed icons and color filters too, and some code logic to sync it all up. It needs continued updates, as editors keep evol…
Earlier quoted context omitted.
git is a blockchain
No it’s not. A blockchain is a Merkle tree whose canonical “master branch” is agreed upon by everyone and difficult or impossible to change (e.g. due to PoW or a similar mechanism). A git repository is just a Merkle tree.
is it easy for you to go edit historical commits in the linux repo?
If you do a bit of a repo dive, the repo was initially MIT licensed from its initial commit for at least a couple of years before that license was replaced by Apache 2.0, so there's an argument to be made that that license also applies.
The Apache or MIT license would permit you to continue using it for all versions up to the last commit which used that license. Any later commits under a different license would not be Apache licensed and you would need to follow the new terms if using those newer versions. The new license doesn't prevent you from sharing forks of the older version which was Apache/MIT licensed.
> "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License.
This covers not just the users, but also the "author" here who exercises the permissions granted below:
> 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form.
> 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions:
> (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and
So let's interpret that. Regardless of the whatever intent to re-license the code exists in the mind of the author, in order to distribute the code which was contributed by others, the only legal means to distribute this code must comply with the requirements of the license. Technically they could remove all code contributions which were contributed by others (I've done this in the past, it's a pain to do right), or seek permission from the others to add additional grants that are not included in the Apache license here (I've seen various projects do the post-facto CLA thing for this). But that has not happened here.
So (in my opinion) the github repo of the author is a currently infringing the copyright of all the other contributors. Any one of whom could enforce it or raise a DMCA take down notification on the repo.
So given that we're talking about material that is in breach of copyright, it's likely that being able to enforce a license on that as a consumer is not really a thing which is possible as the conditions on what must be included bind the person distributing the material not the person receiving it.
Nobody is gonna pay for a VSCode theme.
People pay for mere color schemes. https://draculatheme.com/
Free themes are a dime a dozen.
Paid themes means someone's incentivized to keep working on it and adding icons, &c.
Earlier quoted context omitted.
What about this clause: "The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software" It sounds like they went out of the way to remove that copyright notice. Am I misinterpreting that part? Genuinely curious since this stuff affects me....
As the original Copyright holder, you can do that. It just doesn't make the old Apache licensed version disappear.
Earlier quoted context omitted.
There's nothing wrong with building proprietary software of a couple of thousand lines of code, including themes. And people should be able to ask for money in exchange for their work. What's wrong is the bait and switch, as these projects end up being popular because of their FOSS nature.
"What's wrong is the bait and switch,[..]" Morally wrong, legally not so much. If it is under a permissive license (and it was MIT originally as others have pointed out) you can always cut a proprietary version. That doesn't take away the right to use the permissively licensed code of course.
Of course, but then, the legality of it is irrelevant.
Free markets work because consumers can exercise their freedom to choose, and in such instances it's easy, given that the reason for why many such projects see wide adoption is their FOSS nature.
A member of the community did a deep security analysis of the extension and found multiple red flags that indicate malicious intent and reported this to us. Our security researchers at Microsoft confirmed this claims and found additional suspicious code.
We banned the publisher from the VS Marketplace and removed all of their extensions and uninstalled from all VS Code instances that have this extension running. For clarity - the removal had nothing to do about copyright/licenses, only about potential malicious intent.
Expect an announcement here with more details soon https://github.com/microsoft/vsmarketplace/
As a reminder, the VS Marketplace continuously invests in security. And more about extension runtime trust can be found in this article https://code.visualstudio.com/docs/editor/extension-runtime-...
Thank you!
Earlier quoted context omitted.
That's untrue. I've created https://monokai.pro , to my knowledge the first commercial theme. It's been going strong for years now. People are willing to pay for nice things. Especially if it takes longer to create it yourself. A theme is more than a list of colors. Monokai Pro contains custom designed icons and color filters too, and some code logic to sync it all up. It needs continued updates, as editors keep evol…
Happy Monokai customer here! I want to make themes using my own palette but nothing supports OKLCH and I don't wanna convert to HEX.