https://bugs.kde.org/show_bug.cgi?id=441367
johnathan <testing1237...@yahoo.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |testing1237...@yahoo.com
--- Comment #2 from johnathan <testing1237...@yahoo.com> ---
i would add my inputs. Linus Sebastian from LTT on YouTube did the switch to
Linux videos and yesterday they released the first video in the series.
It was simply embarrassing. pop os failed spectacularly, mint had live image
monitor issues and it reminded me of high school project that the kid didn't
put a lot of thought in and the kid was still proud of showing it off,
stumbling along the way.
I have been using neon since 5.12 full time, so i know these things "should not
happen" but since they did to a novice like Linus and Luke, maybe we need to
look at how we can improve new comers.
The on-boarding experience is a good thing. I would like to add, with ideas
from the video to show people how to do basic stuff, like install packages. Pop
os failed because of Pop os fault. doesn't matter. the user was let down. How
about we inform the user about various install formats, like flatpak and snap
and deb and how they are different. Small texts, just pointers.
I did not understand why Linus had to use a software to find if all devices
were set up, why doesn't the software at "on-boarding" time do that check and
say "there are drivers missing for this device. should i check to see if there
is a driver?" and install it also at the same time?
How about we put the "whats new in Kde" blog posts in this on-boarding
experience ?
using the package manager is supposed to "prevent" users from bricking their
setups generally.
oh, would it be possible to more "humanize" error screens? we do say "you are
about to take this step. the following will be removed", can we improve by
saying "proceed with caution. doing this might brick your system" instead of a
wall of text?
--
You are receiving this mail because:
You are watching all bug changes.
