Here is the fifth issue of This Week in Lubuntu Development. You can read the previous issue here.

Changes

General

Lubuntu 18.04 was released!

Some work was done on the Lubuntu Manual by Lubuntu contributor Lyn Perrine and Lubuntu Translations Team Lead Marcin Mikołajczak. You can see the commits they have made here.

We need your help with the Lubuntu Manual! Take a look at PROGRESS.md on our GitHub or Launchpad repositories, or contact us for ways to help there. Otherwise, if you know another language, you can also help with translations! Pull requests on GitHub or Merge Requests on Launchpad are always welcome.

The Cosmic Cuttlefish is now open for development so the Lubuntu team has been hard at work syncing and merging things from Debian, and starting work on bugfixes. Here’s what we have done in the Cosmic cycle this far:

Synced a new version of lxqt-l10n from Debian which includes some packaging updates.

Synced a new upstream version of Transmission, 2.94, from Debian. Thanks to Julian Andres Klode for sponsoring the upload!

A lot of core changes have happened for the Cosmic Cuttlefish this far which may affect Lubuntu; far too many to list here. Thanks to everyone who has helped open up the archive this cycle!

Infrastructure and Project Changes

Lubuntu is switching to LXQt for 18.10

This is a huge change we have been planning for years, and we’re finally doing it.

Simon Quigley, Lubuntu’s Release Manager, broke the news on the Ask Noah Show and Softpedia Linux wrote an article the next day. We’ve received mixed feedback so far from the people we’ve talked to, so here’s a quick FAQ:

Q: Why are you switching? A: This is for quite a few reasons, but here are the main ones:

Upstream LXDE development has drastically slowed, and most if not all of the desktop is GTK 2, which is losing support and will eventually be phased out.

LXQt development upstream is fairly active, and LXQt is based off of the Qt 5 framework, which has a tendency to be more stable than GTK (no dependency on GNOME).

Q: LXQt is not yet on 1.0; do you have concerns about stability? A: Upstream LXQt only hits 1.0 when it’s Wayland-complete, and is not necessarily an accurate mark of stability. LXQt was marked as “stable” for the 0.11 release (arguably for the 0.10 release), and with steady progress on 0.13, we could reach 1.0 sooner than later.

Q: Lubuntu has been promising to switch for ages. Why has it taken this long? A: This was for two main reasons which have been resolved: lack of team resources, and the technology hasn’t been in place quite yet. We don’t want to switch close to an LTS release, because we take users’ stability very seriously. LXDE has been rock solid and stable, and while it is potentially subject to bitrot, tends to work very well. So the ideal time to switch is right after the LTS so we have close to two years to iron things out before rolling it out to LTS users. We didn’t decide to make the switch after the 16.04 LTS release because we were having some glaring issues, and team resources were scarce. Between that time and now, Lubuntu has also changed Release Managers and gained new members of the team. So, after evaluation both in person at LinuxFest NorthWest among part of the Lubuntu team, and online with the whole Lubuntu team shortly after the release, we decided this was the right time to jump.

Q: Will Lubuntu still be as light as it once was? A: Yes and no. Lubuntu, with this transition, is no longer what it originally was. As we use more modern technologies, Lubuntu will use more resources (which is inevitable). However, while we won’t have the amount of granular minimalism that we once had, the statistics we have seen internally strongly suggest that users won’t see much of an increase. Some people may have noticed that in the release announcement for 18.04, we bumped the system requirements to 1 GB of RAM at minimum (among other things); this wasn’t because Lubuntu had actually gotten larger, it was because we hadn’t updated those particular values in ten years. Yes, Lubuntu can probably run with less, but as we move forward, applications like web browsers can and will use more resources.

Q: I have Lubuntu running in production environments which need support of an LXDE Lubuntu (18.04 or 16.04) for longer than the length of the support cycle. Can I still get support? A: Contact Simon Quigley. We are absolutely open to working with you, and, in fact, we are in the process of setting up a more formal framework for this. More details to come.

Q: Lxqt? lxqt? LxQt? LXQT? What is it? A: It’s LXQt. It used to be named LxQt, but it has since been renamed LXQt.

So far, to work towards this, we have reworked the seeds, updated the metapackage, and made a fix to our Calamares settings to fix the installer. Expect steady progress, and furthermore, the daily ISOs use LXQt now.

Roadmap

We don’t have a Cosmic Cuttlefish release schedule yet at the time of writing, but when we do, you can find it here. The tentative 18.10 release date is October 18, 2018.

Have an idea for what the next Lenny should look like? Let the Artwork Team know in the comments. 🙂

Miscellaneous

Simon Quigley and Walter Lapchynski from Lubuntu were at LinuxFest NorthWest 2018! Here are some pictures from the event:

Here’s an ePaper watch that William Wold (who works on the Mir team) made.

Lots of the stickers we had laid out were taken, so Walter brought some additional ones.

Valorie Zimmerman from Kubuntu (top right) helps with the booth while Dustin Krysak from Ubuntu Budgie (bottom right) writes Python with his daughter, while Walter and Simon were at a talk.

Simon helps a conferencegoer (right) put Linux on their 2009 MacBook Pro (center) while Dustin (left back) talks with another conferencegoer.

Lubuntu would like to thank Ubuntu for helping fund this trip for Walter and Simon. You can donate to the same funds which made this possible here (while increasing the “Community” slider).

Contact us

Feel free to get in touch with us here for support, and for press/marketing purposes or if you have a private inquiry, you can get in touch with Release Manager Simon Quigley here.