Re: [Development] QCS2016 Session Notes - QUIPs for Qt

> On 21 Nov 2016, at 21:11, André Pönitz wrote: > > QUIPs were not meant to require new or different tooling, and I still > believe such will be needed. Me too. See? we have consensus. ;-) ___ Development mailing list

Re: [Development] QCS2016 Session Notes - QUIPs for Qt

On November 21, 2016 20:02:54 André Pönitz wrote: > On Mon, Nov 21, 2016 at 11:06:52AM +, Edward Welbourne wrote: >> Giuseppe D'Angelo: >> >> I would also like to point out that, despite we have a repository, we >> >> still don't have a tool for properly discussing the

Re: [Development] QCS2016 Session Notes - QUIPs for Qt

On Mon, Nov 21, 2016 at 03:29:01PM +0300, Konstantin Tokarev wrote: > > > 21.11.2016, 15:26, "Giuseppe D'Angelo" : > > On Mon, Nov 21, 2016 at 12:58 PM, Oswald Buddenhagen > > wrote: > >>>  Any idea to how to actually make this work? > >>  how about

Re: [Development] QCS2016 Session Notes - QUIPs for Qt

On Mon, Nov 21, 2016 at 11:06:52AM +, Edward Welbourne wrote: > Giuseppe D'Angelo: > >> I would also like to point out that, despite we have a repository, we > >> still don't have a tool for properly discussing the actual content of > >> QUIPs. > >> > >> * Gerrit does not work because comments

Re: [Development] QCS2016 Session Notes - QUIPs for Qt

On November 21, 2016 14:29:10 Shawn Rutledge wrote: > >> On 21 Nov 2016, at 12:06, Edward Welbourne wrote: >> >> Giuseppe D'Angelo: I would also like to point out that, despite we have a repository, we still don't have a tool for properly

Re: [Development] QCS2016 Session Notes - QUIPs for Qt

> On 21 Nov 2016, at 12:06, Edward Welbourne wrote: > > Giuseppe D'Angelo: >>> I would also like to point out that, despite we have a repository, we >>> still don't have a tool for properly discussing the actual content of >>> QUIPs. >>> >>> * Gerrit does not work

Re: [Development] QCS2016 Session Notes - QUIPs for Qt

On November 21, 2016 13:51:10 Oswald Buddenhagen wrote: > On Mon, Nov 21, 2016 at 01:37:50PM +0100, Marco Bubke wrote: >> On November 21, 2016 12:58:59 Oswald Buddenhagen >> wrote: >> > how about taking the existing processes seriously and

Re: [Development] QCS2016 Session Notes - QUIPs for Qt

On Mon, Nov 21, 2016 at 01:37:50PM +0100, Marco Bubke wrote: > On November 21, 2016 12:58:59 Oswald Buddenhagen > wrote: > > how about taking the existing processes seriously and exercising social > > pressure on those who think they are above them? > > Sorry, not

Re: [Development] QCS2016 Session Notes - QUIPs for Qt

On November 21, 2016 12:58:59 Oswald Buddenhagen wrote: > On Sun, Nov 20, 2016 at 08:38:50PM +0100, Giuseppe D'Angelo wrote: >> On Thu, Nov 10, 2016 at 12:29 PM, Oswald Buddenhagen >> wrote: >> > the repository has been created. >> >> I

Re: [Development] QCS2016 Session Notes - QUIPs for Qt

21.11.2016, 15:26, "Giuseppe D'Angelo" : > On Mon, Nov 21, 2016 at 12:58 PM, Oswald Buddenhagen > wrote: >>>  Any idea to how to actually make this work? >>  how about taking the existing processes seriously and exercising social >>  pressure on

Re: [Development] QCS2016 Session Notes - QUIPs for Qt

On Mon, Nov 21, 2016 at 12:58 PM, Oswald Buddenhagen wrote: >> Any idea to how to actually make this work? >> > how about taking the existing processes seriously and exercising social > pressure on those who think they are above them? May I just say that prefer a tool

Re: [Development] QCS2016 Session Notes - QUIPs for Qt

