@alan_g

Hehe got it! Thx for everything. I'm going to learn those two for now.

@FloVanUB This is super exciting!!! Loving some good rust on ubport.

@fredldotme Hi! I accidentally tried installing F5122 using the F5121 option in the ubport installer, and it went on installing successfully. It even let me booted one time before failing to boot again.

If you need to test anything to get ubport on F5122 as well. I'm willing to help.
Thx again. Awesome stuff you're doing.

@alan_g

Thanks for the reply! These are tremendously helpful feedback.

While kernel/gadget/hallium is a bit out of my league now, I'm playing a bit naive here and see if I can get some of the points you mentioned into some subtasks that I'm able to tackle on my own.

About the kernel/gadget part, if the POC just targeted building on one device, would something like pixel3a or failrphone4 be straight forward enough? Unfortunately without c/c++ knowledge(rust/python for me), I think the most I can do is map the various shell script into the build yaml and see what's next. Another approach I think I might try is to use the rpi4 which has ubuntu core support and try something on top of it.

The lomiri transition to wayland seems like a high priority before any of my vague assumption can happen.

I think two option I might be able to try is either:

• run lomiri as it is on mir which I assume is possible with ubuntu core
• learn about confined-shell and mirway and see if I can get lomiri running as a standalone snap on a ubuntu core device.

@alan_g

Hehe got it! Thx for everything. I'm going to learn those two for now.

@alan_g

Thanks for the reply! These are tremendously helpful feedback.

While kernel/gadget/hallium is a bit out of my league now, I'm playing a bit naive here and see if I can get some of the points you mentioned into some subtasks that I'm able to tackle on my own.

About the kernel/gadget part, if the POC just targeted building on one device, would something like pixel3a or failrphone4 be straight forward enough? Unfortunately without c/c++ knowledge(rust/python for me), I think the most I can do is map the various shell script into the build yaml and see what's next. Another approach I think I might try is to use the rpi4 which has ubuntu core support and try something on top of it.

The lomiri transition to wayland seems like a high priority before any of my vague assumption can happen.

I think two option I might be able to try is either:

• run lomiri as it is on mir which I assume is possible with ubuntu core
• learn about confined-shell and mirway and see if I can get lomiri running as a standalone snap on a ubuntu core device.

@arubislander

To be honest I don't think it should be and It would be.
For example, I have some experience running and building snaps, it's definitely something I'm pleasantly doing.
If we can utilize the userbase of snap packagers to help the ubport team, and take some of the maintenance burden from their shoulder, it might be a healthy thing for the project from my perspective. This might provide a new angle to attract more contributors to the project after all.

All in all, the point of this post is kinda reach out to someone more experience than I am, and see if someone had already tried similar stuff like the original comment above. Maybe it's not as hard as I think it would be.

Re: How could Snappy Ubuntu Core be interesting for us?

This is a flashback on the original comment above.

Upon reading the recent news about ubuntu core for desktop use cases. https://ubuntu.com/blog/ubuntu-core-an-immutable-linux-desktop
I'm wondering if it's beneficial for the ubport project to do something similar? As a long time fan of the whole ubuntu touch project, I think once canonical dropped support, ubport has been taking a super huge responsibility to not only make things work, improve it when it's needed, but also to maintain the packages and transitioned it when matured. I think this huge responsibility kinda sucks the ubport team's energy from more interested features they want to invest.

I'm wondering if it's possible to build a POC of ubports that are:

• port hallium into gadget/kernel snap
• core20 or 22 base snap
• ubport shell as a snap, provides snap slots so other app(snap) can consume it if permitted by the user
• install an snap that consumes one of the slots from ubport shell snap

@ziggutas Flash tool 0.9.25.0 works on ubuntu 18.04, that might be easier.

@fredldotme Hi! I accidentally tried installing F5122 using the F5121 option in the ubport installer, and it went on installing successfully. It even let me booted one time before failing to boot again.

If you need to test anything to get ubport on F5122 as well. I'm willing to help.
Thx again. Awesome stuff you're doing.

@fredldotme Thx! Looking forward to use this as my n5 replacement.

Nice!!! Does this support anbox? I'm still deciding to get a oneplus 3 or xperia x to help testing. Any suggestion?

Q1: What's the plan onward about libertine?
With libhandy and kirigami maturing, we can assume more desktop's app's will be mobile optimized. It seems to be easier finding desktop apps that support mobile then the other way around. It aligns with the convergence goal too.

Q2: What kind of specification would new ports need for convergence to work? More broadly speaking, are there specific plan about this?

Guys you rock!!!

@FloVanUB This is super exciting!!! Loving some good rust on ubport.