<div dir="ltr"><br><div class="gmail_extra"><br><div>2017-03-01 22:38 GMT-05:00 Tony Anderson <span dir="ltr"><<a href="mailto:tony_anderson@usa.net" target="_blank">tony_anderson@usa.net</a>></span>:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div>
Sorry Laura<br> </div></blockquote><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div bgcolor="#FFFFFF">
The money is better kept in the bank until Sugar Labs has an
objective and understands what kind of resources it needs. <br>
<br></div></blockquote><div><br></div><div>Thanks for writing Tony!<br><br></div><div>First and for the sake of democracy, let's make it clear to all learners here that there is a regular process for Budgetary decisions at Sugar Labs: it is the Sugar Labs Oversight Board as a whole, who are responsible for approving Budgetary decisions by a majority of votes over specific proposals expressed on specific motions.<br><br>So far, the Open Badges initiative is still maturing in a wiki page thanks to everybody's feedback. <br><br> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div bgcolor="#FFFFFF">
It is good that Sugar Labs is considering a budget for this year (a
gross dereliction last year). However, an organization makes a
budget to fund its planned projects for the year. </div></blockquote><div><br><br>As humans, we should hurry to gain consciousness that money is a
dynamic resource that transfers trust and passion whenever invested in
human resources.<br><br></div><div>The ideal scenario would be to have a Budget planned ahead for every year. <br><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div bgcolor="#FFFFFF">I have never heard
of one that starts out with 'we have this money, how can we spend
it.'<br>
<br></div></blockquote><br>So far because of our lack of financial planning, funds have remained unused and unfortunately this financial paralysis has translated into loosing more and more funds! According to Adam, Sugar Labs missed receiving US$40,000 because of our collective inaction with the Trip Advisor grant :( <br></div><div> <br><br></div><div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div bgcolor="#FFFFFF">
Our goal for localization should be to enable our users to perform
localization on their own laptops, i.e. view it as an opportunity
for constructive learning.<br></div></blockquote><div><br></div><div>+1<br><br>If you have any specific proposal for the 2017 SL Budget to consider please do share.<br><br></div><div> <br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div bgcolor="#FFFFFF">
Naturally, the professionals can do it faster and more efficiently.
That is always the problem when you are trying to develop the
capabilities of learners, but that investment is the business we are
in. Localization is interesting because the most important skill is
knowledge of two languages such as English and Yoruba. This is
precisely the skill that is readily available in a Sugar deployment
in a Yoruba-speaking region (and not in a professional enclave in
Boston).<br>
In Peru, it is incomprehensible that we don't have current
localization in every local language since every Peruvian child has
a laptop with Sugar.<br>
<br></div></blockquote><div><br><br>I agree English learning must be part of the learners outcome when contributing to localization. One thing important to clarify is that not "every Peruvian child has
a laptop with Sugar". <br><br></div>As for planning localization efforts, one thing important to understand from local context is that languages Quechua and Aymara are shared with other Andean countries. All other languages are Amazonian languages shared with the other countries on the Amazon Basin, where there are more than 350 indigenous ethnic groups, who speak more than 300 languages. <br><br> <br></div><div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div bgcolor="#FFFFFF">
The major need for Sugar Labs is to create a process for releasing
Sugarversions to be installed on current platforms: PCs, Raspberry
Pi, and Windows 10. The resources capable of accomplishing that have
professional skills and a day job. They need to be motivated to
spend their own time. They need to be 'sung' heroes but will
probably be 'unsung'.<br>
<br></div></blockquote><br></div><div>Wishful thinking won't take us in any direction. We need to be assertive and decide on how to better support our infrastructure and the work of active contributors as they do deliver! <br><br></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div bgcolor="#FFFFFF">
First, an active contributor contributes to meet a perceived need.
Currently, we greet potential contributors with 'create a
development environment and fix a random bug'. We ask our potential
contributors to be familiar with git (although it isn't actually
used). We don't ask these candidates to become familiar with Sugar
or read 'Making your own Sugar activity'.<br>
<br></div></blockquote><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div bgcolor="#FFFFFF">
We need to ask contributors to the build and distribute project what
they know about uefi and grub2, livecd tools, making debian images
for Raspberry Pi, and so on. </div></blockquote><div><br><br><div>After many successfully delivered and deployed
open source products, I have learned you can not ask developers to do X or Y. They would do what they like and they will use what they feel
comfortable with. I guess that is why we need to be creative and design innovative engaging strategies.<br><br></div> <br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div bgcolor="#FFFFFF">This skill set is available at XSCE and
I have never heard a discussion there about how those talented
volunteers are to be compensated. </div></blockquote><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div bgcolor="#FFFFFF">Several are at ScaleX at this
moment, a location where it might be possible to recruit some of the
technical skills Sugar Labs needs. Adam Holt is there, so at least
one SLOB could be working in the interest of Sugar Labs.<br></div></blockquote><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div bgcolor="#FFFFFF">
We have approved an 'outreachy' intern but I have no idea what
project the intern will be asked to undertake (generating an SOAS
image from our github repository would be high on my list).</div></blockquote><div> </div><div> </div></div><div class="gmail_quote">I think the Outreachy experience will be a nice learning case. I understand sponsorship is meant for first time contributors as the objective of the program seems to be to sponsor the work of a potential contributor that otherwise wouldn't be able to contribute, pretty similar to the Open Badges stipend philosophy is proposing.<br><br></div><div class="gmail_quote"><div>For sure Walter will explain the time line and procedures for the project proposals where necessary.<br></div><div><br><br>As for the 2017 Budget, Sugar Labs needs doable specific proposals for funding and investing as a healthy financial planning should consider a minimum of 5 years ahead. <br><br>Regards <br><br></div><div bgcolor="#FFFFFF">Laura V<br><br><br>
<div><div class="gmail-h5"><div class="gmail-m_-6432807567766443148moz-cite-prefix">On 03/02/2017 09:16 AM, Laura Vargas
wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr"><br>
<div class="gmail_extra"><br>
<div class="gmail_quote">2017-02-25 20:33 GMT-05:00 Tymon
Radzik <span dir="ltr"><<a href="mailto:dwgipk@gmail.com" target="_blank">dwgipk@gmail.com</a>></span>:
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="ltr">
<div>
<div> Our funds deserve to be spent in more
orgnization-beneficial way. <br>
</div>
<div><br>
</div>
</div>
</div>
</blockquote>
<div><br>
<div>Hello Tymon,<br>
<br>
</div>
Sorry it took me a while to reply. <br>
</div>
<div><br>
This Budget discussion is an open door for proposals,
please do share yours as this policy making is also an
educational process and therefore an ideal arena for
learning!<br>
<br>
<br>
Open Badges are proposed as an award for historic
achievements, there is no conflict of interest when you
have numeric results that support your performance. <br>
<br>
I think this discussion leads to the question of what
would make a Sugar Labs member an <b>active contributo</b>r?
and of course, would rewarding active contributors
stimulate regular members to become active contributors?<br>
<br>
Those are valid questions that should and can be easily
tested with for example the implementation Open Badges.<br>
<br>
I would say at least one of the following must happen for
a given period of time for a regular member to be
considered an active contributor: <br>
</div>
<div><br>
</div>
<div>1- The member contributed periodically to at least one
of the Sugar Labs Teams.<br>
<br>
</div>
<div>2- The member has had active leaderships of at least
one of the Sugar Labs Projects.<br>
<br>
</div>
<div>3- The member directly contributed with code and/or
with Sugar Projects translations.<br>
</div>
<div><br>
<br>
</div>
<div>All this data is available from logs, wiki, mailing
list, etc. I hope for the future of the community and it's
users, the recognition of active contributors becomes soon
an open strategy for Sugar Labs evolution.<br>
<br>
</div>
:D<br>
</div>
<div class="gmail_quote">
<div><br>
</div>
<div>Regards,<br>
</div>
<br>
-- <br>
<div>Laura V.<br>
<font color="#ff00ff"><b>
I&D SomosAZUCAR.Org</b></font></div>
<div><br>
</div>
<div><font size="2"><span>“No paradox, no
progress.” </span></font></div>
<div><font size="2"><span>~ Niels Bohr</span></font><br>
<br>
</div>
Happy Learning!<br>
<div> </div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="ltr">
<div>Best,<br>
</div>
Tymon<br>
<div>
<div>
<div><br>
</div>
</div>
</div>
<br>
</div>
</blockquote>
</div>
<br>
<div dir="ltr">
<div><br>
</div>
</div>
</div>
</div>
</blockquote>
<br>
</div></div></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
</blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature"><div dir="ltr"><div>Laura V.<br><font color="#ff00ff"><b>
I&D SomosAZUCAR.Org</b></font></div><div><br></div><div><font size="2"><span style="color:rgb(102,102,102);font-family:"helvetica neue",helvetica,arial,sans-serif">“No paradox, no progress.” </span></font></div><div><font size="2"><span style="color:rgb(102,102,102);font-family:"helvetica neue",helvetica,arial,sans-serif">~ Niels Bohr</span></font><br><br></div><div>Happy Learning!<br><br></div></div></div>
</div></div>