On Sun, Nov 20, 2016 at 08:38:50PM +0100, Giuseppe D'Angelo wrote: > On Thu, Nov 10, 2016 at 12:29 PM, Oswald Buddenhagen > wrote: > > the repository has been created. > > I would also like to point out that, despite we have a repository, we > still don't have a tool

Re: [Development] QCS2016 Session Notes - QUIPs for Qt

Giuseppe D'Angelo: >> I would also like to point out that, despite we have a repository, we >> still don't have a tool for properly discussing the actual content of >> QUIPs. >> >> * Gerrit does not work because comments cannot be threaded, they >> don't stick to multiple reviews, and they can

Re: [Development] QCS2016 Session Notes - QUIPs for Qt

On Sunday 20 November 2016 20:29:01 Giuseppe D'Angelo wrote: > On Tue, Sep 20, 2016 at 9:27 AM, Thiago Macieira > > wrote: > > Can you remember the list of C++11 features we're allowed to use? We had > > a discussion on the mailing list. > > Going back to this

Re: [Development] QCS2016 Session Notes - QUIPs for Qt

On Sun, Nov 20, 2016 at 9:13 PM, Marco Bubke wrote: > Do you think about a wiki where you can comment? I think you want something > with the capability to describe, comment, argument and poll with a version > history. Like you described email is a terrible tool for it. If a

Re: [Development] QCS2016 Session Notes - QUIPs for Qt

On November 20, 2016 20:39:08 Giuseppe D'Angelo wrote: > On Thu, Nov 10, 2016 at 12:29 PM, Oswald Buddenhagen > wrote: >> the repository has been created. > > I would also like to point out that, despite we have a repository, we > still don't have a

Re: [Development] QCS2016 Session Notes - QUIPs for Qt

On Thu, Nov 10, 2016 at 12:29 PM, Oswald Buddenhagen wrote: > the repository has been created. I would also like to point out that, despite we have a repository, we still don't have a tool for properly discussing the actual content of QUIPs. * Gerrit does not work

Re: [Development] QCS2016 Session Notes - QUIPs for Qt

On Tue, Sep 20, 2016 at 9:27 AM, Thiago Macieira wrote: > > Can you remember the list of C++11 features we're allowed to use? We had a > discussion on the mailing list. Going back to this particular point: so should this list go into the QUIPs repository, or in qtbase?

Re: [Development] QCS2016 Session Notes - QUIPs for Qt

On 10/11/16 14:21, "Development on behalf of Jędrzej Nowacki" wrote: On torsdag 10. november 2016 12.29.12 CET Oswald Buddenhagen wrote: > the easiest would be going with the normal approval rights,

Re: [Development] QCS2016 Session Notes - QUIPs for Qt

On torsdag 10. november 2016 12.29.12 CET Oswald Buddenhagen wrote: > the easiest would be going with the normal approval rights, but limit > the submit button to a "QUIP owners" group which would consist of lars > (and possibly a _few_ deputies). Considering expected traffic there it could be

Re: [Development] QCS2016 Session Notes - QUIPs for Qt

On Wed, Nov 09, 2016 at 06:49:08PM +, Edward Welbourne wrote: > > Agree with meta/quips > > +1, > the repository has been created. next point: permissions. i don't think the regular ones are appropriate - they are way too anarchic for a process that is supposed to reflect *actual* community

Re: [Development] QCS2016 Session Notes - QUIPs for Qt

> Agree with meta/quips +1, Eddy. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] QCS2016 Session Notes - QUIPs for Qt

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/quip

Re: [Development] QCS2016 Session Notes - QUIPs for Qt

---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] QC

Re: [Development] QCS2016 Session Notes - QUIPs for Qt

> -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 No

Re: [Development] QCS2016 Session Notes - QUIPs for Qt

On 11/09/16 16:01, Oswald Buddenhagen wrote: > > i can offer meta/ as an alternative. +1 ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development

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

Re: [Development] QCS2016 Session Notes - QUIPs for Qt

