Meeting was quite productive, we had some overall discussion and have
some action items as follows:
Short term:
Add key in knsrc files to let content get marked as dangerous so
that we can show a different warning in the dialog (d_ed)
This will be done immediately and backported
The topic of store content has come up repeatedly throughout last
year. It's clear what we're showing to users now doesn't meet modern
expectations and our messaging is not the clearest. It's in the
spotlight currently, we can use that energy to do something
productive.
Lets discuss this in a
Plasma 5.27 is not getting any more regular timed releases. However in
the past for LTS releases we have said that we would just make them
on-demand if there's enough stuff.
I've seen enough patches over the last month that warrant putting into
5.27 with people not cherry-picking some major fixes
I don't want to set a precedent for many others.
I would have rejected this if the MR was only just opened, or if this
wasn't a KCM section that's specifically titled "Advanced settings" or
we were having this discussion later.
But given it closes some bugs, I think it's reasonable to go ahead.
> If folks agree, I can do that.
Do it, but given it's an cross-repo change lets do it after alpha
rather than rushing.
David
We can definitely ship the files. We used to.
I'm surprised we need to ship the stock "kde" file, in theory it
should roll back to a stock file. As per the docs:
> The service_name argument specifies the name of the service to
apply and will be stored as PAM_SERVICE item in the new
There is a thread at
https://invent.kde.org/plasma/plasma-desktop/-/issues/112 with a
proposed change in the planned version numbers of 6.
If any distro people want to weigh in on that thread about whether
it's better or worse or neither that would be appreciated.
David
I would be strongly opposed to having it somewhere the user hasn't
explicitly opened, like the first-run wizard. It's more important that
we come across as a product that's on par with a commercial offering
than raise the extra cash.
Having a set of names appear when you click the donate button
On Mon, Sep 18, 2023 at 5:45 AM Neal Gompa wrote:
me of them, I've got ideas, others less so.
>
> The first thing that came up was that KiCad seems to need help and has
> had a bad experience interfacing with some folks over resolving their
> issues moving into a Wayland world.
Given I'm quoted,
in February
Due to the delay of KDE Gear by an additional patch release of 23.08
will be made.
David Edmundson
As a reminder this meeting is tonight in 3 hours.
David
That was true, we need to research and see if it's still true.
Gnome have dropped their cap_sys_nice.
For setting nice we many options:
- kwin_wayland_wrapper can be cap_sys_nice set it the nice a child
PID (needs verifying)
- maybe the systemd cgroup settings for priority are as good/better
-
Video call at https://meet.kde.org/b/ada-mi8-aem
A time has been chosen on the poll with a clear winner:
4th September 18:00 CEST
See you all there
David Edmundson
h multiple rounds of
elimination.
Open discussion ahead of time is available at:
https://invent.kde.org/teams/frameworks-devs/kf6-workboard/-/issues/55
David Edmundson
For kwayland I would suggest to keep it in it's own repo kept being
called kwayland
Dialog is in Plasma-framework which is moving to workspace anyway. I'm
not sure of the status of that move is.
I would put suggest putting D stuff in plasma-framework (or whatever
it ends up being called)
b) merge it into the gamepad-kcm repo itself
I would suggest doing this. It'll be easiest for future gamepad-kcm
devs to find than any other repo, and means it'll be obvious if it
ever becomes obsoleted.
David
We've discussed a few times an issue with plasma-integration and
supporting Qt5 and Qt6 clients.
When we release Plasma 6, we need to ensure that a Qt5 and Qt6 builds
are released. We need users to have both as they are plugins where
users might have Qt5 and Qt6 codebases.
Right now master
On Sun, May 21, 2023 at 9:47 AM Laurent Montel wrote:
>
> Hi,
> I use plasma6/kf6 more than 1 week.
> But I found a bug:
> - apps is not restoring
> - autostart apps is not started.
Those two are quite possibly related.
I would double check your dbus activation stuff is working correctly,
then
I'm not very happy accepting that MR. It's not that minimal.
>so that we have adequate metadata set for the following Plasma
version.
Can we backport just:
```configGeneral.writeEntry("LastSeenVersion", "5.27");```
?
The rest is not needed on the first release from my understanding?
On Tue, Jan 10, 2023 at 4:48 AM Fusion Future wrote:
>
> Is it possible to make Hebrew/Jewish calendar available in Plasma 5.27?
> The code is largely borrowed from the Indian calendar backend so the
> actual change is small.
>
> https://invent.kde.org/plasma/kdeplasma-addons/-/merge_requests/313
if anything is slightly controversial or exceptions are needed.
If there are any major things stuck in review, please respond to this
email and make a fuss so they can be prioritised.
David Edmundson
https://community.kde.org/Schedules/Plasma_5
- https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/1131
That's a tiny change so it's fine.
- https://invent.kde.org/plasma/kinfocenter/-/merge_requests/111:
Whilst slightly bigger. It is fully encapsulated and there's no risk
of this causing regressions elsewhere.
For that reason
My two big concerns moving forward are:
- Making sure tests are stable and reproducible. This is a problem
with any test framework used, we need tests to be reproducible locally
on everyone's machine and on some random packaging server. As soon as
we start checking kickoff opens "dolphin" as a
Scripted and pushed.
Lets take discussion about individual repos to the relevant MRs.
https://invent.kde.org/plasma/kwin/-/merge_requests/2327 only has some
nits left.
I'm happy to say we can land that as long as it goes in by the end of tomorrow
As a reminder it is the soft feature freeze tomorrow 05/05/2022
Any massive refactors, new repos and big changes that have potential
fallout should land by the end of the day.
It is not a hard feature freeze, small features can still be added
that goes right up until the day of the beta 19th of
>let's go for it at least p-w and plasma-integration and slowly aim for
>everywhere
plasma-integration is an example where the tests have failed since
November **2020**! without anyone following up.
Fixed that one now:
https://invent.kde.org/plasma/plasma-integration/-/merge_requests/43
Though
There's a new flag we can set on CI to fail a job if unit tests fail.
https://www.volkerkrause.eu/2022/04/09/kde-ci-required-unit-tests.html
Catching things as early as possible will unquestionably be a good thing.
Realistically right now this is going to cause some merge failures as
we know
>Please checkout new attached proposal
The list of KCMs is ambitious. Everything takes twice as long as you
expect when you hit roadblocks, review comments and unexpected bugs.
Cut it down to 4 and you'll still have an effective GSOC.
A big aspect of student selection comes from experience of
I'm sure everyone is excited:
Full schedule and joining instructions available at:
https://invent.kde.org/plasma/plasma-workspace/-/issues/32
Looking forward to seeing your all
David
>(But where should the setting be saved? "~/.profile" or a config file
like "startkderc"? The latter may require modifying
If a problem is hard to solve, change the problem.
It's an environment variable because that was a good tool for the
problem it was solving at the time. But there's no
Can I suggest Plasma people attend the frameworks meeting tomorrow
afternoon. Then we can use that meeting to at least get up to speed
with the Qt6 ports and some idea of timelines.
David
The last 5.X release definitely needs to be an LTS. That's unmovable.
We can't have two active LTSs, it'd be a backporting nightmare and at
best it would be a lie to claim we're actively supporting both.
An LTS now effectively means we can't start Plasma 6 for another year.
I personally think
https://invent.kde.org/plasma/kdeplasma-addons/
applets/dict
Done: https://doodle.com/poll/s4ycfqwhua99a7h6?utm_source=poll_medium=link
Please fill in. Ignore the date, assume it's for every Monday.
Does it appear instantly when you press the third letter?
Does searching for "do" (for dolphin) work correctly?
If so, I have a suspicion on what's happening.
> I'm firmly confident it's entirely possible to match a substring in under 8ms
> and react to the Enter key in time. Remember: you
How?
We want the wallpaper because it looks nicer.
What you're seeing is the result of kwin keeping the visuals of the
window alive after plasmashell has closed. Kwin can't know to remove
containments from that.
David
Not for the part in question.
See
https://github.com/KDE/plasma-nm/blob/v5.20.5/applet/contents/ui/PopupDialog.qml#L63
We have seen similar bugs in the past which have been fixed by porting
the ScrollView to PlasmaComponents3 instead of PC2.
David
Just to clarify all of this:
>From now on 5.23 branch is forked.
Master is open to any new changes, new features and new strings and
can depend on new frameworks.
The 5.23 branch is open to bug fixes only, but doing these bugfixes is
actively encouraged!
They should be committed on master and
>Once again apologies for this mess.
It's ok. I know you're doing it to move plasma mobile forward. I
should have looked at that review when you had first asked, so that's
on me too.
Glad we have a plan that works for us all.
The QML port is otherwise really quite good, I'm happy to take care
And I had mentioned this in the review weeks ago, so this is not a surprise.
Just did some last-minute forced QA.
- The title is in lowercase
- After selecting an entry to change:
- the margins are wrong
- there's no title for what you're actually selecting
- It lists "C" as a locale,
We said in that meeting that you could ask on this thread for an
exemption (that was on the 6th).
Waiting until literally the release day and then asking for the
exemption and then merging within minutes of each other is absolutely
not ok!
David
On Thu, Sep 9, 2021 at 4:41 PM Nate Graham wrote:
>
> I would recommend considering the following releases active:
>
> - Current released Plasma release + all of its bugfix releases
> - Previous Plasma release (last bugfix version only)
> - Latest LTS Plasma release (last bugfix version only)
>
>
Excellent news!! Thanks very much
> Once the scripts have been proven successfully for Frameworks, we will look
> at extending them to projects that depend only on Frameworks and repositories
Does this mean we would like Plasma to wait a while before merging?
Is it worth us creating the kde-cli
I don't think the KConfigXT stuff is worth rushing.
>
> Integrate plasma-pa KCM "Advanced" options in the main page
> - https://invent.kde.org/plasma/plasma-pa/-/merge_requests/71
>
Ack, it's been on review for ages, we should do something more useful with that.
Consider it as having an
On Tue, Aug 31, 2021 at 5:04 PM Nate Graham wrote:
>
> Here are some big ones that need review:
>
> Port Keyboard KCM to KConfigXT. We seems to have two MRs for this?!
> - https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/453
> -
CC'ing BSD people as only BSD is affected.
https://build.kde.org/job/Plasma/job/libksysguard/job/kf5-qt5%20FreeBSDQt5.15/295/
I'm stumped on this, the code looks fine.
The build started failing from an SVN_SILENT translation update, so it's
probably come from an external situation.
David
Bumping this thread to say, this (a bump of plasma-wayland-protocols)
has just happened again and I imagine we have two more landing this
week.
This probably will result in broken CI for a few days, which is far
from ideal, but it's why we have our feature freeze early.
David
Soft feature freeze is nearly here.
Soft freeze takes effect on Thursday the 2nd September. After that we
are to avoid any ridiculously big changes and huge refactors.
If there are any major things stuck in review, please respond to this
email so they can be prioritised. If there are any new
This is now resolved.
We will want to bump the versions manually at some point.
>Fix KDE_COMPILERSETTINGS_LEVEL at known working version (5.84.0) and only
I think this makes the most sense, especially if combined with one of
the magic scripts we have to update all versions like we have for
frameworks version currently.
David
> are we sure that this is an upstream QT issue?
It's where I would bet on. But lets not rule anything out.
Does this also happen for the context menu on the desktop as well as
folder icons?
Can you add a debug of m_menuPosition just before menu->popup in
plasma-desktop foldermodel.cpp
If
We have an open MR that wants to break the API of kscreenlocker greet:
https://invent.kde.org/plasma/kscreenlocker/-/merge_requests/29
Effectively this would make any LNF package that shipped a custom
screenlocker to break. Currently the proposal just breaks, but I think
we can make it fall back
It is unfortunate. It has been noticed and discussed, but I think
everyone just expected someone else to do it.
>and there were 3 releases from 5.22 already.
Yeah, that's from ideal!
> So I wonder how this can be made part of the release process to
make sure we have CI coverage for Plasma's
We discussed this some more, and we are not in favour of moving
forwards for Fedora:
Reasons given were:
- It either cuts into our beta period, or causes us issues with
framework releases.
- Fedora has regular releases anyway
- It collides with the promo plans above
- .0 releases tend to not
https://bugs.kde.org/show_bug.cgi?id=350365
David Edmundson changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
I have booked all Friday morning for a super fun activity.
Group bug triage!
It'll be more fun than it sounds. Albeit that is quite a low bar to beat :)
David
> though would be two different mainfiles in the package depending if
> it's loaded as containment or as an applet?
Yes. Either potentially we can use the "X-Plasma-MainScript" property
in the metadata , or worst case we install as two packages and they
both pull in the same private library.
>
On Thu, May 13, 2021 at 4:52 PM Marco Martin wrote:
>
> Hi all,
> Since KF6 work is starting, I've been thinkig a lot how i would like
> plasma to be refatored, since now there may be a window of doing some
> incompatible changes.
> Here is a write down of this, wall of text ahead, I *hope* i
On Mon, May 3, 2021 at 11:05 AM Bhushan Shah wrote:
>
> On Thursday, 29 April, 2021 4:40:35 PM IST David Edmundson wrote:
> > At the end of the day is the soft freeze for Plasma 5.22, with the
> > beta out on the 13th of May.
> >
> > After this point we should av
>Shall we go ahead with
https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/560 or
We have this freeze to give ourselves a target and make sure we don't
have people merging in a whole new KCM rewrite or doing something
controversial. Hard feature freeze is still at the beta.
This is
At the end of the day is the soft freeze for Plasma 5.22, with the
beta out on the 13th of May.
After this point we should avoid any huge refactors and big features
until we split the branch.
Small features and changes can still land, we just now start to be
cautious so things can get an
> It seems these days the only real user of plasma-frameworks & krunner
> libraries is the Plasma shell itself, with other applications only providing
> plugins/extensions and only targeting Plasma again.
That is mostly in line with other discussions in plasma. There is a
ticket splitting
On Mon, Apr 12, 2021 at 4:21 PM Nate Graham wrote:
>
>
>
> On 4/12/21 9:15 AM, David Edmundson wrote:
> > No objections.
> >
> > Be sure to CC sysadmins before doing bulk moves.
>
> Saying what? Also what qualifies as bulk?
Please move Product blah to
No objections.
Be sure to CC sysadmins before doing bulk moves.
David
https://bugs.kde.org/show_bug.cgi?id=350365
David Edmundson changed:
What|Removed |Added
Resolution|--- |WAITINGFORINFO
Status|CONFIRMED
https://bugs.kde.org/show_bug.cgi?id=350365
David Edmundson changed:
What|Removed |Added
CC||k...@davidedmundson.co.uk
--- Comment #57
Nicofee
As discussed I raised the min. CMake requirement for all Plasma repos
to 3.16. There was some fallout in kinfocenter and systemsettings that
has been fixed.
That prompted some cmake cleanup in KWin
https://invent.kde.org/plasma/kwin/-/merge_requests/749
I am fine with this.
> Thoughts?
If in doubt about distro requirements kde-distro-packagers is the best
mailing list.
Anything we can say will be just guessing.
David
>Ping. https://invent.kde.org/plasma/sddm-kcm/-/merge_requests/3 is ready
to merge now. Can we have that exception?
Yes, no-one objected, so go ahead.
David
I am fine with anything.
I no longer have my initial objections. Especially as it is only a few
hundred lines.
We can solve the global_remove problem too.
For now I would say let's build it inside kwayland-server as a purely
internal tool and not install the binary. It makes life easier.
David
> Noah is qqc2-breeze-style to be included? It has not yet passed kdereview.
If it has not passed kdereview we shouldn't be including it, sorry.
I believe the intended first target is plasma-mobile, so we have the
option of making separate beta tarball outside the release schedule
that could
Plasma 5.21 has a feature freeze in a few days on the 7th January.
If anything needs urgent attention from reviewers, please do reply
here ASAP so they can be prioritised.
David
One down:
https://invent.kde.org/frameworks/kirigami/-/merge_requests/200
It does. I've tried to collect some stats and provide some context on
the change.
Taking just plasma-workspace, we have a lot of lines over 100
characters at the moment.
3817 lines to be exact. ~3.3% [1]
We also have 146 lines over 160 chars. One is 383 chars long!
When the limit was 100 we had
Looks like you managed.
If you haven't managed to subscribe, you can find everything you need
at: https://mail.kde.org/mailman/listinfo/plasma-devel
David
There has been lots of work on this lately, especially by Alexander Lonhau.
Both in the clang-format file and with some custom changes, and some
changes throughout the code.
If anyone has specific objections please be sure to note any specific
concerns ASAP before plasma is updated.
David
> Ialso found KCalendarSystem is pretty
> well designed but it's in kdelibs4support and I can't found the successor.
> I also write down my thoughts here and feel free to check it out and let
> me know what you think. (
To provide some background. KCalendarSystem was what we had, whilst Qt
had
If you build kwin master from scratch stray files from old builds can
cause crashes.
We've had a few duplicate bug reports of this, so I'm sending an email.
The most important file to remove is.
$prefix/lib/qt5/plugins/org.kde.kwin.waylandbackends/KWinWaylandWaylandBackend.so
You can also safely
>
> As distribution package maintainers, we would like Plasma developers to
> slightly alter the release schedule to align releases with a more
> distribution friendly cycle. You could consider shortening one release
> cycle (and then keep the 6 month schedule) to align releases.
>
We have in the
davidedmundson added a comment.
> I wonder if we could "share" that .xml between server and client somehow..
We do in some cases. Interface headers are installed into
/usr/share/dbus-1/interfaces
Then KWinDBusInterfaceConfig.cmake.in tells other projects where these files
are
davidedmundson added a comment.
> Does it mean we now have to manually synchronize DBus API here in .xml and
on KWin side?
It does, but that's easier to do that keeping code in sync
REPOSITORY
R120 Plasma Workspace
REVISION DETAIL
https://phabricator.kde.org/D22846
To:
In a similar topic I've been pointed to a tool called qmlformat. It's
basically clang-format for QML.
It seems to work quite well. It insists on a very specific code layout :
https://doc.qt.io/qt-5/qml-codingconventions.html
id first, then newly declared properties and so on. This makes the
Jan Blackwill has bumped this in a recent MR:
https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/381
It's a bit easier to visualise the changes, but note gitlab isn't showing
all the changes. It still does better than Phabricator did last year which
just fell over completely.
>
> this seems to happen on a live usb flash drive only.. (or when booting
> the iso file in virtualbox)
> it is very easy to reproduce and it makes no sense to me at all.
>
>
This ISO on your website: https://life-edu.eu/public/life-2004-1.iso ?
David
Feedback on the "beta review day"
The day was worthwhile - we got 3 or 4 new people involved.
Mostly the day ended up being users with specific bugs that only they had,
and us using the real-time chat and having time set aside to get on with
fixing things quicker than we could have done on
On Mon, Sep 21, 2020 at 7:44 AM Lasath Fernando wrote:
> Hello There!
>
> I don't know if any of you remember me -
>
Of course!
it's been many years since I made any contributions to KDE. However, I
> would like to change that! :D
> Recently, I became the maintainer for a plasma applet called
Blog post done and published.
http://blog.davidedmundson.co.uk/blog/plasma-beta-review-day/
>
> Or will that be determined who who shows up and what they want to do? :)
>
A bit of that :)
We can certainly have a set of small regressions for when someone says "I
want to fix something", and we can try and prioritise things.
David
>
> I have some questions:
>
> - What actually happens during the review day? What do you do?
>
To be completely honest, it's slightly free-flow.
I used to run some years ago (e.g
https://community.kde.org/Get_Involved/Quality/Beta/4.10/Plasma
I'll draft a blog ready for proof reading by the meeting tomorrow.
David
On Fri, Sep 18, 2020 at 3:45 PM Kai Uwe Broulik
wrote:
> Hi,
>
>
> > Is it possible for the application to change its own "show in history"
> > setting, instead of the user going to System Settings to do this?
>
> It is not.
>
Let's back up a bit, what's the end goal we're trying to achieve for
>yet it gets built on windows. shall we stop
doing that
AFAIK it is used and this was something explicitly requested.
There is a KF6 workboard task to get into frameworks for kf6
David
davidedmundson added a comment.
But I could still just copy the relevant lines into kcmshell directly instead
of linking.
REPOSITORY
R120 Plasma Workspace
REVISION DETAIL
https://phabricator.kde.org/D23883
To: heikobecker, #plasma
Cc: davidedmundson, asturmlechner, plasma-devel, Orage,
davidedmundson added a comment.
> Any update here? Can this hack be dropped now?
I did follow up on that. A distro is still wanting to do the setup which
requires this opt-in hack.
REPOSITORY
R120 Plasma Workspace
REVISION DETAIL
https://phabricator.kde.org/D23883
To: heikobecker,
1 - 100 of 8190 matches
Mail list logo
