11–20 of 119 posts
Did GitHub ever respond to the concerns about CoPilot? Specifically whether they trained it on private repos or GPL?
copilot is just a prototype. imagine in 10-20 years, software engineers as we know it will be obsolete.
Could they use the blurb of text at the top to give me like... a noun to describe what this is? It just says some vagueness about the future and investigating and exploring. Is it a conference? A team? An initiative? How does it work? Whatever this is supposed to be selling me on, they're doing a terrible job because I can't figure out what it is!
Earlier quoted context omitted.
It was trained on all public repos, and only public repos. They did not pay attention to licensing.
Wow, that's crazy. Do we have something official that says as much?
Heads up, that page has no `` tag so the browser tab is `githubnext.com/`. That is a _VERY_ minor nit, but still an SEO ding (you're github, that doesn't matter much), and a rough edge that could be buffed out.
Bonus points for adding a favicon too. :)
Could they use the blurb of text at the top to give me like... a noun to describe what this is? It just says some vagueness about the future and investigating and exploring. Is it a conference? A team? An initiative? How does it work? Whatever this is supposed to be selling me on, they're doing a terrible job because I can't figure out what it is!
Their team consists of engineers and researchers.
Earlier quoted context omitted.
That's such a vague and novel area, that I don't think lawyers will recommend/allow commenting on it unless required by court of law. There is no precedent on if a computer reading your code or looking at the image is fair-use or not.
why not train it on copyright material also? whats the prima-facie reason for not doing so? i mean if you are doing "all public repos", why not everything else?
The code being covered by copyright and the code being publicly accessible are two different things.