Re: KDE review request: KDominate

> Albert Vaca Cintora <[email protected]> hat am 28.02.2026 14:57 CET ge=
schrieben:
>=20
>=20
> On Sat, Feb 28, 2026 at 1:19=E2=80=AFPM Harald Sitter <[email protected]> wr=
ote:
> > One could argue going through review while not being a KDE repo (i.e. i=
n repo-metadata) makes no sense since you can't follow the process and mark=
 it in-review
> > =20
> >  https://develop.kde.org/docs/getting-started/add-project/review/#proce=
ss
> > =20
> >  I guess the answer is that it needs moving.
>=20
> Oh, I thought moving would happen *after* it got reviewed and accepted.
>=20
> About the instructions you linked, I did miss the item about updating rep=
o-metadata, but actually I'm not sure I understand it. It says:
>=20
> >=C2=A0Make a merge request to repo-metadata to set the lifecycle key to =
lifecycle: in-review
>=20
> But it doesn't mention which file within=C2=A0repo-metadata I should crea=
te/update.

You'll get a file as part of moving to a proper shared namespace. For that =
you need to file a sysadmin request.

I guess the docs need a bit more detail for the case when a project starts =
"in KDE". Something like

- create project in your namespace
- push some initial code
- file sysadmin request to have it moved to some shared namespace
- this results in lifecycle:playground
- then follow the review process to move on from there

CCing Thiago in the hopes that I don't have to update the docs :D

HS