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 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 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 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
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 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
