Difference between revisions of "Local Labs"
Jump to navigation
Jump to search
m (move todo items to todo list) |
|||
| Line 5: | Line 5: | ||
'''Welcome to the Local Sugar Labs project.''' | '''Welcome to the Local Sugar Labs project.''' | ||
| − | + | A local Sugar Lab would: | |
| − | |||
| − | |||
| − | |||
| + | * adapt the technology and pedagogy to an area's culture and resources (e.g, developing activities and content specific to the region) | ||
| + | * help translate Sugar to the local language | ||
| + | * support sugar deployments in area schools | ||
| + | * create a local community devoted to the Sugar Labs principles, making Sugar more open and sustainable | ||
| + | * provide for communication,between the local communities and the global Sugar Labs community | ||
| − | + | A distributed project—we chose to name Sugar Labs, plural deliberately—where there is a local sense of ownership and associated entrepreneurship feels like the right course for us as an organization. Sugar Labs "central" is the community itself, which would be responsible for setting clear goals and maintaining any necessary infrastructure needed by the project as a whole, while the regional labs would use the own means to make Sugar relevant to their local communities. But what is the "business model" for a successful Sugar Lab? It seems that some necessary conditions for success would be: | |
| + | * a university connection as a local human resource | ||
| + | * a local pilot user group to learn from | ||
| + | * a local passion or sub-goal that provides a rational for the work. | ||
| + | What are other considerations? And are these initial "conditions" correct? Your input would be of great value to our efforts. Please join the discussion. | ||
== Pros and Cons == | == Pros and Cons == | ||
Revision as of 18:00, 25 November 2008
This article is a stub. You can help Sugar Labs by expanding it.
Welcome to the Local Sugar Labs project.
A local Sugar Lab would:
- adapt the technology and pedagogy to an area's culture and resources (e.g, developing activities and content specific to the region)
- help translate Sugar to the local language
- support sugar deployments in area schools
- create a local community devoted to the Sugar Labs principles, making Sugar more open and sustainable
- provide for communication,between the local communities and the global Sugar Labs community
A distributed project—we chose to name Sugar Labs, plural deliberately—where there is a local sense of ownership and associated entrepreneurship feels like the right course for us as an organization. Sugar Labs "central" is the community itself, which would be responsible for setting clear goals and maintaining any necessary infrastructure needed by the project as a whole, while the regional labs would use the own means to make Sugar relevant to their local communities. But what is the "business model" for a successful Sugar Lab? It seems that some necessary conditions for success would be:
- a university connection as a local human resource
- a local pilot user group to learn from
- a local passion or sub-goal that provides a rational for the work.
What are other considerations? And are these initial "conditions" correct? Your input would be of great value to our efforts. Please join the discussion.
Pros and Cons
Pros
- Good source of self sustaining revenue.
Cons
- Would SL directly engaging in work-for-hire cause a conflict of interest with our members and partners