I also want to rescind my suggestion to include xss-lock, and recommend not to include thunar and firefox (some users are starting to go the flatpak direction so don't want stuff such as firefox on the host - I might be one of them, but don't know yet).

After reading through some responses to an earlier post where I suggested adding a couple extra things I have personally swung completely the other way.

My current thinking is that the base spin should only include the i3 sanctioned utilities (i3lock, i3status, etc.) and a terminal (seems uxrvt has already been selected for this).

Any experienced i3 users are likely opinionated already (and anything extra in the base spin could probably be stepping on their toes).

Any new i3 users would probably find a very limited package set underwhelming (when compared to the other spins). Whereas no packages with an explanation of why, and how to proceed might produce a better experience for them.

The Qubes installer (which is also Anaconda) has a "SOFTWARE SELECTION" section. Although it currently only has one option (xfce de), it seems that they intend to ultimately allow the user to select different desktop environments in the future (see screen shot in the "Installation summary" section at https://www.qubes-os.org/doc/installation-guide/).

Does anybody know how to add this "SOFTWARE SELECTION" section to the i3 spin Anaconda installer? Then the base i3 spin could be minimal, and there could be a couple options with progressively more stuff thrown in such as:

nothing - don't install anything extra
minimal - add things such as xss-lock (ie. things recommended in the default i3 config)
functional - add things that a typical user would want (ie. thunar, firefox, bluetooth)
full - rice it up (ie. music player, calendar, etc.)

Also, I have been experimenting with using flatpaks instead of .rpm where it makes sense, and so far the results seem pretty good. I guess the use of flatpaks will trend up over time. But it does introduce the complexity to spins regarding what would be an rpm (ie. i3status, xss-lock, probably thunar, etc. - basic utilities that make the system work) and what should be flatpak (ie. firefox, music player, etc. - desktop apps that the user interacts with for work or amusement). Is there even a way to install flatpaks during install? Is this something that should be considered, or should flatpaks continue to be completely ignored in favor of a 100% .rpm install?

Casey

On 1/28/21 4:13 PM, Dan Čermák wrote:

Eduard Lucena <x3mboy@fedoraproject.org> writes:

Good to know. afaik we should have thunar or any file browser of choice and
probably check about xss-lock and we will be ready to ship.

While I like xss-lock, I don't think that we should ship it: it's been
untouched since 2014.

Having a file browser sounds like a good idea. I've been using pcmanfm
for years and am quite happy with it, but I have no objections against
Thunar or anything other, provided it gets the job done and doesn't pull
in a bazillion extra packages.


Cheers,

Dan

_______________________________________________
Fedora i3 SIG mailing list -- i3wm@lists.fedoraproject.org
To unsubscribe send an email to i3wm-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/i3wm@lists.fedoraproject.org