<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p><br>
</p>
<div class="moz-cite-prefix">On 05/03/2022 18:16, Ben Cooksley
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CA+XidOFJWVAeFNi_k2Dw=mPrV1jsseXaMTe=Xh_k1M7E9BbipA@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div dir="ltr">On Sun, Mar 6, 2022 at 6:00 AM Stephen Kelly <<a
href="mailto:steveire@gmail.com" moz-do-not-send="true"
class="moz-txt-link-freetext">steveire@gmail.com</a>>
wrote:<br>
</div>
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex"><br>
On 26/02/2022 10:38, Volker Krause wrote:<br>
> On Sonntag, 20. Februar 2022 16:02:59 CET Stephen Kelly
wrote:<br>
>> Hello,<br>
>><br>
>> The Qt 5 based Grantlee libraries were depended on
by some KDE applications.<br>
>><br>
>> For Qt 6, I've created a separate repo for
KTextTemplate for one of the<br>
>> Grantlee libraries. The other library is separate
and can be dealt with<br>
>> separately.<br>
>><br>
>> Currently the code lives here:<br>
>><br>
>> <a
href="https://github.com/steveire/ktexttemplate"
rel="noreferrer" target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://github.com/steveire/ktexttemplate</a><br>
>><br>
>> I'd like to get the process moving on getting this
reviewed and into KF6.<br>
>><br>
>> It's not clear to me what the next step is. I tried
googling terms like<br>
>> "how to submit a library to kde frameworks", but
didn't find anything<br>
>> useful.<br>
>><br>
>> <a href="https://techbase.kde.org/KDE_Frameworks"
rel="noreferrer" target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://techbase.kde.org/KDE_Frameworks</a>
describes how to build<br>
>> frameworks, but not how to submit a new one.<br>
>><br>
>> I've checked and I can still use <a
href="http://invent.kde.org" rel="noreferrer"
target="_blank" moz-do-not-send="true">invent.kde.org</a>,
so it would be good if<br>
>> there is a standard process I can follow for the
rest.<br>
> I don't think the process of integrating a so far
external project into<br>
> Frameworks happened often enough for this to be
documented as a streamlined<br>
> process. I'd suggest the following steps:<br>
><br>
> (1) Import the repo into <a
href="http://invent.kde.org" rel="noreferrer"
target="_blank" moz-do-not-send="true">invent.kde.org</a><br>
> (2) Go through the KDE Review process<br>
> (3) Request inclusion into Frameworks<br>
><br>
> Happy to see this moving :)<br>
<br>
<br>
Ok. I was thinking there might be some 'review' area of
invent.k.o, but <br>
I've just made<br>
<br>
<a href="https://invent.kde.org/skelly/ktexttemplate"
rel="noreferrer" target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://invent.kde.org/skelly/ktexttemplate</a><br>
<br>
Does that satisfy (1)?<br>
</blockquote>
<div><br>
</div>
<div>It starts the process yes.</div>
<div> </div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
<br>
I think there are changes like CamelCase headers to conform
to KF6 <br>
norms. I'm not sure if others can help with that now. Can
any KDE <br>
account push to the above repo?<br>
</blockquote>
<div><br>
</div>
<div>No, only you are able to push to that repository, but
people can send you merge requests.</div>
<div><br>
</div>
<div>To give people access to the repository you can either:</div>
<div>a) Invite the teams/kde-developers group to the
repository as a 'Developer' which will grant access to it;
or</div>
</div>
</div>
</blockquote>
<p><br>
</p>
<p>I've done this part now.</p>
<p>I thought I started the KDE Review process when I sent the
original email here, but without a written-down process I'm not
certain.</p>
<p>Maybe things can be moved along now?<br>
</p>
<p>Thanks,</p>
<p>Stephen.<br>
</p>
<br>
</body>
</html>