Live data from Hacker News

Material Theme has been pulled from VS Code's marketplace

github.com

51–60 of 424 posts

Re: Material Theme has been pulled from VS Code's marketplace

#51

Earlier quoted context omitted.

So many people who are otherwise functional in society, for whatever reason just can't play well with others when it comes to online communication. This can be true for both software maintainers and users. People can't just leave their emotions at the door and file a bug report or respond to a help request, without including a little personal jab or passive aggressive snipe. Looking at some of those replies to users,…

> People can't just leave their emotions at the door and file a bug report or respond to a help request, without including a little personal jab or passive aggressive snipe. Looking at some of those replies to users, it looks like this guy just couldn't keep himself from including those unnecessary little put downs. My consideration on this is: A lot of software that at least I write privately is rather a manifestati…

If we stick by what you say, the maintainer may be uninitiated by copycat culture. Forking is a form of it, but so is shameless copying. If a person perceives theft, then they may respond in all kinds of abhorrent ways. Of course, we onlookers will yell out that it’s not that big of a deal in this case, but we can do nothing about the individuals perception.

Is this the person’s first time having an idea of theirs taken (appropriately or inappropriately)? Their sense of right and wrong may be just fine (speaking of value systems), but their reaction is intense.

There’s either more to the story or baby just experienced a little bit of life, and it hurts.

Edit:

From the maintainers:

Today we found Sublime Text authors just stole the WHOLE repository publishing the theme again, under their name, by replacing ANY reference of original authors with their names.

We opened a pull-request to restore the original theme made by us with all the credits. Let's see if they accept it, or they want to keep the stolen repository.

As I suspected Watson, the persons perceives theft.

Re: Material Theme has been pulled from VS Code's marketplace

#53

Earlier quoted context omitted.

Your general understanding is wrong, as there's nothing in either BSD or MIT that allows for re-licensing, and nothing else gives you that right. You can incorporate MIT/BSD code in a proprietary project, but that imported code itself remains BSD/MIT licensed. For many projects, this is a technicality, but no, you can't claim copyright on MIT/BSD code that isn't yours.

>as there's nothing in either BSD or MIT that allows for re-licensing But also nothing preventing you from doing it. MIT can be relicensed, for sure.

Of course not. What makes you believe that?

The MIT license is not very long, and it contains this sentence:

> The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

Which clearly state that you can't remove that license to put your own.

Re: Material Theme has been pulled from VS Code's marketplace

#54

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.

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....

Re: Material Theme has been pulled from VS Code's marketplace

#55

Earlier quoted context omitted.

Your general understanding is wrong, as there's nothing in either BSD or MIT that allows for re-licensing, and nothing else gives you that right. You can incorporate MIT/BSD code in a proprietary project, but that imported code itself remains BSD/MIT licensed. For many projects, this is a technicality, but no, you can't claim copyright on MIT/BSD code that isn't yours.

>as there's nothing in either BSD or MIT that allows for re-licensing But also nothing preventing you from doing it. MIT can be relicensed, for sure.

No, it cannot. You can incorporate an MIT licensed work into a work that is licensed differently, but compatibly (not a real problem with MIT), but now you have three works that are under different licenses: the MIT part, the "other" part and the whole. The MIT part stays MIT. Someone can cherry-pick just that file (or file snippet) and use it under MIT, without caring about the license of the whole.

Re: Material Theme has been pulled from VS Code's marketplace

#56
post #35
post #18

Earlier quoted context omitted.

The old commit history can still be accessed here: https://github.com/material-theme/vsc-material-theme/activit...

This doesn't capture all of it though. There's also a bunch more that you can access by looking at commits in the Pull Requests.

It does, you just needs to find the last one before force push and click “browse repository at this point” and it will slow the pre force push history

Re: Material Theme has been pulled from VS Code's marketplace

#57

Earlier quoted context omitted.

>as there's nothing in either BSD or MIT that allows for re-licensing But also nothing preventing you from doing it. MIT can be relicensed, for sure.

Of course not. What makes you believe that? The MIT license is not very long, and it contains this sentence: > The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. Which clearly state that you can't remove that license to put your own.

> What makes you believe that?

Probably the sublicense wording that many techies confuse with relicensing.

Also sloppy wording in discussions like HN where "relicense" is sometimes used as a shortcut for "combined with a compatibly-licensed work in a larger work that can be used under the whole-work license".

Re: Material Theme has been pulled from VS Code's marketplace

#58

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 evolving with new UX/UI elements.

Re: Material Theme has been pulled from VS Code's marketplace

#60

Earlier quoted context omitted.

"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.

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.
Post reply on HN