quality/tickets

Fork 0

Centralize code contribution guidelines (especially wrt AI) #870

New issue

Open

opened 2026-02-04 13:34:07 +00:00 by kparal · 4 comments

kparal commented

2026-02-04 13:34:07 +00:00

Owner

I wanted to copy-paste Adam's snippets to some other projects, but I resisted and created this ticket instead. Let's do it better. Instead of copy-pasting similar guidelines everywhere, and then having a maintenance hell (have you noticed that the hyperlink in relval's readme is going to a wrong page?), let's have a single document with Quality contribution guidelines, and then we can simply link to it from everywhere.

The guidelines document would likely include:

A link to general Fedora contribution guidelines/contributor agreement
An explanation of Developer's Certificate of Origin
An AI contribution requirements
and maybe something else

We can store it in https://forge.fedoraproject.org/quality/tickets (either as part of the README or maybe as a separate file), or in a new page somewhere under https://fedoraproject.org/wiki/QA .

Thoughts?

Currently all our projects deal with contribution guidelines/requirements individually, which means most of them don't deal with it at all, and some (Adam's) have custom extensive instructions especially wrt AI contributions, e.g. in [relval](https://forge.fedoraproject.org/quality/relval/#bugs-pull-requests-etc). I wanted to copy-paste Adam's snippets to some other projects, but I resisted and created this ticket instead. Let's do it better. Instead of copy-pasting similar guidelines everywhere, and then having a maintenance hell (have you noticed that the hyperlink in relval's readme is going to a wrong page?), let's have a single document with Quality contribution guidelines, and then we can simply link to it from everywhere. The guidelines document would likely include: * A link to general Fedora contribution guidelines/[contributor agreement](https://docs.fedoraproject.org/en-US/legal/fpca/) * An explanation of Developer's Certificate of Origin * An AI contribution requirements * and maybe something else We can store it in https://forge.fedoraproject.org/quality/tickets (either as part of the README or maybe as a separate file), or in a new page somewhere under https://fedoraproject.org/wiki/QA . Thoughts?

adamwill commented

2026-02-04 16:39:43 +00:00

Owner

have you noticed that the hyperlink in relval's readme is going to a wrong page?

look, the page has 13 numbered links, okay? That's a big number! Us arts grads can't reliably count past 5. We're like LLMs.

edit: anyway it's perfect and has always been this way

Thoughts?

Sounds good to me!

> have you noticed that the hyperlink in relval's readme is going to a wrong page? look, the page has 13 numbered links, okay? That's a big number! Us arts grads can't reliably count past 5. We're like LLMs. edit: anyway it's perfect and [has always been](https://forge.fedoraproject.org/quality/relval/commit/f9c9047a4f97c703f208a0efefe50cdcfc33eae8) [this way](https://forge.fedoraproject.org/quality/relval/commit/9e099f72454719e57ae9ccefd4fbb4ae82365530) > Thoughts? Sounds good to me!

😆 1

kparal added the

points

label

2026-02-05 15:08:28 +00:00

adamwill added the

Work Item

Task

label

2026-02-10 20:51:16 +00:00

adamwill commented

2026-04-07 23:14:27 +00:00

Owner

are you planning to work on this, @kparal , or should I commence the copy/paste frenzy? :D

kparal commented

2026-04-08 13:32:15 +00:00

Author

Owner

If the "copy/paste frenzy" means creating a central document and linking to it from everywhere, yes please, go ahead 😉

adamwill commented

2026-04-08 17:11:47 +00:00

Owner

no, I meant just copying the text into a bunch of repos like you didn't want to do. I was attempting to shame you into doing the thing you did want to do. ;)

No labels

Rows
Columns