On Samstag, 5. März 2022 19:16:02 CET Ben Cooksley wrote:
> On Sun, Mar 6, 2022 at 6:00 AM Stephen Kelly <steve...@gmail.com> wrote:
> > On 26/02/2022 10:38, Volker Krause wrote:
> > > On Sonntag, 20. Februar 2022 16:02:59 CET Stephen Kelly wrote:
> > >> Hello,
> > >> 
> > >> The Qt 5 based Grantlee libraries were depended on by some KDE
> > 
> > applications.
> > 
> > >> For Qt 6, I've created a separate repo for KTextTemplate for one of the
> > >> Grantlee libraries. The other library is separate and can be dealt with
> > >> separately.
> > >> 
> > >> Currently the code lives here:
> > >> 
> > >> https://github.com/steveire/ktexttemplate
> > >> 
> > >> I'd like to get the process moving on getting this reviewed and into
> > 
> > KF6.
> > 
> > >> It's not clear to me what the next step is. I tried googling terms like
> > >> "how to submit a library to kde frameworks", but didn't find anything
> > >> useful.
> > >> 
> > >> https://techbase.kde.org/KDE_Frameworks describes how to build
> > >> frameworks, but not how to submit a new one.
> > >> 
> > >> I've checked and I can still use invent.kde.org, so it would be good if
> > >> there is a standard process I can follow for the rest.
> > > 
> > > I don't think the process of integrating a so far external project into
> > > Frameworks happened often enough for this to be documented as a
> > 
> > streamlined
> > 
> > > process. I'd suggest the following steps:
> > > 
> > > (1) Import the repo into invent.kde.org
> > > (2) Go through the KDE Review process
> > > (3) Request inclusion into Frameworks
> > > 
> > > Happy to see this moving :)
> > 
> > Ok. I was thinking there might be some 'review' area of invent.k.o, but
> > I've just made
> > 
> > https://invent.kde.org/skelly/ktexttemplate
> > 
> > Does that satisfy (1)?
> 
> It starts the process yes.
> 
> > I think there are changes like CamelCase headers to conform to KF6
> > norms. I'm not sure if others can help with that now. Can any KDE
> > account push to the above repo?
> 
> No, only you are able to push to that repository, but people can send you
> merge requests.
> 
> To give people access to the repository you can either:
> a) Invite the teams/kde-developers group to the repository as a 'Developer'
> which will grant access to it; or
> b) Ask Sysadmin to move the repository into libraries/ which is where it
> would go prior to becoming a Framework (which it can only do when it
> completes KDE Review)

I'd say let's do (b) next so it's in a more canonical place and easier to 
find, and then trigger the KDE Review process.

Regards,
Volker

Attachment: signature.asc
Description: This is a digitally signed message part.

Reply via email to