-
Notifications
You must be signed in to change notification settings - Fork 206
/
about-us.html
executable file
·260 lines (250 loc) · 17 KB
/
about-us.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
---
layout: default
title: About Us - Sugar Labs
permalink: /about-us/index.html
---
<!-- Title section -->
<div class="section-title1">
<span class="tag tag-regular">ABOUT US</span>
</div>
<!-- Introduction section -->
<section id="testimonial">
<div class="container">
<div class="row">
<div class="col-md-12" >
<div class="row justify-content-center">
<div class="col-md-8 col-md-push-2" >
<div class="section-title text-center">
<h2>Sugar Labs:<br><br> a community for learning and software-development</h2>
<p class="customParagraphStyle">The Sugar development platform is available under the free/libre software GNU General Public License (GPL) to anyone who wants to extend it. “Sugar Labs” is a registered USA 501(c)(3) tax-exempt, not-for-profit organization, which serves as a support base and gathering place for the community of educators and software developers who want to extend the platform and who have been creating Sugar-compatible applications.</p>
</div>
</div>
</div>
</div>
</div>
</div>
</section>
<!-- "Mission" section -->
<section id="call-to-action">
<div class="container">
<div class="row">
<div class="col-md-12" >
<div class="row justify-content-center">
<div class="col-md-8 col-md-push-2" >
<h2 id="mission">MISSION</h2>
<p class="customFontSize"><a href="https://wiki.sugarlabs.org/go/Trademark" class="hrefCustomColor">Sugar Labs®</a> is a volunteer-driven member project of a nonprofit corporation. Originally part of the One Laptop Per Child project, Sugar Labs coordinates <a href="https://wiki.sugarlabs.org/go/Sugar_Labs/Getting_Involved" class="hrefCustomColor">volunteers</a> around the world who are passionate about providing educational opportunities to children through the Sugar Learning Platform. Sugar Labs® is supported by donations and is seeking <a href="https://wiki.sugarlabs.org/go/Sugar_Labs/Donate" class="hrefCustomColor">funding</a> to accelerate development.</p>
</div>
</div>
</div>
</div>
</div>
</section>
<!-- "Principles" section -->
<section id="testimonial">
<div class="container">
<div class="row">
<div class="col-md-12" >
<div class="row justify-content-center">
<div class="col-md-8 col-md-push-2" >
<div class="section-title text-center">
<h2>PRINCIPLES</h2>
<p class="customParagraphStyle">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 <a href="https://flors.wordpress.com/2008/05/04/the-paradigm-of-the-open-organization/" class="hrefCustomColor">here</a>, which are the author's own translation of an <a href="http://web.archive.org/web/20050317231119/http://interactors.coop/organizacionabierta" class="hrefCustomColor">original text in Spanish.</a></p>
</div>
</div>
</div>
<div class="row">
<div class="col-md-12">
<div class="testimonial-carousel">
<div id="testimonial-slider2" class="owl-carousel">
<div>
<h4><b>Identity</b></h4>
<p><ul class="leftAlign">
<li>1. Clear mission – Fully disclosed objectives.</li>
<li>2. Declared commitments – Affinities and aversions explained.</li>
<li>3. Declared outside connections – Relationships with other organizations explicitly listed.</li>
</ul></p>
</div>
<div>
<h4><b>Structure</b></h4>
<p><ul class="leftAlign">
<li>1. Horizontal organization – Teams and facilitators work on responsibilities and agreements.</li>
<li>2. Identified contributors – Who is who, people are reachable.</li>
<li>3. Clear responsibilities – Who is in charge of what.</li>
<li>4. Activities described – All of the ongoing work is acknowledged.</li>
</ul></p>
<h6>See <a href="https://wiki.sugarlabs.org/go/Wiki_Team/Guide/Wiki_Structure" class="hrefCustomColor">Wiki Structure</a> for a guide to how the wiki models Sugar Labs' structure.</h6>
</div>
<div>
<h4><b>Operation</b></h4>
<p><ul class="leftAlign">
<li>1. Open participation – Anybody can access the information and get a first responsibility.</li>
<li>2. Meritocracy – Responsibilities are acquired (or lost) based on one's skills, results, and contributors’ support.</li>
<li>3. Voluntary (non-)engagement – Nobody is forced to be involved or to keep responsibilities.</li>
</ul></p>
</div>
<div>
<h4><b>Information</b></h4>
<p><ul class="leftAlign">
<li>1. Regular reports – Reported activities and future plans allow monitoring and participation.</li>
<li>2. Information accessible – Even internal operational information is available by default.</li>
<li>3. Explicit confidentiality – It is explained what matters are confidential, why, and who can access them.</li>
</ul></p>
<h6>We try to operate <a href="https://wiki.sugarlabs.org/go/Archive/Current_Events/2009-06-10#En_plein_air" class="hrefCustomColor">en plein air</a>.</h6>
</div>
<div>
<h4><b>Goods</b></h4>
<p><ul class="leftAlign">
<li>1. Economic model – Feasibility and sustainability plans are exposed. (Please see/contribute to the discussion here.)</li>
<li>2. Resources – Inventory of items detailing who contributed what and why.</li>
<li>3. Public accounts – It’s clear where the money comes from and where it goes.</li>
</ul></p>
<h6>A special <a href="https://wiki.sugarlabs.org/go/Sugar_Labs/Thank_You" class="hrefCustomColor">thanks</a> to our contributors.</h6>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</section>
<!-- "Goals" section -->
<section id="call-to-action">
<div class="container">
<div class="row">
<div class="col-md-12" >
<div class="row">
<div class="col-md-12">
<h2>GOALS</h2>
</div>
</div>
<div class="row">
<div class="col-md-4">
<div class="border-box boxDownload2">
<h2 >Education Goals</h2>
<p>Sugar is useful only to the extent it is used by the learning community. Thus, Sugar Labs is working with educators around the world to focus on these learning challenges:</p>
<hr>
<ul class="leftAlign listDiscStyle">
<li class="listFont customFontSize2" >To make Sugar and Sugar activities freely and readily available to learners everywhere.</li>
<li class="listFont customFontSize2" >To explore and share best practices.</li>
<li class="listFont customFontSize2" >To provide a forum for discussion and support for technology for learning.</li>
<li class="listFont customFontSize2" >To provide mechanism for evaluation and dissemination of results.</li>
</ul>
</div>
</div>
<div class="col-md-4">
<div class="border-box boxDownload3">
<h2 >Technical Goals</h2>
<p>Sugar supports the notions that learners should “share by default” and be able to “explore, express, debug, and critique.” Thus Sugar puts an emphasis on “activities” rather than “applications.” The foundation will focus on solving the challenges that are relevant to these aspects of the interface, namely:</p>
<hr>
<ul class="leftAlign listDiscStyle">
<li class="listFont customFontSize2">To make it “simple” to share Sugar activities. This will require an architecture that allows discovery of activities.</li>
<li class="listFont customFontSize2">To create versions of Sugar that run on multiple operating systems and on multiple hardware platforms. It should be “simple” to install Sugar everywhere. Specifically, it means packaging for every distribution and every virtual machine—removing hardware-related dependencies wherever possible.</li>
<li class="listFont customFontSize2">To make it “simple” to write Sugar activities. This necessitates stable APIs and example code that uses these APIs.</li>
<li class="listFont customFontSize2">To make Sugar activities even more secure. Our principal user community is comprised of children; they must be protected from malware, phishing, botnets, etc.</li>
</ul>
</div>
</div>
<div class="col-md-4">
<div class="border-box boxDownload2">
<h2 >Community Goals</h2>
<p>Sugar Labs is here to support community innovation, entrepreneurship, and enterprise. Sugar Labs would like to help community members start projects that help sustain and grow the Sugar technology and learning communities:</p>
<hr>
<ul class="leftAlign listDiscStyle">
<li class="listFont customFontSize2">To provide local and regional technical and pedagogical support.</li>
<li class="listFont customFontSize2">To create new learning activities and pedagogical practice.</li>
<li class="listFont customFontSize2">To provide localization and internationalization of software, content, and documentation.</li>
<li class="listFont customFontSize2">To provide integration and customization services.</li>
</ul>
</div>
</div>
</div>
</div>
</div>
</div>
</section>
<!-- "Projects" section -->
<section id="testimonial">
<div class="container">
<div class="row">
<div class="col-md-12" >
<div class="row justify-content-center">
<div class="col-md-8 col-md-push-2" >
<div class="section-title text-center">
<h2>Projects</h2>
<p class="customParagraphStyle">Sugar Labs is working on a few <a href="https://wiki.sugarlabs.org/go/Category:Project" class="hrefCustomColor">projects</a> focused on delivering specific goals in a defined time period. The "Projects" panel in the Sugar Labs wiki sidebar holds our premier projects. Please also see these project home pages:
<ul>
<li><a href="https://wiki.sugarlabs.org/go/Sugar_Creation_Kit" class="hrefCustomColor">Sugar Creation Kit</a></li>
<li><a href="https://wiki.sugarlabs.org/go/Sugar_on_a_Stick" class="hrefCustomColor">Sugar on a Stick</a></li>
<li><a href="https://wiki.sugarlabs.org/go/Math4Team" class="hrefCustomColor">Math4 Project</a></li>
<li><a href="https://wiki.sugarlabs.org/go/Summer_of_Code" class="hrefCustomColor">Summer of Code</a></li>
</ul>
</p>
</div>
</div>
</div>
</div>
</div>
</div>
</section>
<!-- "Local labs" section -->
<!--
This section to be reintroduced once we have a plan for local labs; currently the only link below that works is Sugar Labs DC.
<section id="call-to-action">
<div class="container">
<div class="row">
<div class="col-md-12" >
<div class="row justify-content-center">
<div class="col-md-8 col-md-push-2" >
<h2>LOCAL LABS</h2>
<p class="customFontSize">A local Sugar Lab adapts the technology and pedagogy to an area's culture and resources (e.g., developing activities and content specific to a region); helps translate Sugar to the local language(s); supports Sugar deployments in area schools; creates a local community devoted to the Sugar Labs principles, making Sugar more open and sustainable; provides for communication, between the local communities and the global Sugar Labs community; develops Local content and software that can be used not only for local purposes but also for the overall community; hosts, co-hosts or partners in the organization of conferences, workshops, talks and meetings related to the use or development of Sugar. Please visit these Local Labs:
<ul>
<li><a href="http://co.sugarlabs.org/go/Laboratorios_Azúcar_Colombia" class="hrefCustomColor">Sugar Labs Colombia</a></li>
<li><a href="http://cl.sugarlabs.org/go/Página_Principal" class="hrefCustomColor">Sugar Labs Chile</a></li>
<li><a href="https://wiki.sugarlabs.org/go/Sugar_Labs_DC" class="hrefCustomColor">Sugar Labs DC</a></li>
<li><a href="http://pe.sugarlabs.org" class="hrefCustomColor">Sugar Labs Peru</a></li>
<li><a href="http://ar.sugarlabs.org" class="hrefCustomColor">Sugar Labs Argentina</a></li>
</ul>
</p>
</div>
</div>
</div>
</div>
</div>
</section>
-->
<!-- "Roadmap" section -->
<section id="testimonial">
<div class="container">
<div class="row">
<div class="col-md-12" >
<div class="row justify-content-center">
<div class="col-md-8 col-md-push-2" >
<div class="section-title text-center">
<h2>Roadmap</h2>
<p class="customParagraphStyle">The <a href="https://wiki.sugarlabs.org/go/Sugar_Labs/Roadmap" class="hrefCustomColor">Sugar Community roadmap</a> is used to guide our community efforts:
<ul>
<li>Mission, Vision, Values</li>
<li>Distribution</li>
<li>Deployments</li>
<li>Quality Assurance</li>
<li>Infrastructure</li>
</ul>
</p>
</div>
</div>
</div>
</div>
</div>
</div>
</section>
<!-- "Return to main page" button section -->
<section id="call-to-action">
<div class="container">
<div class="row">
<div class="col-md-12" >
<a href="{{ site.baseurl }}/" ><button type="button" class="btn bt-raised btn-custom bt bt-ripple lastButtonMargin" >Return to main page</button></a>
</div>
</div>
</div>
</section>