For a long time now the URLs to our apps have been inconsistent. Sometimes the URLs have the application name, sometimes the URLs have the application purpose. Sometimes they are .fpo subdomains, sometimes they are after the domain name, sometimes they're under apps.fpo, or admin.fpo.
It would be nice to at least have the official set of Fedora infra-supported apps on one consistent scheme. Based on what other distros use, I would suggest the pattern be:
$purpose.fedoraproject.org
Where purpose is what the app is used for. So some examples:
builds.fedoraproject.org (koji) updates.fedoraproject.org (bodhi) acls.fedoraproject.org (pkgdb) (or pkgdb if acls is too confusing, we don't have to be 100% consistent) packages.fedoraproject.org (apps.fpo/packages) accounts.fedoraproject.org (FAS) meetings.fedoraproject.org (meetbot) calendar.fedoraproject.org (fedocal) lists.fedoraproject.org (mailman) wallpapers.fedoraproject.org (nuancier) elections.fedoraproject.org (elections) sources.fedoraproject.org (cgit for pkgs) mirrors.fedoraproject.org (mirror manager) easyfix.fedoraproject.org (easyfix)
Sometimes the subdomain name can just be the name of the app if the name of the app is sufficiently descriptive. Sometimes the name of the app isn't, though, in which case we need to come up with a descriptive name for it. I'm happy to suggest any that are tricky to come up with.
On top of this, the old urls should work as redirects... we might even want to set up $appname.fpo too in the cases where it'd be helpful.
(Also major kudos to the work puiterwijk has done thus far with our login system so we can actually even think about making this change now!)
I'm a little leary of making a bunch of redirects. redirects cause support issues sometimes (ie, user is going to 'updates' which is broken, but 'bodhi' works or the like, but I think it would be nice to have all the reasonable names.
Perhaps we could add all the purpose names, the app names and the old redirects, but then make a note to drop those old redirects after say a year? and make sure they are no longer advertised anywhere... then we can drop them down the road.
I guess this work needs:
@kevin i think dropping the legacy redirects after a year is completely reasonable. Maybe a reminder blog / ML post every month for the last 3 months before their retirement would help too.
@kevin If I can be of assistance implementing this I am happy to help.
Metadata Update from @kevin: - Issue priority set to: Waiting on Asignee
Metadata Update from @kevin: - Issue priority set to: Next Meeting (was: Waiting on Assignee)
So ticket #6397 and #5644 came up in the infrastructure meeting today (2018-07-12). We would like to get this discussed at the Dresden Flock (2018-08) and get an answer of which policy we need to follow towards naming of projects in the future. The outcome of this will be dealt with in the meeting of 2018-08-23 and the tickets will be closed shortly afterwords.
Metadata Update from @kevin: - Issue priority set to: Waiting on External (was: Next Meeting)
another one for Next-Meeting?
Well, we don't need more discussion here I don't think... we just need someone to drive the changes.
Metadata Update from @cverna: - Issue tagged with: backlog
closing this in favour of https://pagure.io/fedora-infrastructure/issue/6397
Metadata Update from @cverna: - Issue close_status updated to: Duplicate - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.