Yes, let's remove the 'potential naming conventions' section; it doesn't belong in this particular document.<br><br>> I happen to think that the dual-desktop Sugar/Gnome approach of the <br>> XO-1.5 is brilliant and I'd like to see it on every Gnome desktop for example.<br>
<br>+100. Indeed, getting Gnome design mavens to weigh in and find fault with and help out with Sugar development so that they are comfortable with that would be an excellent community-building exercise. <br><br>SJ<br><br>
<br><div class="gmail_quote">On Thu, Oct 29, 2009 at 5:04 PM, Sean DALY <span dir="ltr"><<a href="http://sdaly.be">sdaly.be</a>@<a href="http://gmail.com">gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
My apologies for the delay, I've had a very full plate.<br>
<br>
I wish to comment on Question 2, "Should SL be neutral about<br>
<div class="im">distributions containing Sugar, and refuse to endorse one over<br>
another?"<br>
<br>
</div>This question is unfortunately ambiguous. Let me explain, then answer<br>
it in the manner of my Norman forbears ;-)<br>
<br>
A key part of the Sugar Labs message is that hardware is secondary -<br>
that Sugar should potentially run on most anything; one could say<br>
"hardware-agnostic".<br>
<br>
Implied in that message is that operating systems are secondary, too.<br>
The VirtualBox solutions are well-crafted with their approach of<br>
aiding parents and teachers get Sugar up and running without<br>
installing an entirely new OS just to do so.<br>
<br>
Distributions are secondary as well. They provide the basis for Sugar<br>
to run, but for classroom needs, the less said the better; an ideal<br>
Sugar machine is turned on and shows the Home View shortly after,<br>
finds the rest of the class on the network, and so on.<br>
<br>
This is not to demean the enormous work that goes into distributions<br>
to work on varied hardware, nor to make Sugar work over the varied<br>
distributions (and I'm not forgetting the enormous XS school server<br>
work). It's just that Sugar benefits from the meme that the distro or<br>
hardware is irrelevant. Sugar benefits because the industry-centric<br>
discussion of "Windows machines versus Apple machines versus Linux<br>
machines" becomes an education-centric discussion of "how best to help<br>
children learn with a screen on a computing device".<br>
<br>
Concerns about preferable treatment towards one distro or another<br>
distract from a supertruth: the true competitor of Sugar and the<br>
distros it runs on is the system preinstalled on most PCs, which today<br>
is Microsoft Windows.<br>
<br>
There is a key difference between the GNU/Linux distributions and the<br>
two other predominant proprietary operating systems: GNU/Linux systems<br>
are open and thus closest to our education mission of "low floor, no<br>
ceiling".<br>
<br>
>From a marketing perspective - the point of view of "how best to<br>
inform millions of teachers that there is an alternative?" - we are<br>
obliged to seem to "endorse" one distro over another. But that's a<br>
function of our combat to find a place for Sugar, not playing<br>
favorites... "The right tool for the job". On a grassy hillside, we<br>
send in the cavalry; on a swift river, we launch the boats. Worrying<br>
about preferring the cavalry to the marines misses the point of our<br>
objective... nobody would send the boats up the hill.<br>
<br>
So. Fedora is playing a key role in the OLPC-OS and on today's Sugar<br>
on a Stick for the forseeable future; however, it's weak with OEMs and<br>
in education. Not to worry, Ubuntu is gaining traction with OEMs (cf.<br>
M. Shuttleworth goal: "Ubuntu as the default alternative to Windows").<br>
meanwhile, OpenSuSE has the most complete education-oriented offer and<br>
LTSP work. Other distros offer different advantages; the list goes on.<br>
The Try Sugar page should be a colorful garden of choices available;<br>
which shouldn't stop us from prominently recommending (as opposed to<br>
"endorsing", which implies exclusivity) a low-risk way to experience<br>
Sugar to bewildered first-time visitors.<br>
<br>
Today, Sugar on a Stick is the pillar of our marketing and<br>
brand-building because it disassociates Sugar from the XO or indeed<br>
any hardware; it makes Sugar instantly understandable to anyone that<br>
it is software. As a Sugar Labs brand, it needs to be protected. To be<br>
supported, it needs to be a stable software stack. None of which<br>
precludes anyone from doing any liveUSB they wish with Sugar on it; it<br>
just shouldn't be called Sugar on a Stick.<br>
<br>
I've said before that our marketing mix would inevitably need<br>
adjustments as OEM deals happen. Such deals will mean Sugar reliably<br>
preinstalled and supported on thousands of machines, a fabulous<br>
development for children. This would not be bad news for Sugar on a<br>
Stick, which I believe will remain the best way to try (and possibly<br>
the best way to deploy) Sugar for years to come; as the OLPC XOs will<br>
remain Sugar's native home and overwhelming installed base for years<br>
to come (supporting which I feel as a personal responsibility).<br>
Rather, all these ways will together contribute to the perception that<br>
Sugar will work on something old, something new, something borrowed,<br>
something blue.<br>
<br>
(On a related topic, we are not even debating the role of desktops,<br>
which only goes to show how poorly their role is perceived in the<br>
stack, particularly in comparison to distros. I happen to think that<br>
the dual-desktop Sugar/Gnome approach of the XO-1.5 is brilliant and<br>
I'd like to see it on every Gnome desktop for example.)<br>
<br>
So yes, we should be neutral about distros in general, while choosing<br>
the best distros for solving the challenges we face... at the risk of<br>
appearing to "endorse" one over another, or two over five, or four<br>
over nine, or whatever.<br>
<br>
thanks<br>
<br>
Sean<br>
<br>
P.S. The potential naming conventions section is a marketing<br>
discussion, and although it's an attempt to seek solutions, it<br>
unfortunately completely disregards how the existing brand is being<br>
built.<br>
<div><div></div><div class="h5"><br>
<br>
<br>
<br>
<br>
On Tue, Oct 27, 2009 at 11:14 PM, Sean DALY <<a href="http://sdaly.be" target="_blank">sdaly.be</a>@<a href="http://gmail.com" target="_blank">gmail.com</a>> wrote:<br>
> I need to express my position on the two questions I haven't yet.<br>
><br>
> I will do so tomorrow, it's late I'm a bit tired to express myself<br>
> clearly tonight.<br>
><br>
> thanks<br>
><br>
> Sean<br>
><br>
><br>
> On Tue, Oct 27, 2009 at 6:05 PM, Samuel Klein <<a href="http://meta.sj" target="_blank">meta.sj</a>@<a href="http://gmail.com" target="_blank">gmail.com</a>> wrote:<br>
>> We are close to consensus consensus on the first two points. Help with<br>
>> wording a final report would be appreciated. I wish I could extrapolate<br>
>> Bill B's position from some of his earlier comments, but I cannot :)<br>
>><br>
>> We don't have consensus on the specific wording of the 3rd question, but do<br>
>> on the underlying principle of 'not being confusing' -- there are two<br>
>> suggestions that a more specific name than "Sugar on a Stick" be used, as<br>
>> that name is a normal English phrase and could naturally refer to a whole<br>
>> class of distributions.<br>
>><br>
>> Since there's already a mailing list and some history behind "Sugar on a<br>
>> Stick", are there any others on this list that would like to see a more<br>
>> specific name? Does anyone expect this list to refer to all distributions<br>
>> of Sugar on removable devices, or is there broad agreement that this is for<br>
>> a specific team, concept, and product?<br>
>><br>
>> Finally, are there any other questions that have been raised that people<br>
>> feel we should address?<br>
>><br>
>> SJ<br>
>><br>
>> On Thu, Oct 22, 2009 at 11:51 PM, Benjamin M. Schwartz<br>
>> <<a href="mailto:bmschwar@fas.harvard.edu">bmschwar@fas.harvard.edu</a>> wrote:<br>
>>><br>
>>> Samuel Klein wrote:<br>
>>> > Ben, Bill, DSD and Faisal -- can you please weigh in and share your<br>
>>> > thoughts?<br>
>>><br>
>>> Happy to.<br>
>>><br>
>>> "Should Sugar Labs be a GNU/Linux distributor, rather than just an<br>
>>> upstream producing Sugar releases?"<br>
>>><br>
>>> Yes. Sugar Labs should do whatever is needed to make Sugar easily<br>
>>> available to our audience. When this goal is best achieved by<br>
>>> distributing complete operating systems including Sugar, we should have no<br>
>>> qualms about doing so. However, Sugar Labs should also continue to<br>
>>> emphasize the availability of Sugar through the mechanisms of existing<br>
>>> distro package managers, in order to reach users who already run GNU.<br>
>>><br>
>>> "Should SL be neutral about distributions containing Sugar, and refuse to<br>
>>> endorse one over another?"<br>
>>><br>
>>> Yes. Sugar Labs does not now have a mechanism for making blanket<br>
>>> endorsements, and it should not instate one. Conversely, Sugar Labs<br>
>>> should help users to choose their best option for deploying Sugar,<br>
>>> depending on their individual needs, and this will typically mean<br>
>>> recommending a particular distribution best suited for each user.<br>
>>><br>
>>> "Should 'Sugar on a Stick' be a phrase that SL asks its community to avoid<br>
>>> using unless they refer to the SoaS-Fedora distribution?"<br>
>>><br>
>>> No. We should give this distribution a unique, identifiable name that<br>
>>> cannot be confused with a generic description of an entire class of<br>
>>> distributions.<br>
>>><br>
>><br>
>><br>
>> _______________________________________________<br>
>> SoaS mailing list<br>
>> <a href="mailto:SoaS@lists.sugarlabs.org">SoaS@lists.sugarlabs.org</a><br>
>> <a href="http://lists.sugarlabs.org/listinfo/soas" target="_blank">http://lists.sugarlabs.org/listinfo/soas</a><br>
>><br>
>><br>
><br>
</div></div></blockquote></div><br>