<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">Am 26.03.25 um 15:28 schrieb David
Edmundson:<br>
</div>
<blockquote type="cite"
cite="mid:CAGeFrHCP8QrztrVZjwb_kTAYisEf0FdhSiugRe_CYsLvkRjUWA@mail.gmail.com">
<blockquote type="cite">
<pre wrap="" class="moz-quote-pre">
I'd lean towards merging them in one repo. Neither are useful on their own, are they?
</pre>
</blockquote>
<pre wrap="" class="moz-quote-pre">
Only benefit is the ability to change the backend in the future
without a messy git history.</pre>
</blockquote>
<p><span style="white-space: pre-wrap">I wouldn't worry too much about that since it's rather hypothetical. Having two repos that are tightly coupled has been a headache in the past (remember kwin and kwayland-server?).</span></p>
<p><span style="white-space: pre-wrap">So my suggestion would be to make one plasma-loginmanager repo
</span></p>
<p><span style="white-space: pre-wrap">
</span></p>
<blockquote type="cite"
cite="mid:CAGeFrHCP8QrztrVZjwb_kTAYisEf0FdhSiugRe_CYsLvkRjUWA@mail.gmail.com">
<blockquote type="cite">
<pre wrap="" class="moz-quote-pre">Then it probably makes sense to move the repo(s) to the plasma namespace.
</pre>
</blockquote>
<pre wrap="" class="moz-quote-pre">
Yeah, will do once we know where we want them.
</pre>
<blockquote type="cite">
<pre wrap="" class="moz-quote-pre">I'm a bit confused about "I also aim to incubate it into the KDE ecosystem to have full autonomy over the project and merging stuck patches.".
</pre>
</blockquote>
<pre wrap="" class="moz-quote-pre">
What I was trying to say was that we should host the backend part we
need, and maybe cherry-pick some pending PRs from SDDM.
I want to leave upstream SDDM alone so I don't actively break things
others might be using.
David
</pre>
</blockquote>
</body>
</html>