Re: KDE review request: KDominate

--0000000000008ebd4e064be2bda0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Sat, Feb 28, 2026 at 1:19=E2=80=AFPM Harald Sitter <[email protected]> wrot=
e:

> One could argue going through review while not being a KDE repo (i.e. in
> repo-metadata) makes no sense since you can't follow the process and mark
> it in-review
>
> https://develop.kde.org/docs/getting-started/add-project/review/#process
>
> I guess the answer is that it needs moving.
>

Oh, I thought moving would happen *after* it got reviewed and accepted.

About the instructions you linked, I did miss the item about updating
repo-metadata, but actually I'm not sure I understand it. It says:

> Make a merge request to repo-metadata to set the lifecycle key to
lifecycle: in-review

But it doesn't mention which file within repo-metadata I should
create/update. I see that each project has a directory like
`projects-invent/<group>/<repo name>`, but in my case it's not clear to me
if I should create `projects-invent/albertvaka/kdominate` or
`projects-invent/kgames/kdominate` (even though it's not under kgames yet).
It seems weird to use albertvaka, since I don't see any other personal repo
there...

As you can see it is the first time I'm going through this process, so
sorry in advance for the mistakes. The upside is that I approach it with
fresh eyes so we will be able to spot anything that isn't clear, like the
line above :)

Albert

--0000000000008ebd4e064be2bda0
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div class=3D"gmail_quot=
e"><div dir=3D"ltr" class=3D"gmail_attr">On Sat, Feb 28, 2026 at 1:19=E2=80=
=AFPM Harald Sitter &lt;<a href=3D"mailto:[email protected]" target=3D"_blank"=
>[email protected]</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" s=
tyle=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);pad=
ding-left:1ex">
One could argue going through review while not being a KDE repo (i.e. in re=
po-metadata) makes no sense since you can&#39;t follow the process and mark=
 it in-review<br>
<br>
<a href=3D"https://develop.kde.org/docs/getting-started/add-project/review/=
#process" rel=3D"noreferrer" target=3D"_blank">https://develop.kde.org/docs=
/getting-started/add-project/review/#process</a><br>
<br>
I guess the answer is that it needs moving.<br></blockquote><div><br></div>=
<div>Oh, I thought moving would happen *after* it got reviewed and accepted=
.</div><div><br></div><div>About the instructions you linked, I did miss th=
e item about updating repo-metadata, but actually I&#39;m not sure I unders=
tand it. It says:</div><div><br></div><div>&gt;=C2=A0Make a merge request t=
o repo-metadata to set the lifecycle key to lifecycle: in-review</div><div>=
<br></div><div>But it doesn&#39;t mention which file within=C2=A0repo-metad=
ata I should create/update. I see that each project has a directory like `p=
rojects-invent/&lt;group&gt;/&lt;repo name&gt;`, but in my case it&#39;s no=
t clear to me if I should create `projects-invent/albertvaka/kdominate` or =
`projects-invent/kgames/kdominate` (even though it&#39;s not under kgames y=
et). It seems weird to use albertvaka, since I don&#39;t see any other pers=
onal repo there...</div><div><br></div><div>As you can see it is the first =
time I&#39;m going through this process, so sorry in advance for the=C2=A0m=
istakes. The upside is that I approach it with fresh eyes so we will=C2=A0b=
e able to spot anything that isn&#39;t clear, like the line above :)</div><=
div><br></div><div>Albert</div></div></div>
</div>
</div>

--0000000000008ebd4e064be2bda0--