And pkgdb.fp.o as a redirect to admin.fp.o/pkdb could exist similarly to {koji,bodhi}.fp.o. And to be perfect the same could be done with {accounts,fas}.fp.o => admin.fp.o/accounts :-) So at the end all infrastructure services will be available as <service>.fp.o

At some point we could have that redirect to admin.fedoraproject.org/pkgdb/search/* --- At the moment, I don't like the URL format for the search string.

Note that the redirects are just redirects. Having truly separate domains at the moment would break the single-sign-on cookie which can only be sent back to the originating domain (ie: back to admin.fp.o).

Well, this is probably not primarily meant for the Fedora maintainers as their entry point to the system. More likely I would like people outside of the Fedora universe able to find information about the particular package (exactly the same what http://packages.debian.org/<nameofpackage> does). Therefore, I don't think authorization and https issues are not that important.

Actually, I would not even mind, if the redirect was actually redirect, not mod_rewrite, so that the user would in the end got http://admin.fp.o/pkgdb URL (thus eliminating the problem with SSL authentication).

We do have:

bugz.fedoraproject.org/packagename

Which goes to a list of bugs on the package and all the other pkgdb info.
Would this work for this request? Or would something else/further be desired?

In the end, I don't think this bug matters any more, all those who need this functionality could work around it with Firefox's smart keywords (aka bookmarked searches).

This could be WONTFIXed, I don't care.