VS Code inserting 'Co-Authored-by Copilot' into commits regardless of usage (github.com/microsoft)

Crivens said:
And what about the commits already done? They fixed nothing, they stopped doing the thing that got people enraged. What they did is they stopped to widdle from the high board into the public pool. And, as cracauer@ pointed out, they seem to plan on starting it again.
Click to expand...
Very crucial. Do the subsequent commits have to explicitly revoke co-authorship? Or is it like licensing: once released under X, it can't be revoked?
 
bakul said:
Sorry, I should've written "fixed it" instead of fixed it.

Of course not. This is to deal with negative publicity.
Click to expand...
Do a bad/evil/insidious thing, hope no one notices.
Oh crap they saw this, scramble, manage the fallout without recognizing the root cause.
 
If VS Code mandates this practice, then it should no longer be used. I use Codex and GitHub; when I merge, it indicates that the merge originates from the branch me/Codex/branch-xyz, which is normal. However, if GitHub mandates Copilot, then GitHub should no longer be used. Easier said than done, I know...
 
bakul said:
Sorry, I should've written "fixed it" instead of fixed it.
Click to expand...
No offence was intendet.

What I could imagine, this was meant as a poison pill for changes in licences, for the fear of licences including a "No AI training" clause. When you want to re-licence something under that, you need to get the OK from all authors. Now you need to ask copilot for his OK...

And it might target the GPL (and others) in a roundabout way, since now copilot has "written" parts of GPL code, so if you suddenly see the same appear somewhere else, it was the same author. Not that he copied this, your honor, he wrote both parts. No need to put that under the GPL also.
You know that NT was written in 2 weeks in a cabin in the woods, with no other input. Or that was what MS claimed, wasn't it? So DEC had no hold over it? Anyhow, this has opened a huge can of worms, let's see who goes fishing with this.
 
CShell said:
LOL - They ended their discussion thread on this issue with:

Code: 
Closing comments on this to prevent further spam.
Please feel free to open issues for things that are VS Code-related.
Click to expand...
I guess their definition of SPAM and mine are different. It would have been more factual, and deserving of more respect to say "Closing comments on this to prevent further criticism of Microsoft."
 
You must log in or register to reply here.
Back
Top