Replies: 2 comments 8 replies
-
💬 Your Product Feedback Has Been Submitted 🎉 Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users. Here's what you can expect moving forward ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities. Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐ |
Beta Was this translation helpful? Give feedback.
-
Select Topic Area
Product Feedback
Body
Co-Pilot seems to openly admit itself that open-source code is repurposed without adhering to attribution requirements:
It seems to me like training such an AI in such a non-adhering manner on GitHub projects risks causing major damage to developer relations and trust, and could be perceived as theft. I would like to suggest this practice should therefore be reviewed and changed. An alternative would for example be to ask projects to opt-in with some sort of incentive to do so, e.g. a wider range of co-pilot access for free or similar.
While I heard sometimes this is worked around via an automated duplicate detection, I assume that will never catch all corner cases and it seems more prudent to work on the training data.
Beta Was this translation helpful? Give feedback.
All reactions