Would it make sense to have this sprint as part of the BoFs and Workshops week at Akademy? Or maybe we can have a smaller session as a prep-event for the actual sprint.

BTW, Akademy is nearing, registration is open. Could we send a mail to all (!) contributors who have a KDE commit account? I think this does make a lot of sense to trigger everyone (especially new contributors) to come to this event.

Here are my 2 cents.

Another website like that is https://whatcanidoformozilla.org

One of nice example I found earlier : https://howcanihelpubuntutouch.io/

Perhaps it could also pull Junior Jobs from Bugzilla? It’s a good idea, having it readily (and semi-permanently) available. I don’t know if we could get it done in time for Plasma 5.13 (assuming the idea is approved).

We can choose any topic from the sub-tasks listed on the overarching Onboarding Goal task. I will be adding some more sub-tasks there in the following days (like improving documentation, gathering feedback etc). Feel free to leave a comment there if you came up with anything that needs to be tackled and is not mentioned already.

Definitely possible. Having never planned or attended a sprint before, I'm completely unqualified to organize one. I was just proposing things that seemed like they needed urgent fixing.

In T8621#140403, @ngraham wrote:

Maybe we need two sprints? One for Usability and one for Productivity? The thing is, they're inter-related. All the KCM porting work you guys did at the plasma sprint was more codey than designey, but definitely improved usability.

The Usability & Productivity initiative isn't just about design and user interfaces; that's only the "Usability" part. "Productivity" definitely includes efficiently accessing, saving, and streaming files from remote locations--particularly Samba shares, which are ubiquitous in the business and professional worlds. This is a major pain point that I hear about over and over and over again from our users, and experience myself.

I'm a bit confused as to the intention of this sprint. The people commenting on T6831 this is a sprint for are all designers and usability people. This list of goals is effectively an extreme very low-level KIO bug sprint.

It's usually pretty hard unfortunately :/

Any chance these could be streamed or recorded for those who can’t attend? Or is a sprint too chaotic to capture effectively?

Under the subheading of "Documentation", can we discuss code commenting? And ideally - encourage it? The API docs are good and generally well-maintained, but inside the applications themselves, the quantity and quality of code comments varies quite a bit. Some of our products are quite large and use many of the Frameworks together. It can be daunting at times to decipher how a block of code works and why it was constructed in the way it was.

In T6832#136906, @neofytosk wrote:

And more about bugzilla's usefulness here:
https://mail.kde.org/pipermail/kde-community/2018q1/004274.html

Maybe it's worth to add to the describtion of this task:

Vault uses FUSE, no block-level for the time being. I was toying with Tomb and preallocated fixed-size containers in the filsystem which uses Luks in the back, but I'm not sure it can be made to work properly.

In T8447#136980, @dvratil wrote:

@gregormi This is only partially related. We already have an option how to automatically decrypt all incoming emails in KMail, although it's not very intuitive to set up. You can create a local filter (Settings -> Configure filters) for all incoming emails and choose the "Decrypt" action. The reason it's not done by default is due to privacy concerns. For example you may want to keep your personal emails always encrypted on your employer's computer so they can't read your private emails.

@ivan: tanx for the input

Vault does not support public-private key encryption - it is out of the project's scope. And it would be quite strange for the user to see items like "KMail Index for ABCDEFGH01234... key" in the list of existing vaults. :)

@gregormi also think about the privacy impact. If you use an unsecured laptop, the mails can be accessed without any password etc. Also when you use IMAP the unencrypted mails would saved back to your mailserver and would be accessible there. It might be usescases for that. But I think the propper way is to make sure, that we can handle the encrypted mails all the way down without removing the encryption.

@gregormi This is only partially related. We already have an option how to automatically decrypt all incoming emails in KMail, although it's not very intuitive to set up. You can create a local filter (Settings -> Configure filters) for all incoming emails and choose the "Decrypt" action. The reason it's not done by default is due to privacy concerns. For example you may want to keep your personal emails always encrypted on your employer's computer so they can't read your private emails.

