bmo VS mojo

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.

Initial thoughts

If you end up doing web development, check out Mojolicious:

https://mojolicious.org/

If you choose to go down the Mojolicious road, there's lots of deployment information and guides in the Mojolicious Cookbook.

I guess this will make it harder to search for Mojo(licious)-related stuff. 😩

But if I want the return value of 'test_p' or the error message 'This is an error', I can't seem to figure that out. I tried looking at the promise tests (https://github.com/mojolicious/mojo/blob/main/t/mojo/promise.t) but that didn't seem to work either.

Several! The 3 big players in order of release are Catalyst, (released in 2005), Dancer2 (Dancer was first released in 2009, but went through a complete re-write as Dancer2 around 2013), and Mojolicious (released in 2010).

This project sounds to me like the perfect excuse to learn Mojolicious if you're interested in converting your scripts into a web application using Perl.

Awesome! I still use Perl on a pretty regular basis both for work and fun. I really enjoy it. Definitely take a look at Mojolicious if you haven't already. It's primarily focused on being a web framework (both server and client), but it's nicely modular so you can use bits and pieces of the stack. In i3mojo, I used the Mojo::IOLoop event loop, Mojo::Base as a base class system, and Mojo::UserAgent as a web client for some plugins.

Last time I used Perl for anything web it was via https://mojolicious.org/

It even does event-based and websockets