News for hackers. Stuff that matters.
Re:An Open Source Lawyer’s View on the Copilot Class Action ... by amarant on Thursday November 10, 2022 @02:33AM (#33543368)
Probably the ToS. You've granted GitHub specifically license to use your code under the terms of the ToS, they effectively have 2 licenses. They can therefore choose under which licence they want to use your code, and will choose the most permissive one, or the one they have the best understanding of: in this case the ToS.

Other parties are not granted license under the ToS, and so will have to abide by the AGPL.

Re:An Open Source Lawyer’s View on the Copilot Class Action ... by World177 on Thursday November 10, 2022 @03:05AM (#33543583)
License takes precedence when you don’t own the copyright. ToS takes precedence when legally allowed and you do own the copyright.
Re:An Open Source Lawyer’s View on the Copilot Class Action ... by khalt on Thursday November 10, 2022 @03:25AM (#33543713)
ToS regularly gets thrown out in Europe if considered unfair. Much of OSS is written in the rest of the world.

(Of course the GitHub ToS do not allow any CoPilot activities in the first place.)

Re:An Open Source Lawyer’s View on the Copilot Class Action ... by Xylakant on Thursday November 10, 2022 @03:34AM (#33543778)
That statement is dangerous. ToS often gets thrown out in business to consumer transactions where the business has a significantly better negotiation position (legal counsel,…) It’s a consumer protection mechanism. In business to business interactions, the chance of getting a ToS thrown out is much lower since it’s assumed that the playing field is much more level.
Re:An Open Source Lawyer’s View on the Copilot Class Action ... by frumper on Thursday November 10, 2022 @11:53AM (#33549370)
The blog post articulates how GitHub TOS does allow CoPilot.