Re: Plasma-nm: passing on maintainership
On 4/10/22 14:06, Jan Grulich wrote: Hi, When I joined KDE as a developer, I started as a newbie working on NetworkManager and ModemManager integration and ended up writing one of the core Plasma components. Thanks to this I gained a lot of experience, attended a few Akademy conferences and met amazing people. I'm really grateful for the experience and I consider it as an important part of my life. Unfortunately, as life goes on and new projects appear, I found that I basically have zero time to dedicate to anything related to NetworkManager/ModemManager integration in KDE and all the bugs assigned to me for these components don't get enough attention from my side. For that reason I would like to ask to update bugzilla components for *kf5-networkmanager-qt*, *kf5-modemmanager-qt* and *plasma-nm* to have plasma-devel as default assignee and find someone who can be assigned by default to all code reviews to lead these projects. I will still happily help from time to time to explain some things around plasma-nm, but I will no longer be able to actively fix bugs and develop new features. I will still be around, mostly working on things around Flatpak, PipeWire, etc. Thank you. Best regards, Jan Grulich Thanks for all the work (features and bugs alike, as you know software is always a mixed bag :D), and yes, indeed a very core component of Plasma. As Jonathan said, don't be a stranger, KDE has very good memory :) Regards, Ahmad Samir OpenPGP_signature Description: OpenPGP digital signature
Re: akademy 2022 BOF notes
So with Plasma 5.27 as an LTS that means 5.24 will be dropped as an LTS. Kubuntu and Opensuse people (and anyone else using the LTS): should we have one more release of Plasma 5.24 in say January? Jonathan
Re: Plasma-nm: passing on maintainership
Thank you for all your work on the network stack over the years! And also thank you for performing some offboarding. :) Hopefully we can find someone else to pick up the torch. Nate On 10/4/22 14:06, Jan Grulich wrote: Hi, When I joined KDE as a developer, I started as a newbie working on NetworkManager and ModemManager integration and ended up writing one of the core Plasma components. Thanks to this I gained a lot of experience, attended a few Akademy conferences and met amazing people. I'm really grateful for the experience and I consider it as an important part of my life. Unfortunately, as life goes on and new projects appear, I found that I basically have zero time to dedicate to anything related to NetworkManager/ModemManager integration in KDE and all the bugs assigned to me for these components don't get enough attention from my side. For that reason I would like to ask to update bugzilla components for *kf5-networkmanager-qt*, *kf5-modemmanager-qt* and *plasma-nm* to have plasma-devel as default assignee and find someone who can be assigned by default to all code reviews to lead these projects. I will still happily help from time to time to explain some things around plasma-nm, but I will no longer be able to actively fix bugs and develop new features. I will still be around, mostly working on things around Flatpak, PipeWire, etc. Thank you. Best regards, Jan Grulich
Re: Plasma-nm: passing on maintainership
Many thanks for your important work over the years. I've updated those 3 products in bugzilla to default to plasma-bugs@. Don't be a stranger, Akademy in Greece next year will be sunny. Does anyone on this list have an interest in taking on Plasma-nm bugs? Jonathan On Tue, 4 Oct 2022 at 13:06, Jan Grulich wrote: > Hi, > > When I joined KDE as a developer, I started as a newbie working on > NetworkManager and ModemManager integration and ended up writing one of the > core Plasma components. Thanks to this I gained a lot of experience, > attended a few Akademy conferences and met amazing people. I'm really > grateful for the experience and I consider it as an important part of > my life. Unfortunately, as life goes on and new projects appear, I found > that I basically have zero time to dedicate to anything related to > NetworkManager/ModemManager integration in KDE and all the bugs assigned to > me for these components don't get enough attention from my side. > > For that reason I would like to ask to update bugzilla components for > *kf5-networkmanager-qt*, *kf5-modemmanager-qt* and *plasma-nm* to have > plasma-devel as default assignee and find someone who can be assigned by > default to all code reviews to lead these projects. I will still happily > help from time to time to explain some things around plasma-nm, but I will > no longer be able to actively fix bugs and develop new features. > > I will still be around, mostly working on things around Flatpak, PipeWire, > etc. > > Thank you. > > Best regards, > Jan Grulich > >
Plasma-nm: passing on maintainership
Hi, When I joined KDE as a developer, I started as a newbie working on NetworkManager and ModemManager integration and ended up writing one of the core Plasma components. Thanks to this I gained a lot of experience, attended a few Akademy conferences and met amazing people. I'm really grateful for the experience and I consider it as an important part of my life. Unfortunately, as life goes on and new projects appear, I found that I basically have zero time to dedicate to anything related to NetworkManager/ModemManager integration in KDE and all the bugs assigned to me for these components don't get enough attention from my side. For that reason I would like to ask to update bugzilla components for *kf5-networkmanager-qt*, *kf5-modemmanager-qt* and *plasma-nm* to have plasma-devel as default assignee and find someone who can be assigned by default to all code reviews to lead these projects. I will still happily help from time to time to explain some things around plasma-nm, but I will no longer be able to actively fix bugs and develop new features. I will still be around, mostly working on things around Flatpak, PipeWire, etc. Thank you. Best regards, Jan Grulich
akademy 2022 BOF notes
Those are the raw unedited notes for the plasma bof at akademy. probably not super clear to who wasn't there, but ask and discuss anything not clear Plasma BoF Akademy 2022 Things we want in 5.27 Noah: New spectacle Noah: has something to finish for the Breeze effort to see if the list highlight in plasma style can be done Kai MUST to port KPBI to manifest v3 Aleix: port system dialogs to the qtquick dialogs, so they can work better in plamo Marco: window tiling refactor in kwin tied one layout per output and VD combination Marco & David: multiscreen containment mapping robustness overhaul Plasma 5.27 becomes a new LTS, with ongoing maintenance releases until Plasma 6 is out Planning for Plasma 6 boring release or visual overhaul? new qstyle is infeasible icon overhaul using Ken Vermette's WIP work? using the naming scheme and release schedule of KDE gear based on date, and release the same day as gear apps? might make sense, but could give some flooding problems for promo, needs to be discussed with them plasma-framework will be moved to the Plasma group to be released along with Plasma instead of Frameworks Move all Breeze theme assets and data into Breeze repo Eventually move SVG handling out of Plasma Framework and into its own Framework Wayland multiple shells per client Remove concept of scriptengines, merge DeclarativeAppletScript into main library Sprint Before or after 5.27? to be discussed in the mailing list
