Will have to wait until after freeze to do this, as it affects the proxies.

Note that the next version of pagure will have namespaced linked differently than the project name so while it won't support the URL scheme described above you will be able to see all the projects in a certain namespace.

In fact, looking at https://redhat.bluejeans.com/5287691063 it looks like it's already in place.

So still not the URL scheme asked but does allow to list by namespace:

• https://src.fedoraproject.org/projects/rpms/*
• https://src.fedoraproject.org/projects/container/*
• https://src.fedoraproject.org/projects/modules/*

@pingou I get that the /* urls work, the problem is they are completely counter-intuitive. You also can't find a link to them any where (like "see all modules" at the top of a module or something). Most people would "guess" the namespace above even without links hinting.

You also can't find a link to them any where

Well, check the link on "modules/" at the top of https://src.fedoraproject.org/modules/memcached

(Note the next release will make this clearer but not including the / in either of the links)

I don't like the redirects idea, I'd prefer if pagure just supported something here.

Could we perhaps under "Projects" list all the namespaces? ie, rpms/ containers/ modules/ etc

So, the top level at https://src.fedoraproject.org/ has:

Welcome to Fedora's repository for package maintenance. If you're looking to download software to run, look at https://getfedora.org/, or a Fedora Mirror. You can also find source RPMs for Fedora-packaged software there. The source code for building those packages is found here.
If you are looking for RPM spec files, module and container definitions, Fedora-specific patches, tests, and so on, you're in the right place. You can browse packages and packagers — and you can fork, improve, and submit pull requests.
If you are already a package maintainer, feel free to consult the docs on using pagure. If you'd like to become a package maintainer, see this guide.
Note that package issues are still tracked in Bugzilla, not with Pagure's issue feature.

Is this configurable anywhere? How about if we added links in there to projects/rpms/* and so forth.

I would expect people to look at the top level page here if they somehow got off track looking.
Would that solve this?

https://pagure.io/pagure/pull-request/4408 should be in the next release.

:spaghetti:

Commit 566b0f6c fixes this issue

I think there will be soon a flatpak namespace, does that means that it will require a new release of pagure to add that ?

I'll open the PR to include the flatpaks namespace in the template :)