+1 for qt/quips, I don't think of it as a web site thing either. -Louai _ From: Kai Koehne <kai.koe...@qt.io<mailto:kai.koe...@qt.io>> Sent: Tuesday, November 8, 2016 3:48 AM Subject: Re: [Development] QCS2016 Session Notes - QUIPs for Qt To: Oswald

Re: [Development] QCS2016 Session Notes - QUIPs for Qt

> -Original Message- > From: Development [mailto:development-bounces+kai.koehne=qt.io@qt- > project.org] On Behalf Of Oswald Buddenhagen > Sent: Tuesday, November 08, 2016 11:15 AM > To: development@qt-project.org > Subject: Re: [Development] QCS2016 Session No

Re: [Development] QCS2016 Session Notes - QUIPs for Qt

On Tue, Nov 08, 2016 at 09:11:23AM +, Lars Knoll wrote: > Yes, let’s get the repo created and this whole thing off the ground. > so, anyone has a concrete proposal for a fully qualified repository name? www/quips? > As noted, we need a better way to document results of discussions,

Re: [Development] QCS2016 Session Notes - QUIPs for Qt

Yes, let’s get the repo created and this whole thing off the ground. As noted, we need a better way to document results of discussions, decisions and processes. Grepping through a mailing list archive and trying to figure out which opinion prevailed in the end is not that ;-) Cheers, Lars On

Re: [Development] QCS2016 Session Notes - QUIPs for Qt

Louai Al-Khanji said: > this is not a bureaucratization process. It is about having a way to document the final conclusions of discussions we already have. In the process, it shall also force us to be explicit and leave fewer dangling ambiguities, where different parties have subtly different

Re: [Development] QCS2016 Session Notes - QUIPs for Qt

velopment [mailto:development-bounces+kai.koehne=qt.io@qt- > project.org] On Behalf Of Tero Kojo > Sent: Monday, September 26, 2016 9:01 AM > To: Louai Al-Khanji <louai.al-kha...@qt.io>; development@qt-project.org > Subject: Re: [Development] QCS2016 Session Notes - QUI

Re: [Development] QCS2016 Session Notes - QUIPs for Qt

evelopment@qt-project.org > Subject: Re: [Development] QCS2016 Session Notes - QUIPs for Qt > > Hi, > > This initiative is much appreciated, thank you Louai! > Having been in the session at QtCon, I don't have any problems with the > proposed format and process as outlined in

Re: [Development] QCS2016 Session Notes - QUIPs for Qt

Sent: tiistai 20. syyskuuta 2016 1.45 > To: development@qt-project.org > Subject: [Development] QCS2016 Session Notes - QUIPs for Qt > > Hi all, > > Here are my notes from the QUIPs session. Thank you for your patience. :-) > > QUIPs are a proposed design process for

Re: [Development] QCS2016 Session Notes - QUIPs for Qt

21.09.2016, 12:34, "Friedemann Kleint" : > Hi, > > technically speaking: is using the .rst format set in stone? I find this > difficult to handle; one needs a local web server to view it AFAIK. .md > comes to mind as alternative? Are you implying that you need local web

Re: [Development] QCS2016 Session Notes - QUIPs for Qt

On quarta-feira, 21 de setembro de 2016 11:34:02 PDT Friedemann Kleint wrote: > Hi, > > technically speaking: is using the .rst format set in stone? I find this > difficult to handle; one needs a local web server to view it AFAIK. .md > comes to mind as alternative? How is that different from

Re: [Development] QCS2016 Session Notes - QUIPs for Qt

Hi, On 09/21/16 12:34, Friedemann Kleint wrote: > Hi, > > technically speaking: is using the .rst format set in stone? I find > this difficult to handle; one needs a local web server to view it > AFAIK. .md comes to mind as alternative? > We discussed this at QtCon and settled on ReStructured

Re: [Development] QCS2016 Session Notes - QUIPs for Qt

Hi, technically speaking: is using the .rst format set in stone? I find this difficult to handle; one needs a local web server to view it AFAIK. .md comes to mind as alternative? Regards, Friedemann -- Friedemann Kleint The Qt Company GmbH ___

