Done :)

how, where, when? I'm confused.

I've meant that the configuration would be decentralized.

Sorry, I don't your request. What do you mean by decentralized ?

Instead of putting the information about the pipeline of a particular package in this repo, I'd like to store it in the dist-git repo of the package itself.

Ok, yes that's possible and that's the default behavior of Zuul actually but we have decided to prevent this by default with (zuul/include: []) https://pagure.io/fedora-project-config/blob/master/f/resources/fedora.yaml#_33 that tell Zuul to ignore any .zuul.yaml or zuul.d/ self contained in the distgit. Because we think a global configuration is easier to handle.

But if you need more freedom regarding the CI customization then we can remove the include: [] statement. This way you could provide a .zuul.yaml in each distgit and even add new jobs directly in your distgits.

If you choose this option, you should:
- 1/ remove the zuul/include: [] from fedora-project-config
- 2/ add the .zuul.yaml into each distgit
- 3/ remove the project's pipelines definitions from fedora-zuul-jobs-config

How does the .zuul.yaml file look like? Like this?

- project:
    name: rpms/python3
    templates:
      - build
      - lint
      - test
      - publish

yes, like this, and even you could remove the 'name: rpms/python3' because the project stanza will apply to the current repository only (true for untrusted repositories but not for config repositories).

@churchyard does this work for you?

@fbo should we document this as an option in https://fedoraproject.org/wiki/Zuul-based-ci under "Advanced topics" ?

I wasn't able to test this yet, sorry.

@apevec Yes we should and here is the new wiki section: https://fedoraproject.org/wiki/Zuul-based-ci#In-project_Zuul_configuration_.28.zuul.yaml.29

Let me know if I could close the issue as it documented.

Let's re-open if needed.