Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Generative AI/Low Effort Contribution Policy #2417

Merged
merged 10 commits into from
Nov 8, 2024

Conversation

austinlparker
Copy link
Member

This adds a new section to the contributor's guide addressing the usage of LLMs/GenAI in contributing to OpenTelemetry.

Copy link
Member

@mx-psi mx-psi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we talk about the project itself using LLM tooling? For example, on opentelemetry-collector-releases we have been testing dosu (see example here: open-telemetry/opentelemetry-collector-releases#701 (comment))

I guess if we want to cover this it should go in the FAQ for maintainers

guides/contributor/genai.md Outdated Show resolved Hide resolved
@austinlparker
Copy link
Member Author

Should we talk about the project itself using LLM tooling? For example, on opentelemetry-collector-releases we have been testing dosu (see example here: open-telemetry/opentelemetry-collector-releases#701 (comment))

I guess if we want to cover this it should go in the FAQ for maintainers

I added a new section to the FAQ addressing Dosu and other LLM-based tooling.

Copy link
Member

@mx-psi mx-psi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Content LGTM, but it looks like the .cspell.yaml change triggered some autoformat on your code editor, we could split that into a separate PR

Copy link
Contributor

@breedx-splk breedx-splk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @austinlparker, I hope this helps reduce some of the LLM thrash. Do you think there's an opportunity to link to this from the code-of-conduct.md as well? Seems like it might be valuable to somehow indicate that repeated, lazy LLM-based submissions can constitute a conduct violation.

@austinlparker
Copy link
Member Author

Thanks @austinlparker, I hope this helps reduce some of the LLM thrash. Do you think there's an opportunity to link to this from the code-of-conduct.md as well? Seems like it might be valuable to somehow indicate that repeated, lazy LLM-based submissions can constitute a conduct violation.

@open-telemetry/governance-committee thoughts on explicit CoC expansion?

@mtwo
Copy link
Member

mtwo commented Oct 29, 2024

Seems fine with me. Our CoC inherits from the CNCF CoC, correct? If so, would we propose those changes upstream?

@austinlparker
Copy link
Member Author

Seems fine with me. Our CoC inherits from the CNCF CoC, correct? If so, would we propose those changes upstream?

It does. I'm not sure we really need to specifically add this as a CoC violation, as repeated violations of a published policy would be a violation of the 'positive environment' section of the CoC (see https://github.com/cncf/foundation/blob/main/code-of-conduct.md#our-standards).

Copy link
Contributor

@danielgblanco danielgblanco left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for putting this together

@austinlparker austinlparker merged commit b4abf25 into open-telemetry:main Nov 8, 2024
4 checks passed
@yurishkuro
Copy link
Member

I just re-read the guidance and my suggestion is to rewrite it without referencing LLMs. The overall guidance boils down to "don't create garbage/useless PRs", and "if you do we will block you". If a PR is high quality then it's irrelevant if it's created with GenAI help or not. We can expect most PRs to be done with AI assistance in the near future, so the guidance to "disclose that fact" serves no purpose.

@svrnm
Copy link
Member

svrnm commented Nov 11, 2024

@yurishkuro can you move your comment into a dedicated issue so we can continue the discussion there? Thanks

@yurishkuro
Copy link
Member

#2435

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

10 participants