Here are some thoughts on threat models for this, not sure if we have a better place yet to discuss this, so I'll just put it here :)

Hi, just found this task (after the announcement on community list).

In T7050#119392, @knauss wrote:

Do we have a tag to combine all task that are connected to this? Or how we have an overview what to do?
F.ex. T7430 is one […]

In T7116#119541, @jsamuel wrote:

Thanks @ltoscano. But is there a way to check whether an application is part of the bundle or not? Reference: https://www.kde.org/applications/ includes Krita, Calligra.

In T7116#119539, @ltoscano wrote:

In T7116#119538, @jsamuel wrote:

There is now one item on Wikidata that documents and links all KDE applications on Wikidata. Click on any KDE application (especially if you are the developer) and contribute by improving it. Several key information has already been added. Thanks.

It should be fixed and make it more clear though. The wikipedia article associated to that item is about the "KDE Applications" bundle, not *all* applications by KDE.

So only applications part of the bundle should be linked from that object, and not others outside the bundle (like Krita, partitionmanager, Calligra, etc).

In T7116#119538, @jsamuel wrote:

There is now one item on Wikidata that documents and links all KDE applications on Wikidata. Click on any KDE application (especially if you are the developer) and contribute by improving it. Several key information has already been added. Thanks.

There is now one item on Wikidata that documents and links all KDE applications on Wikidata. Click on any KDE application (especially if you are the developer) and contribute by improving it. Several key information has already been added. Thanks.

I also would support some kind of first run wizard setting up standard keyboard shortcuts and panel widgets. Especially for migrating Windows users. I believe it is feasible to make the wizard in an unobtrusive way. E.g. an icon could be shown in the system tray which shows popup that informs the user briefly about the existence of the customization wizard. Ideally, the wizard can also be run at a later time with a fine-grained selection of what should be changed from the installation default (or back to the default).

We should be cautious in mixing up what Calamares (not a KDE project) does with what the desktop environment might do. For background, Calamares can be used in two ways:

• as a system installer; you boot a live CD or memory stick, and install some (Linux) system to a hard disk
• as a system configurator; you boot a newly purchased laptop and it starts into a "newuser" which reconfigures the system with the user preferences (and login name) you give

Do we have a tag to combine all task that are connected to this? Or how we have an overview what to do?
F.ex. T7430 is one, where we need to have to look at. Because we need to think about how to implement a good proxy support for application and an override structure...

Firefox and other software ask you after your account. Would be nice to have one single account (secret service) somewhere (your cloud, hard disk, ...) where everything is stored and one login would be the universal key. Kde vaults by default where all setting dictionaries will be stored.

In T6831#119228, @jensreuterberg wrote:

There is a huge amount of antipathy towards installation wizards but one idea me and @adridg have talked and worked a little on is making Calamares have a "first set up" thing during the installation phase where you usually have a random slideshow. So instead of seeing random information that few bothers with you use that time to set up things for the core user (multiple users is a bit of a PITA)

This proposal unfortunately was not selected as a goal for KDE as a whole to focus on.
That does not mean that we should not work on it, of course. As the discussion here shows, there is a relevant subset of the community who is interested in this topic, and I think we should work on it anyway, even if the whole of KDE is not focusing on it.

These are two different things, and both relevant. Yes, things should work "out of the box". Yes, things should ideally be self-explanatory.
Games (regardless of platform) and many mobile apps and OSes have shown, however, that it's often not possible for everything to be self-explanatory. Or if you make it so, you end up with a "chatty UI" that annoys users once they've figured it out.

In general it is not so much wizards but first-run experience.

As a scientist who used KDE for many years, I can say that Kile and KBibTeX are two very good programs which were used quite a bit. I think it is the ultimate setup for writing documents in LaTeX (nowadays in strong competition with the online services Overleaf and ShareLaTeX).

This is the goal that will have the best positive outcome: easy for everybody, powerful on request.

I agree. Wizards in mobile are simple, to the point and disappear once you learned your way around. We could follow a similar concept for wizards on the desktop.

In T6831#119265, @colomar wrote:

I keep hearing "I hate first-run wizards / tutorials" from people, but they are so prevalent and effective in the mobile (and game) world that I believe we have to overcome our grudge from the negative experiences from yesteryear (and yes, most of the first-run wizards or tutorials in old KDE applications were pretty bad as well) and embrace well-designed first-time user experiences as a good thing.

In T6831#119228, @jensreuterberg wrote:

There is a huge amount of antipathy towards installation wizards but one idea me and @adridg have talked and worked a little on is making Calamares have a "first set up" thing during the installation phase where you usually have a random slideshow. So instead of seeing random information that few bothers with you use that time to set up things for the core user (multiple users is a bit of a PITA)

One thing that i have noticed from my project is that non kde people try to often help via the github fork . We should maybe find a way to work with PRs made via Github. Submiting a Pr then having it autoclose and told go make an account here and get anarchist and do your commit this way , then your github name (or email) is not ok because it usually just a nickname this now creates a git configuration burden to fix before contrubiting.

