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" <development-bounces+lars.knoll=qt...@qt-project.org on behalf of filippocucche...@gmail.com> 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? 2016-09-20 18:46 GMT+02:00 Thiago Macieira <thiago.macie...@intel.com>: > 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 >> discussions on the mailing list that often end somewhat inconclusive. > > Discussions on content still happen on the mailing list for maximum > reachability. The discussion on codereview is just the editorial workflow. > > -- > Thiago Macieira - thiago.macieira (AT) intel.com > Software Architect - Intel Open Source Technology Center > > _______________________________________________ > Development mailing list > Development@qt-project.org > http://lists.qt-project.org/mailman/listinfo/development -- Filippo Cucchetto _______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development _______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development