<div dir="ltr"><br><br><div class="gmail_quote">On Thu, Oct 9, 2008 at 11:50 PM, Steve Hodge <span dir="ltr"><<a href="mailto:stevehodge@gmail.com">stevehodge@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div dir="ltr"><div class="Ih2E3d"><br></div><div>Yes. I don't see the harm in people talking about features they would like to see provided they don't harass the devs about them. I don't think the "submit a patch" response adds anything to the discussion though. It tends to put people on the defensive because it can appear as if it's discounting the idea (i.e. people can take it as "the only way this is getting in is if you do it yourself"). And it doesn't really encourage people to actually get involved either as it can come across as "if you're not capable of making the patch then you should shut up". It just seems a little hostile really. What I'd like to see instead of just "submit a patch" is something like "this sounds easy/hard/impossible, but you could start looking at AClass/BPlugin/CLibrary code if you want to implement it".</div>
</div></blockquote><div><br></div><div>Then again, "submit a patch" also means your idea has merit and should be submitted as a patch but...</div><div><br></div><div>Kevin</div></div></div>