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 t
On Tuesday, 3 October 2023 08:33:02 CEST Benson Muite wrote:
> 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 an
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's
> see if we can get something t
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
>> ready
>> for a kde review.
>
> Even two y
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 Schwan wrote:
On Monday, 2 Octobe
On Monday, 2 October 2023 21:53:06 CEST Albert Astals Cid wrote:
>
> This method of review is really sub-optiomal.
>
> Who checked all those marks? There's no way to know.
>
> Was it someone expert in the area?
>
> Was it someone that knows has no idea what the checks mean?
>
> Or was it the s
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.
>
> Features include
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 with md5 was not a good id
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 checksum
13 matches
Mail list logo
