> -----Original Message----- > From: Development [mailto:development-bounces+kai.koehne=qt.io@qt- > project.org] On Behalf Of Oswald Buddenhagen > Sent: Wednesday, November 09, 2016 4:01 PM > To: development@qt-project.org > Subject: Re: [Development] QCS2016 Session Notes - QUIPs for Qt > > On Tue, Nov 08, 2016 at 04:50:00PM +0100, Louai Al-Khanji wrote: > > +1 for qt/quips, I don't think of it as a web site thing either. > > > well, i don't want it in qt/ - this is not a generic namespace for stuff that > doesn't fit elsewhere. everything in there *should* be aggregated by qt5.git > (with an accurate status field), or be a submodule of an aggregated module. > > i can offer meta/ as an alternative.
meta/quips would work for me, too. or qt-project/quips? > or maybe qtqt/ - that one already exists, but i suspect the objections will be > the same as to www/. No idea what qtqt/ should stand for :) > > Kai Koehne wrote: > > > I'd slightly prefer > > > > > > qt/quips > > > > > > because it's not directly related to the website, even if we'll > > > generate an html presentation out of it. We might even consider > > > adding it to qt/qt5.git at one point ... > > > that makes no sense to me at all. the scope if this is certainly wider than > the > qt product itself. Why do you think so? This is the repository where we want to document processes and design decisions for Qt, the project _and_ the product. It's surely more meta than most of the modules, but we've also projects like qt/qtqa and qt/qtrepotools, which do not contain a qt module, either. Regards Kai _______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development