I would really like to see a proper nextcloud / owncloud account support for calendars and contacts.

A while ago, i believe Alan posted and you guys discussed that order for UBPorts to switch to wayland, the steps were:

1. Upgrade Mir to a newer version
2. Design the missing Wayland protocols to replace Mir protocol internally
3. Migrate the internal Mir to Wayland

Now that OTA-12 is soon out, and a newer (1.2 - but 1.8 was released recently?) Mir is in place, where are you guys with this project and how high does it rank on your priority scope?

Now that latest mir is almost done (i guess you guys are aiming OTA-9), what is next on your focus list? What's your priority in:

• mainline devices (pine / purism)
• anbox
• full wayland (replacing mir protocol)
• unity desktop
• hidl hardware layer
• whatever cool thing i missed

Do you have any plans to allow CARDDAV to be configured as CALDAV as part of the regular accounts section (instead of using commandline syncevolution)?

I'd love to hear what's in scope for OTA-3, and how things are progressing towards Halium / Xenial.

On your blog post you've made some statements about the purism hardware that appear to have been copied of the crowdfunding page. In several Q&A sessions and blogposts, purism have however answered questions related to hardware that deviates from that. For instance, in this reddit Q&A they claim dual sim is in the current spec list https://www.reddit.com/r/IAmA/comments/87tbfl/todd_weaver_from_purism_doing_a_reddit_ama/

Could you have purism check the specs your posted are up to date? For me, dual sim is a Big Deal for instance

Dekko has some uncommon options, like under authentication type and force ssl/tls - you should probably try changing those around a little.

I noticed, for example, that GMAIL defaults to "plain" authentication but requires "login" ...

If that doesn't work, please join us at the dekko user group on telegram and we'll try to help!

I've seen a lot of talk about Halium flash by; is there any overview of the Halium ports already available or being worked on?

A while ago, i believe Alan posted and you guys discussed that order for UBPorts to switch to wayland, the steps were:

1. Upgrade Mir to a newer version
2. Design the missing Wayland protocols to replace Mir protocol internally
3. Migrate the internal Mir to Wayland

Now that OTA-12 is soon out, and a newer (1.2 - but 1.8 was released recently?) Mir is in place, where are you guys with this project and how high does it rank on your priority scope?

Dekko has some uncommon options, like under authentication type and force ssl/tls - you should probably try changing those around a little.

I noticed, for example, that GMAIL defaults to "plain" authentication but requires "login" ...

If that doesn't work, please join us at the dekko user group on telegram and we'll try to help!

In terms of "what is home", i typically use the "scopes" app rather then the dash. For me, on the phone, the dash is just a place of shortcuts for apps that I open a lot.

There's no real value in the empty background right now - nothing there i cannot do from elsewhere except see nothing. If convergence comes, then putting stuff on the desktop makes sense (if we liked gnome, we wouldn't be here). Or, setting a default home app could also work (and then you could default that to a "desktop" app that shows shortcuts ...).

If any real option gets coded, we would indeed need a way to get there. Swipe left is for the drawer (and apps), which is a change I'll at least have to get used to instead of accessing the scopes app in the spread. You could put a desktop icon on the drawer somewhere, which would re-inforce the drawer as the unit of navigation. You could also put both the open drawer (as a replaces of the scope app) as well as the background as defaults in the spread. You could also just do both.

Concerning the "click outside" from the spread: it's a new form of interaction. It might be more intuitive if there's a card to select from, and if that card is always at the same place.

Also, "hide apps" sounds wrong to me. I want to (positively) go home, not (negatively) hide other stuff.

Now that latest mir is almost done (i guess you guys are aiming OTA-9), what is next on your focus list? What's your priority in:

• mainline devices (pine / purism)
• anbox
• full wayland (replacing mir protocol)
• unity desktop
• hidl hardware layer
• whatever cool thing i missed

Congrats to a succesfull 2018! You've managed to get onto Xenial, almost deprecated Oxide, almost reached Halium and you're closing in on Mir.

What are your personal coolest achievements of 2018, and what are you looking for mostly in 2019?

@alan_g Same here; maven versioning which i'm used to also goes from 1.5.6-SNAPSHOT -> 1.5.6 (release).

My vote is for FAST. Smaller changes at every release usually means it's easier to fix, and said fix is always only 2 weeks away (unless you also want to be able to do hotfixes to stable, which might mean days away).

Given all the above, i would suggest having a manual step before RC gets promoted to stable; just to have someone look around to check how many people have actually used the RC to address stability. It also means that, in case of vacation times, nothing gets promoted automatically.

I do have a question: can you actually OTA the entire population within a day?

There was an announcement that ubports would look into supporting the new librem 5 device. This device is famously supporting actual mainline linux through PureOS. Having a mainline device means that it (i guess?) it would not need to run on top of halium or libhyrbris.

There are however other attempts to run mainline on devices, such as postmarketOS which currently has (partial) support for the Nexus 5 and Sony Z2 (tablet and phone).

What are your plans to support mainline devices in general? I suppose you'll make a mainline version to run on the librem 5? Would you make a mainline rootfs? If the Nexus 5 has "good enough" mainline support, would you migrate the nexus 5 builds to run mainline instead?

Question for purism: how is the process going of designing a phone? Are you on track with where you though you'd be by now? Is it more difficult then the laptops? How "libre" is the iMX stack compared to the intel stack - are there bootloaders and Management Engines to dodge here as well?

How will having a second "base" (one halium, one GNU) impact our development? Will we have two types with different update strategies, or will they always be based on the same ubuntu version?

I can imagine, for instance, that the much newer kernels available for the Purism phone will make certain features much easier to make available.