I think doing a session to the oVirt developers will help remediate some of the time you're spending with each develop on their own, plus it might give us ideas for what to plan to OST V2, in terms of scale and requirements.
We should schedule a session but only after:
We update OST's doc.
We ease the process of running OST locally.
We ease the process of developing tests to OST.
I've opened an epic that contains the needed tasks for making the interaction with OST better.
The session can also contain an explanation about how package management works in OST.
does it make sense for to do a session soon or we want to wait for more content/fixes to come in?
I believe this can be counted for the session/presentation you’re about to do on Lago/OST/Vagrant.