Q&A 44 This Saturday 16/02/2019 @ 19:00UTC
Q1) Aside from the flu, how was FOSDEM, and what cool things transpired there? (Also, hope everyone is getting well!)
Q2) What will development of Ubuntu Touch for the PinePhone and Librem 5 will look like, i.e., what will be changed in the OS vs. install on Halium devices, and how will having more-open non-Android devices appear on the market affect UBPorts' plans going forward? (Not asking for an ETA or status. )
lfortanet last edited by
Do we have had any contact with the Pine64 proyect and his phone? Do we have any new about Librem 5?
last edited by
How was Fosdem? Was it good to meet in person? Was it time well spent?
lduboeuf last edited by
I'm on devel channel , how can i know what are the changes between updates to eventually test or report correctly bugs/progress ?
mymike last edited by
what about app development API? the trend now is to move to qqc2 (with its suru style) but it's missing some important components that are present only in uitk (which is going to be deprecated)
Ergo is not ready yet
my short term solution/workaround/proposal is to extend the qqc2 suru style (transforming it in a minimal toolkit) adding components such as Icon, Action, UbuntuShape, ListItem (for swipe right/left)
I'd like aslo to contribute for the future sdk/APIs but since there isn't an official roadmap idk if it is worth to invest in a direction that (maybe) won't be the official one, so I'm asking what you think about this, thanks guys!
@mymike the app developers i have talked to find it makes most sense to use native qqc2 components wherever possible and have only the missing ones on top of qqc2 in our own toolkit. From looking at https://gitlab.com/dobey/ergo/issues/5 it seems thats the idea already pursuit by ergo right @dobey? Suggestion: I think it makes most sense to declare ergo as something official.
Personally I don't really understand the discussion here https://gitlab.com/dobey/ergo/issues/4. (But the reason may be my lack of insight in those stuff.) I would hope we don't need to throw away all the work that has gone into our beloved qqc2 Suru style theme.
Is the halium-7.1 UT build for FP2 that was set-up during the live-porting-session could be made available for enthusiastic FP2 testers like me ?
dobey last edited by
@mymike the app developers i have talked to find it makes most sense to use native qqc2 components wherever possible and have only the missing ones on top of qqc2 in our own toolkit. From looking at https://gitlab.com/dobey/ergo/issues/5 it seems thats the idea already pursuit by ergo right @dobey?
Yes, mostly. QQC2 itself is not ideal for much of the convergence landscape, so the idea is that Ergo will be a cohesive converged toolkit based on QQC2.
Since we are fresh out of FOSDEM are there plans to be attending a tech show like FOSDEM as vendors rather than guests? I think having some publicity for UTs features like convergence would generate some good interest for the project.
Question for Q&A: What is the status on this moment about Anbox ?
corvusd last edited by corvusd
@lduboeuf not is this bug and this app. Is in contact app I said. Because I make this answer and only. Are someone maintained this app? For this important bugs by the way.
corvusd last edited by corvusd
@Lakotaubp There is a question. About bug only is a explanation, for the need to have some maintainer this important app for this disturb bugs.
lduboeuf last edited by lduboeuf
@corvusd oh right sorry for the mistake.
Seems to be reported here : https://github.com/ubports/address-book-app/issues/56
Lakotaubp last edited by
@Michael Hi your a bit late sorry, the Q&A was last weekend. Keep an eye out though the next one should be long shortly on the 2ND of March if all goes to plan.