@Flohack I would give it time. I don't know about other people, but personally I'm not placing any expectations on UBPorts or Yunit for quick results -- I'd much rather everyone just took some time to patiently explore the codebases that exist, than have anyone feel pressured to get things done straight away.

@alan_g I'll reach out to @mariogrip directly w.r.t. all things UBPorts.

You've been more than generous with your time, but is it OK to still ping you about Mir(AL)-related issues w.r.t. the USC refactoring? No worries if not.

On a slightly bigger note:

I would really, really urge everyone involved in UBPorts to take on the key advice here:

everyone (not just devs, or an "in crowd") must be able to see the the workflow (and status of work items).

Right now if I go to ubports.com and click on "Community" or "Join us", I get a lot of pages about stuff like the different steering committees and whatever, but (despite clicking on multiple different links), there's NOTHING about easy ways to start taking useful action.

If anything it's even more offputting because pretty much the first thing one sees on the "Get Involved" page is the link to become a member ... which jumps straight into statutes, 6-month commitment, etc. etc. etc. Most people would like to have a way to dip their toes in the water first before thinking about jumping in that deep!

It would be far better to have an easy way for people to just start doing small things, get engaged through doing stuff, and learn by experience whose commitment is up to the standard expected of full members.