Just found out the Matrix rooms but it seems the core dev team is not there.

Telegram went so downhill over the past few months that I can't even register anymore.

Is there any other way to communicate with core developer team given that Lomiri has freedom of choice in its manifesto but is tied to a single communication platform?

@lduboeuf Thanks, will give it a try. Hope it works on the host machine as well rather than needing a connected device because I am using it as a desktop.

I read the documentation, it seems it's meant to be used for building packages for Lomiri, not working on Lomiri itself?

@lduboeuf How do you build?

@lduboeuf This is another package with its own dependencies different from lomiri itself.

https://gitlab.com/ubports/development/core/lomiri/-/blob/main/debian/control?ref_type=heads

https://gitlab.com/ubports/development/core/lomiri-ui-toolkit/-/blob/main/debian/control?ref_type=heads

I am building from https://github.com/ubports/ubports-pdk

@lduboeuf Must be something else because this concerns the init system which was changed after 14.10 to systemd by default. We are speaking of 10 years ago... The core team is building the package quite often so they must be using some other version. I checked all other branches but they all require upstart.

Can't bypass it because it's a requirement to build lomiri itself which I am aiming to work on.

Seems like this is the last culprit for me to start contributing to the development of Lomiri.

https://gitlab.com/ubports/development/core/lomiri-ui-toolkit/-/blob/main/debian/control?ref_type=heads#L384

The reason I am posting here and not in Telegram is because I prefer to have those clear and sorted for anyone joining after me so that we have some kind of up to date wiki of issues and how to resolve them.

Got it working here is the useful issue - https://github.com/ubports/ubports-pdk/issues/40

Now I can do ubports-clone lomiri and start it as a DE.

@Keneda https://forums.ubports.com/topic/11362/trying-to-help-developing-lomiri-questions/10

@Keneda Thanks, now I fully understand. My bad I didn't do my homework. Best of luck to the UBports team. If only they made contributing as an open-source developer a little more easier, a little more straight-forward I will jump wagons as I have a few tasks in mind to work on. As an ex-Scrum Master I am used to this type of thinking where if you make it easy enough for others to contribute and focus on removing impediments then volunteer power will multiply and give you even more time to make the process easier and more welcoming.

@wgarcia Seems like a valid argument. There is so much effort going towards the mobile form factor that it's lacking in new fresh ideas simply because all resources is focused there. I also maybe overestimated the resource of UBports but I always thought that as a company behind it all you have to do is make it easy to work on for open-source developers - updated documentation, up to date tools to get started. While they are full on developing themselves while the tools needed for external people to come in are completely left behind unmaintained.

For example https://github.com/ubports/ubports-pdk

Issues open for 3 years while internal devs are climbing up the mountain alone.

@gpatel-fr Thanks the commits history reveals quite a lot. What's interesting is that if we take specific aspects like the menu drawer, the compiz window manager settings Unity 8 is far more limited compared to Unity 7. This doesn't seem like reusing what was there but rather excluding large parts of it. The parts that made it unique.

The functionality that Lomiri has for desktop as of now is not much more different than a KDE theme. Very few new effects, lots of existing ones missing. The whole layout just seems bland like a Word/Excel stylesheet rather than something building on the Unity 7 design and presenting new concepts on top.

@kugiigi Technology tends to evolve based on what's already been achieved. So for example when we talk about Wayland 20 years later than Compiz of course it is expected to be more feature rich and better while it's barely comparable as of yet in terms of effects, plugins, modularity etc.

Speaking about Lomiri surely the new stack and platform means starting from scratch but if you have the prototype of what has to be achieved and surpassed it's only natural to expect for example simple things like menu category drawers to be done years ago. From what I see the main effort is porting the new tech but that doesn't stop UI from evolving separately if only in QMLs and UI/UX sketches.

In conclusion comapred to early 2000s progress nowadays everything seems non-innovative and slow to come.

