Jdiesel 1431 Posted December 10, 2018 Posted December 10, 2018 You're missing the point, or my point at any rate. Of course the devs can do what they want with their code. What they can't do, or at least shouldn't, is advertise a product as open source, promote on that basis, and then go to closed-source without making it clear that's what happened. There are many people that used and supported Emby based on the license and they deserve to be informed that that's changed. Luke & co. should have made a post about this in the forums or in the blog, not try to sweep it under the rug. It's disheartening that even mentioning this gets responses like yours, which amount to "shut up and go away". I'm sure once 3.6 is released the Emby devs will clear up any wording to ensure that it is clear what is and isn't opensource. Until then, as it stands, the current release version 3.5.3 is opensource and is licensed under GPL-2.0. So I'm not sure where the issue lies? You want Emby to change the messaging before the product has been released? Give them some time to get things sorted out.
chowbok 132 Posted December 10, 2018 Author Posted December 10, 2018 I'm sure once 3.6 is released the Emby devs will clear up any wording to ensure that it is clear what is and isn't opensource. Until then, as it stands, the current release version 3.5.3 is opensource and is licensed under GPL-2.0. So I'm not sure where the issue lies? You want Emby to change the messaging before the product has been released? Give them some time to get things sorted out. The betas have already been released, marked GPL-2.0 at Github, without the source. Betas count.
Jdiesel 1431 Posted December 10, 2018 Posted December 10, 2018 (edited) The betas have already been released, marked GPL-2.0 at Github, without the source. Betas count. I'm not seeing that https://github.com/MediaBrowser/Emby.Releases The repository for 3.5.3, yes https://github.com/MediaBrowser/Emby Edited December 10, 2018 by Jdiesel
chowbok 132 Posted December 10, 2018 Author Posted December 10, 2018 Okay, my mistake. The "Releases" are in a separate repo that doesn't have a license indicated. But the main repo still says GPL-2.0, so it's an easy mistake to make. Plus the website license still says that "the software" is GPL-2.0, with no indication that "the software" does not refer to beta releases. Anyway, my main point still stands, which is that there should have been (and still should be) an announcement that the betas and the future release are no longer GPL. I shouldn't have to be following comments on a closed github issue, or reading the tea leaves from a three-year-old interview with Luke, or happening to notice that the binary repo is missing the little GPL icon, to know that that's the case. I'll stop with this thread now. I won't argue with anyone else who posts here, I've made my case. I still really like Emby and will continue to be a paying customer. I just think the devs need to understand that they need to be open with their userbase, even if that means sharing news that might not be popular. 1
CBers 7450 Posted December 10, 2018 Posted December 10, 2018 I'll stop with this thread now. I still really like Emby and will continue to be a paying customer. Enjoy your content Closed. 1
Recommended Posts