<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Nov 8, 2016 at 11:12 AM, Tony Anderson <span dir="ltr"><<a href="mailto:tony_anderson@usa.net" target="_blank">tony_anderson@usa.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
Hi, Walter<br>
<br>
Currently for GSOC and GCI, we tell applicants to create a
development environment. I think that is a mistake. One of the great
strengths of Sugar is that it is it's own development environment.
For example, the design of Sugar is that Browse as an activity can
be installed directly as an xo bundle with a version number
independent of the Sugar version number. This, of course, has two
advantages - a new version of Browse can be used on earlier versions
of Sugar and the release of Sugar provides the ability to execute
Sugar activities but is not dependent on them.<br></div></blockquote><div><br></div><div>I don't understand what you are trying to say here re GCI. We have introductory tasks for setting up either the Sugar developer environment, installing from Sugar on a Stick, or installing the Sugarizer environment. Not sure how at least most coding tasks can proceed without one of those. Of course, some activities, e.g. the Python version of Turtle Blocks can run without Sugar and the individual JS apps can run in a browser, but what does that have to do with the example you cited? Could you please clarify?</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div text="#000000" bgcolor="#FFFFFF">
<br>
GCI can be a great opportunity to develop a Sugar release which can
be installed on standard PCs and supported by Sugar Labs. Possibly
a Debian release supported by Sugar Labs would be most flexible. In
this case there ctHould also be SD card images which work on models of
the Raspberry Pi. Such a release could be enhanced by users working
independently and then submitting their working changes for
incorporation in future official releases.<span class="HOEnZb"><font color="#888888"></font></span></div></blockquote><div><br></div><div>Do you mean a Windows PC? Getting a full Sugar running native in Windows is a bigger task than we can ask for in GCI. If you mean running on PC hardware, doesn't Sugar on a Stick or yum install Sugar on Ubuntu already do this?</div><div><br></div><div>That said, Alan got Turtle Blocks running in Windows. (I haven't tested it since I don't have access to a Windows box.) Maybe we could have tasks for doing the same for more activities?</div><div><br></div><div>regards.</div><div><br></div><div>-walter</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div text="#000000" bgcolor="#FFFFFF"><span class="HOEnZb"><font color="#888888">
<br>
Tony</font></span><div><div class="h5"><br>
<br>
<div class="m_-3300166787133034501moz-cite-prefix">On 11/07/2016 10:25 AM, Walter Bender
wrote:<br>
</div>
</div></div><blockquote type="cite"><div><div class="h5">
<div dir="ltr">Great news. Sugar Labs was once again accepted as
one of the organizations participating in Google Code In.
<div><br>
</div>
<div>We have a few weeks to prepare. If you are interested in
being a mentor, please contact me and also please sign up at <a href="https://codein.withgoogle.com" target="_blank"></a><a class="m_-3300166787133034501moz-txt-link-freetext" href="https://codein.withgoogle.com" target="_blank">https://codein.withgoogle.<wbr>com</a></div>
<div><br>
</div>
<div>If you have project/task ideas, please send them my way or
add them to the wiki page at <a href="https://wiki.sugarlabs.org/go/Google_Code_In_2016#This_is_a_stub_for_25.2B_example_tasks_new_for_GCI_2016" target="_blank">https://wiki.sugarlabs.org/<wbr>go/Google_Code_In_2016#This_<wbr>is_a_stub_for_25.2B_example_<wbr>tasks_new_for_GCI_2016</a>.</div>
<div><br>
</div>
<div>As always, I am very much looking forward to GCI.</div>
<div><br>
</div>
<div>regards.</div>
<div><br>
</div>
<div>-walter<br clear="all">
<div><br>
</div>
-- <br>
<div class="m_-3300166787133034501gmail_signature">
<div dir="ltr">
<div><font><font>Walter Bender</font></font><br>
<font><font>Sugar Labs</font></font></div>
<div><font><a href="http://www.sugarlabs.org" target="_blank"><font>http://www.sugarlabs.org</font></a></font><br>
<br>
</div>
</div>
</div>
</div>
</div>
<br>
<fieldset class="m_-3300166787133034501mimeAttachmentHeader"></fieldset>
<br>
</div></div><span class=""><pre>______________________________<wbr>_________________
Sugar-devel mailing list
<a class="m_-3300166787133034501moz-txt-link-abbreviated" href="mailto:Sugar-devel@lists.sugarlabs.org" target="_blank">Sugar-devel@lists.sugarlabs.<wbr>org</a>
<a class="m_-3300166787133034501moz-txt-link-freetext" href="http://lists.sugarlabs.org/listinfo/sugar-devel" target="_blank">http://lists.sugarlabs.org/<wbr>listinfo/sugar-devel</a>
</pre>
</span></blockquote>
<br>
</div>
<br>______________________________<wbr>_________________<br>
Sugar-devel mailing list<br>
<a href="mailto:Sugar-devel@lists.sugarlabs.org">Sugar-devel@lists.sugarlabs.<wbr>org</a><br>
<a href="http://lists.sugarlabs.org/listinfo/sugar-devel" rel="noreferrer" target="_blank">http://lists.sugarlabs.org/<wbr>listinfo/sugar-devel</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><font><font>Walter Bender</font></font><br><font><font>Sugar Labs</font></font></div><div><font><a href="http://www.sugarlabs.org" target="_blank"><font>http://www.sugarlabs.org</font></a></font><br><a href="http://www.sugarlabs.org" target="_blank"><font></font></a><br></div></div></div>
</div></div>