OFf the top of my head, features that would make MarkNotes/KleverNotes a killer note-taking app:

You want us to write the changelog here, correct? I can start doing that for my applications

Ah that meant "Plasma Browser Integration"

Note that this is more of a feature request/rant, not really a goal. You also don't list any champions, so it's not even eligible to vote.

Specifically we can measure this via submission frequency and quantity of unresolved bugs, feature requests, and issues in general relating to organization in addition to user feedback from surveys, supplemented by general feedback across the community and those interested in this goal. Additional objective metrics could include satisfaction as reported in polls and surveys directed at users and the KDE Community and similar types of requests for feedback.

Just a few things to point out (not a negative against the proposal) since no one else did yet:

This is a feature request, no?

This all sounds well and good, but how will we get to this point? Aka, I feel like this goal is more pie-in-the-sky then something practical I feel like we can achieve. Like, why/how are we at the point where someone can say something like this:

Interesting goal, but I'm not really sure if this is a worthy goal. We don't make hardware, and we (usually, except for Neon) don't make distributions. Some of this stuff *could* be verified by us, such as:

Yup, this sounds too much like a feature request. If this was spun into a goal, it would sound a lot like the small businesses goal anyway

(Raising to Needs Triage because of champion)

This seems more of a Redox goal than a KDE goal ;-)

Perhaps this is not a grand goal by itself, but could this be viewed as part of the accessibility goal? (As accessibility also encompasses usability improvements that enhance the overall flow)

Do you mean a browser application or a browser engine? One is much harder to develop than the other...

If you're not interesting in working on this @julianbraha then I'm afraid it can't be a goal since no one else has stepped up. Either way, this is more of a feature request than a goal for all of KDE to follow.

There is a fair amount of overlap but one thing to keep in mind is that most small businesses don't have a dedicated "IT Person" who's one and only job is to handle the IT for business. Therefore, any kind of solution like good systemd-homed support will require a very "user friendly" way to set things up. I mean, no longer needing to use the console to set everything up so that means there needs to be a simple GUI for everything.

On the other hand, the needs for a small business is a lot less than a larger one. For example, my network /home/ and share drives are running on a Raspberry Pi and there is almost no performance hit because it's on a slow server. We also don't need multiple domains or multiple VPNs in a single network. So scaling in this case means going from 3 computers to about 20. After 20 computers in a single location, you are probably more of a mid-sized business with slightly different needs.

These are all opinions, where is the actual proposal @medmedin ?

This goal is too short, and I agree with Sephatrix that combining it with the other goal would fit better. Plus, this has almost no benefits for our users.

This sounds interesting, but I'm not convinced it needs to be a "KDE Goal". This sounds more in-line with something like grant work or a GSoc project. This will be in effect for multiple years, but with a dedicated team this could be solved in a few months independently from the rest of KDE. Not to dissuade you from the interesting work, but I'm just commenting on the goal-ness :)

I was really confused at first thinking this meant "input" as in "feedback" but reading it more I really like this proposal (and totally not biased because my work is mentioned by name :))

See https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/2895

We use PlasmaExtras.Menu now