<br><br><div class="gmail_quote">On Wed, Oct 14, 2009 at 7:14 AM, Tomeu Vizoso <span dir="ltr"><<a href="mailto:tomeu@sugarlabs.org">tomeu@sugarlabs.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On Tue, Oct 13, 2009 at 03:40, Bernie Innocenti <<a href="mailto:bernie@codewiz.org">bernie@codewiz.org</a>> wrote:<br>
> El Mon, 12-10-2009 a las 22:36 -0400, Bernie Innocenti escribió:<br>
>> Hello,<br>
>><br>
>> Michael just passed by the Acetarium and, since the dinner was late, we<br>
>> found the time to test and review his latest prototype^W patch.<br>
>><br>
>> I'm loving how the menus suddenly are now snappy and responsive. Please,<br>
>> test it yourself and report back. If we like this change, I think we<br>
>> should go on and also kill the code that this patch makes redundant.<br>
>> (please, let's not add another configurable knob!)<br>
><br>
> BTW, Michael and I have a "small disagreement" on how a maintainer<br>
> should react to the present patch. From a purely functional PoV, this<br>
> patch is short, correct and low impact. Yeah, but... who's ever going to<br>
> clean up after it if we do not demand the cleanup to be merged<br>
> atomically with the patch that opens the need for it? Once the patch is<br>
> in, the maintainer would no longer have a stick to brandish while saying<br>
> "now eat your veggies!".<br>
><br>
> (Michael replies: "This is a flawed position because it leads to absurd<br>
> conclusions. More specifically, it actively discourages the current<br>
> contributor from submitting more patches by denying the satisfaction of<br>
> seeing their existing patch merged, delays the deferral of a correct and<br>
> believable patch that introduces behavior you yourself describe as<br>
> 'desirable' and, last but not least, misses an opportunity to involve<br>
> inexperienced contributors by providing appropriate "on-ramp" bugs like<br>
> the proposed refactoring.)<br>
<br>
</div>I'm more concerned about developers proposing big user experience<br>
changes because they feel it's better. Before I look at the patch I<br>
would like to know if there's agreement from people close to our users<br>
that this behavior change is desired. How can we get that?<br></blockquote><div><br></div><div>People could take both versions to a group of kids and video how it goes. </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
Thanks,<br>
<br>
Tomeu<br>
<font color="#888888"><br>
--<br>
«Sugar Labs is anyone who participates in improving and using Sugar.<br>
What Sugar Labs does is determined by the participants.» - David<br>
Farning<br>
</font><div><div></div><div class="h5">_______________________________________________<br>
Sugar-devel mailing list<br>
<a href="mailto:Sugar-devel@lists.sugarlabs.org">Sugar-devel@lists.sugarlabs.org</a><br>
<a href="http://lists.sugarlabs.org/listinfo/sugar-devel" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Caroline Meeks<br>Solution Grove<br>Caroline@SolutionGrove.com<br><br>617-500-3488 - Office<br>505-213-3268 - Fax<br>