bmo VS perl5

Mozilla is using a mix of Bugzilla, Jira, Github Issues, and $DEITY knows what else, depending on the team or project in question. A good rule of thumb is that for any major system (code hosting, bug tracking, chat, wiki, CI, etc) Mozilla has at _least_ two- one homegrown and/or OSS, another a proprietary service- and a simmering battle over which should be used.

Most of Firefox engineering was still on their fork of Bugzilla (https://github.com/mozilla-bteam/bmo) when I left back in 2021.

My only little contributions to KDE so far (until now) has been through reporting bugs (and also helping a few people here and there with their issues on forums such as this one). I wanted to figure out if something could be done to improve the bug reporting experience. When I looked at the bugzilla instance used by Mozilla at https://bugzilla.mozilla.org I was surprised by how good it looked compared to the standard bugzilla. Unfortunately, as it turned out, Mozilla is using a forked version of bugzilla (the repository is here) and hence, you can't just take the theme files from there and apply it directly on a normal bugzilla instance. I tried and it looked broken.

I've literally taken the css files from https://github.com/mozilla-bteam/bmo/tree/master/skins/standard (which is the forked version of bugzilla which Mozilla uses on https://bugzilla.mozilla.org like we discussed the other day.

I was not signed into GitHub. I opened the permalink and it displayed fine. I opened the raw page in another tab; it was fine.

Nothing to do with a fixing the trap, it turns out: https://github.com/Perl/perl5/commit/4197fe35a33e6471f8f532abfd06cd6c120f180e which leads to https://rt.perl.org/perl5/Ticket/Display.html?id=109408

As we mentioned last week, this week we are working on a portable, symbolic link implementation that also works on Windows. You can see our progress here. To implement this, the Perl win32/win32.c source code would be greatly appreciated.