[TOPIC 11/17] GPL enforcement

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



1. Peff: Hypothetically if a company would not distribute the sources of a modified version of git they ship. What should we do about it? Should we take legal actions and make them aware that they are doing something they should not do? Making sure they also treat other projects better.

2. Brandon: Would we gather together with other projects affected by this company?

3. Peff: How hard do we want to take it on this company?

4. Ed: I’m also bothered by this. And they just send me a tar ball. At Microsoft we are aggressive about doing this right.

5. Jonathan N: Can we make it really easy to comply, e.g. by making a build target that contains everything?

6. ZJ: They could just push to GitHub. That would be fine.

7. Peff: I brought this up, because we were made aware of this by the Conservancy. So I wanted to hear how people are feeling about it.

8. Brian: A more aggressive approach would be appropriate if we have made them aware of the issue and they decided to not comply on purpose.

9. Peff: Code change doesn’t matter, whether it’s a security fix or feature. And I’m fine giving them a bit of lag time, like a day. Not a day.

10. Peff: You’re not obliged to send the source code, but you should provide the offer to share the source. In this case, they sent us a tar ball, but the sources are not on their open-source. So they probably do not yet apply.

11. CB: But everyone on Mac can request to send you the source code. We could release a form somewhere to give people an easy option to request this.



[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux