4 ms·
Technically, Google would only be required to make a written offer, and we could ship physical medium copies to folks who wrote them.
by DannyBee 14y ago
Technically, Google would only be required to make a written offer, and we could ship physical medium copies to folks who wrote them.
- 0x0 14y agoBut then the first recipient could post it online on github or whatever.
- DannyBee 14y agoSure, but the parent said "it was required by the Linux kernel GPL2 license to release the kernel source code" This is not technically true.
- H3g3m0n 14y agoYes they are required to release it. 'Release' doesn't have to mean 'on the internet'. Even if it's sent out on 5¼ inch floppies by the slowest postal service known to man and only makes its way onto the internet by a 3rd party its still released.
- DannyBee 14y ago1. Besides being an engineer, I'm an IP lawyer specializing in open source (and run open source license compliance for Google), so I tend to use very precise terminology since the licenses do. 2. I actually was the person who put up the current glass kernel release. 3. Again, the parent i responded to implied Google has some affirmative obligation to place the source code on the internet. They don't. They are only required to make a written offer. Someone can take them up on that written offer, yes, and then they could repost it to the internet, but Google definitely has no affirmative obligation to place the GPL'd source code on the internet as was implied. We do it anyway, because it's the right thing to do, but ...
- doktrin 14y ago> We do it anyway, because it's the right thing to do, but ... I don't really understand where this is going. Is there some implication that Google would stand to benefit in any way from not releasing the code?
- barista 14y agomust be the case otherwise why would they not release the Glass platform code? The kernel code is not that interesting anyways.
- DannyBee 14y agoNo, it's just a common misconception about the GPL, and it actually pops up on GPL violation lists, so i figured i'd take the time to point out it's not correct, and apparently start a large group of random replies about it. I personally think the written offer approach should never have been added, but ...
- saurik 14y agoThat written offer must accompany the physical product. Google did not do this as far as I know. I mean, if we are going to be technical about this, the GPL states that even if you distribute the code via a "network server", you still must provide, accompanying the physical product, a "written offer" (it's the same clause) to give the user said code via that path. Really, all doe88's point was is that when Google sold this thing, they were already on the hook for this: he didn't even mention the "Internet" (your technicality), he just said "release", and providing a written offer in the box would have satisfied that. I don't even think doe88 was aggravated at Google: he seemed to just be pointing out that this isn't really news.
- DannyBee 14y agoYou are thinking of GPLv3, not GPLv2, when you speak of the network server distribution. :)
- OGinparadise 14y ago>> Sure, but the parent said "it was required by the Linux kernel GPL2 license to release the kernel source code" >> This is not technically true. You sir, are, technically... Do you work for Google by any chance? It's good manners to technically declare any conflict of interest. Not technically required, but technically suggested by the technicians at HN
- DannyBee 14y agoI've mentioned a number of times i work for google, and try to do so when appropriate. I removed it from my HN profile after I started getting folks bringing it up randomly.
- dllthomas 14y agoIt seems practically required, since the only thing such an action would by them is scorn.
- deleted 14y ago[deleted]
- shadowmint 14y agoI dont care if I get down-voted for making a comment unrelated directly to this; Thank you. You are my personal hero for today DannyBee, for speaking calmly and making sense on HN.
- tptacek 14y agoYou should follow all his comments. He's like this all the time. It's a little freaky.
- sc00ter 14y agoSo do you work for Google, or do you do work for Google? I only ask because in earlier comments you lectured on the correct use of terminology, yet having said explicitly you work for Google you now talk about the company in the 3rd person plural as if you are not an employee.
- nmcfarl 14y agoI think this is an unfair standard, and although I am a founder at my place of employment you can be assured that I will not use "we" to describe my positions on topics without sign off. As a general rule my opinions and those of the firm are divergent. When I speak I speak only for myself.
- EGreg 14y agoWell if we are going to be technical about it, why is Google even required to make a written offer under the GPL? They can, for example, never release the source code for software that didn't make it (in binary form) onto the devices. Right? http://www.gnu.org/licenses/gpl-faq.html#GPLRequireSourcePostedPublic http://www.gnu.org/licenses/gpl-faq.html#GPLRequireSourcePos... Let's make this question more relevant ... if you write server code that isn't released 'to the public', but powers your website which is publicly accessible, must you release the source code if your server was "linked with" (whatever that means) GPLed code?
- spicyj 14y agoNo. That's why the AGPL was created: http://en.wikipedia.org/wiki/Affero_General_Public_License http://en.wikipedia.org/wiki/Affero_General_Public_License