**** BEGIN LOGGING AT Wed Jan 31 03:00:02 2018 Jan 31 08:01:06 pidge: heya! can i pester you with a small licensing question? given a layer that contains gplv3-ed software, AFAICS i am required to hand out the layer as necessary build metadata. but am i required to put it under a specific license too? Jan 31 08:57:52 LetoThe2nd: generally metadata is MIT licensed, see e.g. COPYING.MIT in the bigger layers Jan 31 08:58:40 LetoThe2nd: the question is what license things like patches are under, you could make the case that oneliners cannot have a license for being too short Jan 31 09:01:54 koen: and being obvious, not creative etc etc :-) the vmware defence :-D Jan 31 09:04:30 yeah Jan 31 09:04:40 you could make a case for the opposite as well Jan 31 09:12:43 koen: ok but how does that comply with gplv3? Jan 31 09:13:51 i mean, doesn't gplv3 basically require me to hand out the metadata so the thing can be rebuilt? i'm not talking about the patches, their licensing is clear. Jan 31 09:17:56 LetoThe2nd: it's 'tools and scripts', right? Jan 31 09:18:13 LetoThe2nd: so technically you just need to include run.do* Jan 31 09:18:35 LetoThe2nd: but licensing of scripts and metadata doesn't have much to do with the source license Jan 31 09:19:28 LetoThe2nd: gedankenexperiment: build gplv3 stuff with visual studio Jan 31 09:22:24 koen: that experiment does not totally apply, IMHO. its more like. 1) build stuff with VS 2) do some packaging magic in a custom script. now assume that actually using the output of 1) requires some kind of packaging, albeit not necessarily done the way my personal 2) does it. Jan 31 09:23:42 so do i have to provide my personal script 2)? because if i do, putting it under any other license than gplv3 too seems kinda pointless. Jan 31 09:27:48 mind, we're not talking about signing or any form of tivoization. just some kind of processing to change the form the data Jan 31 09:28:37 I like MIT, since it's basically a "I don't care" Jan 31 09:28:59 if you make your script gplv3, how would that interact with the rest? Jan 31 09:29:34 because anybody else who receives the sources actually needs the script too? Jan 31 09:33:45 think of the situation in OE, that a major part of your know how actually is in "how to make things work together". as a company that wants to sell hardware, its only natural for us to think about what know how we actually have to hand out, and what not. sources and patches are totally clear, and will (mostly happily) be provided. Jan 31 09:42:50 Tizen re-invented: https://fosdem.org/2018/schedule/event/tizen_rt/ Jan 31 09:44:34 Crofton: \o/ Jan 31 15:24:52 paulbarker: can you add the "opening hours" for the booth to the wiki? I need that to work out when to wake up on sunday :) Jan 31 16:18:48 armpit, ping? Jan 31 16:20:47 armpit, if you have a further issue ping myself or novaldex... Jan 31 16:24:39 k Feb 01 00:38:34 khem, the last patchset, with the PRId stuff last version... Feb 01 00:38:36 https://github.com/LinuxPDA/meta-openembedded/commits/master Feb 01 00:38:55 I'd wait 2.0.2 to commit **** ENDING LOGGING AT Thu Feb 01 03:00:03 2018