10:30.10 | *** join/#ol Garf_ (i=Garf@d54C2A046.access.telenet.be) |
11:17.06 | *** join/#ol Garf (i=Garf@pdpc/supporter/active/Garf) |
11:52.08 | *** join/#ol a-atwood (n=xf009976@proxysb01.ext.ti.com) |
15:42.04 | *** join/#ol TimRiker (n=timr@12.110.19.201) |
15:42.04 | *** mode/#OL [+o TimRiker] by ChanServ |
17:33.57 | *** join/#ol Crofton|laptop (n=balister@hc6521ca9.dhcp.vt.edu) |
19:41.05 | *** join/#ol Marius777 (i=kvirc@dslb-084-058-006-140.pools.arcor-ip.net) |
20:10.41 | *** join/#ol TimRiker (n=timr@pdpc/supporter/bronze/TimRiker) |
20:10.41 | *** mode/#OL [+o TimRiker] by ChanServ |
20:28.46 | *** join/#ol Garf (i=Garf@pdpc/supporter/active/Garf) |
21:07.46 | *** join/#ol GarfTop (i=Garf@pdpc/supporter/active/Garf) |
23:29.51 | TimRiker | mindfunk: re msg. nope. |
23:31.14 | mindfunk | TimRiker: so... the general perception is that MV was not in complience with the GPL |
23:31.26 | mindfunk | TimRiker: though, it looks like they might be |
23:31.40 | mindfunk | TimRiker: they just distro patches.... way late |
23:31.47 | TimRiker | they give full source to everyone they give binaries to. hence they are in compliance. |
23:32.10 | TimRiker | now, they don't help their customers comply, but that's a different issue. |
23:32.19 | mindfunk | oh... I thought you had to give the full source to everyone... |
23:32.26 | TimRiker | nope. |
23:32.38 | mindfunk | wait... can TI distro thier source? |
23:32.52 | mindfunk | based on the GPL, of course |
23:33.11 | TimRiker | course you can't restrict whoever you give it to, so a MV customer can give it to everyone, but then it's the customer that has to also give the source, not MV. |
23:33.24 | mindfunk | right |
23:33.47 | mindfunk | so... it would be kosher for me, to say, give the MV linux source to someone outside of TI |
23:33.54 | TimRiker | yes. any source TI gets from MV that is gpl/lgpl or other open source license, TI can distribute the sources. |
23:34.04 | mindfunk | cool |
23:34.17 | mindfunk | thanks |
23:34.19 | mindfunk | brb |
23:34.23 | TimRiker | now, that parts easy.. the question is.. can TI distribute the source rpms that TI gets from MV? |
23:35.16 | TimRiker | the source rpm also contains a spec file and may contain patches. the licensing on the spec file is not specified anywhere that I'm aware of. |
23:35.55 | TimRiker | does the source rpm constitute an "combined work" ? unproven in court. opinions vary. |
23:36.04 | TimRiker | s/ an / a / |
23:37.20 | TimRiker | while I was there, I asked MV if TI could distribute everything we got in the package. and if not, what pieces we could not distribute and why. |
23:37.54 | TimRiker | never got an answer I was happy with. they have a java config tool that is non-free so at least that cannot be distributed. |
23:38.30 | TimRiker | I don't know of anything else that can't be, but we never got confirmation from MV on that. |
23:45.18 | mindfunk | TimRiker: I took a class at MV, the instructor claimed that nothing on the CD was "proprietary" |
23:45.27 | mindfunk | and that MV was entirely OS |
23:45.42 | mindfunk | but, I didn't have much confidense in that |
23:46.22 | TimRiker | well, iirc the cd has the non-free java app on it. |