On Sun, 2013-09-15 at 16:09 +0200, Dimitri Fontaine wrote: > Peter Eisentraut <pete...@gmx.net> writes: > > It shouldn't be in the commit fest if it has no patch. > > What should I do if my goal is to get community consensus on the best > way to solve a problem, and want to start the discussion with some > proposals?
Post it to the pgsql-hackers list. > My understanding is that a Commit Fest is mainly about Reviewing, that's > why I still added an entry for two designs that I need feedback on > before actually coding a solution. > > Writing the code is the easiest part of those proposals, but that's only > true as soon as we decide what code we should be writing. I understand why using the commit fest process is attractive for this, because it enables you to force the issue. But the point of the commit fest is to highlight patches whose discussion has mostly concluded and get them committed. If we add general discussion to the commit fest, it'll just become a mirror of the mailing list, and then we'll need yet another level of process to isolate the ready patches from that. -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
