sible there)
>
> This may be a stupid question, but why didn't you use qtkeychain which has
> backends for all major OS and which we use in most if not all KDE apps that
> store passwords?
>
> https://github.com/frankosterfeld/qtkeychain
>
> Regards,
> Ingo
--
Marco Martin
oid I think it would really make no sense as the
> application needs a DBus connection to SecretService which is not
> really possible there)
This may be a stupid question, but why didn't you use qtkeychain which has
backends for all major OS and which we use in most if not all KDE app
Thanks,
I got it mostly working.
However i had to disable Android and windows because of the dependency
to GNOME libsecret which i don't think is available there?
(also, on Android I think it would really make no sense as the
application needs a DBus connection to SecretService which is not
really
On 7/17/25 2:39 PM, Marco Martin wrote:
Should it already be moved to another more public-facing repo to start
to setup CI ?
No, you can setup CI even in your personal repo.
Cheers,
Vlad
Should it already be moved to another more public-facing repo to start
to setup CI ?
On Tue, Jul 15, 2025 at 3:22 PM Marco Martin wrote:
>
> Hi all,
>
> I have been working over the last months on an application called Keep Secret.
> It is intended to be a password manager gui which uses the Secr
Hi all,
I have been working over the last months on an application called Keep Secret.
It is intended to be a password manager gui which uses the Secret
Service DBus api
as backend, therefore it works with KWallet, gnome-keyring, oo7 etc..
The current home is:
https://invent.kde.org/mart/keepsec
Hello,
KNightTime (https://invent.kde.org/vladz/knighttime) provides scheduling
helpers for the dark-light cycle. Intended users are KWin, plasmashell.
It can be used for Night Light, Day/Night wallpapers, changing the color
scheme or the desktop theme based on time of day.
Currently, the pr
On Donnerstag, 13. März 2025 11:58:36 Mitteleuropäische Normalzeit Martin
Koller wrote:
> I recently got a bug report for kolourpaint saying it's missing the
> KDE colors in the KF6 version, just to find out that these color definition
> files were part of kdelibs4support (don'
I recently got a bug report for kolourpaint saying it's missing the
KDE colors in the KF6 version, just to find out that these color definition
files were part of kdelibs4support (don't ask me why) which got removed.
So how to solve this?
Are these color files (e.g. /etc/xdg/colors
El dijous, 19 de desembre del 2024, a les 17:45:29 (Hora estàndard del Centre
d’Europa), Mathis Brüchert va escriure:
> Hello everyone,
>
> Carl asked me to request a kde review of my app "Powerplant". Here is the
> issue:
>
> https://invent.kde.org/utilities/powerp
Hello everyone,
Carl asked me to request a kde review of my app "Powerplant". Here is the issue:
https://invent.kde.org/utilities/powerplant/-/issues/5
Thank you in advance:))
Mathis
On 04/11/24 12:49 am, Ingo Klöcker wrote:
KDE's Licensing Policy (https://community.kde.org/Policies/Licensing_Policy)
doesn't list the MPL(2.0) as allowed license for "source code and related data
files in KDE repositories".
This doesn't mean that we couldn&#x
On Sat, Nov 9, 2024 at 7:20 AM Tomaz Canabrava wrote:
>
>
>
> On Mon, 4 Nov 2024 at 09:51 Sune Vuorela wrote:
>>
>> On 2024-11-03, Neal Gompa wrote:
>> > It's not that simple. The reason I suggested MPL-2.0 is because
>> > LGPL-2.1-or-later is effectively the same as GPL-2.0-or-later with
>> > R
On Mon, 4 Nov 2024 at 09:51 Sune Vuorela wrote:
> On 2024-11-03, Neal Gompa wrote:
> > It's not that simple. The reason I suggested MPL-2.0 is because
> > LGPL-2.1-or-later is effectively the same as GPL-2.0-or-later with
> > Rust because it's statically linked.
> >
people lgpl does not forbid
On 2024-11-04, Sune Vuorela wrote:
[looks like half a sentence disappeared between brain and keyboard]
> On a more 'matter of taste'-note, it does look like someone has went
> overboard with templates. While I like and understand templates,
I think this might be a bit too much and could probably b
On 2024-11-03, Neal Gompa wrote:
> It's not that simple. The reason I suggested MPL-2.0 is because
> LGPL-2.1-or-later is effectively the same as GPL-2.0-or-later with
> Rust because it's statically linked.
>
> MPL-2.0 preserves the copyleft at a per source file level, but allows
> the binary arti
ms.
> > If no one has issues with it, I will switch to it.
>
> Yes, it has a high degree of compatibility due to how it works as a license.
KDE's Licensing Policy (https://community.kde.org/Policies/Licensing_Policy)
doesn't list the MPL(2.0) as allowed license for "sourc
On 2024-11-01, Carl Schwan wrote:
> This is a KDE Review request for md4qt. md4qt is a Markdown parser
> for Qt projects.
Where do you expect it to 'land' ? Frameworks? apps/libraries?
What api compatibilities are expected?
What does it do that Qt's markdown support in Q
use any license violations but the bridge code is based of the method
signatures of the original libraries.
Third, Upstream `cxx-qt` project uses Apache-2.0+MIT and I planned to do
the same but KDE's Licensing policy doesn't mention any thing about
Apache-2.0.
I'd say just stick the
need to install the libraries. I don't think this should
> >>>>>> cause any license violations but the bridge code is based of the method
> >>>>>> signatures of the original libraries.
> >>>>>> Third, Upstream `cxx-qt` project uses Ap
gt; >>>> Third, Upstream `cxx-qt` project uses Apache-2.0+MIT and I planned to do
> >>>> the same but KDE's Licensing policy doesn't mention any thing about
> >>>> Apache-2.0.
> >>> I'd say just stick the same license on it as the KDE Frame
ibraries.
Third, Upstream `cxx-qt` project uses Apache-2.0+MIT and I planned to do
the same but KDE's Licensing policy doesn't mention any thing about
Apache-2.0.
I'd say just stick the same license on it as the KDE Frameworks in
question.
Given they are a directly derived work an
e is based of the method
>> signatures of the original libraries.
>> Third, Upstream `cxx-qt` project uses Apache-2.0+MIT and I planned to do
>> the same but KDE's Licensing policy doesn't mention any thing about
>> Apache-2.0.
> I'd say just stick the same
ge code is based of the method
> >> signatures of the original libraries.
> >> Third, Upstream `cxx-qt` project uses Apache-2.0+MIT and I planned to do
> >> the same but KDE's Licensing policy doesn't mention any thing about
> >> Apache-2.0.
> > I
7;s Licensing policy doesn't mention any thing about
Apache-2.0.
I'd say just stick the same license on it as the KDE Frameworks in
question.
Given they are a directly derived work and also uses the KDE Frameworks
underneath, giving any other license is just going to be confusing for
od
> > signatures of the original libraries.
> > Third, Upstream `cxx-qt` project uses Apache-2.0+MIT and I planned to do
> > the same but KDE's Licensing policy doesn't mention any thing about
> > Apache-2.0.
>
> I'd say just stick the same license on it
Hi,
This is a KDE Review request for md4qt. md4qt is a Markdown parser
for Qt projects.
It is is currently used by Klevernotes and I would like to use it in the future
also for a block editor in Marknote if I find the time (similar to
https://rubymamistvalove.com/block-editor).
The KDE Review
KDE's Licensing policy doesn't mention any thing about
> Apache-2.0.
I'd say just stick the same license on it as the KDE Frameworks in
question.
Given they are a directly derived work and also uses the KDE Frameworks
underneath, giving any other license is just going to be confusin
On Wed, Oct 30, 2024 at 7:04 PM Darshan Phaldesai
wrote:
>
> Hello!
> I am working on a rust bridge for KF6 called `cxx-kde-frameworks`. It is
> built on top of `cxx-qt` by KDAB. It will allow you to make applications
> (and maybe widgets :) ) completely in rust.
> The project
Hello!
I am working on a rust bridge for KF6 called `cxx-kde-frameworks`. It is
built on top of `cxx-qt` by KDAB. It will allow you to make applications
(and maybe widgets :) ) completely in rust.
The project is in the process of incubation and releasing it's first
version. (
already said in chat, I agree that incompatible changes should be
discussed first.
In addition, I want to say that such changes are documented here:
https://kde-builder.kde.org/en/misc/changelog.html
Andrew.
Hi,
On 2024-07-15 21:50, christ...@cullmann.io wrote:
Hi,
On 2024-07-15 20:13, Andrew Shark wrote:
You mean new python dependencies? I never added them. Oppositely, I
reduce them. For example, I gladly got rid of the "promise"
dependency.
yes, with dependencies I meant Python libs and the Py
Hi,
On 2024-07-15 20:13, Andrew Shark wrote:
You mean new python dependencies? I never added them. Oppositely, I
reduce them. For example, I gladly got rid of the "promise"
dependency.
yes, with dependencies I meant Python libs and the Python version.
There was some rather lengthy discussions
On 2024-07-13 15:52, christ...@cullmann.io wrote:
On 2024-07-12 23:01, Thiago Masato Costa Sueto wrote:
Hi,
I'd like to ask about the status of the KDE Review for kde-builder.
The existing issue tracking this has been without activity for a
while: https://invent.kde.org/sdk/kde-bu
On 2024-07-12 23:01, Thiago Masato Costa Sueto wrote:
Hi,
I'd like to ask about the status of the KDE Review for kde-builder.
The existing issue tracking this has been without activity for a
while: https://invent.kde.org/sdk/kde-builder/-/issues/84
So far ashark seems to have fulfilled
Hi,
I'd like to ask about the status of the KDE Review for kde-builder.
The existing issue tracking this has been without activity for a while:
https://invent.kde.org/sdk/kde-builder/-/issues/84
So far ashark seems to have fulfilled what was asked of them, and I believe
they're just w
request, do tell me if I missed something!
> I followed this documentation for it
> https://develop.kde.org/docs/getting-started/add-project/#kde-review
19th May 2024. KDE today announces the release of KDE Frameworks 5.116.0.
KDE Frameworks are 83 addon libraries to Qt which provide a wide
variety of commonly needed functionality in mature, peer reviewed and well
tested libraries with friendly licensing terms. For an introduction see
https
On 09.04.2024 13:51, Sune Vuorela wrote:
On Mon, Apr 8, 2024 at 10:05 AM wrote:
and deprecating the kdesrc-build. That way we can move forward with new tool.
I don't think reviewing or not of kde-builder should have any effect on
kdesrc-build.
I think also we should be slightly wa
On Wednesday, May 1, 2024 2:43:55 PM Central European Summer Time Mattia
Basaglia wrote:
> Hello,
>
> I'd like to have Glaxnimate enter KDE review.
Really great app!
I will put in my todo list to feature it more prominently in
https://kde.org/for/creators/ and you might see a
/docs/getting-started/add-project/#kde-review
On Wednesday, 1 May 2024 14:43:55 CEST Mattia Basaglia wrote:
> Review checklist:
> https://invent.kde.org/graphics/glaxnimate/-/issues/666
Hi Mattia,
Slightly out-of-scope of the regular review checklist, I'm building glaxnimate
on FreeBSD with KF5. The use of submodules and bundled libraries i
Hello,
I'd like to have Glaxnimate enter KDE review.
Glaxnimate is an editor for animated vector graphics, mostly geared
towards lottie animations.
It started as a Qt-based app, integration with KDE frameworks is ongoing.
Review checklist:
https://invent.kde.org/graphics/glaxnimate/-/i
El dimarts, 9 d’abril del 2024, a les 12:51:50 (CEST), Sune Vuorela va
escriure:
> On Mon, Apr 8, 2024 at 10:05 AM wrote:
> > and deprecating the kdesrc-build. That way we can move forward with new
> > tool.
> I don't think reviewing or not of kde-builder should have any e
On Mon, Apr 8, 2024 at 10:05 AM wrote:
> and deprecating the kdesrc-build. That way we can move forward with new tool.
I don't think reviewing or not of kde-builder should have any effect on
kdesrc-build.
I think also we should be slightly wary of changing a long-running 20y
old tool wr
On Tue, Apr 9, 2024 at 11:26 AM Kevin Kofler wrote:
>
> ash...@linuxcomp.ru wrote:
> > I've been working on KDE Builder project. This is a reimplementation of
> > kdesrc-build in Python.
>
> What is the point of rewriting a tool originally written in a stable
> la
ash...@linuxcomp.ru wrote:
> I've been working on KDE Builder project. This is a reimplementation of
> kdesrc-build in Python.
What is the point of rewriting a tool originally written in a stable
language that guarantees long-term backwards compatibility (since the
origina
On Mon, Apr 8, 2024 at 10:05 AM wrote:
>
> Hi all!
>
> I've been working on KDE Builder project. This is a reimplementation of
> kdesrc-build in Python. At this point, the tool is rather mature, but some
> minor bugs may probably be unnoticed. I'd like to officiall
Hi all!
I've been working on KDE Builder project. This is a reimplementation of kdesrc-build in Python. At this point, the tool is rather mature, but some minor bugs may probably be unnoticed. I'd like to officially request a review of KDE Builder for declaring it official tool, and d
10th February 2024. KDE today announces the release of KDE Frameworks 5.115.0.
KDE Frameworks are 83 addon libraries to Qt which provide a wide
variety of commonly needed functionality in mature, peer reviewed and well
tested libraries with friendly licensing terms. For an introduction see
https
de-frameworks-devel for heads-up, replies please only to
> > > kde-core-deve))
> > >
> > > I hit the problem that when working on a repo which would like to use
> > > latest
> > > KF development state to integrate some new KF API just added in
> > >
Am Samstag, 27. Januar 2024, 18:22:35 CET schrieb Friedrich W. H. Kossebau:
> moving slowly, but moving :)
>
> Would there be any objections to declare the kde(re)review phase to be
> successfully completed now? See below for comments on the checklist.
So 10 days passed and no actu
Am Sonntag, 4. Februar 2024, 19:22:28 CET schrieb Ben Cooksley:
> On Mon, Feb 5, 2024 at 4:28 AM Friedrich W. H. Kossebau
>
> wrote:
> > Hi,
> >
> > ((cc:kde-frameworks-devel for heads-up, replies please only to
> > kde-core-deve))
> >
> > I hit
Am Montag, 5. Februar 2024, 00:15:00 CET schrieb Julius Künzel:
> > Besides all the resource costs to create flatpaks on master builds by
> > default
> every time, when those are usually not used by anyone anyway.
>
> It is important to mention that the pipelines on master usually publish to
> the
Am Montag, 5. Februar 2024, 10:58:07 CET schrieb Ben Cooksley:
> On Mon, Feb 5, 2024 at 4:28 AM Friedrich W. H. Kossebau
>
> wrote:
> > So, how to solve those problems? Did I miss something?
> > Could flatpak builds on master branches be made on-demand rather?
>
> For the record, my rebuild of t
On Mon, Feb 5, 2024 at 4:28 AM Friedrich W. H. Kossebau
wrote:
> Hi,
>
> ((cc:kde-frameworks-devel for heads-up, replies please only to
> kde-core-deve))
>
> I hit the problem that when working on a repo which would like to use
> latest
> KF development state to integr
hat
otherwise I wonder what makes you so confident to know nobody uses it?
Cheers,
Julius
04.02.2024 19:23:06 Ben Cooksley :
> On Mon, Feb 5, 2024 at 4:28 AM Friedrich W. H. Kossebau
> wrote:
>> Hi,
>>
>> ((cc:kde-frameworks-devel for heads-up, replies please only to
>
On Mon, Feb 5, 2024 at 4:28 AM Friedrich W. H. Kossebau
wrote:
> Hi,
>
> ((cc:kde-frameworks-devel for heads-up, replies please only to
> kde-core-deve))
>
> I hit the problem that when working on a repo which would like to use
> latest
> KF development state to integr
e a number of old files where the
> > contributors might be hard to contact for an explicit license statement
> > (CMakeLists.txt, AUTHOR, Messages.sh, ...)
> >
> > Given the same is true for most other KDE games and then some KDE
> > software,
> > and Skladnik
Hi,
((cc:kde-frameworks-devel for heads-up, replies please only to kde-core-deve))
I hit the problem that when working on a repo which would like to use latest
KF development state to integrate some new KF API just added in cooperation
with that very repo wanting to use it, I cannot do so when
following GNOME
app: https://apps.gnome.org/Curtail/
Here is the issue to track the kde review
https://invent.kde.org/graphics/optiimage/-/issues/2
I already fill all the trivial checkbox: e.g. CI running and reuse conformance.
Clazy is unfortunately not working due to the lack of compiler s
h any of those packages/platforms, but I assume that
> > checkbox
> > is rather some kind of "nice to have", not blocking the process actually?
>
> This sort of comment makes me really sad. The All About the Apps goal,
> which in principle is still ongoing, was an
license statement (CMakeLists.txt,
> AUTHOR, Messages.sh, ...)
>
> Given the same is true for most other KDE games and then some KDE software,
> and Skladnik is actually some (very) old KDE software, just other than its
> KDE games siblings for some time had been excluded from release c
not blocking the process actually?
>
This sort of comment makes me really sad. The All About the Apps goal,
which in principle is still ongoing, was an attempt to get KDE developers
to realise it was important not just to write apps but to actually make
them available to users, I find it astonishi
Hi,
moving slowly, but moving :)
Would there be any objections to declare the kde(re)review phase to be
successfully completed now? See below for comments on the checklist.
Am Sonntag, 12. November 2023, 22:57:55 CET schrieb Friedrich W. H. Kossebau:
> Hi,
>
> REVIEW PHASE START
&g
s:
> >
> > It allows the user, through the use of a keyboard shortcut or a
> > dolphin servicemenu, to have a quick preview of the files that are
> > shown in the folder without having to open the default application.
> >
> > Similar applications are Gnome Sushi and Qu
lphin servicemenu, to have a quick preview of the files that are
shown in the folder without having to open the default application.
Similar applications are Gnome Sushi and Quick Look (Mac os).
Hi,
this looks like a cool project, congrats!
From a KDE perspective code quality concerns are m
program (initially in python) to get better at programming
and because some people were used to Quick look/Gnome sushi and were not
satisfied with the thumbnails shown in dolphin.
Example:
https://www.reddit.com/r/kde/comments/165aqp8/any_kde_dolphin_replacment_sugestion_or_quick/
> I'
On 2024-01-17, Danilo Agostini wrote:
> It allows the user, through the use of a keyboard shortcut or a dolphin
> servicemenu, to have a quick preview of the files that are shown in the
> folder without having to open the default application.
>
> Similar applications are Gnome Sushi and Quick Look
Hi, I developed an application and was thinking about doing the incubation
process but I'm not sure if my application will be accepted due to some
defects.
What my application does:
It allows the user, through the use of a keyboard shortcut or a dolphin
servicemenu, to have a quick preview of the
13th January 2024. KDE today announces the release of KDE Frameworks 5.114.0.
KDE Frameworks are 83 addon libraries to Qt which provide a wide
variety of commonly needed functionality in mature, peer reviewed and well
tested libraries with friendly licensing terms. For an introduction see
https
14th December 2023. KDE today announces the release of KDE Frameworks 5.113.0.
KDE Frameworks are 83 addon libraries to Qt which provide a wide
variety of commonly needed functionality in mature, peer reviewed and well
tested libraries with friendly licensing terms. For an introduction see
https
://invent.kde.org/accessibility/accessibility-inspector Thanks Ben for
taking care of that quickly.
Aside from moving the repo, I made the UI translatable and started modernizing
a bit the codebase and fixing bugs.
The tracking issue for KDE Review is here:
https://invent.kde.org/accessibility
On Sunday, 12 November 2023 22:57:55 CET Friedrich W. H. Kossebau wrote:
> Would the file COPYING (GPLv2) in the toplevel dir then default the license
> for these files?
> See https://phabricator.kde.org/source/svn/browse/trunk/kdegames/;10132
> In short, what to do here for reuse checks? Ignore, b
Aug. 30th 1998, first released by the name KSokoban with KDE
1.1, to be part of KDE for 10 years up to the last KDE 3 release. Then stalled
over Qt4/KDELibs4 porting, though the last 15 years bit by bit ported by
different people to since last year even build and run against future Qt6/
KF6
12th November 2023. KDE today announces the release of KDE Frameworks 5.112.0.
KDE Frameworks are 83 addon libraries to Qt which provide a wide
variety of commonly needed functionality in mature, peer reviewed and well
tested libraries with friendly licensing terms. For an introduction see
https
Hi,
I came to my attention that there is a merge request to move the incubator and
kde review checklist to develop.kde.org.
As it contains some additional changes instead of a simple move, I think it
would make sense to ask for additional reviews on this mailing list.
See
https
On Sun, Oct 22, 2023 at 6:15 PM Jonah Brüchert wrote:
>
> Hi everyone!
>
>
> I moved Qrca to KDEReview.
>
> It is a QR-Code scanner and generator for mobile and desktop devices. It
> is based on Prison and QtMultimedia.
>
> The repository is located here: https://invent.kde.org/utilities/qrca/
>
>
It already seems to be part of KDE so it doesn't need a review to
enter KDE Review, KDE Review is already a review process in itself.
https://community.kde.org/Policies/Application_Lifecycle
Aleix
On Wed, Oct 4, 2023 at 9:50 PM Mathis Brüchert wrote:
>
> Hello,
>
> could y
Hi everyone!
I moved Qrca to KDEReview.
It is a QR-Code scanner and generator for mobile and desktop devices. It
is based on Prison and QtMultimedia.
The repository is located here: https://invent.kde.org/utilities/qrca/
If you find anything that needs changing, please comment on the issue
19th October 2023. KDE today announces the release of KDE Frameworks 5.111.0.
KDE Frameworks are 83 addon libraries to Qt which provide a wide
variety of commonly needed functionality in mature, peer reviewed and well
tested libraries with friendly licensing terms. For an introduction see
https
Hello,
Kalm has moved to KDE Review (https://invent.kde.org/plata/kalm/-/issues/2).
Please take a look and raise an issue in GitLab if you see something that
should be changed.
It should probably go to https://invent.kde.org/utilities.
Kalm visualizes breathing techniques to help you kalm down
--
> From: *KDE Invent*
> Date: Thu, Oct 5, 2023 at 6:58 PM
> Subject: KDE Craft Blueprints | Failed pipeline for master | 03023ae7
> To:
>
>
>
> [https://invent.kde.org/uploads/-/system/appearance/header_logo/1/kde-logo-white-blue-128x128.png]
>
>
Craft blueprints testing is failing for craft internal reasons.
-- Forwarded message -
From: KDE Invent
Date: Thu, Oct 5, 2023 at 6:58 PM
Subject: KDE Craft Blueprints | Failed pipeline for master | 03023ae7
To:
[image: ✖] Pipeline #493762 has failed!
Project Packaging <ht
Hi, thanks for CCing me, Justin.
I took a look at the wiki page history, at past mailing list discussions
about KDE Review, and at the issues on Invent tagged with KDE Review, and I
see three things:
* The majority of new projects since 2020 up until this year did not have
an issue for tracking
https://invent.kde.org/office/marknote/
<https://invent.kde.org/office/marknote/-/issues/24>so that it can be
moved to Kde review?
It is a small note taking app saving your notes to Markdown files.
here is the issue: https://invent.kde.org/office/marknote/-/issues/24
<https://invent.
Hello,
could you please review https://invent.kde.org/office/marknote/
<https://invent.kde.org/office/marknote/-/issues/24>so that it can be
moved to Kde review?
It is a small note taking app saving your notes to Markdown files.
here is the issue: https://invent.kde.org/office/ma
cksum two years. I piked it up again recently and I think this
> >> is now ready for a kde review.
> >
> > Even two years ago, checking stuff with md5 was not a good idea, unless
> > just for checking for transfer errors.
> >
> > But maybe add a sha3 variant
On Tuesday, 3 October 2023 03:31:26 CEST Justin Zobel wrote:
> I think it's clear we need some sort of process documentation for KDE
> Review, who is expected to do what, and in which order.
>
> I've cc'd Thiago on this as they are KDE's documentation writer, let
On 10/2/23 09:52, Sune Vuorela wrote:
> On 2023-10-01, Carl Schwan wrote:
>> Hello,
>>
>> I started writting a small application to generate and compare files with
>> their
>> checksum two years. I piked it up again recently and I think this is now
>> re
I think it's clear we need some sort of process documentation for KDE
Review, who is expected to do what, and in which order.
I've cc'd Thiago on this as they are KDE's documentation writer, let's
see if we can get something together.
On 3/10/23 07:42, Carl Sc
e checkmarks. For me I see these checkmarks as stuff I
need to do before sending a mail to kde-core-devel, as it is just the basic
stuff and it doesn't make sense to request a review if this is not done.
Cheers,
Carl
El dilluns, 2 d’octubre de 2023, a les 22:55:05 (CEST), Nate Graham va
escriure:
> On 10/2/23 13:53, Albert Astals Cid wrote:
> > El diumenge, 1 d’octubre de 2023, a les 21:49:36 (CEST), Carl Schwan va
> > Who checked all those marks? There's no way to know.
>
> If you scroll down to "Activity",
On 10/2/23 13:53, Albert Astals Cid wrote:
El diumenge, 1 d’octubre de 2023, a les 21:49:36 (CEST), Carl Schwan va
Who checked all those marks? There's no way to know.
If you scroll down to "Activity", it says who checked them after the
issue was opened.
I agree that the person who opened th
El diumenge, 1 d’octubre de 2023, a les 21:49:36 (CEST), Carl Schwan va
escriure:
> Hello,
>
> I started writting a small application to generate and compare files with
> their checksum two years. I piked it up again recently and I think this is
> now ready for a kde review
On 2023-10-01, Carl Schwan wrote:
> Hello,
>
> I started writting a small application to generate and compare files with
> their
> checksum two years. I piked it up again recently and I think this is now
> ready
> for a kde review.
Even two years ago, checking stuff wi
On Mon, Oct 2, 2023 at 10:16 AM Ingo Klöcker wrote:
> On Sonntag, 1. Oktober 2023 21:49:36 CEST Carl Schwan wrote:
> > It would be great if someone could create a product on bugs.kde.org and
> > assign myself to the product.
>
> Are you sure you cannot create the product yourself?
>
> https://bug
On Sonntag, 1. Oktober 2023 21:49:36 CEST Carl Schwan wrote:
> It would be great if someone could create a product on bugs.kde.org and
> assign myself to the product.
Are you sure you cannot create the product yourself?
https://bugs.kde.org/editproducts.cgi
Regards,
Ingo
signature.asc
Descripti
Hello,
I started writting a small application to generate and compare files with their
checksum two years. I piked it up again recently and I think this is now ready
for a kde review.
Features includes:
- Generate checksum from a file
- Compare two files
- Verify a file with a given
10th September 2023. KDE today announces the release of KDE Frameworks 5.110.0.
KDE Frameworks are 83 addon libraries to Qt which provide a wide
variety of commonly needed functionality in mature, peer reviewed and well
tested libraries with friendly licensing terms. For an introduction see
https
1 - 100 of 2392 matches
Mail list logo
