As mentioned on -devel I'd be happy to be the Board sponsor for this.

Happy to answer follow-up questions from the board meeting here

+1

I think this is a great idea. I have a couple concerns about implementation though.

First, I'd like us to have a clearer sense of what goes in vs what does not.
"Likely to be eventually merged" is a judgement call, not an impartial criteria.
I don't think we have to fully solve this to get the ball rolling, but I'd like us to put some more thought into it.
My concern is that people are going to get upset about what is or isn't pulled in.

Second, I'm a little concerned about possible NVR corner cases.
Using a different dist tag might not always work as desired.
For example, if a pending MR bumps the package to a new version, and then stream proceeds to ship updates for the old version (or a not-as-new version), then the fasttrack user will be missing these stream updates.
This is a simple example, but there could be more esoteric issues lurking across the breadth of specfiles.

I'd love some sort of workflow specified for what happens if the merge request is closed out but not merged.