Re: [Development] QCS2016 Session Notes - QUIPs for Qt

On terça-feira, 20 de setembro de 2016 22:30:56 PDT Sergio Ahumada wrote: > which 5-year-old feature are we missing? The new UI. I want to see all comment, in all files, from all reviews, along with the review message, in one page. The new UI also has the ability to comment on multiple lines

Re: [Development] QCS2016 Session Notes - QUIPs for Qt

On 20.09.2016 21:26, Thiago Macieira wrote: On terça-feira, 20 de setembro de 2016 19:04:07 PDT Filippo Cucchetto wrote: Really? Shouldn't be better to just announce a proposal on the mailing list and then shift the discussion and feedbacks on the codereview? It may come as a shock to you,

Re: [Development] QCS2016 Session Notes - QUIPs for Qt

I could agree, but basically you're saying that the problem is the tool and not the idea to discuss the details on the codereview. At the end a proposal is for sure a document (thus a sort of source file) and so gerrit would help matching the discussion with the actual version of the document

Re: [Development] QCS2016 Session Notes - QUIPs for Qt

On terça-feira, 20 de setembro de 2016 19:04:07 PDT Filippo Cucchetto wrote: > Really? > Shouldn't be better to just announce a proposal on the mailing list > and then shift the discussion and feedbacks > on the codereview? It may come as a shock to you, but the Gerrit user interface is horrible.

Re: [Development] QCS2016 Session Notes - QUIPs for Qt

My thinking. I’m fine to have initial discussions on the mailing list, but agreeing on and nailing down details will be a lot easier to do on codereview. Lars On 20/09/16 19:04, "Development on behalf of Filippo Cucchetto"

Re: [Development] QCS2016 Session Notes - QUIPs for Qt

Really? Shouldn't be better to just announce a proposal on the mailing list and then shift the discussion and feedbacks on the codereview? 2016-09-20 18:46 GMT+02:00 Thiago Macieira : > On terça-feira, 20 de setembro de 2016 08:54:05 PDT Lars Knoll wrote: >> And it

Re: [Development] QCS2016 Session Notes - QUIPs for Qt

On terça-feira, 20 de setembro de 2016 08:54:05 PDT Lars Knoll wrote: > And it formalizes the way we can discuss and comment on things, as QUIPs > would be reviewed in codereview, then approved there. I believe it’ll lead > to a better workflow and better decision making in the project than >

Re: [Development] QCS2016 Session Notes - QUIPs for Qt

> [*] https://wiki.qt.io/Template:QUIP > If someone with more Wiki-template-foo could please review this, I'm > sure it can be improved; in particular, it uses 000{{{1}}} where clearly > some analogue of formatting {{{1}}} with %03d would be more apt. Sorry, obviously I meant %04d ...

Re: [Development] QCS2016 Session Notes - QUIPs for Qt

On 20/09/16 09:27, "Development on behalf of Thiago Macieira" wrote: On terça-feira, 20 de setembro de 2016 09:02:11 PDT André Somers wrote: > So, could you please explain, preferably without

Re: [Development] QCS2016 Session Notes - QUIPs for Qt

On terça-feira, 20 de setembro de 2016 09:02:11 PDT André Somers wrote: > So, could you please explain, preferably without relying on all the > acronyms, what problems this bureaucratization effort is trying to > resolve, and how it fits the rest of our work flow (like making feature > requests in

Re: [Development] QCS2016 Session Notes - QUIPs for Qt

Hi, Thanks for posting this, it finally cleared up a few postings by Thiago from just after the event. I wrestled my way through this whole thing, trying to get through the self-referential nature of all the acronyms. Somewhere in the middle I finally found what a QUIP is supposed to be.

[Development] QCS2016 Session Notes - QUIPs for Qt

Hi all, Here are my notes from the QUIPs session. Thank you for your patience. :-) QUIPs are a proposed design process for Qt, modeled after Python’s PEPs. QUIP 1 introduces the general concept: http://quips-qt-io.herokuapp.com/quip-0001.html QUIP 2 details the Qt governance model, it’s