As an advocate for Sugar in the field in my work, I'm chiming in to support Walter's point. <div><br></div><div>What might help Sugar is a designer who can articulate a strong design point of view by understanding the needs of the users and translating them, guided by the Sugar core design principles, into a plan for development. <div>
<br></div><div>Design is not a set of isolated decisions about what features to add or take away but how to move consistently toward a goal, in Sugar's case an OS and computing environment that can help children as they learn. </div>
<div><br></div><div>Designers have particular skills that are not obvious. Good ones are masters at modeling the needs of users in astonishing detail and accuracy, and it is their job to negotiate the terrain between the stated design goals of an organization, the user experience, and the implementation by developers. </div>
<div><br></div><div>It's not only Apple that has a distinct design point of view but really any company that makes a product that works and grows. So Bernie, I think what you were asking for is not a Dictator, who suggests, approves or denies features, but someone to lead by articulating the user model and helping the community develop it in a coordinated effort. </div>
<div><br></div><div>Barbara</div><div><br></div><div>~~~~~~~~~~~~~~~~~~~~~</div><div>Barbara Barry, PhD</div><div>Director of Learning</div><div>One Laptop per Child Foundation</div><div>OLPC Middle East</div><div><br></div>
<div><br></div><div><br></div><div><br></div><div><br></div><div><br><br><div class="gmail_quote">On Sat, Nov 20, 2010 at 8:42 AM, Walter Bender <span dir="ltr"><<a href="mailto:walter.bender@gmail.com">walter.bender@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><div></div><div class="h5">On Sat, Nov 20, 2010 at 4:32 AM, Martin Dengler<br>
<<a href="mailto:martin@martindengler.com">martin@martindengler.com</a>> wrote:<br>
> On Fri, Nov 12, 2010 at 12:06:56AM -0500, Michael Stone wrote:<br>
>> Martin and I talked for bit this evening and I believe that I managed to<br>
>> persuade him to support my [UI Dictator team] proposal.<br>
><br>
> I do, for the reasons mentioned in Michael's "key arguments".<br>
><br>
>> P.S. - Later [...] we discovered a confusion about the mandate of<br>
>> the proposed committee; to wit:<br>
>><br>
>> Is the main purpose of the committee to act as a UI Maintainer (e.g., by<br>
>> deciding which UI-related patches to merge) or is the main purpose of the<br>
>> committee to make UI-related decisions on an as-requested basis?<br>
><br>
> I think it is both act as maintainer and make UI-related decisions.<br>
> It seems we're re-invented the Design Team. I spoke with Gary Martin<br>
> and Bernie and, despite having lost the logs of my conversation with<br>
> Gary, my hazy recollection is that that they also came to this<br>
> conclusion.<br>
><br>
> With that in mind, I think we should just have more people actively<br>
> participate in the design team. I'm interested, so have put my name<br>
> down on <a href="http://wiki.sugarlabs.org/go/Design_Team/Contacts#Team_Members" target="_blank">http://wiki.sugarlabs.org/go/Design_Team/Contacts#Team_Members</a><br>
> . I hope anyone else interested in being active, will do the same.<br>
> Michael Stone, Bernie Innocenti, I'm looking at you.<br>
><br>
> Gary, can you add / correct anything from our conversation?<br>
><br>
> Michael, is there anything I've misunderstood/misremembered about your<br>
> proposal? Would you want the Design Team to adopt your "what does the<br>
> committee do"[1] responsibilities?<br>
><br>
> Martin<br>
><br>
> [1] <a href="http://lists.sugarlabs.org/archive/sugar-devel/2010-November/028615.html" target="_blank">http://lists.sugarlabs.org/archive/sugar-devel/2010-November/028615.html</a><br>
><br>
><br>
</div></div><div class="im">> _______________________________________________<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>
><br>
><br>
<br>
</div>I mostly kind of agree with this. But adding a bunch of developers to<br>
the design team will not help it accomplish its design goals. We need<br>
more designers involved. And we need to stay focused on Sugar's core<br>
design principles. One thing I do remember from your IRC discussion<br>
with Gary (I was on the edge of the conversation) is the need to bring<br>
the HIG up to date. While this may be considered tactical, I think it<br>
is strategic, in that sets the tone for all further actions. (For the<br>
same reason, I have been advocating for an architectural document from<br>
the Engineering perspective.)<br>
<br>
-walter<br>
<font color="#888888"><br>
--<br>
Walter Bender<br>
Sugar Labs<br>
<a href="http://www.sugarlabs.org" target="_blank">http://www.sugarlabs.org</a><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></div></div>