<p dir="ltr"><br /> On 15 Sep 2013 18:55, "Andrew Dunstan" <<a
href="mailto:andrew@dunslane.net">andrew@dunslane.net</a>>wrote:<br /> ><br /> ><br /> > On 09/15/2013
05:52PM, Jeff Janes wrote:<br /> ><br /> >> On Sun, Sep 15, 2013 at 6:51 AM, Peter Eisentraut <<a
href="mailto:peter_e@gmx.net">peter_e@gmx.net</a><mailto:<a
href="mailto:peter_e@gmx.net">peter_e@gmx.net</a>>>wrote:<br /> >><br /> >> On Sat, 2013-09-14 at
22:15+0200, Dimitri Fontaine wrote:<br /> >> ><br /> >> > This proposal comes with no patch
becauseI think we are able to<br /> >> > understand it without that, so that it would only be a waste
of<br/> >> > everybody's time to attach code for a random solution on the<br /> >> list here<br
/>>> > to that email.<br /> >><br /> >> It shouldn't be in the commit fest if it has no
patch.<br/> >><br /> >><br /> >> I thought the general recommendation was the opposite, that planning
androad maps should be submitted for review before non-trivial coding is started; and that despite the name the
commitfestis the best way that this is done. Of course now I can't find the hackers thread where this recommendation
wasmade...<br /> >><br /> >><br /> ><br /> > It is unquestionably correct that roadmaps and planning
shouldbe made available for review and discussion. But the assertion that this should be done via the commitfest is
not.The commitfest app has never been for anything other than code, that I am aware of, and I am quite sure you will
findfierce resistance to any notion that design discussions should take place anywhere but on this mailing list.<br
/><pdir="ltr">Well the code reviews should also go via the list so that's neither here nor there.<p dir="ltr">One of
theoriginal problems the commitfest was aiming to solve was Tay people would had be a project, make some tentative
progress,ask if they're on the right track or how to tackle some problem, hear nothing until feature freeze at which
pointthe original author had moved on and dropped the project.<p dir="ltr">In other words, "forcing the issue" is one
ofthe original design goals of commitfests.
