1. When
- Date: Saturday 29th August 2020
- When: 15.00 UTC
2. Agenda
Getting GNOME 3.38 + Tracker 3 ready for release : https://gitlab.gnome.org/GNOME/Initiatives/-/issues/17
3. Present
4. Notes
4.1. Blockers for Tracker 3.0 release as part of GNOME 3.38
- Nautilus
- Tag manager rewrite - done by Sam and ready for review
- Starred files migration from Tracker 2.x
- Maintainers want an automatic migration for best user experience
- Is the migration done by Nautilus, or gsd-housekeeping ?
- Does the migration script depend on distro-provided tracker 2.x, or embed its own copy of libtracker-sparql?
- Sam to prototype this
- Photos
- The port is feature complete but very lacking in testing
- Rishi hasn't had time to look at it and comment
- It's not sensible to merge it right before the freeze
- This means we need a solution where Photos uses tracker 2.x while the rest of GNOME uses Tracker 3
- If Photos installs suitable domain-specific .service files, it could spawn tracker-miner-fs 2.x on demand. This avoids double indexing at all times except when Photos is in use.
- Distros will need to install tracker 2.x but DISABLE autostart for tracker-miner-fs 2.x for this.
- Carlos to look at this
- Distros may have 'new package' deadlines which could make it hard for them to ship tracker 2.x and 3.x in parallel
- Not much we can do as an upstream, but lets send a mail to distributor-list and make the situation clear.
- Bundling tracker 2.x inside the few packages that still need it could be an option.
- Sam to draft a suitable mail
- Not much we can do as an upstream, but lets send a mail to distributor-list and make the situation clear.
- Issues;
https://gitlab.gnome.org/GNOME/tracker/-/issues/235 -- this is not fixed, but it is possible to workaround. Dropped from milestone.