Describe what you would like us to do:

Document where the sources for https://src.fedoraproject.org/ are. I expected to find them somewhere at the footer, or at least at https://src.fedoraproject.org/about/

You mean the "Powered by pagure" line in the footer?

Yep.

@abitrolly Just to make it clear, if you click on pagure in Powered by pagure you will get redirected to https://pagure.io/pagure

I assume you want to know where https://pagure.io/pagure-dist-git is hosted. Is this right?

Yes, I am redirected to https://pagure.io/pagure and I want to discover https://pagure.io/pagure-dist-git (if that is therepository for the Pagure instance at https://src.fedoraproject.org/).

https:/src.fedoraproject.org runs the code from https://pagure.io/pagure as well
as the one from https://pagure.io/pagure-dist-git so there is no one place to
send people to, it will depend on what you want to report.
The UI for src.fp.o is stored in upstream in pagure, the extras API endpoints
are in pagure-dist-git, the basic features are in pagure, the scripts to
generate the extras JSON files are in pagure-dist-git...
So we could provide a link to both but I doubt it will be that useful as it is
not always obvious where people should open a ticket depending on the issue/RFE
they have.

Is it a fork of Pagure or config?

If it is a configured version of Pagure, then the "Powered by pagure" line can be changed to "Powered by Pagure (see the config)".

Is it a fork of Pagure or config?

Neither, it's a pagure with a 3rd party extension (pagure-dist-git) and custom
theming (which is stored upstream)

Powered by Pagure and pagure-dist then.

Added https://pagure.io/pagure-dist-git/pull-request/150 but it needs more info, about how it is used for creating src.fedoraproject.org in comparison with plain Pagure installation.

Dist-Git, which has a slightly different access model than regular Pagure Git systems.

Would be nice to see a short explanation how it is different that a new plugin is required.
Would be nice to know which parts of UI are in Pagure (theme) and which parts are not (user facing endpoints?)
What are the "extras API endpoints"? Is "extras" some specific concept? What are those "extras" that scripts are needed to generate JSON files for them?

If it is not the Dist-Git repo, then /about page could provide all the details so that people know where to send patches (and could bring up their test instance).

@abitrolly Most of the information could be found in the pagure documentation https://pagure.io/docs/pagure/

@zlopez there is only generic information that is not connected to src.fedoraproject.org

@abitrolly Yes, the documentation is only for pagure, not for src.fedoraproject.org.

It looks like this is waiting to get added to pagure-dist-git and then we will pick it up on the next update.

Therefore I will close this upstream... please re-open if there's further actions we need to do now.

Reopening as the upstream is not responding.

• https://pagure.io/pagure-dist-git/pull-request/149
• https://pagure.io/pagure-dist-git/pull-request/150

Still not enough info in https://src.fedoraproject.org/about/ - if it is a dist-git installation? If is it a plain pagure-dist-git plugin? In which repo the config of s.f.o is maintained? It s.f.o the site where fedpkg fetches data from?

In the past I pushed changes to my forks on s.f.o. Due to not using it for some time I forgot about the fedpkg requirement. Coming back for another one off contribution I tried an hour to fix it at the wrong ends (first API keys on s.f.o, then SSH keys on a.f.o, because I was used to paguire.io's way of handling access, my web search did not help; then searching infrastructure tickets, then reading documentation).

Maybe add something like the following to the about page:

How to contribute code:

• introduction
• workflow example

It would be better to discuss changes in a PR, but the blocker is that changes for s.f.o are not reviewed https://pagure.io/pagure-dist-git/pull-request/150

The "introduction" link is not enough, because it again, doesn't explain what is s.f.o, where its code it, how it related to a.f.o Its send PR instructions are links to generic Pagure docs, which do not connect the package that user dnf install to the code that lives on s.f.o (or a.f.o).

s.r.o? a.s.o?

@pingou these were typos from a different project. Fixed.

[backlog refinement]
The plan for this ticket is following:
- Merge all opened PR's on pagure-dist-git
- Release new version
- Close this ticket

pagure-dist-git has been upgraded in production.

Should be fixed. Thanks for your patience.