It sounds to me like Martin is on top of this issue. I don't think FESCo needs to get involved at this time.

I do not understand what @jpokorny is proposing FESCo to do and as @bowlofeggs Martin seems to be handling the open Bugzilla bug as well.

@jpokorny please explain what you are requesting from FESCo.

Sorry for being too vague.

It was partly caused also by me not knowing the exact cause of the
questinable circumstance I've observed. But I managed to nail that
down, eventually:
https://bugzilla.redhat.com/show_bug.cgi?id=1648024#c17

It looks to me that there's a vested interest on Fedora side for that
not happening, otherwise #1359 would not be dealt with as well.
So you can take this ticket as a heads-up that the reporters of
said bug found a loophole that effectively bypasses what was once
a ruling-power based predestined way to deal with with Firefox vs.
OpenH264, and in turn, it exposes users to various shortcomings, e.g.,
one more thing out of packaging system's control despite it's not
easily discoverable until there's a user's profile vs. system versioning
mismatch, which accidentally happens to be the case these days (and even
then, it's nothing obvious for users to discover).

I don't know what technicals means are there to prevent this loophole,
by FESCo being aware of this alleged violation can hardly put new
obstacles into the resolution, hopefully the opposite.

(yes, I am perhaps bad with processes, was there a better way to get
the message out to the respective Fedora leadership, barring devel ML
that I intentionally skipped here for being aware of possible noise?)

I'm not sure if this is still relevant, but according to my recent experience the firefox is not using cisco openH264 anymore, but rather ffmpeg (See https://pagure.io/teamsilverblue/issue/57).

So i'm not sure if the cisco repo even provides something useful now.

I don't think there's anything for FESCo to do here and the maintainer is handling the issue.

I don't think there's anything for FESCo to do here and the maintainer is handling the issue.

+1

Ack. We agreed to close this.

Thank you for the information.