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" <[email protected]> > To: "Mikhail Svetkin" <[email protected]> > Cc: "[email protected]" <[email protected]> > Subject: Re: [Development] Request to move qt-labs/qhttpserver out of qt-labs > > > On 3 Feb 2020, at 08:15, Mikhail Svetkin <[email protected]> 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 > [email protected] > https://lists.qt-project.org/listinfo/development > _______________________________________________ Development mailing list [email protected] https://lists.qt-project.org/listinfo/development
