KDE review request: KDominate

[Nicolas Fella]

On 2/28/26 3:47 PM, Harald Sitter wrote:
>> Albert Vaca Cintora<albertvaka at gmail.com> hat am 28.02.2026 14:57 CET geschrieben:
>>
>>
>> On Sat, Feb 28, 2026 at 1:19 PM Harald Sitter<sitter at kde.org> wrote:
>>> 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.

For some reason I can't explain that is a common misconception as of 
recently. The last few review requests *all* made that mistake. Nobody 
really questioned it until now, but it's not how it's supposed to work.

>> 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.
> 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20260228/7768f15d/attachment.htm>