I have a question to that because I encountered this issue years ago when I used Thunderbird with Enigmail. I assume the indexing we are talking about here takes place in the local mail client, not in a web client, right? I wonder why incoming encrypted mails are also stored encrypted? Why not always decrypt those mails permanently? This would prevent losing old mail because of lost private key and there would be no problem with indexing. In this Enigmail bug report (https://sourceforge.net/p/enigmail/bugs/1/) from 2003 this request was made. The main reason for not implementing it is a technical one ("this feature is blocked by necessary Thunderbird changes") not fundamental ones. I thought the goal of end-to-end encryption is protect the data when it is underway and not also on the end-points themselves. Are there any reasons why KDE PIM does not decrypt incoming encrypted mail permanently? (or is there already and option to do that? Then sorry for the fuzz)

Related to T7014

In regard to UNCOFIRMED/CONFIRMED status, there's a relevant discussion here:
https://mail.kde.org/pipermail/kde-community/2018q1/004395.html
And more about bugzilla's usefulness here:
https://mail.kde.org/pipermail/kde-community/2018q1/004274.html

It should be added to the kdepim workboard

In T7116#134920, @richardbowen wrote:

What do you think about a dedicated stack for web development? As there is C++, Qt/QML for the desktop, like wise a dedicated/preferred programming language(s) and framework can be chosen for the web. This would help in onboarding contributors to the web side of things and potentially make management of the web stack easier for both the developers and the system admins.

What do you think about a dedicated stack for web development? As there is C++, Qt/QML for the desktop, like wise a dedicated/preferred programming language(s) and framework can be chosen for the web. This would help in onboarding contributors to the web side of things and potentially make management of the web stack easier for both the developers and the system admins.

@ngraham ok i did open new bug report : https://bugs.kde.org/show_bug.cgi?id=392339
i hope you will add list this in "Top-notch usability and productivity for basic software" thank you

@manuelmuzzurru, the best place for that kind of request is in the form of a Bugzilla ticket for frameworks-kio.

hi, did you see my comment for filesystem in dolphin (panel information)?

As a newcomer and junior-jobs guy, I'm happy to see this initiative being pushed forward by the Top People(tm) of the KDE organization. I've been stumbling my way through a few patches with the help of @rkflx and @ngraham, the latter of which agreed to mentor me in the ways of KDE. Henrik has been patient with me as I learn C++ and has given me a few assignments for Spectacle bugfixing. Nate has been a good guide to the environment and community. I'm sure there are many more like these two out there. Busy people, but willing to share their knowledge and expertise.

On thing we could use is an official policy regarding whether the stable or master branch is more appropriate for any given patch. Right now it's often not clear for edge cases such as D10651: Fix thumbnail hover icon show-in-fullscreen action. In that patch, a bug was fixed that led to a behavior change. Stable or master? We committed to master to be safe, but it wasn't as clear as we would have preferred.

hi, i wish to ask you:

Recently, I tried to find out KDE best practices to work with Docbook.

I really like UHD's explanatory text above the login box. We should implement that, with some short documentation and a link pointing to identity.kde.org. Who has the power to do this? KDE Sysadmins?

In T7646#127445, @ngraham wrote:

Out of curiosity, what are our criteria for considering this task done?

Well, I reply to myself as I got the following notification just after making the post above :
https://phabricator.kde.org/D10461
gmenu-dbusmenu-proxy
"This application finds windows using GTK GMenu DBus interfaces [1] and forwards them through DBusMenu. This way no adjustments in Plasma are needed."

Hi ! I wonder whether this one would fit in the KDE usability list : global menus don't work with GTK apps, cf :
https://github.com/kotelnik/plasma-applet-active-window-control/issues/78

I have updated https://community.kde.org/Get_Involved#Getting_in_touch_and_working_together and https://community.kde.org/Infrastructure/Phabricator#Logging_in, and included a picture highlighting the login button.

Hi everyone, I feel bad for being quiet over the last couple of weeks. Lots of changes happening in Jan-Feb for me, and also FOSDEM and the KDE Promo sprint are coming up. I'll try to push this goal forward in a consistent way once all these have passed.

@mmustac this is done now!

@ngraham Great to hear that. I will be one of the first to test your explanations if they are also ready for noobs like me :-D And provide my feedback of course.

Yes, it will be a redirect to https://community.kde.org/Get_Involved

Is it going to be a redirect to the existing pages? The example of page shown is a bit too much developer-oriented compared to https://community.kde.org/Get_Involved

@mmustac Yup, I've proposed that and already gotten buy-in and permission to do it. Just working on getting my access to change the page.

What about editing the "Get involved" page on kde.org as first step?
I am missing an up2date step by step guide to get a working development environment.
Because I really would like to get started.

FWIW, I updated https://community.kde.org/Get_Involved#Getting_in_touch_and_working_together with a more clear and concise description of how to sign up and log into Phabricator.

In T6831#124835, @IlyaBizyaev wrote:

The recently introduced KWallet support in VLC is cool; can it also be implemented for Firefox? When a master password is set, Firefox asks for it on every launch, which for me is usually just after unlocking my Wi-Fi passwords with KWallet. If Firefox could make use of KWallet (like Chrome and Opera do), it'd be one password prompt less on every device boot :)

The recently introduced KWallet support in VLC is cool; can it also be implemented for Firefox? When a master password is set, Firefox asks for it on every launch, which for me is usually just after unlocking my Wi-Fi passwords with KWallet. If Firefox could make use of KWallet (like Chrome and Opera do), it'd be one password prompt less on every device boot :)

It would be awesome if we could have a page like https://whatcanidoformozilla.org/#!/progornoprog/advocate

In T7116#123722, @dhaumann wrote:

I think we could obtain the relevant list of contributors from the sysadmins: all accounts that were created since last Akademy.

I would like to add another todo item to the list: All new contributors (e.g. the ones who committed a patch for the first time within the last year) should get a personal email, asking them to please attend the KDE conference. I think Akademy is an integral part of holding people together. As such, we need to push those a bit who are unsure (I was in this situation myself in 2004).

For now I added some information at https://community.kde.org/Get_Involved#Ways_to_contribute

SO, being very much green I wanted to ask you or anyone where/who I would go to for website edits. After some searching, I quickly found the webpage is wiki style. Because of how crazy it has been, I had to ask in the irc how to get to the registration link again so I can submit sample language and placement on community.kde.org. Wouldn't you know, valorie and I started talking about the issue, and bingo, she agreed to put changes to page as suggested. I also pitched for the auto-forward link like mozilla. Pretty cool! This is my first contribution...and it was surprising to see how easy and simple it was. Thanks again for the support and encouragement.

Find below the merged version of previous comments, as requested.