In T8693#157223, @raddison wrote:You also tend to formulate your words in an accusatory and inflammatory way that puts people on the defensive.
I intend no harm. Lower your shields :)
- Queries
- All Stories
- Search
- Advanced Search
Feed Advanced Search
Advanced Search
Advanced Search
Aug 28 2018
Aug 28 2018
Aug 27 2018
Aug 27 2018
Ok. In that case the new bug with the single commit fix for solid can stand as the new tracker for this. :)
Ah, the history is coming back to me now. :)
I will mark the original bug as invalid anyway.
In T9525#157248, @ngraham wrote:It's a little different.
It's a little different. There were two attempts to fix the issue. T8471 requested that the first one (which didn't work) be backported. Since it didn't work, I closed the task. Later an actual fix for the issue was made, that we have all verified actually works. :) This is https://cgit.kde.org/solid.git/commit/?id=122a6cd8989a4bd3096fddea908a1c2b223be62a
In T9525#157245, @rikmills wrote:@ngraham So this is not the same as?
@ngraham So this is not the same as?
In T9525#157242, @ngraham wrote:Gotcha, thanks. One reason why I prefer Phab is that I can never find the right component on Launchpad. I am not able to find the Launchpad page corresponding to the KDE Solid Framework package. Where should I file it?
Gotcha, thanks. One reason why I prefer Phab is that I can never find the right component on Launchpad. I am not able to find the Launchpad page corresponding to the KDE Solid Framework package. Where should I file it?
Yup. I don't mind taking things from Phab tasks, but the SRU team needs a bug report. 😉
Ah OK, is that the correct procedure for this?
Please file a bug report in Launchpad and fill out the SRU bug template, and I'll be happy to hustle this through.
You also tend to formulate your words in an accusatory and inflammatory way that puts people on the defensive.
raddison added a comment to T8381: Let's improve the look 'n feel of the installer and use more meaningful visuals and wording.
I have translated the Neon slideshow so I'm pretty sure the text is not incorporated into images. Anyway, making the text translatable is a necessity IMO. Non-English users will not be impressed by a partially translated installer.
Aug 21 2018
Aug 21 2018
ngraham updated the task description for T9466: Get Global Menu support for all apps working out of the box in Cosmic.
Aug 19 2018
Aug 19 2018
After this year's Akademy I got motivation once more to work on this. I'll try to do a test Pootle server and keep track of the task here: https://phabricator.kde.org/T3650
Aug 17 2018
Aug 17 2018
kubuntu-settings (1:18.04ubuntu12) cosmic; urgency=medium
- Remove our custom default kwinrc so new installations and newly created users have 'present windows' effect hot corner in top left once more.
Closing per Rick above.
Should this be closed?
Aug 8 2018
Aug 8 2018
Do your other rewrites in another task, please. Let's leave this task for this specific string, and not clutter it unnecessarily.
Aug 7 2018
Aug 7 2018
ngraham added a comment to T8381: Let's improve the look 'n feel of the installer and use more meaningful visuals and wording.
Indeed, we need the text to remain text, rather than be being embedded into images. Not only would that break the translation workflow, it would make changing anything (including translations) an order of magnitude harder.
oysteins added a comment to T8381: Let's improve the look 'n feel of the installer and use more meaningful visuals and wording.
In T8381#153813, @raddison wrote:@ngraham Would you favor an all-image slide show, where text is incorporated into images (kinda like what Neon does)?
it must be frustrating for you too since you don't manage to get anything done.
Absolutely.
Surely there are more fun or productive things you could be doing with your time.
Correct.
No, I truly do not know what you mean. Apport is just a simple crash reporter tool. It discloses everything it will submit. It doesn't send any user data anywhere without the user's explicit consent. It's also disabled on LTS releases already. I'm not sure what problem you're trying to solve.
Lol, Nate, you know what I mean. I had to formulate it somehow :)
And I'd like to know what makes you call apport "snoopware". :)
In T8693#153830, @ngraham wrote:What snoopware?
@oysteins Let us collaborate. Please post the text from all instances right here and I'll try to re-write it in English.
What snoopware?
Actionable path: purge all snoopware out of Kubuntu.
raddison renamed T8693: Make Kubuntu Compliant with KDE's Privacy Policies from Document ubuntu-report, apport, popularity-contest, whoopsie, kerneloops, etc. properly to Make Kubuntu Compliant with KDE's Privacy Policies.
raddison added a comment to T8381: Let's improve the look 'n feel of the installer and use more meaningful visuals and wording.
In T8381#153814, @mparillo wrote:Would that make translations more difficult? That is, instead of merely substituting text, images need to be re-created?
mparillo added a comment to T8381: Let's improve the look 'n feel of the installer and use more meaningful visuals and wording.
Would that make translations more difficult? That is, instead of merely substituting text, images need to be re-created?
raddison added a comment to T8381: Let's improve the look 'n feel of the installer and use more meaningful visuals and wording.
@ngraham Would you favor an all-image slide show, where text is incorporated into images (kinda like what Neon does)?
In T9303#153597, @oysteins wrote:Raddison, please read the description again, and you'll see that I proposed to fix the full stop. And while I agree that other texts could benefit from polish, may I suggest that you submit that in a new task; this one is merely about these two sentences.
Aug 4 2018
Aug 4 2018
Raddison, please read the description again, and you'll see that I proposed to fix the full stop. And while I agree that other texts could benefit from polish, may I suggest that you submit that in a new task; this one is merely about these two sentences.
No space after full stop. Signing out :(
I'll look into it as soon as I get a moment.
It should all be re-written from scratch. It's way too verbose and contentwize meaningless. 16.04 actually makes some sense but 18.04 is awful. No offence intended but that's the obvious truth.
Aug 2 2018
Aug 2 2018
ach added a comment to T8378: By default, no app should minimize to the system tray instead of quitting.
Let's try to define what we^W I are trying to define:
michaeltunnell added a comment to T8378: By default, no app should minimize to the system tray instead of quitting.
Steam, Discord, Spotify, many Email Clients, many torrent clients, VPN clients, Twitter Clients, and many more close to the system tray as a default function.
Aug 1 2018
Aug 1 2018
raddison added a comment to T7979: Use kicker by default for Application Launcher : Wait until 18.10; re-test.
That wasn't my intention in the slightest but I'll still take your advice.
It should have been obvious as soon as the defaults were changed. That way upstream could have been engaged earlier or the altering couldn't have been delayed. It was an unfortunate happening. All I'm saying is that maybe we can learn something from it. Lol, I'm not blaming anyone. It was OUR failure.
ngraham added a comment to T7979: Use kicker by default for Application Launcher : Wait until 18.10; re-test.
You stated it in a rude and insulting manner, and you suggested that Kubuntu contributors may have hidden impure motivations. That's unacceptable behavior.
raddison added a comment to T7979: Use kicker by default for Application Launcher : Wait until 18.10; re-test.
Oh, c'mon! Let's not blow it out of proportions. I just stated my opinion.
Nobody knew about the upstream bug until we were actually using the new setting. That's how bugs get found.
It was a upstream bug indeed. Which should have been sorted out before and not after altering the defaults. So the order was all wrong.
It's an upstream bug, and it would have to be fixed there anyway. In fact, the fact that Slight RGB font hinting is not the default setting upstream is itself a bug, so once upstream fixed that bug, Kubuntu would have experienced the issue in question anyway regardless of whether or not we made this change ourselves.
A good example of why you should be cautious when changing upstream settings.
I trust that whatever you choose, it'll work for anyone *who knows* how the desktop works so +1 from me. Still, this task lacks any logical or methodological framework.
ngraham added a comment to T7979: Use kicker by default for Application Launcher : Wait until 18.10; re-test.
On the subject of Kickoff vs Kicker, it goes far beyond the (legitimate and important) desire to be friendly to new users and not-very-technically-proficient users. Rather, Kickoff suffers significant usability problems and productivity reducers for expert users like us, too. The most prominent of them is the agonizingly slow Applications tab, which has no "All Apps" view and requires a large amount of precision mousing to navigate between the categories.
ngraham added a comment to T7979: Use kicker by default for Application Launcher : Wait until 18.10; re-test.
That's not constructive, @raddison. If divergence from upstream defaults is inappropriate, then we wouldn't really have distros at all. We're all trying to make Kubuntu better. If you'd rather argue than do that, you're welcome to go do it somewhere else. If you'd like to stick around, please avoid impugning other people's motivations and using charged language ("just a a front-end for propaganda"). Thanks.
raddison added a comment to T7979: Use kicker by default for Application Launcher : Wait until 18.10; re-test.
Whatever you like, but I can't shake the feeling that you're pushing your own agenda, instead of the wider community's. You're also implying that the user base is not very smart. I don't know who on earth coined this "new user" concept that is void of any real significance and it's just a a front-end for propaganda. The user is expected to learn how the desktop works and all these deviations from upstream defaults are not very smart. This is not addressed to anyone in particular. Changing some defaults won't make Kubuntu any better.
Jul 31 2018
Jul 31 2018
I think it would also be beneficial for Kubuntu to consult KDE's policies on data collection and telemetry. https://community.kde.org/Policies/Telemetry_Policy and find out whether Kubuntu is compliant with those.
Jul 24 2018
Jul 24 2018
Any news?
:)
Jul 20 2018
Jul 20 2018
Your choice, and if we do, then fractional-scale-factor-hi-dpi users of Kate and KDevelop on Bionic will be happy!
Well, if the commit works, I don't see any reason why we can't cherry-pick it.
It is a problem for 5.9 (confirmed), but I thought it best not to unnecessarily mess with the LTS release.
KCI and other experimental PPAs is the only place we had 5.10, and then only as then only as the 5.11 debian packaging for 5.11 did not exist at the time. All that can update to 5.11 when it's ready.
tsimonq2 triaged T9244: Backport fix for https://bugreports.qt.io/browse/QTBUG-66036 as Wishlist priority.
we should consider cherry-picking the fix into our Qt 5.10 and 5.11 branches
Jul 19 2018
Jul 19 2018
rikmills updated the task description for T9199: Update not-installed to format suported by dh_missing.
You don't have to ask the majority to determine a good default. That's the job of a good UX designer, using the skill of empathy.
rikmills updated the task description for T9199: Update not-installed to format suported by dh_missing.
Jul 18 2018
Jul 18 2018
The whole point of good defaults is that they should work well for the majority of people and use cases without needing to be changed.