sprint for usability and productivity goal
Open, Needs TriagePublic

Description

Goal:

Improve I/O, network file access, and disk management, which currently need a lot of work to function adequately in a professional setting.

Here are some ideas in descending order of impact and urgency:

Topics:

Improve KIO's Samba sharing support and ability to supply access to files on Samba shares for non-KDE apps (LibreOffice, Inkscape, GIMP, etc)
This is a critical issue for increasing Plasma adoption among businesses, artists, and anyone who stores or accesses files on network locations and uses non-KDE software in Plasma.

Fix outstanding bugs in Solid framework (which controls disk management and mounting)

Finally finish up and land PolicyKit support in KIO

Improve Places Panel UX

Improve Open/Save dialog UX

Dolphin improvements and new features

General KIO file management improvements and new features

People that would like to attend:

Suggestions for place and time:

Some place in the USA would be nice :)

Other relevant things:

lydia created this task.May 1 2018, 1:51 PM
ngraham updated the task description. (Show Details)May 1 2018, 2:35 PM
ngraham updated the task description. (Show Details)May 1 2018, 4:20 PM
ngraham updated the task description. (Show Details)May 1 2018, 4:22 PM
ngraham updated the task description. (Show Details)May 1 2018, 4:52 PM
aacid added a subscriber: aacid.May 1 2018, 7:53 PM

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.

Having a KIO sprint would be great, having a visual/usability sprint would be great. Any sort of mix isn't something I can see working out.

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.

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.

bshah added a subscriber: bshah.May 2 2018, 3:23 AM

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.

I personally think that the goals and topics you have added for this sprints are too unrealistic to achieve in one sprint which could last for week or less.. It is entirely possible that just single bug mentioned in list can take a whole week for whole fix-review-fix cycle, and you would never get through some bugs without relevant developers not being present at sprint. My personal view point for sprints is, instead of Fix N bugs, you should write down a topics which needs the 1:1 discussion, for instance KDE's human interface guidelines is excellent example of topic you may want to discuss at sprint in person with other developers/designers. But not samba share bugs...

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.

Yeah, yor these Frameworks issues, it seems like what's needed is not so much 1:1 face time, but rather just more manpower.

aacid added a comment.Jun 13 2018, 9:51 PM

FWIW I may be interested in attending, i didn't add myself to the list above because I would not want to be a "voter" on the place/date but i would be interested in being notified when the place/date is chosen to see if i can join :)