We have https://phabricator.kde.org/phurl/ which powers links like https://go.kde.org/u/systickets. Currently creation of new shortened URLs is limited to "Community Admins".

We could review that policy and expand the permissions, or add more people to the Community Admins group.

I see, didn't know this one.

While e.g. "https://go.kde.org/u/systickets" is still slightly long (not only in proportional fonts ;) ) awhen compared to the goo.gl one, and I was more thinking of things like "https://kde.org/jj", might be still short enough.
Guess phurl and go.kde.org could serve this purpose for now, we could also try with sysadmin right first and extend if demand and usage is high enough.

Any chance the u/ could be removed from the path? go.kde.org + term are okayish to memorize also for giving away the url on-the-fly e.g. in discussions, while the u/ is hard to remember correctly, given no mnemonics and also no direct purpose.

At the Phabricator level it's not currently possible to remove the /u/ part. But I think we could do it in our Apache configuration.

Unfortunately anything short of a new domain won't get us anything shorter than go.kde.org :)

I'm not a huge fan of kde.org/jj, we only created that because of byzantine policies imposed by the Google OSPO team when taking Google Code-In applications a while back.

Editing of urls once created can be delegated easily enough as the modification policy for each PHURL is separate.

@kossebau if we change the url form to https://go.kde.org/<something> that will be fine for your purposes I assume?
An Apache level redirect which forwards go.kde.org/<something> to phabricator.kde.org/u/<something> should do the trick here to keep Phabricator happy.

In T7816#125380, @bcooksley wrote:

@kossebau if we change the url form to https://go.kde.org/<something> that will be fine for your purposes I assume?
An Apache level redirect which forwards go.kde.org/<something> to phabricator.kde.org/u/<something> should do the trick here to keep Phabricator happy.

Yes, having an url pattern of "go.kde.org/" + "term" should be good for my/our :) purposes.

Being able to say and hear "find the $stuff at go.kde.org/$stuff" should work both for link passers and link receivers, in hallways, on the phone and in chat :)

We should also standardize on lowercase with the term path, so people do not have to remember casing or rather know what the casing is.

Once we have that, we should also switch from using kde.org/jj to go.kde.org/jj and possbly go.kde.org/juniorjobs, so that new service is well promoted in the KDE community.

Oki, I shall make the needed arrangements for this tonight.