- User Since
- Jun 5 2015, 8:50 PM (127 w, 6 d)
Approval from my side. Thanks.
Fri, Oct 27
For me as an occasional code contributor, I notice that I find it especially tedious to get a proven local runtime environment ready for local testing of non-trivial programs. For example, this tutorial https://community.kde.org/Guidelines_and_HOWTOs/Build_from_source#Set_up_the_runtime_environment describes which environment variables should be set for this purpose. Quite a few and I am not sure if all entries are still valid. I guess every developer ends up with his/her own script or scripts to handle this issue (including having some convenience message on the bash prompt message showing if the correct variables are set). Maybe this could be extracted to a maintained and standardized script that can be used anywhere where Qt/KF5 based-programs are developed. The script and a guide how one would use it in combination with Kdevelop (or automatic integration with the Launch > Environments) could facilitate getting started.
Sat, Oct 21
I've added 'Windows 7 Power Users' as a target groups.
Here is a short quote from the conclusion of the post
Oct 16 2017
Hi Nate, do you have any suggestions to add to this RR?
Any suggestions how to proceed with this?
Thanks for committing, Nate.
Oct 15 2017
Rebase, run _update_all_files.sh and fix outdated desktop files
Oct 14 2017
@ltoscano, can we commit this?
Oct 3 2017
I think good and stable bindings to Python (see e.g. https://phabricator.kde.org/D7736) can help to attract new contributors. Python is often used in educational contexts. It can be used for quick prototyping, could be used to write small productivity tools with Python/Qt on top of KFrameworks or extending existing applications like Kate with Python-based plugins. This could serve as a low level entry to get familiar with Qt and KDE related technologies.
There are people of _all_ ages (elder people even more than younger ones) who care about privacy and know that it has implications on our democratic society. Or want to use their old computer hardware as long as it breaks. In my experience, teaching the mere existence and values of GNU/Linux/KDE software can be an eye-opener. Possible additional target groups: elder people, teachers, environmental protection groups.
Is this goal also include undergraduate schools or should this be a separate goal?
Sep 23 2017
Aug 8 2017
Aug 5 2017
Aug 4 2017
- add FSearch and AngrySearch to search tools
- Add new grouping "screenrecorder" with Peek and Simples Screen Recorder
- Add new grouping "mouse-tools"
- Add new grouping "font-tools"
- Add new grouping "language-dictionary"
- In KInfoCenter the "Module Help" button seems to be broken. E.g. "Help" on the Memory KCM starts the Help Center at the correct location but the corresponding "Module Help" button in KInfoCenter opens a Help Center page titled with "Documentation not Found".
Aug 3 2017
- remove obsolete KCOREADDONS_VERSION check
Jul 30 2017
Dec 22 2016
As I wrote here (https://bugs.kde.org/show_bug.cgi?id=373668#c14) in my experience a combination of different things (only one of them being the keyboard layout) is responsible for wrong password entry. I believe novice users would be happy if they were given detailed hints what might be wrong (especially when they are at the login screen where it is currently not possible to run a web search to get help). From this point of view, having this RFC implemented would be step in the right direction.