Live data from Hacker News

Gitlab Duo

about.gitlab.com

41–50 of 160 posts

Re: Gitlab Duo

#41

Earlier quoted context omitted.

GitLab team member here. Thanks for your feedback. GitLab Duo provides AI-assisted features in the DevSecOps lifecycle. GitLab Duo Chat was released as GA last week [0] Code Suggestions are GA, too, and help with code completion and generation [1] The documentation provides more insights on availability and usage [2] Helpful learning resources: If you are looking for practical examples and prompt tips for Duo Chat, b…

Did you use Gitlab Duo to write this comment?

Great idea ;-)

But actually, no. I had these helpful tips in mind, and wanted to share them with everyone quickly. There is always an opportunity to learn together, and get inspired from feedback :-)

Re: Gitlab Duo

#43
post #27

From that page: > Will my code be used for training AI models? > GitLab does not train generative AI models based on private (non-public) data. The vendors we work with also do not train models based on private data. So they will steal your code if it is public, ignoring license. Understood.

I’ve been feeling more and more that we should reconsider open source licenses to protect our rights as authors from LLM vendors. I’m not against them basing their models on my work. I do have reservations on them generating their models on my work and creating derivative works without respecting the license. It’s why I’ve started to use the MIT license less and less and have adopted various from the GPL family. Models trained in OSS should be open sourced IMO.

Re: Gitlab Duo

#44
post #27

From that page: > Will my code be used for training AI models? > GitLab does not train generative AI models based on private (non-public) data. The vendors we work with also do not train models based on private data. So they will steal your code if it is public, ignoring license. Understood.

If a person can read it and learn from it, AI should be able to do the same.

Re: Gitlab Duo

#46
post #27

From that page: > Will my code be used for training AI models? > GitLab does not train generative AI models based on private (non-public) data. The vendors we work with also do not train models based on private data. So they will steal your code if it is public, ignoring license. Understood.

Given that it's public, yes, gitlab as well as every other model on earth will be trained from it. Is it right? I don't know. Can we stop it? Absolutely not. Honestly, I find it comforting that gitlab is at least being straightforward about it

I would not call that straightforward. Being straightforward would mean including something like "we & our vendors might (or will) train generative AI models based on public data", instead of letting us infer that for ourselves.

Re: Gitlab Duo

#47
post #27

From that page: > Will my code be used for training AI models? > GitLab does not train generative AI models based on private (non-public) data. The vendors we work with also do not train models based on private data. So they will steal your code if it is public, ignoring license. Understood.

Given that it's public, yes, gitlab as well as every other model on earth will be trained from it. Is it right? I don't know. Can we stop it? Absolutely not. Honestly, I find it comforting that gitlab is at least being straightforward about it

Straightforward? I very much disagree.

You could maybe convince me that it is straightforward when measured against only corporate speak, but if not looked at as corporate speak it is very much not straightforward. Straightforward would be an explicit "Yes, we train from public code regardless of the license"

Re: Gitlab Duo

#48
post #27

From that page: > Will my code be used for training AI models? > GitLab does not train generative AI models based on private (non-public) data. The vendors we work with also do not train models based on private data. So they will steal your code if it is public, ignoring license. Understood.

that's what github and software heritage do too. apparently just publishing your software code means it's open game even if it's all rights reserved.

Just in case people didn't know, the phrase "all rights reserved" does not have any legal consequence (in the early days of copyright people felt it was necessary, but all rights are automatically granted), and uploading content to Github means that you must also license it to Github and other Github users as per the ToS. It is your responsibility to ensure that you can grant that license.

https://docs.github.com/en/site-policy/github-terms/github-t...

In addition, one has to consider whether the act of studying a project whose sources you have legally obtained to gain experiences applied in other contexts where the original license may not apply or be upheld is an issue. This applies to humans as much as to ML.

Post reply on HN