<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
+1<br>
<br>
<div class="moz-cite-prefix">On 05/26/2015 09:29 PM, Samuel
Greenfeld wrote:<br>
</div>
<blockquote
cite="mid:CA+cAqjP9f9-8FYWFSWDJrWRWwqR4AFcDP-u4Lp-ad=LB+2qj1Q@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>Looking at past minutes, I think I am proposing more of a
change in procedure than topics for the oversight meeting. We
need to get more people involved than are present in the IRC
meetings.<br>
<br>
</div>
<div>In general I am echoing what was said on the "Planning for
the Future" email thread from three months ago. <br>
<br>
But some topics (for the oversight meeting or an all-hands
meeting) would be:<br>
</div>
<br>
<ol>
<li>What can Sugar publicly commit to having in terms of
users/developers/finances/etc. beyond what was mentioned in
the deployment survey.<br>
<br>
Witness Dan's complaints over the 3 million number, James
noting no one filed a bug report for Sugar 0.105.1 yet, the
lack of candidates for past elections, the lack of
interaction between the XS development and Sugar development
communities, etc.<br>
<br>
It also would be useful to know what users/developers/etc.
could publicly commit to Sugar.<br>
<br>
<br>
</li>
<li>What is being done to address the main issues raised by
deployments in the latest development survey.<br>
<br>
<br>
</li>
<li>A complete holistic overhaul of how releases are done and
marketed. Sugar was originally created with a "if you build
it, they will come" approach that many community members
have at least privately complained about.<br>
<br>
We need real-world examples of how to integrate Sugar with
curriculums, reference deployments willing to speak with
prospective ones, etc.<br>
<br>
Setting up Sugar needs to be no harder than a child using it
for the first time.<br>
<br>
<br>
</li>
<li>What is being done to attract new deployments, developers
(besides GSoC) and project sponsors.<br>
<br>
<br>
</li>
<li>I would like to propose a "Sugar Ambassador" program
similar to the Fedora one where less-technical members of
the community could engage with other groups to figure out
what they would need to use Sugar. This does not
necessarily mean that we need to fly them everywhere; but it
would give us a good idea of what might be required to
obtain gain certain types of deployments.<br>
<br>
</li>
</ol>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Tue, May 26, 2015 at 1:47 PM, Walter
Bender <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:walter.bender@gmail.com" target="_blank">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 dir="ltr">The next Sugar Labs oversight board meeting
is on Monday. Anyone in the community is, as always,
welcome to suggest discussion topics.
<div><br>
</div>
<div>-walter</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote"><span class="">On Tue, May 26,
2015 at 1:28 PM, Samuel Greenfeld <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:samuel@greenfeld.org" target="_blank">samuel@greenfeld.org</a>></span>
wrote:<br>
</span>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
<div class="h5">
<div dir="ltr">
<div>
<div>
<div>I know there have been various board
and development meetings for Sugar.<br>
<br>
But I would like to propose having an
"all-hands" meeting where anyone in the
Sugar community as well as related groups
(deployments, schoolserver, etc.) could
raise a topic and attend.<br>
</div>
<br>
</div>
If there are few enough people, we might be
able to do this with a Google Hangout. For
larger crowds we should try to get permission
to use an international conference bridge (to
avoid a dozen echo cancelers getting confused
by each other).<br>
<br>
</div>
<div>There are a lot of things that need to be
done that I suspect could happen given a wider
audience.<br>
</div>
<div><br>
---<br>
</div>
<div>SJG<br>
</div>
</div>
<br>
</div>
</div>
_______________________________________________<br>
Sugar-devel mailing list<br>
<a moz-do-not-send="true"
href="mailto:Sugar-devel@lists.sugarlabs.org"
target="_blank">Sugar-devel@lists.sugarlabs.org</a><br>
<a moz-do-not-send="true"
href="http://lists.sugarlabs.org/listinfo/sugar-devel"
target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a><br>
<br>
</blockquote>
</div>
<span class="HOEnZb"><font color="#888888"><br>
<br clear="all">
<div><br>
</div>
-- <br>
<div>Walter Bender<br>
Sugar Labs<br>
<a moz-do-not-send="true"
href="http://www.sugarlabs.org" target="_blank">http://www.sugarlabs.org</a><br>
</div>
</font></span></div>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Sugar-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Sugar-devel@lists.sugarlabs.org">Sugar-devel@lists.sugarlabs.org</a>
<a class="moz-txt-link-freetext" href="http://lists.sugarlabs.org/listinfo/sugar-devel">http://lists.sugarlabs.org/listinfo/sugar-devel</a>
</pre>
</blockquote>
<br>
</body>
</html>