[Development] Request to move qt-labs/qhttpserver out of qt-labs

[Mikhail Svetkin]

>
> Where to we plan to put add-ons that we publish via that ?


I think It would be nice to have a new namespace qt-addons in Qt project
git repository.

OTOH, we should have a consistent place where contributors can see how
> different modules do things. Do you plan to document your branching policy?
>

I wanted to use a classic git flow approach. It would be nice to have wiki
pages or something like github provides. Where every addon can describe
their stuff.



Best regards,
Mikhail


On Mon, Feb 3, 2020 at 4:07 PM Jason H <jhihn at gmx.com> wrote:

> I just want to say that the qthttpserver is the most impactful
> contribution to Qt for me in along time.
> Having a http server in Qt has allowed saved me so much work, provide so
> many additional integrations with ease.
> ***** would use again.
>
> Given hoe much positive impact it has had, I would like to see it as a
> main part of Qt though.
>
> > Sent: Monday, February 03, 2020 at 9:29 AM
> > From: "Volker Hilsheimer" <volker.hilsheimer at qt.io>
> > To: "Mikhail Svetkin" <mikhail.svetkin at gmail.com>
> > Cc: "development at qt-project.org" <development at qt-project.org>
> > Subject: Re: [Development] Request to move qt-labs/qhttpserver out of
> qt-labs
> >
> > > On 3 Feb 2020, at 08:15, Mikhail Svetkin <mikhail.svetkin at gmail.com>
> wrote:
> > >
> > > Hello,
> > >
> > > I would like to make request to move qthttpserver from qt-labs
> namespace to a new namespace qt-addons or qt-extensions.
> > >
> > > The main reason is that it is not a research project anymore. I
> believe that the module is ready to become a self contained library as part
> of Qt Project and a good example of Qt marketplace.
> >
> >
> > Yes indeed! Thanks for being awesome :)
> >
> >
> > > I also would like to request to have an independent branch policy for
> the new repository. It will allow to speed up development of qthttpserver
> and it will not slow down Qt6 works.
> >
> >
> > It makes little sense to me to have the same branching policy for every
> module, irrespective of their maturity, complexity, release practices etc.
> E.g. new modules might want to start with the cherry-picking model right
> away, or not have the notion of LTS branches to begin with.
> >
> > OTOH, we should have a consistent place where contributors can see how
> different modules do things. Do you plan to document your branching policy?
> >
> > Volker
> >
> > _______________________________________________
> > Development mailing list
> > Development at qt-project.org
> > https://lists.qt-project.org/listinfo/development
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/development/attachments/20200204/c844f4da/attachment-0001.html>