Open Bug 1710908 Opened 9 months ago Updated 3 months ago

Allow to target messages by any "app package" (MSIX/snap/flatpack) status

Categories

(Firefox :: Installer, enhancement, P1)

enhancement

Tracking

()

People

(Reporter: nalexander, Unassigned)

References

(Blocks 1 open bug)

Details

In discussions for MSIX packaging, we're concerned about what to do for users who install via MSIX were we to stop producing MSIX packages. We have numerous in-product "messaging surfaces"; this ticket tracks allowing those surfaces to target based on the "app package" status. This would apply to MSIX/Windows app packages, but potentially also to snap/flatpak packages as well.

It's possible that this Just Works, but I don't think so -- I think the targeting uses a fairly restricted set of attributes and simple logic.

rachel: my guess is that the messaging subsystem group that used to be under :jimt would know about this. Can you choose somebody and NI them about this? Or ask them independently, there's no real need to connect this to MSIX and/or this project.

Flags: needinfo?(rtublitz)

(In reply to Nick Alexander :nalexander [he/him] from comment #1)

rachel: my guess is that the messaging subsystem group that used to be under :jimt would know about this. Can you choose somebody and NI them about this? Or ask them independently, there's no real need to connect this to MSIX and/or this project.

Yup! I've found the right person (andreio) - he's PTO till next week, so will checkin then and keep my NI? here until we have an answer.

Flags: needinfo?(rtublitz)

(In reply to Nick Alexander :nalexander [he/him] from comment #0)

In discussions for MSIX packaging, we're concerned about what to do for users who install via MSIX were we to stop producing MSIX packages. We have numerous in-product "messaging surfaces"; this ticket tracks allowing those surfaces to target based on the "app package" status. This would apply to MSIX/Windows app packages, but potentially also to snap/flatpak packages as well.

It's possible that this Just Works, but I don't think so -- I think the targeting uses a fairly restricted set of attributes and simple logic.

Hey Andrei! Could you help us track this down? If it doesn't Just Work, understanding the rough level of effort to get this working for MSIX format would be helpful here.

Flags: needinfo?(andrei.br92)

We haven't used similar targeting before so it depends how this information is surfaced (I'm not sure). I've noticed that flatpak Firefox is tagged under distribution that's available in telemetry but also as distribution.id pref (reading prefs and values is a "no-code" solution).
If this packaging is not similar (we don't have a pref to read) then exposing the information for targeting should still be easy to do but it will require to ride the trains.

Flags: needinfo?(andrei.br92) → needinfo?(nalexander)

(In reply to Andrei Oprea [:andreio] from comment #4)

We haven't used similar targeting before so it depends how this information is surfaced (I'm not sure). I've noticed that flatpak Firefox is tagged under distribution that's available in telemetry but also as distribution.id pref (reading prefs and values is a "no-code" solution).
If this packaging is not similar (we don't have a pref to read) then exposing the information for targeting should still be easy to do but it will require to ride the trains.

Andrei -- thanks, this is helpful. I don't see an obvious reason that we shouldn't follow suit and set distribution and the distribution.id pref in this use case.

mkaply: does this seem sensible?

Flags: needinfo?(nalexander) → needinfo?(mozilla)

Yes, I think it makes sense for us to package a distribution.ini with this for telemetry. Should make things much simpler.

I can setup a private repo in mozilla-partners that has the info and our build infra should have the ability to pull it for packaging.

Flags: needinfo?(mozilla)
Group: partner-confidential
You need to log in before you can comment on or make changes to this bug.