4 ms·

Code (co)created with Copilot has to follow all the licenses of the source (heh) code. This generally means at the very least automatically including in project

Code (co)created with Copilot has to follow all the licenses of the source (heh) code. This generally means at the very least automatically including in projects getting help from Copilot a copy of all the licenses involved, and attribution for all the people the code of which Copilot has been trained on. (Not sure for the cases where there is no license and therefore normal copyright applies, but AFAIK this isn't the case for any code on Github, which automatically gets an open source licence ? EDIT : Code in public repositories seems to be "forkable" on Github itself but not copyable (to elsewhere). That's some nasty walled garden stuff right there, I wonder how legal that ToS is ? I could see how this could make them to incentivize people to stop using other licenses on Github, to not have to deal with this license mess... EEE yet again ?)

neom 5y ago
So I guess then, the first thing they should have done, is trained it to understand licenses, and used that as a first principle for how they built the system?
- whimsicalism 5y ago
  Is it a derivative work of GPL licensed work if it is trained on the license? Is the GPL license text under GPL?
  - deleted 5y ago
    [deleted]
  - BlueTemplar 5y ago
    > GNU GENERAL PUBLIC LICENSE > Version 3, 29 June 2007 > Copyright © 2007 Free Software Foundation, Inc. <https://fsf.org/ https://fsf.org/> > Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.
- BlueTemplar 5y ago
  Seems to be too much effort (is it even possible to link the source to the end result ?), and might not be admissible, so just include a database with all of the relevant licenses and authors ?