Compiz was released in 2006 and is still maintained. Unity7 was released in 2010 and is still maintained. My question is why Wayland and Lomiri are so far away in terms of functionality, plugins etc. compared to tech made 20 years ago.

Are we building on top or reinventing the wheel?

@kugiigi I suppose inclusion felt victim to the race to completion.

@arubislander Unfortunately PDK can't find anything of the existing repos.

https://github.com/ubports/ubports-pdk/issues/35

Being open for more than 3 years gives me less hope that someone is even noticing these...

@arubislander Thank you for the clarification. I am very new to this stuff although been a Linux user for 20 years and a developer for 10. I am trying to work precisely on the DE itself. Will give it a go.

The following packages have unmet dependencies:
 libmircommon11 : Breaks: libmircommon9 (< 2.20.2-2ubports1+0~20250611101450.2+ubports~dev~1.gbpc6368b)
                  Breaks: libmircommon9t64 (< 2.20.2-2ubports1+0~20250611101450.2+ubports~dev~1.gbpc6368b) but 2.14.1-4.1ubuntu3 is to be installed
 libmiroil7 : Breaks: libmiroil3 (< 2.20.2-2ubports1+0~20250611101450.2+ubports~dev~1.gbpc6368b)
              Breaks: libmiroil3t64 (< 2.20.2-2ubports1+0~20250611101450.2+ubports~dev~1.gbpc6368b) but 2.14.1-4.1ubuntu3 is to be installed
 libmirplatform30 : Breaks: libmirplatform26 (< 2.20.2-2ubports1+0~20250611101450.2+ubports~dev~1.gbpc6368b)
                    Breaks: libmirplatform26t64 (< 2.20.2-2ubports1+0~20250611101450.2+ubports~dev~1.gbpc6368b) but 2.14.1-4.1ubuntu3 is to be installed
 libmirserver63 : Breaks: libmirserver58 (< 2.20.2-2ubports1+0~20250611101450.2+ubports~dev~1.gbpc6368b)
                  Breaks: libmirserver58t64 (< 2.20.2-2ubports1+0~20250611101450.2+ubports~dev~1.gbpc6368b) but 2.14.1-4.1ubuntu3 is to be installed
 libmirwayland5 : Breaks: libmirwayland4 (< 2.20.2-2ubports1+0~20250611101450.2+ubports~dev~1.gbpc6368b)
                  Breaks: libmirwayland4t64 (< 2.20.2-2ubports1+0~20250611101450.2+ubports~dev~1.gbpc6368b) but 2.14.1-4.1ubuntu3 is to be installed

apt search libmircommon
Sorting... Done
Full Text Search... Done
libmircommon-dev/24.04-1.x 2.20.2-2ubports1+0~20250611101450.2+ubports~dev~1.gbpc6368b amd64
  Mir Display Server - common library - development headers

libmircommon-internal-dev/24.04-1.x 2.20.2-2ubports1+0~20250611101450.2+ubports~dev~1.gbpc6368b amd64
  Mir Display Server - development headers

libmircommon11/24.04-1.x 2.20.2-2ubports1+0~20250611101450.2+ubports~dev~1.gbpc6368b amd64
  Mir Display Server - common library

libmircommon11-dbgsym/24.04-1.x 2.20.2-2ubports1+0~20250611101450.2+ubports~dev~1.gbpc6368b amd64
  debug symbols for libmircommon11

libmircommon9t64/noble 2.14.1-4.1ubuntu3 amd64
  Mir Display Server - common library

Anyone got these resolved?

@kugiigi Thanks. There is such a package. Will give it a try with Noble.

I am getting familiar with clickable and after quite a lot of tweaks I got it building.

Now the question is a controversial contradiction in versions:

If using the default clickable/amd64-20.04-amd64 image it is missing qt5.15.0 needed for the imports of QtQuick 2.15.

If using latest clickable/amd64-ut24.04-1.x-amd64 it is missing libubuntu-app-launch3-dev.

Why is there no intermediate 22.04 image featuring both?

Am I missing something in the setup?