This is just a gut reaction but I feel we should think more in the "Sugar online" direction than in the "Sugar on tablet" one, at least as a first step. I'd love Sugar on tablet as anyone else but I feel it's somewhat unrealistic because it involves skills, moneys and partnerships we don't currently have.<div>
<br></div><div>I also think we should not completely discard Sugar on netbooks (maybe ultrabooks feels less anachronistic? :P). The hybrids that are hitting the market lately might not be mature, cheap or extremely popular, but it's an interesting direction to explore ... Keyboards are not completely dead yet IMO!<br>
<div><br>On Thursday, 7 November 2013, Sean DALY wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">If we are talking about a version number that might make it into a press release at some point, this is a marketing discussion so I have cc'd the list.<div>
<br></div><div>As I've explained previously, the major issue with a v1 seven years after entering production is that it is incomprehensible. Non-techies (i.e. teachers) discovering Sugar will naturally assume there are 0 years of production behind it. Tech journalists will roll on the floor laughing at a Slashdot post e.g. "Seven Years After OLPC's First Laptop, Sugar Reaches V1".</div>
<div><br></div><div>We dealt with this problem when Sugar was numbered Sugar on a Stick v6 was renamed "Sugar on a Stick v1 Strawberry" and the press responded to an easy-to-understand story - that SL had spun off from OLPC and had a first non-OLPC version available. That the technical version number of the underlying Sugar was different was made irrelevant.</div>
<div><br></div><div>We need to do this again. The addition of browser support is a big deal. In my view Sugar should be publicly numbered v2, perhaps with a name i.e. "Sugar v2 Online" or "Sugar v2 Tablet" (or something - this needs marketing work), with a clear story: Sugar opens up a new direction after seven years of production.</div>
<div><br></div><div>The existing technical version numbering system has the merit of being understandable to developers and the deployments community and could be associated internally with the public number, i.e. 2.102, 2.104 etc., which would not box us into a numbering system we can't market. Or perhaps become irrelevant as Daniel N has suggested if we go to continuous development mode.</div>
<div><br></div><div>I have more grey hair than I did when I first proposed we go to v1 six years ago [1]...</div><div><br></div><div>(!)</div><div><br></div><div>So I think we are ready for v2.</div><div><br></div><div>Sean.</div>
<div><br></div><div>[1] <a href="http://lists.sugarlabs.org/archive/marketing/2008-November/000425.html" target="_blank">http://lists.sugarlabs.org/archive/marketing/2008-November/000425.html</a></div><div><br></div><div>
<br></div><div class="gmail_extra">
<br><br><div class="gmail_quote">On Thu, Nov 7, 2013 at 1:21 PM, Gonzalo Odiard <span dir="ltr"><<a href="javascript:_e({}, 'cvml', 'gonzalo@laptop.org');" target="_blank">gonzalo@laptop.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
We already have this discussion for Sugar 0.100,<br>
why not do it again? :)<br>
<br>
With more than 7 years of development and more than 2 million of users,<br>
probably we should accept a 1.0 version is deserved.<br>
<br>
With 6 months more, probably the web api will be more established,<br>
and we are not doing incompatible changes to the python api.<br>
<br>
Anybody have a Really Good Motive(r) to not do it?<br>
<br>
Gonzalo<br>
_______________________________________________<br>
Sugar-devel mailing list<br>
<a href="javascript:_e({}, 'cvml', 'Sugar-devel@lists.sugarlabs.org');" target="_blank">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>
</blockquote></div><br></div></div>
</blockquote></div></div><br><br>-- <br>Daniel Narvaez<br><br>