<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Hi Walter,</p>
<p>To your questions, the following ones are already resolved:<br>
</p>
> * To what extent should the community be engaged?
<div>> * What are the requirements for communication with the
oversight board? With the community?</div>
<div>> * Are there restrictions on how funds will be used (above
and beyond the ones imposed by the SFC)?</div>
<div>> * Will the project administrator have to get SLOB approval
for spending those funds? For each expenditure or just the overall
budget?</div>
<div>> * Is there any expectation of financial reporting?</div>
<p>Please review (again) the following principles (pasted after my
message) which are <b>the main reason </b>I joined Sugar Labs,
copied from the <a moz-do-not-send="true"
href="https://wiki.sugarlabs.org/go/Sugar_Labs">main wiki page</a>
that describes Sugar Labs.</p>
<p>They are very clear with regard to what the expectations are for
<b>everyone </b>here. It is not just expected that we <i>report
</i>when working in the name of Sugar Labs<i>. </i>It is expected
that we <i>work <b>in plain view</b>.</i> It is expected that we
don't have private communications unless we absolutely must. It
also sets the expectation that goods belonging to Sugar Labs are
properly accounted for and up to date.</p>
<p>Unless you disagree with our organizational principles, it would
seem like a distraction of everyone's time to raise the questions
above.<br>
</p>
<p>Regards,</p>
<p>Sebastian<br>
</p>
<h3 style="break-after: avoid; font-weight: bold; color: rgb(0, 0,
0); font-family: "Times New Roman"; font-style: normal;
font-variant-ligatures: normal; font-variant-caps: normal;
letter-spacing: normal; orphans: 2; text-align: start;
text-indent: 0px; text-transform: none; white-space: normal;
widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px;
background-color: rgb(255, 255, 255); text-decoration-style:
initial; text-decoration-color: initial;"><a
moz-do-not-send="true"
href="https://wiki.sugarlabs.org/go/Sugar_Labs">https://wiki.sugarlabs.org/go/Sugar_Labs</a><br>
<span class="mw-headline" id="Principles" style="cursor:
url("https://wiki.sugarlabs.org/images/1/10/TextSmall.cur"),
text;"></span></h3>
<h3 style="break-after: avoid; font-weight: bold; color: rgb(0, 0,
0); font-family: "Times New Roman"; font-style: normal;
font-variant-ligatures: normal; font-variant-caps: normal;
letter-spacing: normal; orphans: 2; text-align: start;
text-indent: 0px; text-transform: none; white-space: normal;
widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px;
background-color: rgb(255, 255, 255); text-decoration-style:
initial; text-decoration-color: initial;"><span
class="mw-headline" id="Principles" style="cursor:
url("https://wiki.sugarlabs.org/images/1/10/TextSmall.cur"),
text;">Principles</span></h3>
<p style="widows: 3; orphans: 3; margin: 1em 0px; line-height:
1.2em; cursor:
url("https://wiki.sugarlabs.org/images/1/10/TextSmall.cur"),
text; color: rgb(0, 0, 0); font-family: "Times New
Roman"; font-size: medium; font-style: normal;
font-variant-ligatures: normal; font-variant-caps: normal;
font-weight: normal; letter-spacing: normal; text-align: start;
text-indent: 0px; text-transform: none; white-space: normal;
word-spacing: 0px; -webkit-text-stroke-width: 0px;
background-color: rgb(255, 255, 255); text-decoration-style:
initial; text-decoration-color: initial;">In order for Sugar to be
successful, it needs the participation of a large number of people
who share common goals while maintaining independence, so that
each participant has the ability to act independently. For these
reasons, Sugar Labs subscribes to the principles described<span> </span><a
rel="nofollow" class="external text"
href="http://flors.wordpress.com/2008/05/04/the-paradigm-of-the-open-organization/"
style="color: inherit !important; background: transparent;
padding: 0px !important; text-decoration: inherit !important;
border-bottom: 1px dotted lightgrey;">here</a>, which are the
author's own translation of an<span> </span><a rel="nofollow"
class="external text"
href="http://web.archive.org/web/20050317231119/http://interactors.coop/organizacionabierta"
style="color: inherit !important; background: transparent;
padding: 0px !important; text-decoration: inherit !important;
border-bottom: 1px dotted lightgrey;">original text in Spanish.</a></p>
<h4 style="break-after: avoid; font-weight: bold; color: rgb(0, 0,
0); font-family: "Times New Roman"; font-size: medium;
font-style: normal; font-variant-ligatures: normal;
font-variant-caps: normal; letter-spacing: normal; orphans: 2;
text-align: start; text-indent: 0px; text-transform: none;
white-space: normal; widows: 2; word-spacing: 0px;
-webkit-text-stroke-width: 0px; background-color: rgb(255, 255,
255); text-decoration-style: initial; text-decoration-color:
initial;"><span class="mw-headline" id="Identity" style="cursor:
url("https://wiki.sugarlabs.org/images/1/10/TextSmall.cur"),
text;">Identity</span></h4>
<ul style="list-style-type: square; cursor:
url("https://wiki.sugarlabs.org/images/1/10/TextSmall.cur"),
text; color: rgb(0, 0, 0); font-family: "Times New
Roman"; font-size: medium; font-style: normal;
font-variant-ligatures: normal; font-variant-caps: normal;
font-weight: normal; letter-spacing: normal; orphans: 2;
text-align: start; text-indent: 0px; text-transform: none;
white-space: normal; widows: 2; word-spacing: 0px;
-webkit-text-stroke-width: 0px; background-color: rgb(255, 255,
255); text-decoration-style: initial; text-decoration-color:
initial;">
<li>Clear mission – Fully disclosed objectives.</li>
<li>Declared commitments – Affinities and aversions explained.</li>
<li>Declared outside connections – Relationships with other
organizations explicitly listed.</li>
</ul>
<h4 style="break-after: avoid; font-weight: bold; color: rgb(0, 0,
0); font-family: "Times New Roman"; font-size: medium;
font-style: normal; font-variant-ligatures: normal;
font-variant-caps: normal; letter-spacing: normal; orphans: 2;
text-align: start; text-indent: 0px; text-transform: none;
white-space: normal; widows: 2; word-spacing: 0px;
-webkit-text-stroke-width: 0px; background-color: rgb(255, 255,
255); text-decoration-style: initial; text-decoration-color:
initial;"><span class="mw-headline" id="Structure" style="cursor:
url("https://wiki.sugarlabs.org/images/1/10/TextSmall.cur"),
text;">Structure</span></h4>
<ul style="list-style-type: square; cursor:
url("https://wiki.sugarlabs.org/images/1/10/TextSmall.cur"),
text; color: rgb(0, 0, 0); font-family: "Times New
Roman"; font-size: medium; font-style: normal;
font-variant-ligatures: normal; font-variant-caps: normal;
font-weight: normal; letter-spacing: normal; orphans: 2;
text-align: start; text-indent: 0px; text-transform: none;
white-space: normal; widows: 2; word-spacing: 0px;
-webkit-text-stroke-width: 0px; background-color: rgb(255, 255,
255); text-decoration-style: initial; text-decoration-color:
initial;">
<li>Horizontal organization – Teams and facilitators work on
responsibilities and agreements.</li>
<li>Identified contributors – Who is who, people are reachable.</li>
<li>Clear responsibilities – Who is in charge of what.</li>
<li>Activities described – All of the ongoing work is
acknowledged.</li>
</ul>
<p style="widows: 3; orphans: 3; margin: 1em 0px; line-height:
1.2em; cursor:
url("https://wiki.sugarlabs.org/images/1/10/TextSmall.cur"),
text; color: rgb(0, 0, 0); font-family: "Times New
Roman"; font-size: medium; font-style: normal;
font-variant-ligatures: normal; font-variant-caps: normal;
font-weight: normal; letter-spacing: normal; text-align: start;
text-indent: 0px; text-transform: none; white-space: normal;
word-spacing: 0px; -webkit-text-stroke-width: 0px;
background-color: rgb(255, 255, 255); text-decoration-style:
initial; text-decoration-color: initial;">See<span> </span><a
href="https://wiki.sugarlabs.org/go/Wiki_Team/Guide/Wiki_Structure"
title="Wiki Team/Guide/Wiki Structure" style="color: rgb(85, 34,
0); background: transparent; padding: 0px !important;
text-decoration: underline; border-bottom: 1px dotted
lightgrey;">Wiki Structure</a><span> </span>for a guide to how
the wiki models Sugar Labs' structure.</p>
<h4 style="break-after: avoid; font-weight: bold; color: rgb(0, 0,
0); font-family: "Times New Roman"; font-size: medium;
font-style: normal; font-variant-ligatures: normal;
font-variant-caps: normal; letter-spacing: normal; orphans: 2;
text-align: start; text-indent: 0px; text-transform: none;
white-space: normal; widows: 2; word-spacing: 0px;
-webkit-text-stroke-width: 0px; background-color: rgb(255, 255,
255); text-decoration-style: initial; text-decoration-color:
initial;"><span class="mw-headline" id="Operation" style="cursor:
url("https://wiki.sugarlabs.org/images/1/10/TextSmall.cur"),
text;">Operation</span></h4>
<ul style="list-style-type: square; cursor:
url("https://wiki.sugarlabs.org/images/1/10/TextSmall.cur"),
text; color: rgb(0, 0, 0); font-family: "Times New
Roman"; font-size: medium; font-style: normal;
font-variant-ligatures: normal; font-variant-caps: normal;
font-weight: normal; letter-spacing: normal; orphans: 2;
text-align: start; text-indent: 0px; text-transform: none;
white-space: normal; widows: 2; word-spacing: 0px;
-webkit-text-stroke-width: 0px; background-color: rgb(255, 255,
255); text-decoration-style: initial; text-decoration-color:
initial;">
<li>Open participation – Anybody can access the information and
get a first responsibility.</li>
<li>Meritocracy – Responsibilities are acquired (or lost) based on
one's skills, results, and contributors’ support.</li>
<li>Voluntary (non-)engagement – Nobody is forced to be involved
or to keep responsibilities.</li>
</ul>
<h4 style="break-after: avoid; font-weight: bold; color: rgb(0, 0,
0); font-family: "Times New Roman"; font-size: medium;
font-style: normal; font-variant-ligatures: normal;
font-variant-caps: normal; letter-spacing: normal; orphans: 2;
text-align: start; text-indent: 0px; text-transform: none;
white-space: normal; widows: 2; word-spacing: 0px;
-webkit-text-stroke-width: 0px; background-color: rgb(255, 255,
255); text-decoration-style: initial; text-decoration-color:
initial;"><font size="+1"><span class="mw-headline"
id="Information" style="cursor:
url("https://wiki.sugarlabs.org/images/1/10/TextSmall.cur"),
text;">Information</span></font></h4>
<ul style="list-style-type: square; cursor:
url("https://wiki.sugarlabs.org/images/1/10/TextSmall.cur"),
text; color: rgb(0, 0, 0); font-family: "Times New
Roman"; font-size: medium; font-style: normal;
font-variant-ligatures: normal; font-variant-caps: normal;
font-weight: normal; letter-spacing: normal; orphans: 2;
text-align: start; text-indent: 0px; text-transform: none;
white-space: normal; widows: 2; word-spacing: 0px;
-webkit-text-stroke-width: 0px; background-color: rgb(255, 255,
255); text-decoration-style: initial; text-decoration-color:
initial;">
<li><font size="+1">Regular reports – Reported activities and
future plans allow monitoring and participation.</font></li>
<li><font size="+1">Information accessible – Even internal
operational information is available by default.</font>
<dl style="cursor:
url("https://wiki.sugarlabs.org/images/1/10/TextSmall.cur"),
text;">
<dd><font size="+1">We try to operate<span> </span><i><b><a
href="https://wiki.sugarlabs.org/go/Archive/Current_Events/2009-06-10#En_plein_air"
title="Archive/Current Events/2009-06-10"
style="color: rgb(85, 34, 0); background:
transparent; padding: 0px !important;
text-decoration: underline; border-bottom: 1px
dotted lightgrey;">en plein air</a></b></i>.</font></dd>
</dl>
</li>
<li><font size="+1">Explicit confidentiality – It is explained
what matters are confidential, why, and who can access them.</font></li>
</ul>
<h4 style="break-after: avoid; font-weight: bold; color: rgb(0, 0,
0); font-family: "Times New Roman"; font-size: medium;
font-style: normal; font-variant-ligatures: normal;
font-variant-caps: normal; letter-spacing: normal; orphans: 2;
text-align: start; text-indent: 0px; text-transform: none;
white-space: normal; widows: 2; word-spacing: 0px;
-webkit-text-stroke-width: 0px; background-color: rgb(255, 255,
255); text-decoration-style: initial; text-decoration-color:
initial;"><font size="+1"><span class="mw-headline" id="Goods"
style="cursor:
url("https://wiki.sugarlabs.org/images/1/10/TextSmall.cur"),
text;">Goods</span></font></h4>
<ul style="list-style-type: square; cursor:
url("https://wiki.sugarlabs.org/images/1/10/TextSmall.cur"),
text; color: rgb(0, 0, 0); font-family: "Times New
Roman"; font-size: medium; font-style: normal;
font-variant-ligatures: normal; font-variant-caps: normal;
font-weight: normal; letter-spacing: normal; orphans: 2;
text-align: start; text-indent: 0px; text-transform: none;
white-space: normal; widows: 2; word-spacing: 0px;
-webkit-text-stroke-width: 0px; background-color: rgb(255, 255,
255); text-decoration-style: initial; text-decoration-color:
initial;">
<li><font size="+1">Economic model – Feasibility and
sustainability plans are exposed. (Please see/contribute to
the discussion<span> </span><a
href="https://wiki.sugarlabs.org/go/Sugar_Labs/Funding"
title="Sugar Labs/Funding" style="color: rgb(85, 34, 0);
background: transparent; padding: 0px !important;
text-decoration: underline; border-bottom: 1px dotted
lightgrey;">here</a>.)</font></li>
<li><font size="+1">Resources – Inventory of items detailing who
contributed what and why.</font></li>
<li><font size="+1">Public accounts – It’s clear where the money
comes from and where it goes.</font></li>
<li><font size="+1">A special<span> </span><a
href="https://wiki.sugarlabs.org/go/Sugar_Labs/Thank_You"
title="Sugar Labs/Thank You" style="color: rgb(85, 34, 0);
background: transparent; padding: 0px !important;
text-decoration: underline; border-bottom: 1px dotted
lightgrey;">thanks</a><span> </span>to our contributors.</font></li>
</ul>
<br class="Apple-interchange-newline">
<p></p>
<br>
<div class="moz-cite-prefix">On 18/09/17 14:57, Walter Bender wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CADf7C8sSOEmqTdLt4xXxh_4FAhKQoXD9NTUrhrYnVDui2xvLrA@mail.gmail.com">
<div dir="ltr">
<div>My apologies in advance for the length of this email. The
lists have been overwhelmed of late with discussions of
procedure and as a consequence, it feels as if technical and
pedagogical discussions have seemingly been marginalized.</div>
<div><br>
</div>
<div>---</div>
<div><br>
</div>
<div>I. TRAVEL ADVANCES</div>
<div><br>
</div>
<div>We had two topics of discussion we were going to consider
between the monthly meetings of the Sugar Labs oversight
board, both of which seemed to have stalled out.</div>
<div><br>
</div>
<div>The first topic was in regards to the process and
conditions under which we would consider travel advances. I
raise this issue now because it impacts Samson, who needs to
prepare his trip to Google well in advance of our next
meeting.</div>
<div><br>
</div>
<div>Laura stated the obvious in her wiki post, essentially: (1)
ask the oversight board and (2) if approved, the oversight
board would ask the SFC [1]. But this formulation doesn't
offer much guidance. What are the criteria for the decision? I
had written up some details in the wiki -- which were
subsequently deleted -- to try to address what I think are the
questions someone would reasonably be asking of us.</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div>(0) Before asking for a travel advance, please consider the
following questions:</div>
<div><br>
</div>
<div>* Is the travel on behalf of Sugar Labs?</div>
<div>* Has the trip been approved by the Sugar Labs oversight
board or some designated representative of the board?</div>
<div>* Do the travel plans comply with the SFC travel policy?
[2] </div>
<div>* Do you need to have a ticket purchased on your behalf?</div>
<div>* Do you need cash for local travel and/or per diem
expenses?</div>
<div><br>
</div>
<div>(1) Anyone traveling on behalf of Sugar Labs may request a
travel advance by sending a written request to the oversight
board <slobs AT <a href="http://lists.sugarlabs.org"
moz-do-not-send="true">lists.sugarlabs.org</a>>. Be sure
to include the reason for your request, the amount requested,
the anticipated dates of travel, and answers to the questions
above.</div>
<div><br>
</div>
<div>(2) The oversight board will discuss the request and may
ask for clarification. The criteria for approval include:</div>
<div><br>
</div>
<div>* availability of funds</div>
<div>* ???</div>
<div><br>
</div>
<div>It may take the board ''up to one week'' to reach its
decision, so please make your request as far in advance as
possible.</div>
<div> </div>
<div>The deliberations of the board will either be published on
a public email list [3] or in a meeting log [4]. The decision
itself will be documented on [5].</div>
<div> </div>
<div>(3) If the travel advance is approved (by at least four
board members) then our liaison with the SFC will communicate
the decision on behalf of the applicant. Note that approval by
the SL oversight board does not guarantee that the SFC will
approve the travel advance. (Past experience suggests that
they are more likely to approve the prepurchase of a ticket
than a cash advance.) The time-frame for the SFC varies widely
and is outside of our control, so again, it is recommended
that you make your request well in advance.</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div>I think it is imperative that the oversight board define
criteria for determining whether or not a travel advance be
considered. For example, we have been inconsistent in regard
to travel advances where a visa is required. We made no
contingency on Ignacio's request for a travel advance to
attend the Google Code-in (GCI) summit, where as we turned
down Samson's request for an advance to get a visa to attend
the Google Summer of Code (GSoC) summit. I would ask for more
clarification as to if and when we consider an advance for the
visa expenses to be acceptable.</div>
<div><br>
</div>
<div>Also, if a group or team (e.g. the GSoC mentors) decides to
send someone to a workshop or meeting and has the cash in hand
(Google funding in this case), are there further criteria that
the oversight board need consider? If so what?</div>
<div><br>
</div>
<div>---</div>
<div><br>
</div>
<div>II. EXTERNAL PROGRAMS</div>
<div><br>
</div>
<div>The second topic of discussion is in regards to the process
and guidelines by which community members engage in external
activities on behalf of Sugar Labs. The case in point is GCI.
We have been participating in GCI for for the past five years
(since 2012) and every year, I have asked the board for
permission to participate. But once granted that permission, I
have taken it upon myself to organize our application, recruit
mentors, solicit projects, and administer the program. I've
engaged the community along the way, holding public meeting
and utilizing the wiki extensively. I think this has worked
out well. I was prepared to proceed along the same lines again
this year, but given the heated climate on the board regarding
process, I thought we should clarify our guidelines first [6].</div>
<div><br>
</div>
<div>I raise this topic now as we will need a head start on our
GCI application before the next scheduled meeting.</div>
<div><br>
</div>
<div>As per above, what are the expectations for someone who
wants to organize a project on behalf of Sugar Labs?</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div>(0) Before asking for permission to engage in an external
activity on behalf of Sugar Labs, please consider the
following questions:</div>
<div><br>
</div>
<div>* To what extent does the project have to align with the
Sugar Labs mission?</div>
<div>* Is the project Free/Libre?<br>
</div>
<div>* Will the project be self-funding or does it require
funding from Sugar Labs?</div>
<div>* What are your qualifications for administering the
program?</div>
<div>* What involvement from the community is required to make
the project a success?</div>
<div>* Is there any risk to the Sugar Labs brand if the project
is not successful?</div>
<div>* [YOUR QUESTION HERE]</div>
<div><br>
</div>
<div>(2) The oversight board will discuss the request and may
ask for clarification. The criteria for approval include:</div>
<div><br>
</div>
<div>[WE NEED TO CONSIDER THESE QUESTIONS IN ORDER TO DEFINE THE
CRITERIA AND TO SET EXPECTATIONS]</div>
<div>* Who can run a project on behalf of Sugar Labs?</div>
<div>* Are there restrictions on the nature of the project?</div>
<div>* To what extent should the community be engaged?</div>
<div>* What are the requirements for communication with the
oversight board? With the community?</div>
<div>* Are there restrictions on how funds will be used (above
and beyond the ones imposed by the SFC)?</div>
<div>* Will the project administrator have to get SLOB approval
for spending those funds? For each expenditure or just the
overall budget?</div>
<div>* Is there any expectation of financial reporting?</div>
<div>* Is the new initiative redundant with or in conflict with
any existing programs?</div>
<div>* Does it require time and commitments from the community
that we cannot credibly fulfill?</div>
<div>* How do we resolve conflicts, such as when more than one
community member wants to administer the same program on
behalf of Sugar Labs?</div>
<div><br>
</div>
<div>It may take the board ''up to one week'' to reach its
decision, so please make your request as far in advance as
possible.</div>
<div> </div>
<div>The deliberations of the board will either be published on
a public email list [3] or in a meeting log [4]. The decision
itself will be documented on [5].</div>
<div> </div>
<div>(3) If the reuqest to engage in an external program on
behalf of Sugar Labs is approved (by at least four board
members) then our liaison with the SFC will communicate the
decision on behalf of the applicant. Note that approval by the
SL oversight board does not guarantee that the SFC will
approve the engagement. The time-frame for the SFC varies
widely and is outside of our control, so again, it is
recommended that you make your request well in advance.</div>
<div><br>
</div>
<div>If there is any contract involved, e.g, signing of a
contract, letter of intent, etc., the SFC will need to do this
on behalf of Sugar Labs. Please be sure to pass any such
material to our liaison to the SFC for processing.</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div>These questions and procedures may seem abstract, but they
have come up again and again in past programs I have been
involved in. For example, when I wrote the Trip Advisor grant,
I ran the proposal past the SFC and SLOB before I submitted
it, including the budget. And I asked and was granted
permission from the oversight board to administer the program
as per the proposal and budget. And yet I have had to have
every allocation of funds -- for travel to workshops and for
translations -- approved individually as well. To me this has
been onerous, but it that is the level of oversight the board
requires, I accept it. But lets please be explicit and
consistent about our requirements and expectations.</div>
<div><br>
</div>
<div>Another example is GCI 2017. While I have been the one
initiating the program every year, and brought up the subject
again this year, I delayed asking for a motion to approve our
participation in anticipation of our establishing guidelines
for such requests [6]. In the meantime, another board member
proposed a motion that we participate, which, as expected,
passed. (I raised the issue of guidelines when casting my
vote.) What I didn't expect was that this same board member
would unilaterally begin community engagement for the program,
with no consultation with the team that had been running it
five years in a row. [7] Is it anything goes? Or do we have
some process by which the community members who have been
running a program on behalf of Sugar Labs are expected to be
consulted?</div>
<div><br>
</div>
<div>I would like to resolve these questions soon as we have a
lot of work to do if we are going to make a successful
application to GCI.</div>
<div><br>
</div>
<div>regards.</div>
<div><br>
</div>
<div>-walter</div>
<div><br>
</div>
<div>---</div>
<div><br>
</div>
<div>[1] <a href="https://wiki.sugarlabs.org/go/Procedures"
moz-do-not-send="true">https://wiki.sugarlabs.org/go/Procedures</a>
(Note: it would make sense to move this page to a subpage in
the Governance section of the wiki.)</div>
<div>[2] <a
href="https://github.com/conservancy/policies/blob/master/Travel/conservancy-travel-policy.txt"
moz-do-not-send="true">https://github.com/conservancy/policies/blob/master/Travel/conservancy-travel-policy.txt</a>
travel policy</div>
<div>[3] <a href="https://lists.sugarlabs.org"
moz-do-not-send="true">https://lists.sugarlabs.org</a></div>
<div>[4] <a
href="https://meeting.sugarlabs.org/sugar-meeting/meetings"
moz-do-not-send="true">https://meeting.sugarlabs.org/sugar-meeting/meetings</a></div>
<div>[5] <a
href="https://wiki.sugarlabs.org/go/Oversight_Board/Decisions"
moz-do-not-send="true">https://wiki.sugarlabs.org/go/Oversight_Board/Decisions</a></div>
<div>[6] <a
href="http://meeting.sugarlabs.org/sugar-meeting/meetings/2017-09-01"
moz-do-not-send="true">http://meeting.sugarlabs.org/sugar-meeting/meetings/2017-09-01</a> <br>
</div>
<div>[7] In #sugar on <a href="http://irc.freenode.net"
moz-do-not-send="true">irc.freenode.net</a> <kaametza>
I would like to ask everybody to start thinking in task-ideas
for the Code In this year</div>
<div><br>
</div>
<div><br>
</div>
-- <br>
<div class="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" moz-do-not-send="true"><font>http://www.sugarlabs.org</font></a></font><br>
<br>
</div>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
IAEP -- It's An Education Project (not a laptop project!)
<a class="moz-txt-link-abbreviated" href="mailto:IAEP@lists.sugarlabs.org">IAEP@lists.sugarlabs.org</a>
<a class="moz-txt-link-freetext" href="http://lists.sugarlabs.org/listinfo/iaep">http://lists.sugarlabs.org/listinfo/iaep</a></pre>
</blockquote>
<br>
</body>
</html>