The only issue I could see with making this happen is Calamares is that not all distros are using it. Some distros (such as arch ) will never use it This creates inconsistancy for KDE users. That is the reasaon I suggest we do it on first login.

There is a huge amount of antipathy towards installation wizards but one idea me and @adridg have talked and worked a little on is making Calamares have a "first set up" thing during the installation phase where you usually have a random slideshow. So instead of seeing random information that few bothers with you use that time to set up things for the core user (multiple users is a bit of a PITA)

I think one way to add to the polish is to have new users do a wizard on their first login to a kde session. This wizard will invite the user to configure kde how they want it Look and Feel. KDE3 used todo this and I propose the new one follows the KDE3 method. First the user would be asked how they want the desktop to Feel some options could include default KDE, mac like , windows like , unity like, custom, etc. Provide some kind of prevew when selecting the options with descriptions here. This step would set up plasma and kwin, Then we move on to the 'Look' Part. Give the user options to customize the color scheme and widget set background, and other look options like icon theme . Then do the About me portion where you can set your user icon and fill out their Telepathy stuff. and then be sure to tell them more settings can be changed In system settings . Also provide a way to make it easy for users to make a Look and Feel theme from their settings so they are less afraid to try new things.

In T6831#119166, @abetts wrote:

Is there room for visual redesign in this proposal? Or are we thinking that this is more of polishing existing applications without a lot of changes?

Congratulations! This task is among the 3 selected ones to focus on for the next 3 to 4 years. It will need all hands on deck to make it reality. If you can help please add yourself to the list in the goal description.

Congratulations! This task is among the 3 selected ones to focus on for the next 3 to 4 years. It will need all hands on deck to make it reality. If you can help please add yourself to the list in the goal description.

Congratulations! This task is among the 3 selected ones to focus on for the next 3 to 4 years. It will need all hands on deck to make it reality. If you can help please add yourself to the list in the goal description.

Is there room for visual redesign in this proposal? Or are we thinking that this is more of polishing existing applications without a lot of changes?

Thanks everyone for helping draft this proposal. The voting has started. If you are an active KDE contributor and have not received an invitation to the vote please send me an email to lydia@kde.org.

Thanks everyone for helping draft this proposal. The voting has started. If you are an active KDE contributor and have not received an invitation to the vote please send me an email to lydia@kde.org.

Thanks everyone for helping draft this proposal. The voting has started. If you are an active KDE contributor and have not received an invitation to the vote please send me an email to lydia@kde.org.

Thanks everyone for helping draft this proposal. The voting has started. If you are an active KDE contributor and have not received an invitation to the vote please send me an email to lydia@kde.org.

Thanks everyone for helping draft this proposal. The voting has started. If you are an active KDE contributor and have not received an invitation to the vote please send me an email to lydia@kde.org.

Thanks everyone for helping draft this proposal. The voting has started. If you are an active KDE contributor and have not received an invitation to the vote please send me an email to lydia@kde.org.

Thanks everyone for helping draft this proposal. The voting has started. If you are an active KDE contributor and have not received an invitation to the vote please send me an email to lydia@kde.org.

Thanks everyone for helping draft this proposal. The voting has started. If you are an active KDE contributor and have not received an invitation to the vote please send me an email to lydia@kde.org.

Thanks everyone for helping draft this proposal. The voting has started. If you are an active KDE contributor and have not received an invitation to the vote please send me an email to lydia@kde.org.

Thanks everyone for helping draft this proposal. The voting has started. If you are an active KDE contributor and have not received an invitation to the vote please send me an email to lydia@kde.org.

I'm a mathematician working in academia, hence a heavy latex user. I've used linux for way over 10 years, with the desktop environment provided by KDE most of the time. I've used and recommended Kile, kbibtex, etc. Unfortunately I should say that, despite being an excellent piece of software, Kile has nowadays been overtaken by TeXstudio, and tools like kbibtex have been left behind in favor of more complete ones like Zotero or Mendeley. I'd love to be able to make something to revert this, hence I've written my name in the list.

The ambitious goal here is to improve the onboarding process for all types of contributors. If we succeed, everyone interested in contributing to KDE should have a clear and supportive path to follow. Of course coders are at the heart of KDE and what it does and lots of this work will inevitably go into that. The way I see it, "making it easy to build something and patch it" should be the case/aim for all types of contributions. =)

Ah my apologies, I thought the goal here was to capture the whole spectrum of contributors. Of course if the goal was to focus on non-coding contributors then this is fine.

In T7116#116225, @ervin wrote:

I'll sound like a broken record but: if we don't solve the "how difficult it is to build something and patch it" *first* all the nice things mentioned here with mentoring etc. (which require people we don't have BTW) won't get us far. People will try, fail immediately because it's too hard and leave again.
Seen that enough with my students the past few years.

I'll sound like a broken record but: if we don't solve the "how difficult it is to build something and patch it" *first* all the nice things mentioned here with mentoring etc. (which require people we don't have BTW) won't get us far. People will try, fail immediately because it's too hard and leave again.
Seen that enough with my students the past few years.

Hope it's OK if I slide in with some last-minute suggestions.