bmo VS exiftool

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.

If you're doing a pipelined bulk processing pass to add metadata tags after extracting them via Speech to text, or have delimited notes in a text file, or ... etc.

You might find ExifTool useful.

It's pure commandline (with a few third party GUI's IIRC) multiplatform and purpose built to display, edit, add media tags to all sorts of AV files.

https://exiftool.org/

> Any method that I've found to clean them up (exporting the originals, deleting them from the library, and then re-importing the JPEGs only seems easiest) will lose all of the years of metadata that I've built up in the library.

The open source tool osxphotos (https://github.com/RhetTbull/osxphotos) can help with this. You can export the JPEG images while preserving metadata using the thrid-party exiftool utility:

`osxphotos export /path/to/export --has-raw --skip-raw --exiftool`

This exports all images that have a raw pair but skips the raw component then uses exiftool (https://exiftool.org/) to write the metadata (keywords, etc.) to the exported JPEG files. You can then re-import these into photos either by dragging them or by running `osxphotos import /path/to/export/*`

Both the export and import commands have many other options for controlling export directory, etc. `osxphotos help export` or `osxphotos docs` to open docs in browser. (Disclaimer: I'm the author of osxphotos)

Check out exiftool.org

Locationator also comes with an optional CLI that can be used to perform reverse geocoding on images from the command line or perform the reverse geocoding and then write the location data to the file's XMP metadata using exiftool. It also comes with two services for doing the same from the Finder or other apps using the Services menu.

Edit: Nevermind, I got it. I used PyExifTool and installed exiftool from exiftool.org.

May not work as not all camera store the serial number in the EXIF, but if you've got exiftool installed you can try running:

I think TIFF has some unique features that makes it more prone to certain security issues[1] compared to other formats, such as storing absolute file offsets instead of relative offsets. So I am not sure TIFF is a good container format, but many camera raws are TIFF-based for some reason.[2]

[1] https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=libtiff

[2] https://exiftool.org/#supported (search for "TIFF-based")

I have struggled with this in the past, and I found the utility called exiftool quite useful.