Without a meeting today, it's probably best to bring this up on the list.
I know that we've been reaching out to upstream to get licensing problems fixed. The responses on the couple of threads I've seen seem generally positive about us providing the licensing audits, and have usually provided some idea of what's needed to fix the problem (at least in terms of scoping out the required changes). But they don't seem to always provide firm commitments to fixing the problems, as all the normal IRL rules apply. In other words, the upstream maintainer may simply be too busy to work on the solution.
I propose that we simply make the rollout a first priority. If there are licensing concerns which must be fixed to install the application somewhere, then module owners must fix the licensing problems themselves (or find someone to commit to doing it within a specific time frame). If we're able to wait for packaging until some later time, then we install now, set a date where we will have all those problems solved, and start the process of fixing them.
In other words, what I'm trying to avoid is blocking on upstream if this team has the capacity to fix these problems and send them patches.
Paul