Hacker News new | past | comments | ask | show | jobs | submit login

Will it be open source? "Free for licensing" isn't quite clear. Will anyone by able to license access to the source code for free? If yes, what about forking?

EDIT:

Okay, this isn't what I've hoped for:

>Disclaimer: Remix OS is only licensed to authorized business partners and pre-loaded on specific product models of those partners;it's not intended for personal use.




yeah this is not great. moving right along...


yeah, it looks like a nice product from the pictures but oh well.

"Right click" is a feature. That makes sense but I still find it funny.


Early adopters in organisations are important.

An .iso you can download gets you those without the 'corporate communications' problems you get when you have to fill out a form, use language like 'licencing' and then get the official IT department to install stuff.


i would early adopt the heck out of this in a VM but they had to get all weird about it. not interesting at all in 2016


I suspect it largely doesn't exist yet. Keep in mind all you see are probably mockups.


It seems that "Remix OS for PC" will be at least "free to use":

> "With that in mind, Remix OS for PC is free to download, free to install, and free to use."

No idea about open source, though.


> free to download, free to install, and free to use

Remix OS is based on Android and Android includes, among other things, the Linux Kernel, which is GPL, which is Copyleft, which would mean that the Remix OS creators would need to provide the source code to users, wouldn't it?


You can build closed and proprietary software on top of GPL software (for certain definitions of "on top of"), as long as any changes to the GPLed software are released as source, and LGPLed software is only linked to dynamically.

Example: If I wrote an alternative GUI system to replace X and the open window managers, I wouldn't necessarily be forced to open-source that system.

Real-world example: My employer uses Linux in some of its products, integrated with our proprietary software in license-compliant ways (and we've got a legal office that verifies that we're following the licenses for all the software that we use, to avoid legal trouble).


Your users have a right to get the full corresponding source of GPLed software you distribute to them, though.


They do have that right. Sometimes the legal office gets requests designed to check our GPL compliance. Every release, we file information on the distributions we use, their versions, which libraries we link to, which compiler versions we use, build instructions for any components that we did a custom compilation of, etc. The CYA paperwork is pretty extensive.


Great to see your enterprise engaged in compliance. The makers of RemixOs don't yet seem to be there though, it seems.


Only if you've modified it. If not, then it's upstream's responsibility to distribute source. And even if you've modified it, I think distributing patchsets is enough, no?


If you distributed binaries made from GPL code to me, you're obliged to provide the source code if I ask you. You can do that by pointing me to an upstream url fine, but you need to be sure that that url will be valid when I ask you.


Even beyond that, we need to be able to prove that the binaries we're distributing were made from the source that we claim they are, and be able to provide exact instructions for a customer to independently re-create the binaries. That usually means that we stick to versions of libraries and compilers that are on the GA installation disks for a system, with exceptions made for a few security-critical libraries like OpenSSL.


Jide replied that the kernel is untouched, so if you want the kernel source for Remix OS just grab AOSP: https://forum.jide.com/index.php?p=/discussion/563/source-co...


They would need to publish any kernel changes they make, but most of the features they list would not require kernel changes.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: