Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [eclipse.org-architecture-council] Scanning for AI generated code with IP issues
Hi Maximilian.

We've never used Black Duck to scan project content. In the past, our IP Team did use Black Duck to scan the sources for some third-party libraries, but we stopped using the tool some number of years ago. The IP Team uses other tools today, but we do not generally scan project code for IP issues.

Our usual practice with project content is to rely on committers understanding their obligations under the Committer Guidelines. More recently, we assembled the Generative Artificial Intelligence Usage Guidelines for Eclipse Committers (and have discussed them in regularly scheduled Architecture Council meetings).

As stated in the policy, the Eclipse Foundation's approach to AI-generated content is this:

The Eclipse Foundation values the human-centric approach to creativity, where Artificial Intelligence (AI) serves as a tool to enhance efficiency. By embracing the power of AI, we prioritise the empowerment of individuals to fully explore and express their creative potential. We believe in leveraging AI to optimise workflows, streamline processes, and minimise mundane tasks, allowing creators to focus on what truly matters: their imaginative pursuits.

Stated otherwise, committers and contributors are going to leverage AI to generate content, so we had better get used to it (and set some guidelines).

We've also discussed this with the committer community via office hours:

https://www.eclipse.org/projects/calendar/#2024-04-11
https://www.eclipse.org/projects/calendar/#2023-04-13

If you have specific concerns, please bring them to the attention of the IP Team (or EMO).

If you want to discuss potential policy changes, our usual practice is to add them to the monthly meeting agenda and discuss them there.

Wayne

On Wed, 2 Oct 2024 at 07:42, Maximilian Koegel via eclipse.org-architecture-council <eclipse.org-architecture-council@xxxxxxxxxxx> wrote:
Dear Eclipse Architecture Council

What are your thoughts on scanning all repositories for AI-generated code that may have potential IP issues (e.g. clones of some other code)? To my knowledge, we have used the Black Duck product line for IP checks in the past, which supposedly supports scanning for code snippets with IP concerns. Is this already being done, or do you think it’s something we should explore further? @Mikael: Can you maybe tell us what is in use now to scan for snippets of code with IP issues. 

Cheers,
Maximilian

--

Dr. Maximilian Koegel

CEO | Principal Software Architect
EclipseSource


EclipseSource GmbH
Messerschmittstrasse 4
80992 Muenchen

General Managers: Dr. Jonas Helming, Dr. Maximilian Koegel
Registered Office: Messerschmittstrasse 4, 80992 Muenchen, Commercial Register Muenchen, HRB 191789
_______________________________________________
eclipse.org-architecture-council mailing list
eclipse.org-architecture-council@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/eclipse.org-architecture-council


--

Wayne Beaton

Director of Open Source Projects | Eclipse Foundation


My working day may not be your working day! Please don’t feel obliged to read or reply to this e-mail outside of your normal working hours.

Back to the top