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?
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.
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
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.
I would really like to see a proper nextcloud / owncloud account support for calendars and contacts.