[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [frameworks-kio] [Bug 384561] Dolphin copy operation is 4,5x slower than cp
From:       Nate Graham <bugzilla_noreply () kde ! org>
Date:       2018-01-21 20:36:05
Message-ID: bug-384561-17878-Rz3gwxaD8D () http ! bugs ! kde ! org/
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=384561

--- Comment #16 from Nate Graham <pointedstick@zoho.com> ---
Yes, unifying duplicates is a big job. I've done a lot of bug screening in my
time, in Bugzilla as well as others, and I doubt hunting for duplicates can be
done by anyone other than a human being.

In general, KDE suffers from a lack of what you might call corporate
professionalism: we don't have many paid programmers or any paid bug screeners;
we don't have project managers to keep projects on task; we don't categorize
bugs based on priority; etc. There are certain projects like Plasmashell that
are run closer to this model, but a lot of KDE is run like a volunteer
organization because, well, that's what it is!

My personal opinion is that a bit more discipline would really help us, if we
can apply it without making the project un-fun to work on, which would defeat
the purpose by repelling volunteers. That's mostly a cultural matter--getting
people to screen bugs for projects they work on and use the Priority field--but
I think having at least one overall release manager would be hugely beneficial,
as that person would have a high level overview of the whole community and
could help keep things on track, which ultimately increases the quality of our
products and generates more excitement and volunteer contribution.

-- 
You are receiving this mail because:
You are watching all bug changes.=
[prev in list] [next in list] [prev in thread] [next in thread]