Re: Reviving lightdm-kde-greeter upstream
It would hardly be convenient for me to maintain several similar repositories in parallel, so if it is located in the KDE infrastructure, I will commit there for sure. But could you please specify more precisely where the requirement to "kill" forks is described? It seems that I looked through the entire tree of links that drop down to the one you specified, and did not find any prohibitions. And the GPL* license does not seem to prohibit the existence of forks. This is important because in particular [1] is a special repository with instructions for building packages into an ALT repository, "Sisyphus" (located in the .gear folder), and it must continue to exist in some form. If the project develops inside KDE, will I be able to merge the changes back to [1]? On 11/25/23 02:14, Albert Astals Cid wrote: El dimecres, 22 de novembre de 2023, a les 9:48:21 (CET), Anton Golubev va escriure: Hello! I am involved in the development of the ALT Linux distribution. Some time ago we started developing the lightdm-kde-greeter fork and I am currently maintaining it[1]. I also push it on gitlab[2]. In addition to porting to Qt5, some features have been added, such as choosing a keyboard layout and connecting to the network. This greeter is currently used by default in our KDE-based builds. I was given the idea to revive this project in the upstream[3]. Personally, I like the idea, and might look into it if someone else finds it useful, and I will be given appropriate access. Since you don't seem to be a KDE devel just yet this would probably have to go through the https://community.kde.org/Incubator program. Have you read https://manifesto.kde.org/ specially the parts that say you'd have to "kill" your forks in [1] and [2] ? Cheers, Albert Regards, [1]: https://git.altlinux.org/gears/l/lightdm-kde-greeter.git [2]: https://gitlab.com/golubevan/lightdm-kde-greeter [3]: https://invent.kde.org/unmaintained/lightdm
[ANNOUNCE] CMake 3.26.6 available for download
We are pleased to announce that CMake 3.26.6 is now available for download. Please use the latest release from our download page: https://cmake.org/download/ Thanks for your support! Changes made since CMake 3.26.5: Brad King (3): curl: Backport SOCKS5 heap buffer overflow fix from curl 8.4.0 Help: Fix ctest(1) manual links to www.cdash.org CMake 3.26.6 Kyle Edwards (1): fileapi: Fix file sets' base directories relative to top source Tomoharu Kitawaki (1): FindCUDAToolkit: Fix nvrtc_builtins library name Zack Galbreath (2): ctest: Update ctest_submit for CDash behavior change ctest: Restore support for http redirects during Submit step
KDE Gear features list
Hello, I started working on the announcement for the the megarelease. For Plasma, Nate collected all the new user facing changes here: https://community.kde.org/Plasma/Plasma_6#User-facing_changes I would appreciate if gear app maintainers and contributors could do the same for KDE gear: https://community.kde.org/Gear/Gear_24.02 I just need a link to commit, MR or bug report and a few words about the change. I'm also working on a sliglty tweeaked format for the announcement which would allow to mention both the big major changes as well as more minor improvements than previously. So don't mind also adding more minor changes to the wiki page, but I can't promise I will manage to mention everything. If you posted your progress already on a blog post (like we do in KDE PIM) a link to that is also great. Cheers, Carl PS: if you are interested in seeing the WIP state for the announcement webpage, feel free to contact me privately. I'm just not posting it here so that it doesn't end up on Reddit.
Re: KDE Gear 24.02 bug fix releases and next Gear releases
On Monday, November 27, 2023 8:57:26?AM GMT+1 Heiko Becker wrote: > Hi everyone, > > the question of the next Gear release (after 24.02) came up in #kde-devel > yesterday evening. Due to this, it also occured to me that we haven't > scheduled any bug fix releases for 24.02 itself. Which is a bit connected > to the first question, because I guess we don't want too many stable > branches at the same time (as in more than 1 really). > > I mostly see three options, but of course please chime if you think of > something else: > > > a) Continue with the usual dates, eg. 24.04 and 24.08. (or omitting 24.04 > and continue with 24.08 right away) > > b) Continue with the usual interval, so 24.06, 24.10 and so on > > c) Slightly change the interval to come back to the proven schedule with > its nice numbers divisible by 4, so something like, 24.05 and 24.08. > > > Personally, I'd favour b) or c). I think a) is either too short or too > long. Not sure how b) would interact with holiday schedules, exams or > distro releases though. b) would mean the major gear releases and plasma releases would be sort of synchronized as both are once ever 4 months and Plasma releases have been happening in February, June and October. This would mean a return of a megarelease from the KDE 4 times, which is a something I would like to see but it is also a controversial idea. As someone who spend a lot of time on the gear and plasma announcements every 2 months, I personally would prefer to spend even more time on a big announcement every 4 months. Also from a promo perspective, having a bit announcement every 4 months for gear + plasma is more effective than having a less big annoucement every 2 months. This might also be good for distros as from a feature perspective, they can align themselve with one 4 months cycle and not 2 different 4 months cycles. But in any case, that would be worse than the status quo is having the gear and plasma announcement just one week or two appart, as it would be quite unsustainable for the promo team in term of work load. And it means a prolonged period of release stress for us. Additionally the first release would eclipse the second one as tech/linux newspapers/youtubers will only report about the first release and not the second one, because they don't want to publish too much KDE news days appart. So if we don't release the major version of Gear and Plasma at the same time, I would prefer to keep them apart as before and go with a) or c). Cheers, Carl > > Regards, > Heiko
Re: KDE Gear 24.02 bug fix releases and next Gear releases
> On Monday, 2023-09-04T05:50:45z David Edmundson wrote: > > [...] The KDE Gear release will move by 2 months [...] I think now I get the confusion: Does this sentence refer to “KDE Gear 23.12” or to the general “KDE Gear release schedule”? I just assumed only 23.12 is delayed, because there was once a discussion about changing the schedule in general, and it was thought to be fine as it is.
Re: KDE Gear 24.02 bug fix releases and next Gear releases
On Monday, November 27, 2023 8:57:26 AM CET Heiko Becker wrote: > the question of the next Gear release (after 24.02) came up in #kde-devel > yesterday evening. [...] > > a) Continue with the usual dates, eg. 24.04 and 24.08. (or omitting 24.04 > and continue with 24.08 right away) > > b) Continue with the usual interval, so 24.06, 24.10 and so on > > c) Slightly change the interval to come back to the proven schedule with > its nice numbers divisible by 4, so something like, 24.05 and 24.08. Hi, As I remember, there wasn’t a more recent announcement than the below, and the linked wiki page does not discuss releases outside 24.02. So I assume that option a) from above is true. 23.08, 24.02, 24.04, then proceed as usual (every 4 months). But if something has changed since the below announcement, I would be happy to learn it, too. :) On Monday, 2023-09-04T05:50:45z David Edmundson wrote: > [...] > > - The KDE Gear release will move by 2 months to allow for the extra > time needed for testing initial Qt6 changes > > - An Alpha will be made in November (a soft freeze in Plasma terms) > > - Betas/RCs will be made throughout December and January (3 releases, > 3 weeks apart) > > - Final release of all 3 major parts in sync in February > > Due to the delay of KDE Gear by [2 months] an additional patch > release of 23.08 will be made. > > David Edmundson On Saturday, 2023-11-25T11:30:05z Albert Astals Cid wrote: > According to https://community.kde.org/Schedules/February_2024_MegaRelease > feature freeze is 29 November (i.e. next week). > > [...]
