Sugar Labs - User contributions [en]

Oversight Board/2017-2019-candidates

2017-09-15T18:24:40Z

SeanDaly:

==Election==

There are to be four (4) [[Oversight Board]] slots to be elected for the 2017-2019 period, currently held by Walter, Adam, Lionel and Sameer.

==Calendar==

{| class="wikitable"
|Stage I
|August 15
|Announcement of election date and first call for candidates.
|-
|Stage II
|August 30
|Reminder of election date and second call for candidates.
|-
|Stage III
|September 15
|[[#Candidates|Candidates' Wiki submissions]] deadline.
|-
|Stage IV
|October 1-15
|Election.
|}

==Candidates==

Candidates should create a Wiki entry at [[#Candidates|Candidates' Wiki submissions]], one entry per candidate, 1500 characters maximum length, sharing their vision and motivation.

Candidates should read and understand the terms of the [[Sugar_Labs/SFC_Fiscal_Agreement|Software Freedom Conservancy Fiscal Agreement]], because such terms bind our behavior as Sugar Labs Oversight Board and all our internal policies and procedures as a Project and as an organization.

Among other terms, please note the Project Management, Communications and Activities terms in the agreement provide that:

2.1. The Oversight Board Will Manage the Project.

2.2. The Project Will Be Free Software.

6. Representation of the Project in Conservancy: The Representative will have the authority to instruct Conservancy on the Project’s behalf on all matters.

The terms contemplate that the Oversight Board elects a single individual to communicate with Conservancy (the “Representative”) and shall notify Conservancy promptly following the election of a new Representative.

By publishing your candidacy below, you imply that in case you are elected a Sugar Labs Oversight board member you will honor the agreement terms.

=Devin Ulibarri=
Devin Ulibarri is a musician and an educator who became interested in free/libre software in 2014 during research for the Center for Music-in-Education (Boston). Devin pursued research into the implications for "software libre in education" which led him to believe that free/libre software is best for teaching and learning. He was soon introduced to SugarLabs, which both empowers teachers/learners with software freedom as well as offers tools to exercise those freedoms in a community setting.

Since his introduction to the SugarLabs community, Devin has participated heavily in the development of Music Blocks, a programming language for music. Within the SugarLabs community, Devin offers conceptual recommendations, design ideas, mockups, testing, minor patches, and community involvement on GitHub and Sugar's IRC. In his local community, Devin has represented Music Blocks software as a workshop lecturer (Constructionism Conference in Thailand, Canopy of Somerville) as well as a class instructor (YMCA Malden).

As an oversight board member, Devin would bring his insight as an experienced classroom teacher, an artist, and a free/libre software advocate. Devin has been described as "a very patient person", which he hopes would be a contribution to the oversight board if elected.

=Walter Bender=
After a decade of working on Sugar, I am reflecting on how we engage learners. We provide programming environments (e.g., Turtle and Music Blocks) and mechanism for debugging, collaboration, expression, and reflection. Our adherence to the principles of Free/Libre Software provides scaffolding for personal expression through programming and for surfacing personal responsibility, a sense of community, and unbounded expectations of Sugar users turned Sugar developers.

Where have we fallen short? Edtech is become big business: selling Apps and content is more lucrative and facile than the hard work of engaging teacher and learners in authentic problem-solving. There is a strong temptation to make things as simple as possible so as to reach the broadest possible audience. But some things are inherently complex. Apps might be fun, but the hard part of “hard fun” is in reaching towards complexity.

We are going where the learners are: Sugar as a Web app, on Android, or on iOS, (Sugarizer) and, tracking the growth of the Maker Movement, we now support Sugar on Raspbian.
“It is said that the best way to learn something is to teach it—and perhaps writing a teaching program is better still in its insistence on forcing one to consider all possible misunderstandings and mistakes.” — Seymour Papert

I have made mistakes, but as part of a learning community we will do better.

“Homework is boring. Looking for bugs is fun.” —Ezequiel Pereira

Let's continue to provide the basis for some fun.

=Sebastian Silva=

The mission of the Sugar Labs Oversight Board is to ensure the community has clarity of purpose and the means to attain its goals.

Sugar Labs needs to recognize that our community is '''diverse'''. Therefore, there are diverse purposes that may be clear and at the same time opposed.

We should provide a '''safe and neutral space''' for dialogue on the technology and education that underlies our projects. We need to approve and enforce a ''code of conduct''.

Finally, the reason for Sugar Labs to exist under the SFC is to '''facilitate the flow of resources''' to volunteers with valuable projects. We should strive to open and fund open calls with funds for development, infrastructure and end user products.

=== About Sebastian ===
Sebastian is father to two precious children that are being homeschooled in collaboration with his dear wife and co-creator Laura Vargas.

As a child, Sebastian learned to program with Logo and soon outgrew it to be charmed with Python and raise the flag of Free/Libre Software. He loves writing Sugar Activities; His latest is a collaborative [http://educa.juegos/#sugarlabs_platform_2017 Python IDE] that he hopes you'll love too.

Currently he lives with his family in a cabin in the Amazon rainforest and teaches Karate and videogame programming to the kids in the vicinity, sustaining a lifestyle seeking harmony with nature and providing services of software artisanship and systems gardening remotely.

=Lionel Laské=
Learn more about my background [[User:Llaske|here]].

Like lot of you I've joined SugarLabs at the beginning of the OLPC project. As cofounder of [http://olpc-france.org OLPC France grassroot], I've worked hard to deploy it on the field and contribute to expand it both in term of activities and in term of French content.
Because the OLPC project and the XO laptop was declining year after year, I've decided 5 years ago to launch the [http://sugarizer.org Sugarizer] initiative. My objective was to write a new page of Sugar history by expanding its compatibility to any device, specifically the favorite education device of today: tablets. I'm very proud that today, two deployments already start to use Sugarizer on Android tablets.

Deployed on more than 2 millions of devices and supported by millions of users, Sugar is the #1 learning platform in the world. But we need to convince this large community that a future exist out of the XO laptop. It's my ambition as candidate to the SugarLabs Oversight Board. As I've done in past month as SLOB member, I will support projects where the goal is to expand the community and give a vision to SugarLabs. Even if it could hurt sometime, I will also refuse to spend our limited resources on ways that not fit into its vision. We're all volunteers and our time is precious, let's continue to invest it where it will be the most useful: give to learners the better free libre education platform.

=Sameer Verma=
My background [[User:Sverma|here]].

== Introduction ==

I am a professor in the Information Systems department at San Francisco State University, in San Francisco, California USA. I also serve on the Board of Directors of the Drupal Association, which gives me significant insights into how large FOSS projects work both in the community and the enterprise. I am the founder of the OLPC San Francisco volunteer community, that continues to be active around OLPC's original mission and projects that have grown from that ecosystem, including Sugar, XS, XOVis and others.

== Experience ==

My experience with Sugar projects are based on a three-pronged approach:

:''Education''

:Understanding constructivist, constructionist, instructional and ad-hoc learning models. I look for accommodating for the gap between what may be prescribed, and what can actually be implemented in the field.

:''Technology''

:Hardware, software, and network combinations that make these projects work in the “middle of nowhere” communities. My professional training comes in handy when working on these technology bits.

:''Social Context''

:Understanding social context is the most important of the three approaches. Providing powerful life-changing educational tools to communities is not enough unless we also understand their cultural and social underpinnings.

== Expected Contribution ==

To maintain Sugar's technology focus as a medium of delivery, while maintaining the education message. I hope to bring my skills and expertise to contribute to the strategic direction of Sugar the project, and its implementations on any device, anywhere.

=Sean Daly=

I am an independent journalist, formerly working for a large company in IT, communications, advertising and marketing. As my children are (mostly) grown, and I set my own work schedule, I will have time to commit to Sugar again. I have been part of Sugar Labs since 2009, including a term as a SLOB, and was Marketing Coordinator for 5 years.

The major changes in "educational technology" - from computer lab, to netbook, to tablet - mean that beyond the XO platform, Sugar must adapt and indeed is doing so, through Sugarizer and other initiatives. At the same time, the rapid growth of social media has created new opportunities to communicate about Sugar, opportunities which are not being seized today.

As a SLOB, I will work to grow our community and to raise awareness of Sugar.

==References==

This election is being run by the [[Sugar_Labs/Governance/Committees#Membership_and_Elections_Committee|Membership and Elections Committee]] which was [[Oversight_Board/Decisions#2017-01-06|appointed in January]], along with Dave Crossland
as an impartial election oversight party.

An update from the Membership and Elections Committee was [http://meeting.sugarlabs.org/sugar-meeting/meetings/2017-08-04T19:01:24#i_2900181 received] during the Oversight Board meeting of August 4. Also listed were the [http://meeting.sugarlabs.org/sugar-meeting/meetings/2017-08-04T19:01:24#i_2900205 expiring slots].

During [http://meeting.sugarlabs.org/sugar-meeting/meetings/2017-09-01T19:10:08 September's meeting] the Board '''confirmed September 27, 2017 as the deadline for new memberships request to participate on 2017-2019 elections'''.

Oversight Board/2017-2019-candidates

2017-09-15T18:23:06Z

SeanDaly: /* Expected Contribution */

==Election==

There are to be four (4) [[Oversight Board]] slots to be elected for the 2017-2019 period, currently held by Walter, Adam, Lionel and Sameer.

==Calendar==

{| class="wikitable"
|Stage I
|August 15
|Announcement of election date and first call for candidates.
|-
|Stage II
|August 30
|Reminder of election date and second call for candidates.
|-
|Stage III
|September 15
|[[#Candidates|Candidates' Wiki submissions]] deadline.
|-
|Stage IV
|October 1-15
|Election.
|}

==Candidates==

Candidates should create a Wiki entry at [[#Candidates|Candidates' Wiki submissions]], one entry per candidate, 1500 characters maximum length, sharing their vision and motivation.

Candidates should read and understand the terms of the [[Sugar_Labs/SFC_Fiscal_Agreement|Software Freedom Conservancy Fiscal Agreement]], because such terms bind our behavior as Sugar Labs Oversight Board and all our internal policies and procedures as a Project and as an organization.

Among other terms, please note the Project Management, Communications and Activities terms in the agreement provide that:

2.1. The Oversight Board Will Manage the Project.

2.2. The Project Will Be Free Software.

6. Representation of the Project in Conservancy: The Representative will have the authority to instruct Conservancy on the Project’s behalf on all matters.

The terms contemplate that the Oversight Board elects a single individual to communicate with Conservancy (the “Representative”) and shall notify Conservancy promptly following the election of a new Representative.

By publishing your candidacy below, you imply that in case you are elected a Sugar Labs Oversight board member you will honor the agreement terms.

=Devin Ulibarri=
Devin Ulibarri is a musician and an educator who became interested in free/libre software in 2014 during research for the Center for Music-in-Education (Boston). Devin pursued research into the implications for "software libre in education" which led him to believe that free/libre software is best for teaching and learning. He was soon introduced to SugarLabs, which both empowers teachers/learners with software freedom as well as offers tools to exercise those freedoms in a community setting.

Since his introduction to the SugarLabs community, Devin has participated heavily in the development of Music Blocks, a programming language for music. Within the SugarLabs community, Devin offers conceptual recommendations, design ideas, mockups, testing, minor patches, and community involvement on GitHub and Sugar's IRC. In his local community, Devin has represented Music Blocks software as a workshop lecturer (Constructionism Conference in Thailand, Canopy of Somerville) as well as a class instructor (YMCA Malden).

As an oversight board member, Devin would bring his insight as an experienced classroom teacher, an artist, and a free/libre software advocate. Devin has been described as "a very patient person", which he hopes would be a contribution to the oversight board if elected.

=Walter Bender=
After a decade of working on Sugar, I am reflecting on how we engage learners. We provide programming environments (e.g., Turtle and Music Blocks) and mechanism for debugging, collaboration, expression, and reflection. Our adherence to the principles of Free/Libre Software provides scaffolding for personal expression through programming and for surfacing personal responsibility, a sense of community, and unbounded expectations of Sugar users turned Sugar developers.

Where have we fallen short? Edtech is become big business: selling Apps and content is more lucrative and facile than the hard work of engaging teacher and learners in authentic problem-solving. There is a strong temptation to make things as simple as possible so as to reach the broadest possible audience. But some things are inherently complex. Apps might be fun, but the hard part of “hard fun” is in reaching towards complexity.

We are going where the learners are: Sugar as a Web app, on Android, or on iOS, (Sugarizer) and, tracking the growth of the Maker Movement, we now support Sugar on Raspbian.
“It is said that the best way to learn something is to teach it—and perhaps writing a teaching program is better still in its insistence on forcing one to consider all possible misunderstandings and mistakes.” — Seymour Papert

I have made mistakes, but as part of a learning community we will do better.

“Homework is boring. Looking for bugs is fun.” —Ezequiel Pereira

Let's continue to provide the basis for some fun.

=Sebastian Silva=

The mission of the Sugar Labs Oversight Board is to ensure the community has clarity of purpose and the means to attain its goals.

Sugar Labs needs to recognize that our community is '''diverse'''. Therefore, there are diverse purposes that may be clear and at the same time opposed.

We should provide a '''safe and neutral space''' for dialogue on the technology and education that underlies our projects. We need to approve and enforce a ''code of conduct''.

Finally, the reason for Sugar Labs to exist under the SFC is to '''facilitate the flow of resources''' to volunteers with valuable projects. We should strive to open and fund open calls with funds for development, infrastructure and end user products.

=== About Sebastian ===
Sebastian is father to two precious children that are being homeschooled in collaboration with his dear wife and co-creator Laura Vargas.

As a child, Sebastian learned to program with Logo and soon outgrew it to be charmed with Python and raise the flag of Free/Libre Software. He loves writing Sugar Activities; His latest is a collaborative [http://educa.juegos/#sugarlabs_platform_2017 Python IDE] that he hopes you'll love too.

Currently he lives with his family in a cabin in the Amazon rainforest and teaches Karate and videogame programming to the kids in the vicinity, sustaining a lifestyle seeking harmony with nature and providing services of software artisanship and systems gardening remotely.

=Lionel Laské=
Learn more about my background [[User:Llaske|here]].

Like lot of you I've joined SugarLabs at the beginning of the OLPC project. As cofounder of [http://olpc-france.org OLPC France grassroot], I've worked hard to deploy it on the field and contribute to expand it both in term of activities and in term of French content.
Because the OLPC project and the XO laptop was declining year after year, I've decided 5 years ago to launch the [http://sugarizer.org Sugarizer] initiative. My objective was to write a new page of Sugar history by expanding its compatibility to any device, specifically the favorite education device of today: tablets. I'm very proud that today, two deployments already start to use Sugarizer on Android tablets.

Deployed on more than 2 millions of devices and supported by millions of users, Sugar is the #1 learning platform in the world. But we need to convince this large community that a future exist out of the XO laptop. It's my ambition as candidate to the SugarLabs Oversight Board. As I've done in past month as SLOB member, I will support projects where the goal is to expand the community and give a vision to SugarLabs. Even if it could hurt sometime, I will also refuse to spend our limited resources on ways that not fit into its vision. We're all volunteers and our time is precious, let's continue to invest it where it will be the most useful: give to learners the better free libre education platform.

=Sameer Verma=
My background [[User:Sverma|here]].

== Introduction ==

I am a professor in the Information Systems department at San Francisco State University, in San Francisco, California USA. I also serve on the Board of Directors of the Drupal Association, which gives me significant insights into how large FOSS projects work both in the community and the enterprise. I am the founder of the OLPC San Francisco volunteer community, that continues to be active around OLPC's original mission and projects that have grown from that ecosystem, including Sugar, XS, XOVis and others.

== Experience ==

My experience with Sugar projects are based on a three-pronged approach:

:''Education''

:Understanding constructivist, constructionist, instructional and ad-hoc learning models. I look for accommodating for the gap between what may be prescribed, and what can actually be implemented in the field.

:''Technology''

:Hardware, software, and network combinations that make these projects work in the “middle of nowhere” communities. My professional training comes in handy when working on these technology bits.

:''Social Context''

:Understanding social context is the most important of the three approaches. Providing powerful life-changing educational tools to communities is not enough unless we also understand their cultural and social underpinnings.

== Expected Contribution ==

To maintain Sugar's technology focus as a medium of delivery, while maintaining the education message. I hope to bring my skills and expertise to contribute to the strategic direction of Sugar the project, and its implementations on any device, anywhere.

[Sean Daly]

I am an independent journalist, formerly working for a large company in IT, communications, advertising and marketing. As my children are (mostly) grown, and I set my own work schedule, I will have time to commit to Sugar again. I have been part of Sugar Labs since 2009, including a term as a SLOB, and was Marketing Coordinator for 5 years.

The major changes in "educational technology" - from computer lab, to netbook, to tablet - mean that beyond the XO platform, Sugar must adapt and indeed is doing so, through Sugarizer and other initiatives. At the same time, the rapid growth of social media has created new opportunities to communicate about Sugar, opportunities which are not being seized today.

As a SLOB, I will work to grow our community and to raise awareness of Sugar.

...

==References==

This election is being run by the [[Sugar_Labs/Governance/Committees#Membership_and_Elections_Committee|Membership and Elections Committee]] which was [[Oversight_Board/Decisions#2017-01-06|appointed in January]], along with Dave Crossland
as an impartial election oversight party.

An update from the Membership and Elections Committee was [http://meeting.sugarlabs.org/sugar-meeting/meetings/2017-08-04T19:01:24#i_2900181 received] during the Oversight Board meeting of August 4. Also listed were the [http://meeting.sugarlabs.org/sugar-meeting/meetings/2017-08-04T19:01:24#i_2900205 expiring slots].

During [http://meeting.sugarlabs.org/sugar-meeting/meetings/2017-09-01T19:10:08 September's meeting] the Board '''confirmed September 27, 2017 as the deadline for new memberships request to participate on 2017-2019 elections'''.

Oversight Board/2017-2019-candidates

2017-09-15T18:19:16Z

SeanDaly: /* Expected Contribution */

==Election==

There are to be four (4) [[Oversight Board]] slots to be elected for the 2017-2019 period, currently held by Walter, Adam, Lionel and Sameer.

==Calendar==

{| class="wikitable"
|Stage I
|August 15
|Announcement of election date and first call for candidates.
|-
|Stage II
|August 30
|Reminder of election date and second call for candidates.
|-
|Stage III
|September 15
|[[#Candidates|Candidates' Wiki submissions]] deadline.
|-
|Stage IV
|October 1-15
|Election.
|}

==Candidates==

Candidates should create a Wiki entry at [[#Candidates|Candidates' Wiki submissions]], one entry per candidate, 1500 characters maximum length, sharing their vision and motivation.

Candidates should read and understand the terms of the [[Sugar_Labs/SFC_Fiscal_Agreement|Software Freedom Conservancy Fiscal Agreement]], because such terms bind our behavior as Sugar Labs Oversight Board and all our internal policies and procedures as a Project and as an organization.

Among other terms, please note the Project Management, Communications and Activities terms in the agreement provide that:

2.1. The Oversight Board Will Manage the Project.

2.2. The Project Will Be Free Software.

6. Representation of the Project in Conservancy: The Representative will have the authority to instruct Conservancy on the Project’s behalf on all matters.

The terms contemplate that the Oversight Board elects a single individual to communicate with Conservancy (the “Representative”) and shall notify Conservancy promptly following the election of a new Representative.

By publishing your candidacy below, you imply that in case you are elected a Sugar Labs Oversight board member you will honor the agreement terms.

=Devin Ulibarri=
Devin Ulibarri is a musician and an educator who became interested in free/libre software in 2014 during research for the Center for Music-in-Education (Boston). Devin pursued research into the implications for "software libre in education" which led him to believe that free/libre software is best for teaching and learning. He was soon introduced to SugarLabs, which both empowers teachers/learners with software freedom as well as offers tools to exercise those freedoms in a community setting.

Since his introduction to the SugarLabs community, Devin has participated heavily in the development of Music Blocks, a programming language for music. Within the SugarLabs community, Devin offers conceptual recommendations, design ideas, mockups, testing, minor patches, and community involvement on GitHub and Sugar's IRC. In his local community, Devin has represented Music Blocks software as a workshop lecturer (Constructionism Conference in Thailand, Canopy of Somerville) as well as a class instructor (YMCA Malden).

As an oversight board member, Devin would bring his insight as an experienced classroom teacher, an artist, and a free/libre software advocate. Devin has been described as "a very patient person", which he hopes would be a contribution to the oversight board if elected.

=Walter Bender=
After a decade of working on Sugar, I am reflecting on how we engage learners. We provide programming environments (e.g., Turtle and Music Blocks) and mechanism for debugging, collaboration, expression, and reflection. Our adherence to the principles of Free/Libre Software provides scaffolding for personal expression through programming and for surfacing personal responsibility, a sense of community, and unbounded expectations of Sugar users turned Sugar developers.

Where have we fallen short? Edtech is become big business: selling Apps and content is more lucrative and facile than the hard work of engaging teacher and learners in authentic problem-solving. There is a strong temptation to make things as simple as possible so as to reach the broadest possible audience. But some things are inherently complex. Apps might be fun, but the hard part of “hard fun” is in reaching towards complexity.

We are going where the learners are: Sugar as a Web app, on Android, or on iOS, (Sugarizer) and, tracking the growth of the Maker Movement, we now support Sugar on Raspbian.
“It is said that the best way to learn something is to teach it—and perhaps writing a teaching program is better still in its insistence on forcing one to consider all possible misunderstandings and mistakes.” — Seymour Papert

I have made mistakes, but as part of a learning community we will do better.

“Homework is boring. Looking for bugs is fun.” —Ezequiel Pereira

Let's continue to provide the basis for some fun.

=Sebastian Silva=

The mission of the Sugar Labs Oversight Board is to ensure the community has clarity of purpose and the means to attain its goals.

Sugar Labs needs to recognize that our community is '''diverse'''. Therefore, there are diverse purposes that may be clear and at the same time opposed.

We should provide a '''safe and neutral space''' for dialogue on the technology and education that underlies our projects. We need to approve and enforce a ''code of conduct''.

Finally, the reason for Sugar Labs to exist under the SFC is to '''facilitate the flow of resources''' to volunteers with valuable projects. We should strive to open and fund open calls with funds for development, infrastructure and end user products.

=== About Sebastian ===
Sebastian is father to two precious children that are being homeschooled in collaboration with his dear wife and co-creator Laura Vargas.

As a child, Sebastian learned to program with Logo and soon outgrew it to be charmed with Python and raise the flag of Free/Libre Software. He loves writing Sugar Activities; His latest is a collaborative [http://educa.juegos/#sugarlabs_platform_2017 Python IDE] that he hopes you'll love too.

Currently he lives with his family in a cabin in the Amazon rainforest and teaches Karate and videogame programming to the kids in the vicinity, sustaining a lifestyle seeking harmony with nature and providing services of software artisanship and systems gardening remotely.

=Lionel Laské=
Learn more about my background [[User:Llaske|here]].

Like lot of you I've joined SugarLabs at the beginning of the OLPC project. As cofounder of [http://olpc-france.org OLPC France grassroot], I've worked hard to deploy it on the field and contribute to expand it both in term of activities and in term of French content.
Because the OLPC project and the XO laptop was declining year after year, I've decided 5 years ago to launch the [http://sugarizer.org Sugarizer] initiative. My objective was to write a new page of Sugar history by expanding its compatibility to any device, specifically the favorite education device of today: tablets. I'm very proud that today, two deployments already start to use Sugarizer on Android tablets.

Deployed on more than 2 millions of devices and supported by millions of users, Sugar is the #1 learning platform in the world. But we need to convince this large community that a future exist out of the XO laptop. It's my ambition as candidate to the SugarLabs Oversight Board. As I've done in past month as SLOB member, I will support projects where the goal is to expand the community and give a vision to SugarLabs. Even if it could hurt sometime, I will also refuse to spend our limited resources on ways that not fit into its vision. We're all volunteers and our time is precious, let's continue to invest it where it will be the most useful: give to learners the better free libre education platform.

=Sameer Verma=
My background [[User:Sverma|here]].

== Introduction ==

I am a professor in the Information Systems department at San Francisco State University, in San Francisco, California USA. I also serve on the Board of Directors of the Drupal Association, which gives me significant insights into how large FOSS projects work both in the community and the enterprise. I am the founder of the OLPC San Francisco volunteer community, that continues to be active around OLPC's original mission and projects that have grown from that ecosystem, including Sugar, XS, XOVis and others.

== Experience ==

My experience with Sugar projects are based on a three-pronged approach:

:''Education''

:Understanding constructivist, constructionist, instructional and ad-hoc learning models. I look for accommodating for the gap between what may be prescribed, and what can actually be implemented in the field.

:''Technology''

:Hardware, software, and network combinations that make these projects work in the “middle of nowhere” communities. My professional training comes in handy when working on these technology bits.

:''Social Context''

:Understanding social context is the most important of the three approaches. Providing powerful life-changing educational tools to communities is not enough unless we also understand their cultural and social underpinnings.

== Expected Contribution ==

To maintain Sugar's technology focus as a medium of delivery, while maintaining the education message. I hope to bring my skills and expertise to contribute to the strategic direction of Sugar the project, and its implementations on any device, anywhere.

[Sean Daly]

I am an independent journalist, formerly working for a large company in IT, communications, advertising and marketing. As my children are (mostly) grown, and I set my own work schedule, I will have time to commit to Sugar again. I have been part of Sugar Labs since 2009, including a term as a SLOB, and was Marketing Coordinator for 5 years.

The major changes in "educational technology" - from computer lab, to netbook, to tablet - mean that beyond the XO platform, Sugar must adapt and indeed is doing so, through Sugarizer and other initiatives. At the same time, the rapid growth of social media has created new opportunities to communicate about Sugar, opportunities which are not being seized today.

As a SLOB, I will work to grow our community and to raise awareness of Sugar.

...

[Candidate Name]

Entry

...

==References==

This election is being run by the [[Sugar_Labs/Governance/Committees#Membership_and_Elections_Committee|Membership and Elections Committee]] which was [[Oversight_Board/Decisions#2017-01-06|appointed in January]], along with Dave Crossland
as an impartial election oversight party.

An update from the Membership and Elections Committee was [http://meeting.sugarlabs.org/sugar-meeting/meetings/2017-08-04T19:01:24#i_2900181 received] during the Oversight Board meeting of August 4. Also listed were the [http://meeting.sugarlabs.org/sugar-meeting/meetings/2017-08-04T19:01:24#i_2900205 expiring slots].

During [http://meeting.sugarlabs.org/sugar-meeting/meetings/2017-09-01T19:10:08 September's meeting] the Board '''confirmed September 27, 2017 as the deadline for new memberships request to participate on 2017-2019 elections'''.

Oversight Board/2017-2019-candidates

2017-09-15T18:18:29Z

SeanDaly: /* [Candidate Name] */

==Election==

There are to be four (4) [[Oversight Board]] slots to be elected for the 2017-2019 period, currently held by Walter, Adam, Lionel and Sameer.

==Calendar==

{| class="wikitable"
|Stage I
|August 15
|Announcement of election date and first call for candidates.
|-
|Stage II
|August 30
|Reminder of election date and second call for candidates.
|-
|Stage III
|September 15
|[[#Candidates|Candidates' Wiki submissions]] deadline.
|-
|Stage IV
|October 1-15
|Election.
|}

==Candidates==

Candidates should create a Wiki entry at [[#Candidates|Candidates' Wiki submissions]], one entry per candidate, 1500 characters maximum length, sharing their vision and motivation.

Candidates should read and understand the terms of the [[Sugar_Labs/SFC_Fiscal_Agreement|Software Freedom Conservancy Fiscal Agreement]], because such terms bind our behavior as Sugar Labs Oversight Board and all our internal policies and procedures as a Project and as an organization.

Among other terms, please note the Project Management, Communications and Activities terms in the agreement provide that:

2.1. The Oversight Board Will Manage the Project.

2.2. The Project Will Be Free Software.

6. Representation of the Project in Conservancy: The Representative will have the authority to instruct Conservancy on the Project’s behalf on all matters.

The terms contemplate that the Oversight Board elects a single individual to communicate with Conservancy (the “Representative”) and shall notify Conservancy promptly following the election of a new Representative.

By publishing your candidacy below, you imply that in case you are elected a Sugar Labs Oversight board member you will honor the agreement terms.

=Devin Ulibarri=
Devin Ulibarri is a musician and an educator who became interested in free/libre software in 2014 during research for the Center for Music-in-Education (Boston). Devin pursued research into the implications for "software libre in education" which led him to believe that free/libre software is best for teaching and learning. He was soon introduced to SugarLabs, which both empowers teachers/learners with software freedom as well as offers tools to exercise those freedoms in a community setting.

Since his introduction to the SugarLabs community, Devin has participated heavily in the development of Music Blocks, a programming language for music. Within the SugarLabs community, Devin offers conceptual recommendations, design ideas, mockups, testing, minor patches, and community involvement on GitHub and Sugar's IRC. In his local community, Devin has represented Music Blocks software as a workshop lecturer (Constructionism Conference in Thailand, Canopy of Somerville) as well as a class instructor (YMCA Malden).

As an oversight board member, Devin would bring his insight as an experienced classroom teacher, an artist, and a free/libre software advocate. Devin has been described as "a very patient person", which he hopes would be a contribution to the oversight board if elected.

=Walter Bender=
After a decade of working on Sugar, I am reflecting on how we engage learners. We provide programming environments (e.g., Turtle and Music Blocks) and mechanism for debugging, collaboration, expression, and reflection. Our adherence to the principles of Free/Libre Software provides scaffolding for personal expression through programming and for surfacing personal responsibility, a sense of community, and unbounded expectations of Sugar users turned Sugar developers.

Where have we fallen short? Edtech is become big business: selling Apps and content is more lucrative and facile than the hard work of engaging teacher and learners in authentic problem-solving. There is a strong temptation to make things as simple as possible so as to reach the broadest possible audience. But some things are inherently complex. Apps might be fun, but the hard part of “hard fun” is in reaching towards complexity.

We are going where the learners are: Sugar as a Web app, on Android, or on iOS, (Sugarizer) and, tracking the growth of the Maker Movement, we now support Sugar on Raspbian.
“It is said that the best way to learn something is to teach it—and perhaps writing a teaching program is better still in its insistence on forcing one to consider all possible misunderstandings and mistakes.” — Seymour Papert

I have made mistakes, but as part of a learning community we will do better.

“Homework is boring. Looking for bugs is fun.” —Ezequiel Pereira

Let's continue to provide the basis for some fun.

=Sebastian Silva=

The mission of the Sugar Labs Oversight Board is to ensure the community has clarity of purpose and the means to attain its goals.

Sugar Labs needs to recognize that our community is '''diverse'''. Therefore, there are diverse purposes that may be clear and at the same time opposed.

We should provide a '''safe and neutral space''' for dialogue on the technology and education that underlies our projects. We need to approve and enforce a ''code of conduct''.

Finally, the reason for Sugar Labs to exist under the SFC is to '''facilitate the flow of resources''' to volunteers with valuable projects. We should strive to open and fund open calls with funds for development, infrastructure and end user products.

=== About Sebastian ===
Sebastian is father to two precious children that are being homeschooled in collaboration with his dear wife and co-creator Laura Vargas.

As a child, Sebastian learned to program with Logo and soon outgrew it to be charmed with Python and raise the flag of Free/Libre Software. He loves writing Sugar Activities; His latest is a collaborative [http://educa.juegos/#sugarlabs_platform_2017 Python IDE] that he hopes you'll love too.

Currently he lives with his family in a cabin in the Amazon rainforest and teaches Karate and videogame programming to the kids in the vicinity, sustaining a lifestyle seeking harmony with nature and providing services of software artisanship and systems gardening remotely.

=Lionel Laské=
Learn more about my background [[User:Llaske|here]].

Like lot of you I've joined SugarLabs at the beginning of the OLPC project. As cofounder of [http://olpc-france.org OLPC France grassroot], I've worked hard to deploy it on the field and contribute to expand it both in term of activities and in term of French content.
Because the OLPC project and the XO laptop was declining year after year, I've decided 5 years ago to launch the [http://sugarizer.org Sugarizer] initiative. My objective was to write a new page of Sugar history by expanding its compatibility to any device, specifically the favorite education device of today: tablets. I'm very proud that today, two deployments already start to use Sugarizer on Android tablets.

Deployed on more than 2 millions of devices and supported by millions of users, Sugar is the #1 learning platform in the world. But we need to convince this large community that a future exist out of the XO laptop. It's my ambition as candidate to the SugarLabs Oversight Board. As I've done in past month as SLOB member, I will support projects where the goal is to expand the community and give a vision to SugarLabs. Even if it could hurt sometime, I will also refuse to spend our limited resources on ways that not fit into its vision. We're all volunteers and our time is precious, let's continue to invest it where it will be the most useful: give to learners the better free libre education platform.

=Sameer Verma=
My background [[User:Sverma|here]].

== Introduction ==

I am a professor in the Information Systems department at San Francisco State University, in San Francisco, California USA. I also serve on the Board of Directors of the Drupal Association, which gives me significant insights into how large FOSS projects work both in the community and the enterprise. I am the founder of the OLPC San Francisco volunteer community, that continues to be active around OLPC's original mission and projects that have grown from that ecosystem, including Sugar, XS, XOVis and others.

== Experience ==

My experience with Sugar projects are based on a three-pronged approach:

:''Education''

:Understanding constructivist, constructionist, instructional and ad-hoc learning models. I look for accommodating for the gap between what may be prescribed, and what can actually be implemented in the field.

:''Technology''

:Hardware, software, and network combinations that make these projects work in the “middle of nowhere” communities. My professional training comes in handy when working on these technology bits.

:''Social Context''

:Understanding social context is the most important of the three approaches. Providing powerful life-changing educational tools to communities is not enough unless we also understand their cultural and social underpinnings.

== Expected Contribution ==

To maintain Sugar's technology focus as a medium of delivery, while maintaining the education message. I hope to bring my skills and expertise to contribute to the strategic direction of Sugar the project, and its implementations on any device, anywhere.

Sean Daly

I am an independent journalist, formerly working for a large company in IT, communications, advertising and marketing. As my children are (mostly) grown, and I set my own work schedule, I will have time to commit to Sugar again. I have been part of Sugar Labs since 2009, including a term as a SLOB, and was Marketing Coordinator for 5 years.

The major changes in "educational technology" - from computer lab, to netbook, to tablet - mean that beyond the XO platform, Sugar must adapt and indeed is doing so, through Sugarizer and other initiatives. At the same time, the rapid growth of social media has created new opportunities to communicate about Sugar, opportunities which are not being seized today.

As a SLOB, I will work to grow our community and to raise awareness of Sugar.

...

[Candidate Name]

Entry

...

==References==

This election is being run by the [[Sugar_Labs/Governance/Committees#Membership_and_Elections_Committee|Membership and Elections Committee]] which was [[Oversight_Board/Decisions#2017-01-06|appointed in January]], along with Dave Crossland
as an impartial election oversight party.

An update from the Membership and Elections Committee was [http://meeting.sugarlabs.org/sugar-meeting/meetings/2017-08-04T19:01:24#i_2900181 received] during the Oversight Board meeting of August 4. Also listed were the [http://meeting.sugarlabs.org/sugar-meeting/meetings/2017-08-04T19:01:24#i_2900205 expiring slots].

During [http://meeting.sugarlabs.org/sugar-meeting/meetings/2017-09-01T19:10:08 September's meeting] the Board '''confirmed September 27, 2017 as the deadline for new memberships request to participate on 2017-2019 elections'''.

Marketing Team/Website

2011-03-29T22:19:17Z

SeanDaly: /* 2011 website revamp */

====http://www.sugarlabs.org====
In the beginning, the Sugar Labs wiki was the homepage. In the spring of 2009, we prepared a small static HTML intro section to give a high-level overview of the project useful for teachers, parents, and journalists and which would direct people to appropriate areas of the wiki and other sites such as the Activities Library.

==2011 website revamp==
In late 2010 and early 2011, agreement[http://www.mail-archive.com/marketing@lists.sugarlabs.org/msg01294.html] was reached to revamp the www.sugarlabs.org website. The MIT Sloan MarketLab students' work has stimulated important reconsideration of the messages we want to project on this public site. (See [[Marketing_Team#MIT_Sloan_MarketLab_Study]] and March 2011 [[Marketing_Team/Meetings|marketing meetings]].)

Professor Stephen Jacobs of RIT is working with us through two of his students, Mike Devine and JT Mengel, to revamp our website. They travelled to New York on March 18, 2011, and spent the day in a workshop with Christian Marc Schmidt. Snapshots of that day's whiteboards are here: [[Media:NYC_2011March18_website_revamp_workshop_whiteboard1.jpg]] and here: [[Media:NYC_2011March18_website_revamp_workshop_whiteboard2.jpg]]; first version of overview of the new website's sections is here: [[Media:Sugarlabs_workshop_20110318.pdf]]

The sections below are a place to explore and summarize ideas collected from our community on how best to market Sugar Labs through a web site for our primary target market, teachers.

===Collaboration===
''Collaboration'' is a prime distinguishing feature of Sugar that we should naturally project in the image of Sugar Labs.

* We must provide a means to collaborate on the public website.
* We must provide a means to build and maintain the website collaboratively.

The general public can collaborate effectively through blog-style comments and social group sites that link with www.sugarlabs.org. Creative tools are available for public expression and collaboration, and we must learn to put our public to "work" with them to properly engage them in the Sugar Labs Learning experience. This will help extend our Learning Platform into the world wide web.
: (A technical [[Collab mockup|collaboration proposal]] was drafted in January 2010.)

The second goal can be accomplished by starting a wiki version of the main content. Marketing volunteers and others can edit, integrate, and migrate the best submissions from the wiki sandbox and other sources to the main web site.

===Joyful learning===

Children and teachers ''delighted in their learning'' experience is another prime distinguishing feature of Sugar deployments. This results from Sugar's founding principles:

* everyone is a teacher and a learner
* humans by their nature are social beings
* humans by their nature are expressive
* we learn through doing, and
* love is a better master than duty

We can proudly point to visual evidence of this in our [http://www.laptop.org/ OLPC deployments] of Sugar.

The public can learn that it is the Sugar software that powers those computers; and it is people, dedicated to the Sugar principles, that drive the communities to collaborate for such joyful learning.

===A learning laboratory===

The public can learn that Sugar Labs is a learning laboratory, where the most important life skill is practiced and espoused. They can learn how we are a laboratory developing catalysts to revolutionize the field of education. We don't work exclusively in such a broad field, but we hope that we can spark others to recognize and advance some of our developments and to help in finding the most successful ways to stimulate others to join in the mission of advancing learning to the highest possible level.

Sugar Labs' role is to be a focus and lens for Learners to learn learning—as we are, and as we begin with the tools and communities we can assemble. We are not a global university, but the public should be able to recognize that we have some powerful ideas and tools, which are uniquely free, and which have great potential to advance learning and education.

===Learning software===

All the inspiring views of education provided by OLPC, XO, and Sugar images prompt all good-hearted souls to imagine wonderful possibilities for a better world. Technologists see similar possibilities in the Sugar software platform in the broad sense, including the style of development and the fundamentally free expression of human intentions to a world of machines.

Our technologists want to learn how to teach machines to learn to collaborate with humans, and our educators want to learn how to teach humans to learn to learn with machines that can let humans collaborate in their learning. Wow! that's a lot of learning. But the freedom to learn that comes from having such free and powerful ideas and the companion of tools is unlimited.

We need your help in unleashing that potential! If you love children and collaboration and learning, and if you can help us with learning technology and software or any of the important bits needed to enliven and liberate our human potential in a project like this, then please join with us and contribute some of those billions of ways that '''''you''''' might help to propel Sugar learning into the future.

===[[Sugar_Labs#Sugar_Labs:_a_community|Sugar Labs: a community]]===
[[Sugar_Labs#Sugar_Labs:_a_community|Sugar Labs®]] is a non-profit association, consisting entirely of the free contributions of volunteers. Please see our [[Sugar_Labs/Getting_Involved|Getting Involved]] page for how you might contribute. Financial [[Sugar_Labs/Donate|donations]] are used to support grassroots learning innovations and face-to-face meetings between developers and educators.

[[Category:Proposal]]

Marketing Team/Website

2011-03-29T22:18:46Z

SeanDaly: /* 2011 website revamp */

====http://www.sugarlabs.org====
In the beginning, the Sugar Labs wiki was the homepage. In the spring of 2009, we prepared a small static HTML intro section to give a high-level overview of the project useful for teachers, parents, and journalists and which would direct people to appropriate areas of the wiki and other sites such as the Activities Library.

==2011 website revamp==
In late 2010 and early 2011, agreement[http://www.mail-archive.com/marketing@lists.sugarlabs.org/msg01294.html] was reached to revamp the www.sugarlabs.org website. The MIT Sloan MarketLab students' work has stimulated important reconsideration of the messages we want to project on this public site. (See [[Marketing_Team#MIT_Sloan_MarketLab_Study]] and March 2011 [[Marketing_Team/Meetings|marketing meetings]].)

Professor Stephen Jacobs of RIT is working with us through two of his students, Mike Devine and JT Mengel, to revamp our website. They travelled to New York on March 18, 2011, and spent the day in a workshop with Christian Marc Schmidt. Snapshots of that day's whiteboards are here: [[Media:NYC_2011March18_website_revamp_workshop_whiteboard1.jpg]] and here: [[Media:NYC_2011March18_website_revamp_workshop_whiteboard1.jpg]]; first version of overview of the new website's sections is here: [[Media:Sugarlabs_workshop_20110318.pdf]]

The sections below are a place to explore and summarize ideas collected from our community on how best to market Sugar Labs through a web site for our primary target market, teachers.

===Collaboration===
''Collaboration'' is a prime distinguishing feature of Sugar that we should naturally project in the image of Sugar Labs.

* We must provide a means to collaborate on the public website.
* We must provide a means to build and maintain the website collaboratively.

The general public can collaborate effectively through blog-style comments and social group sites that link with www.sugarlabs.org. Creative tools are available for public expression and collaboration, and we must learn to put our public to "work" with them to properly engage them in the Sugar Labs Learning experience. This will help extend our Learning Platform into the world wide web.
: (A technical [[Collab mockup|collaboration proposal]] was drafted in January 2010.)

The second goal can be accomplished by starting a wiki version of the main content. Marketing volunteers and others can edit, integrate, and migrate the best submissions from the wiki sandbox and other sources to the main web site.

===Joyful learning===

Children and teachers ''delighted in their learning'' experience is another prime distinguishing feature of Sugar deployments. This results from Sugar's founding principles:

* everyone is a teacher and a learner
* humans by their nature are social beings
* humans by their nature are expressive
* we learn through doing, and
* love is a better master than duty

We can proudly point to visual evidence of this in our [http://www.laptop.org/ OLPC deployments] of Sugar.

The public can learn that it is the Sugar software that powers those computers; and it is people, dedicated to the Sugar principles, that drive the communities to collaborate for such joyful learning.

===A learning laboratory===

The public can learn that Sugar Labs is a learning laboratory, where the most important life skill is practiced and espoused. They can learn how we are a laboratory developing catalysts to revolutionize the field of education. We don't work exclusively in such a broad field, but we hope that we can spark others to recognize and advance some of our developments and to help in finding the most successful ways to stimulate others to join in the mission of advancing learning to the highest possible level.

Sugar Labs' role is to be a focus and lens for Learners to learn learning—as we are, and as we begin with the tools and communities we can assemble. We are not a global university, but the public should be able to recognize that we have some powerful ideas and tools, which are uniquely free, and which have great potential to advance learning and education.

===Learning software===

All the inspiring views of education provided by OLPC, XO, and Sugar images prompt all good-hearted souls to imagine wonderful possibilities for a better world. Technologists see similar possibilities in the Sugar software platform in the broad sense, including the style of development and the fundamentally free expression of human intentions to a world of machines.

Our technologists want to learn how to teach machines to learn to collaborate with humans, and our educators want to learn how to teach humans to learn to learn with machines that can let humans collaborate in their learning. Wow! that's a lot of learning. But the freedom to learn that comes from having such free and powerful ideas and the companion of tools is unlimited.

We need your help in unleashing that potential! If you love children and collaboration and learning, and if you can help us with learning technology and software or any of the important bits needed to enliven and liberate our human potential in a project like this, then please join with us and contribute some of those billions of ways that '''''you''''' might help to propel Sugar learning into the future.

===[[Sugar_Labs#Sugar_Labs:_a_community|Sugar Labs: a community]]===
[[Sugar_Labs#Sugar_Labs:_a_community|Sugar Labs®]] is a non-profit association, consisting entirely of the free contributions of volunteers. Please see our [[Sugar_Labs/Getting_Involved|Getting Involved]] page for how you might contribute. Financial [[Sugar_Labs/Donate|donations]] are used to support grassroots learning innovations and face-to-face meetings between developers and educators.

[[Category:Proposal]]

Marketing Team

2011-03-29T21:54:19Z

SeanDaly: /* Sugar Labs website */

<noinclude>{{ GoogleTrans-en}}{{TeamHeader|Marketing Team}}</noinclude>

<div style="font-size: 1.0em; background: #daffd5; padding: 10px; border: 1px solid #cde7a8" align=left>'''The Sugar Labs Marketing Team exists to spread the good word about Sugar.''' Sugar provides a simple yet powerful means of engaging young children in the world of learning that is opened up by computing and the Internet. It is the job of the Sugar Labs Marketing Team to promote the benefits of Sugar as widely as possible, and to recruit volunteers to help improve the Sugar experience.</div>

{{TOCright}}

== Mission ==
{{:Marketing Team/Mission}}
== Team Coordinator ==

{{:Marketing Team/Coordinator}} (sdaly at sugarlabs.org) is Marketing Coordinator and welcomes ideas and comments but most of all communicators interested in helping out!

== Mailing list ==

Please see our [http://lists.sugarlabs.org/listinfo/marketing Marketing Team mailing list] and its [http://lists.sugarlabs.org/archive/marketing/ archive].

== Projects ==

Deliverables and/or initiatives actively being worked on (with goals and deadlines).

=== MIT Sloan MarketLab Study ===
In late 2010, four students from the MIT Sloan MarketLab worked on a study of the Sugar Labs website. Their conclusions indicate the importance not only of revamping our website (launched two years ago when fewer visuals were available), but of addressing other aspects, in particular installation and support issues, as well as the technical orientation of our web presence.

The study wiki, with raw data, is here: https://sites.google.com/site/marketlabsugar

Of particular interest: the survey results from 85 respondents, here: [[Media:MarketLab_survey_results.pdf]]

A sample fundraising document by the MarketLab team is here: [[Media:Sugar_Fundraising_Text_Proposal.odt]]

The annotated final presentation is here: [[Media:MIT_MarketLab_Annotated_Presentation.odp]]

=== Sugar Labs website revamp ===

Our polished static website as a landing page for Sugar Labs is in the process of being redone (March-May 2011). [[Marketing Team/Website]]

===[[Marketing_Team/Events|Events]]===
See [[Marketing Team/Events]] for a table of events we are targeting.

=== Press page ===

Our Press page is here: http://www.sugarlabs.org/index.php?template=press

Translator assistance welcomed!

=== Sugar stories ===

How Sugar motivates us: a series of profiles on contributors. [[Marketing Team/Sugar stories]]

=== Press contacts list ===

We're working on a [[Marketing Team/Press contacts]] list with education-oriented publications. This list is maintained by the Marketing Coordinator.

=== PR phone line ===

+1.857.265.1100

[[Marketing Team/Phone]] is a number that journalists can call for quotes, interviews, clarifications, etc. about Sugar. This is a VoIP number which at this time forwards either to the Marketing Coordinator, an Oversight Board member, or voicemail which is forwarded as a timestamped soundfile to pr AT sugarlabs DOT org, an account monitored through forwarding by the Marketing Coordinator and two others. Unfortunately, our provider has gone out of business and is stopping service at the end of March 2011; we hope to find a suitable replacement.

=== [[Marketing Team/Swag|Swag]] ===

To view, download, and contribute to swag designs (stickers, t-shirts, business cards, USB sticks, etc.) and coordinate purchasing swag from suppliers, see [[Marketing Team/Swag]].

== Discussions ==

Conversations that may one day turn into projects, or may have in the past been projects.

=== "Audited" Circulation ===

- [[User:Docdtv|Docdtv]]

While a small user community might discourage adoption of a tool,
a large user community can help encourage adoption. And of course,
small communities need always precede large ones! You know the old
expression: "Eat Sugar! 10**9 flies can't be wrong!" <G>

How do you measure the size of a community? A great way to do that
with automata connected to a global communication network is to
have them "phone home" now and then. Now, I hope what I am suggesting
does not break with any covenent, (implicit or explicit, moral or legal).
But would it be so harmful if, say once a day, a Sugar installation
would briefly tell Sugar Labs "Hey, I'm alive on a machine today!"

Some might agree to do this, but worry about a slippery slope.
Would the future of this humble audit parallel the course of the
United States decennial census, growing from a simple enumeration
into a ruthless and arrogant demographic strip-search?

Of course, audits could be of great benefit to end-users, especially
if they included Activity installation audits. For example, they could
evolve into a mechanism for warning the user about a terrible bug
that needs patching, or advertising a follow-on tool almost all users
adopt upon learning about the new existence of same. (I just now learn
that [http://wiki.laptop.org/go/Automatic_software_updates automatic software updates]
are a new feature of the latest ([http://wiki.laptop.org/go/Release_Notes/8.2.0 8.2.0])
OLPC software release.) By "factoring" the audit mechanism into a
system-wide facility, Activity developers would be spared the need
to code such support on their own.

As a courtesy to Sugar users, cooperation in audits should be voluntary.
But every user should be told why such an audit can help him and others.

Naturally, all this is limited by the fact that not every last machine
on which Sugar will be run will be attached to the Internet.

=== Video channels ===

- [[User:Docdtv|Docdtv]]

1. Does a YouTube channel exist? If not, why not?
There already is a channel at Dailymotion with 19 videos as we write:
http://www.dailymotion.com/sugarlabs/1
YouTube may not use an open source codec, but it is an
incredibly popular search engine and affiliate-propagation tool, see:

http://graphics8.nytimes.com/images/2009/12/31/technology/internet/31tubeGrfx/articleInline.jpg

2. First video would be a 60-second TV-style ad explaining

... what Sugar is (leverage OLPC brand-awareness!)

... that it is free

... what you need to run it

... how you get a copy to install

3. Every time a pitch (q.v. below) is created, a YouTube video record of same is made.
The YouTube version can add stills or short video clips to a talking head.

=== Pitches ===

Short, 1-page elevator pitches to sell Sugar to various audiences. Not formalized, but the homepage (www.sugarlabs.org) is the best starting point. [[Marketing Team/Pitches]]

=== Logo ===

See [[Marketing Team/Logo]].

=== Name ===

Ongoing discussion. See [[Marketing Team/Name]]

=== Slogans ===

Several slogan options are available at [[Marketing Team/Slogan]].

== Subpages ==

{{Special:PrefixIndex/Marketing_Team/}}

[[Category:Marketing Team]]
[[Category:Team]]

Marketing Team

2011-03-29T21:53:46Z

SeanDaly: /* Projects */

<noinclude>{{ GoogleTrans-en}}{{TeamHeader|Marketing Team}}</noinclude>

<div style="font-size: 1.0em; background: #daffd5; padding: 10px; border: 1px solid #cde7a8" align=left>'''The Sugar Labs Marketing Team exists to spread the good word about Sugar.''' Sugar provides a simple yet powerful means of engaging young children in the world of learning that is opened up by computing and the Internet. It is the job of the Sugar Labs Marketing Team to promote the benefits of Sugar as widely as possible, and to recruit volunteers to help improve the Sugar experience.</div>

{{TOCright}}

== Mission ==
{{:Marketing Team/Mission}}
== Team Coordinator ==

{{:Marketing Team/Coordinator}} (sdaly at sugarlabs.org) is Marketing Coordinator and welcomes ideas and comments but most of all communicators interested in helping out!

== Mailing list ==

Please see our [http://lists.sugarlabs.org/listinfo/marketing Marketing Team mailing list] and its [http://lists.sugarlabs.org/archive/marketing/ archive].

== Projects ==

Deliverables and/or initiatives actively being worked on (with goals and deadlines).

=== MIT Sloan MarketLab Study ===
In late 2010, four students from the MIT Sloan MarketLab worked on a study of the Sugar Labs website. Their conclusions indicate the importance not only of revamping our website (launched two years ago when fewer visuals were available), but of addressing other aspects, in particular installation and support issues, as well as the technical orientation of our web presence.

The study wiki, with raw data, is here: https://sites.google.com/site/marketlabsugar

Of particular interest: the survey results from 85 respondents, here: [[Media:MarketLab_survey_results.pdf]]

A sample fundraising document by the MarketLab team is here: [[Media:Sugar_Fundraising_Text_Proposal.odt]]

The annotated final presentation is here: [[Media:MIT_MarketLab_Annotated_Presentation.odp]]

=== Sugar Labs website ===

Our polished static website as a landing page for Sugar Labs is in the process of being redone (March-May 2011). [[Marketing Team/Website]]

===[[Marketing_Team/Events|Events]]===
See [[Marketing Team/Events]] for a table of events we are targeting.

=== Press page ===

Our Press page is here: http://www.sugarlabs.org/index.php?template=press

Translator assistance welcomed!

=== Sugar stories ===

How Sugar motivates us: a series of profiles on contributors. [[Marketing Team/Sugar stories]]

=== Press contacts list ===

We're working on a [[Marketing Team/Press contacts]] list with education-oriented publications. This list is maintained by the Marketing Coordinator.

=== PR phone line ===

+1.857.265.1100

[[Marketing Team/Phone]] is a number that journalists can call for quotes, interviews, clarifications, etc. about Sugar. This is a VoIP number which at this time forwards either to the Marketing Coordinator, an Oversight Board member, or voicemail which is forwarded as a timestamped soundfile to pr AT sugarlabs DOT org, an account monitored through forwarding by the Marketing Coordinator and two others. Unfortunately, our provider has gone out of business and is stopping service at the end of March 2011; we hope to find a suitable replacement.

=== [[Marketing Team/Swag|Swag]] ===

To view, download, and contribute to swag designs (stickers, t-shirts, business cards, USB sticks, etc.) and coordinate purchasing swag from suppliers, see [[Marketing Team/Swag]].

== Discussions ==

Conversations that may one day turn into projects, or may have in the past been projects.

=== "Audited" Circulation ===

- [[User:Docdtv|Docdtv]]

While a small user community might discourage adoption of a tool,
a large user community can help encourage adoption. And of course,
small communities need always precede large ones! You know the old
expression: "Eat Sugar! 10**9 flies can't be wrong!" <G>

How do you measure the size of a community? A great way to do that
with automata connected to a global communication network is to
have them "phone home" now and then. Now, I hope what I am suggesting
does not break with any covenent, (implicit or explicit, moral or legal).
But would it be so harmful if, say once a day, a Sugar installation
would briefly tell Sugar Labs "Hey, I'm alive on a machine today!"

Some might agree to do this, but worry about a slippery slope.
Would the future of this humble audit parallel the course of the
United States decennial census, growing from a simple enumeration
into a ruthless and arrogant demographic strip-search?

Of course, audits could be of great benefit to end-users, especially
if they included Activity installation audits. For example, they could
evolve into a mechanism for warning the user about a terrible bug
that needs patching, or advertising a follow-on tool almost all users
adopt upon learning about the new existence of same. (I just now learn
that [http://wiki.laptop.org/go/Automatic_software_updates automatic software updates]
are a new feature of the latest ([http://wiki.laptop.org/go/Release_Notes/8.2.0 8.2.0])
OLPC software release.) By "factoring" the audit mechanism into a
system-wide facility, Activity developers would be spared the need
to code such support on their own.

As a courtesy to Sugar users, cooperation in audits should be voluntary.
But every user should be told why such an audit can help him and others.

Naturally, all this is limited by the fact that not every last machine
on which Sugar will be run will be attached to the Internet.

=== Video channels ===

- [[User:Docdtv|Docdtv]]

1. Does a YouTube channel exist? If not, why not?
There already is a channel at Dailymotion with 19 videos as we write:
http://www.dailymotion.com/sugarlabs/1
YouTube may not use an open source codec, but it is an
incredibly popular search engine and affiliate-propagation tool, see:

http://graphics8.nytimes.com/images/2009/12/31/technology/internet/31tubeGrfx/articleInline.jpg

2. First video would be a 60-second TV-style ad explaining

... what Sugar is (leverage OLPC brand-awareness!)

... that it is free

... what you need to run it

... how you get a copy to install

3. Every time a pitch (q.v. below) is created, a YouTube video record of same is made.
The YouTube version can add stills or short video clips to a talking head.

=== Pitches ===

Short, 1-page elevator pitches to sell Sugar to various audiences. Not formalized, but the homepage (www.sugarlabs.org) is the best starting point. [[Marketing Team/Pitches]]

=== Logo ===

See [[Marketing Team/Logo]].

=== Name ===

Ongoing discussion. See [[Marketing Team/Name]]

=== Slogans ===

Several slogan options are available at [[Marketing Team/Slogan]].

== Subpages ==

{{Special:PrefixIndex/Marketing_Team/}}

[[Category:Marketing Team]]
[[Category:Team]]

Marketing Team/Website

2011-03-29T21:42:12Z

SeanDaly: /* Website 2 */

====http://www.sugarlabs.org====
In the beginning, the Sugar Labs wiki was the homepage. In the spring of 2009, we prepared a small static HTML intro section to give a high-level overview of the project useful for teachers, parents, and journalists and which would direct people to appropriate areas of the wiki and other sites such as the Activities Library.

==2011 website revamp==
In late 2010 and early 2011, agreement[http://www.mail-archive.com/marketing@lists.sugarlabs.org/msg01294.html] was reached to revamp the www.sugarlabs.org website. The MIT Sloan MarketLab students' work has stimulated important reconsideration of the messages we want to project on this public site. (See [[Marketing_Team#MIT_Sloan_MarketLab_Study]] and March 2011 [[Marketing_Team/Meetings|marketing meetings]].)

Professor Jacobs of RIT is working with us through two of his students, Mike Devine and JT Mengel, to revamp our website. They travelled to New York on March 18, 2011, and spent the day in a workshop with Christian Marc Schmidt. Snapshots of that day's whiteboards are here: [[Media:NYC_2011March18_website_revamp_workshop_whiteboard1.jpg]] and here: [[Media:NYC_2011March18_website_revamp_workshop_whiteboard1.jpg]]; first version of overview of the new website's sections is here: [[Media:Sugarlabs_workshop_20110318.pdf]]

The sections below are a place to explore and summarize ideas collected from our community on how best to market Sugar Labs through a web site for our primary target market, teachers.

===Collaboration===
''Collaboration'' is a prime distinguishing feature of Sugar that we should naturally project in the image of Sugar Labs.

* We must provide a means to collaborate on the public website.
* We must provide a means to build and maintain the website collaboratively.

The general public can collaborate effectively through blog-style comments and social group sites that link with www.sugarlabs.org. Creative tools are available for public expression and collaboration, and we must learn to put our public to "work" with them to properly engage them in the Sugar Labs Learning experience. This will help extend our Learning Platform into the world wide web.
: (A technical [[Collab mockup|collaboration proposal]] was drafted in January 2010.)

The second goal can be accomplished by starting a wiki version of the main content. Marketing volunteers and others can edit, integrate, and migrate the best submissions from the wiki sandbox and other sources to the main web site.

===Joyful learning===

Children and teachers ''delighted in their learning'' experience is another prime distinguishing feature of Sugar deployments. This results from Sugar's founding principles:

* everyone is a teacher and a learner
* humans by their nature are social beings
* humans by their nature are expressive
* we learn through doing, and
* love is a better master than duty

We can proudly point to visual evidence of this in our [http://www.laptop.org/ OLPC deployments] of Sugar.

The public can learn that it is the Sugar software that powers those computers; and it is people, dedicated to the Sugar principles, that drive the communities to collaborate for such joyful learning.

===A learning laboratory===

The public can learn that Sugar Labs is a learning laboratory, where the most important life skill is practiced and espoused. They can learn how we are a laboratory developing catalysts to revolutionize the field of education. We don't work exclusively in such a broad field, but we hope that we can spark others to recognize and advance some of our developments and to help in finding the most successful ways to stimulate others to join in the mission of advancing learning to the highest possible level.

Sugar Labs' role is to be a focus and lens for Learners to learn learning—as we are, and as we begin with the tools and communities we can assemble. We are not a global university, but the public should be able to recognize that we have some powerful ideas and tools, which are uniquely free, and which have great potential to advance learning and education.

===Learning software===

All the inspiring views of education provided by OLPC, XO, and Sugar images prompt all good-hearted souls to imagine wonderful possibilities for a better world. Technologists see similar possibilities in the Sugar software platform in the broad sense, including the style of development and the fundamentally free expression of human intentions to a world of machines.

Our technologists want to learn how to teach machines to learn to collaborate with humans, and our educators want to learn how to teach humans to learn to learn with machines that can let humans collaborate in their learning. Wow! that's a lot of learning. But the freedom to learn that comes from having such free and powerful ideas and the companion of tools is unlimited.

We need your help in unleashing that potential! If you love children and collaboration and learning, and if you can help us with learning technology and software or any of the important bits needed to enliven and liberate our human potential in a project like this, then please join with us and contribute some of those billions of ways that '''''you''''' might help to propel Sugar learning into the future.

===[[Sugar_Labs#Sugar_Labs:_a_community|Sugar Labs: a community]]===
[[Sugar_Labs#Sugar_Labs:_a_community|Sugar Labs®]] is a non-profit association, consisting entirely of the free contributions of volunteers. Please see our [[Sugar_Labs/Getting_Involved|Getting Involved]] page for how you might contribute. Financial [[Sugar_Labs/Donate|donations]] are used to support grassroots learning innovations and face-to-face meetings between developers and educators.

[[Category:Proposal]]

Marketing Team/Website

2011-03-29T21:32:34Z

SeanDaly: /* Website 2 */

====http://www.sugarlabs.org====
In the beginning, the Sugar Labs wiki was the homepage. In the spring of 2009, we prepared a small static HTML intro section to give a high-level overview of the project useful for teachers, parents, and journalists and which would direct people to appropriate areas of the wiki and other sites such as the Activities Library.

==Website 2==
In late 2010 and early 2011, agreement[http://www.mail-archive.com/marketing@lists.sugarlabs.org/msg01294.html] was reached to revamp the www.sugarlabs.org website. The MIT Sloan MarketLab students' work has stimulated important reconsideration of the messages we want to project on this public site. (See [[Marketing_Team#MIT_Sloan_MarketLab_Study]] and March 2011 [[Marketing_Team/Meetings|marketing meetings]].)

Professor Jacobs of RIT is working with us through two of his students, Mike Devine and JT Mengel, to revamp our website. They travelled to New York on March 18, 2011, and spent the day in a workshop with Christian Marc Schmidt. Snapshots of that day's whiteboards are here: [[Media:NYC_2011March18_website_revamp_workshop_whiteboard1.jpg]] and here: [[Media:NYC_2011March18_website_revamp_workshop_whiteboard1.jpg]]; first version of overview of the new website's sections is here: [[Media:Sugarlabs_workshop_20110318.pdf]]

The sections below are a place to explore and summarize ideas collected from our community on how best to market Sugar Labs through a web site for our primary target market, teachers.

===Collaboration===
''Collaboration'' is a prime distinguishing feature of Sugar that we should naturally project in the image of Sugar Labs.

* We must provide a means to collaborate on the public website.
* We must provide a means to build and maintain the website collaboratively.

The general public can collaborate effectively through blog-style comments and social group sites that link with www.sugarlabs.org. Creative tools are available for public expression and collaboration, and we must learn to put our public to "work" with them to properly engage them in the Sugar Labs Learning experience. This will help extend our Learning Platform into the world wide web.
: (A technical [[Collab mockup|collaboration proposal]] was drafted in January 2010.)

The second goal can be accomplished by starting a wiki version of the main content. Marketing volunteers and others can edit, integrate, and migrate the best submissions from the wiki sandbox and other sources to the main web site.

===Joyful learning===

Children and teachers ''delighted in their learning'' experience is another prime distinguishing feature of Sugar deployments. This results from Sugar's founding principles:

* everyone is a teacher and a learner
* humans by their nature are social beings
* humans by their nature are expressive
* we learn through doing, and
* love is a better master than duty

We can proudly point to visual evidence of this in our [http://www.laptop.org/ OLPC deployments] of Sugar.

The public can learn that it is the Sugar software that powers those computers; and it is people, dedicated to the Sugar principles, that drive the communities to collaborate for such joyful learning.

===A learning laboratory===

The public can learn that Sugar Labs is a learning laboratory, where the most important life skill is practiced and espoused. They can learn how we are a laboratory developing catalysts to revolutionize the field of education. We don't work exclusively in such a broad field, but we hope that we can spark others to recognize and advance some of our developments and to help in finding the most successful ways to stimulate others to join in the mission of advancing learning to the highest possible level.

Sugar Labs' role is to be a focus and lens for Learners to learn learning—as we are, and as we begin with the tools and communities we can assemble. We are not a global university, but the public should be able to recognize that we have some powerful ideas and tools, which are uniquely free, and which have great potential to advance learning and education.

===Learning software===

All the inspiring views of education provided by OLPC, XO, and Sugar images prompt all good-hearted souls to imagine wonderful possibilities for a better world. Technologists see similar possibilities in the Sugar software platform in the broad sense, including the style of development and the fundamentally free expression of human intentions to a world of machines.

Our technologists want to learn how to teach machines to learn to collaborate with humans, and our educators want to learn how to teach humans to learn to learn with machines that can let humans collaborate in their learning. Wow! that's a lot of learning. But the freedom to learn that comes from having such free and powerful ideas and the companion of tools is unlimited.

We need your help in unleashing that potential! If you love children and collaboration and learning, and if you can help us with learning technology and software or any of the important bits needed to enliven and liberate our human potential in a project like this, then please join with us and contribute some of those billions of ways that '''''you''''' might help to propel Sugar learning into the future.

===[[Sugar_Labs#Sugar_Labs:_a_community|Sugar Labs: a community]]===
[[Sugar_Labs#Sugar_Labs:_a_community|Sugar Labs®]] is a non-profit association, consisting entirely of the free contributions of volunteers. Please see our [[Sugar_Labs/Getting_Involved|Getting Involved]] page for how you might contribute. Financial [[Sugar_Labs/Donate|donations]] are used to support grassroots learning innovations and face-to-face meetings between developers and educators.

[[Category:Proposal]]

File:Sugarlabs workshop 20110318.pdf

2011-03-29T21:23:59Z

SeanDaly: First version of website revamp sections (not pages), from New York workshop on March 18, 2011. Participants: Christian Marc Schmidt and RIT students Mike Devine and JT Mengel.

First version of website revamp sections (not pages), from New York workshop on March 18, 2011. Participants: Christian Marc Schmidt and RIT students Mike Devine and JT Mengel.

File:NYC 2011March18 website revamp workshop whiteboard2.jpg

2011-03-29T21:21:21Z

SeanDaly: Snapshot photo 2 of whiteboard at New York workshop on March 18,2011. Participants: Christian Marc Schmidt and RIT students Mike Devine and JT Mengel.

Snapshot photo 2 of whiteboard at New York workshop on March 18,2011. Participants: Christian Marc Schmidt and RIT students Mike Devine and JT Mengel.

File:NYC 2011March18 website revamp workshop whiteboard1.jpg

2011-03-29T21:19:49Z

SeanDaly: Snapshot photo 1 of whiteboard at New York workshop on March 18,2011. Participants: Christian Marc Schmidt and RIT students Mike Devine and JT Mengel.

Snapshot photo 1 of whiteboard at New York workshop on March 18,2011. Participants: Christian Marc Schmidt and RIT students Mike Devine and JT Mengel.

Marketing Team/Website

2011-03-29T21:11:14Z

SeanDaly: /* Website 2 */

====http://www.sugarlabs.org====
In the beginning, the Sugar Labs wiki was the homepage. In the spring of 2009, we prepared a small static HTML intro section to give a high-level overview of the project useful for teachers, parents, and journalists and which would direct people to appropriate areas of the wiki and other sites such as the Activities Library.

==Website 2==
In late 2010 and early 2011, agreement[http://www.mail-archive.com/marketing@lists.sugarlabs.org/msg01294.html] was reached to revamp the www.sugarlabs.org website. The MIT Sloan MarketLab students' work has stimulated important reconsideration of the messages we want to project on this public site. (See [[Marketing_Team#MIT_Sloan_MarketLab_Study]] and March 2011 [[Marketing_Team/Meetings|marketing meetings]].)

The sections below are a place to explore and summarize ideas collected from our community on how best to market Sugar Labs through a web site for our primary target market, teachers.

===Collaboration===
''Collaboration'' is a prime distinguishing feature of Sugar that we should naturally project in the image of Sugar Labs.

* We must provide a means to collaborate on the public website.
* We must provide a means to build and maintain the website collaboratively.

The general public can collaborate effectively through blog-style comments and social group sites that link with www.sugarlabs.org. Creative tools are available for public expression and collaboration, and we must learn to put our public to "work" with them to properly engage them in the Sugar Labs Learning experience. This will help extend our Learning Platform into the world wide web.
: (A technical [[Collab mockup|collaboration proposal]] was drafted in January 2010.)

The second goal can be accomplished by starting a wiki version of the main content. Marketing volunteers and others can edit, integrate, and migrate the best submissions from the wiki sandbox and other sources to the main web site.

===Joyful learning===

Children and teachers ''delighted in their learning'' experience is another prime distinguishing feature of Sugar deployments. This results from Sugar's founding principles:

* everyone is a teacher and a learner
* humans by their nature are social beings
* humans by their nature are expressive
* we learn through doing, and
* love is a better master than duty

We can proudly point to visual evidence of this in our [http://www.laptop.org/ OLPC deployments] of Sugar.

The public can learn that it is the Sugar software that powers those computers; and it is people, dedicated to the Sugar principles, that drive the communities to collaborate for such joyful learning.

===A learning laboratory===

The public can learn that Sugar Labs is a learning laboratory, where the most important life skill is practiced and espoused. They can learn how we are a laboratory developing catalysts to revolutionize the field of education. We don't work exclusively in such a broad field, but we hope that we can spark others to recognize and advance some of our developments and to help in finding the most successful ways to stimulate others to join in the mission of advancing learning to the highest possible level.

Sugar Labs' role is to be a focus and lens for Learners to learn learning—as we are, and as we begin with the tools and communities we can assemble. We are not a global university, but the public should be able to recognize that we have some powerful ideas and tools, which are uniquely free, and which have great potential to advance learning and education.

===Learning software===

All the inspiring views of education provided by OLPC, XO, and Sugar images prompt all good-hearted souls to imagine wonderful possibilities for a better world. Technologists see similar possibilities in the Sugar software platform in the broad sense, including the style of development and the fundamentally free expression of human intentions to a world of machines.

Our technologists want to learn how to teach machines to learn to collaborate with humans, and our educators want to learn how to teach humans to learn to learn with machines that can let humans collaborate in their learning. Wow! that's a lot of learning. But the freedom to learn that comes from having such free and powerful ideas and the companion of tools is unlimited.

We need your help in unleashing that potential! If you love children and collaboration and learning, and if you can help us with learning technology and software or any of the important bits needed to enliven and liberate our human potential in a project like this, then please join with us and contribute some of those billions of ways that '''''you''''' might help to propel Sugar learning into the future.

===[[Sugar_Labs#Sugar_Labs:_a_community|Sugar Labs: a community]]===
[[Sugar_Labs#Sugar_Labs:_a_community|Sugar Labs®]] is a non-profit association, consisting entirely of the free contributions of volunteers. Please see our [[Sugar_Labs/Getting_Involved|Getting Involved]] page for how you might contribute. Financial [[Sugar_Labs/Donate|donations]] are used to support grassroots learning innovations and face-to-face meetings between developers and educators.

[[Category:Proposal]]

Marketing Team/Website

2011-03-29T21:10:01Z

SeanDaly: /* http://www.sugarlabs.org */

====http://www.sugarlabs.org====
In the beginning, the Sugar Labs wiki was the homepage. In the spring of 2009, we prepared a small static HTML intro section to give a high-level overview of the project useful for teachers, parents, and journalists and which would direct people to appropriate areas of the wiki and other sites such as the Activities Library.

==Website 2==
In late 2010 and early 2011, agreement[http://www.mail-archive.com/marketing@lists.sugarlabs.org/msg01294.html] was reached to revamp the www.sugarlabs.org website. The MarketLab consultants and volunteers have stimulated important reconsideration of the messages we want to project on this public site. (See [[Marketing_Team#MIT_Sloan_MarketLab_Study]] and March 2011 [[Marketing_Team/Meetings|marketing meetings]].)

The sections below are a place to explore and summarize ideas collected from our community on how best to market Sugar Labs through a web site for our primary target market, teachers.

===Collaboration===
''Collaboration'' is a prime distinguishing feature of Sugar that we should naturally project in the image of Sugar Labs.

* We must provide a means to collaborate on the public website.
* We must provide a means to build and maintain the website collaboratively.

The general public can collaborate effectively through blog-style comments and social group sites that link with www.sugarlabs.org. Creative tools are available for public expression and collaboration, and we must learn to put our public to "work" with them to properly engage them in the Sugar Labs Learning experience. This will help extend our Learning Platform into the world wide web.
: (A technical [[Collab mockup|collaboration proposal]] was drafted in January 2010.)

The second goal can be accomplished by starting a wiki version of the main content. Marketing volunteers and others can edit, integrate, and migrate the best submissions from the wiki sandbox and other sources to the main web site.

===Joyful learning===

Children and teachers ''delighted in their learning'' experience is another prime distinguishing feature of Sugar deployments. This results from Sugar's founding principles:

* everyone is a teacher and a learner
* humans by their nature are social beings
* humans by their nature are expressive
* we learn through doing, and
* love is a better master than duty

We can proudly point to visual evidence of this in our [http://www.laptop.org/ OLPC deployments] of Sugar.

The public can learn that it is the Sugar software that powers those computers; and it is people, dedicated to the Sugar principles, that drive the communities to collaborate for such joyful learning.

===A learning laboratory===

The public can learn that Sugar Labs is a learning laboratory, where the most important life skill is practiced and espoused. They can learn how we are a laboratory developing catalysts to revolutionize the field of education. We don't work exclusively in such a broad field, but we hope that we can spark others to recognize and advance some of our developments and to help in finding the most successful ways to stimulate others to join in the mission of advancing learning to the highest possible level.

Sugar Labs' role is to be a focus and lens for Learners to learn learning—as we are, and as we begin with the tools and communities we can assemble. We are not a global university, but the public should be able to recognize that we have some powerful ideas and tools, which are uniquely free, and which have great potential to advance learning and education.

===Learning software===

All the inspiring views of education provided by OLPC, XO, and Sugar images prompt all good-hearted souls to imagine wonderful possibilities for a better world. Technologists see similar possibilities in the Sugar software platform in the broad sense, including the style of development and the fundamentally free expression of human intentions to a world of machines.

Our technologists want to learn how to teach machines to learn to collaborate with humans, and our educators want to learn how to teach humans to learn to learn with machines that can let humans collaborate in their learning. Wow! that's a lot of learning. But the freedom to learn that comes from having such free and powerful ideas and the companion of tools is unlimited.

We need your help in unleashing that potential! If you love children and collaboration and learning, and if you can help us with learning technology and software or any of the important bits needed to enliven and liberate our human potential in a project like this, then please join with us and contribute some of those billions of ways that '''''you''''' might help to propel Sugar learning into the future.

===[[Sugar_Labs#Sugar_Labs:_a_community|Sugar Labs: a community]]===
[[Sugar_Labs#Sugar_Labs:_a_community|Sugar Labs®]] is a non-profit association, consisting entirely of the free contributions of volunteers. Please see our [[Sugar_Labs/Getting_Involved|Getting Involved]] page for how you might contribute. Financial [[Sugar_Labs/Donate|donations]] are used to support grassroots learning innovations and face-to-face meetings between developers and educators.

[[Category:Proposal]]

Marketing Team/Website

2011-03-29T21:09:13Z

SeanDaly: /* http://www.sugarlabs.org */

====http://www.sugarlabs.org====
In the beginning, the Sugar Labs wiki was the homepage. Then, we prepared a small static HTML intro section to give a high-level overview of the project useful for teachers, parents, and journalists and which would direct people to appropriate areas of the wiki and other sites such as the Activities Library.

==Website 2==
In late 2010 and early 2011, agreement[http://www.mail-archive.com/marketing@lists.sugarlabs.org/msg01294.html] was reached to revamp the www.sugarlabs.org website. The MarketLab consultants and volunteers have stimulated important reconsideration of the messages we want to project on this public site. (See [[Marketing_Team#MIT_Sloan_MarketLab_Study]] and March 2011 [[Marketing_Team/Meetings|marketing meetings]].)

The sections below are a place to explore and summarize ideas collected from our community on how best to market Sugar Labs through a web site for our primary target market, teachers.

===Collaboration===
''Collaboration'' is a prime distinguishing feature of Sugar that we should naturally project in the image of Sugar Labs.

* We must provide a means to collaborate on the public website.
* We must provide a means to build and maintain the website collaboratively.

The general public can collaborate effectively through blog-style comments and social group sites that link with www.sugarlabs.org. Creative tools are available for public expression and collaboration, and we must learn to put our public to "work" with them to properly engage them in the Sugar Labs Learning experience. This will help extend our Learning Platform into the world wide web.
: (A technical [[Collab mockup|collaboration proposal]] was drafted in January 2010.)

The second goal can be accomplished by starting a wiki version of the main content. Marketing volunteers and others can edit, integrate, and migrate the best submissions from the wiki sandbox and other sources to the main web site.

===Joyful learning===

Children and teachers ''delighted in their learning'' experience is another prime distinguishing feature of Sugar deployments. This results from Sugar's founding principles:

* everyone is a teacher and a learner
* humans by their nature are social beings
* humans by their nature are expressive
* we learn through doing, and
* love is a better master than duty

We can proudly point to visual evidence of this in our [http://www.laptop.org/ OLPC deployments] of Sugar.

The public can learn that it is the Sugar software that powers those computers; and it is people, dedicated to the Sugar principles, that drive the communities to collaborate for such joyful learning.

===A learning laboratory===

The public can learn that Sugar Labs is a learning laboratory, where the most important life skill is practiced and espoused. They can learn how we are a laboratory developing catalysts to revolutionize the field of education. We don't work exclusively in such a broad field, but we hope that we can spark others to recognize and advance some of our developments and to help in finding the most successful ways to stimulate others to join in the mission of advancing learning to the highest possible level.

Sugar Labs' role is to be a focus and lens for Learners to learn learning—as we are, and as we begin with the tools and communities we can assemble. We are not a global university, but the public should be able to recognize that we have some powerful ideas and tools, which are uniquely free, and which have great potential to advance learning and education.

===Learning software===

All the inspiring views of education provided by OLPC, XO, and Sugar images prompt all good-hearted souls to imagine wonderful possibilities for a better world. Technologists see similar possibilities in the Sugar software platform in the broad sense, including the style of development and the fundamentally free expression of human intentions to a world of machines.

Our technologists want to learn how to teach machines to learn to collaborate with humans, and our educators want to learn how to teach humans to learn to learn with machines that can let humans collaborate in their learning. Wow! that's a lot of learning. But the freedom to learn that comes from having such free and powerful ideas and the companion of tools is unlimited.

We need your help in unleashing that potential! If you love children and collaboration and learning, and if you can help us with learning technology and software or any of the important bits needed to enliven and liberate our human potential in a project like this, then please join with us and contribute some of those billions of ways that '''''you''''' might help to propel Sugar learning into the future.

===[[Sugar_Labs#Sugar_Labs:_a_community|Sugar Labs: a community]]===
[[Sugar_Labs#Sugar_Labs:_a_community|Sugar Labs®]] is a non-profit association, consisting entirely of the free contributions of volunteers. Please see our [[Sugar_Labs/Getting_Involved|Getting Involved]] page for how you might contribute. Financial [[Sugar_Labs/Donate|donations]] are used to support grassroots learning innovations and face-to-face meetings between developers and educators.

[[Category:Proposal]]

Marketing Team/Website

2011-03-29T21:08:20Z

SeanDaly: /* Website 2 */

====http://www.sugarlabs.org====
In the beginning, the Sugar Labs wiki was the homepage. Then, we prepared a small static HTML intro section to give a high-level overview of the project useful for teachers, parents, and journalists and which would direct people to appropriate areas of the wiki and other sites such as the Activities Library.

Christian did the intro and is working on the sitewide navbar: [mailto:anything@christianmarcschmidt.com anything@christianmarcschmidt.com]

==Website 2==
In late 2010 and early 2011, agreement[http://www.mail-archive.com/marketing@lists.sugarlabs.org/msg01294.html] was reached to revamp the www.sugarlabs.org website. The MarketLab consultants and volunteers have stimulated important reconsideration of the messages we want to project on this public site. (See [[Marketing_Team#MIT_Sloan_MarketLab_Study]] and March 2011 [[Marketing_Team/Meetings|marketing meetings]].)

The sections below are a place to explore and summarize ideas collected from our community on how best to market Sugar Labs through a web site for our primary target market, teachers.

===Collaboration===
''Collaboration'' is a prime distinguishing feature of Sugar that we should naturally project in the image of Sugar Labs.

* We must provide a means to collaborate on the public website.
* We must provide a means to build and maintain the website collaboratively.

The general public can collaborate effectively through blog-style comments and social group sites that link with www.sugarlabs.org. Creative tools are available for public expression and collaboration, and we must learn to put our public to "work" with them to properly engage them in the Sugar Labs Learning experience. This will help extend our Learning Platform into the world wide web.
: (A technical [[Collab mockup|collaboration proposal]] was drafted in January 2010.)

The second goal can be accomplished by starting a wiki version of the main content. Marketing volunteers and others can edit, integrate, and migrate the best submissions from the wiki sandbox and other sources to the main web site.

===Joyful learning===

Children and teachers ''delighted in their learning'' experience is another prime distinguishing feature of Sugar deployments. This results from Sugar's founding principles:

* everyone is a teacher and a learner
* humans by their nature are social beings
* humans by their nature are expressive
* we learn through doing, and
* love is a better master than duty

We can proudly point to visual evidence of this in our [http://www.laptop.org/ OLPC deployments] of Sugar.

The public can learn that it is the Sugar software that powers those computers; and it is people, dedicated to the Sugar principles, that drive the communities to collaborate for such joyful learning.

===A learning laboratory===

The public can learn that Sugar Labs is a learning laboratory, where the most important life skill is practiced and espoused. They can learn how we are a laboratory developing catalysts to revolutionize the field of education. We don't work exclusively in such a broad field, but we hope that we can spark others to recognize and advance some of our developments and to help in finding the most successful ways to stimulate others to join in the mission of advancing learning to the highest possible level.

Sugar Labs' role is to be a focus and lens for Learners to learn learning—as we are, and as we begin with the tools and communities we can assemble. We are not a global university, but the public should be able to recognize that we have some powerful ideas and tools, which are uniquely free, and which have great potential to advance learning and education.

===Learning software===

All the inspiring views of education provided by OLPC, XO, and Sugar images prompt all good-hearted souls to imagine wonderful possibilities for a better world. Technologists see similar possibilities in the Sugar software platform in the broad sense, including the style of development and the fundamentally free expression of human intentions to a world of machines.

Our technologists want to learn how to teach machines to learn to collaborate with humans, and our educators want to learn how to teach humans to learn to learn with machines that can let humans collaborate in their learning. Wow! that's a lot of learning. But the freedom to learn that comes from having such free and powerful ideas and the companion of tools is unlimited.

We need your help in unleashing that potential! If you love children and collaboration and learning, and if you can help us with learning technology and software or any of the important bits needed to enliven and liberate our human potential in a project like this, then please join with us and contribute some of those billions of ways that '''''you''''' might help to propel Sugar learning into the future.

===[[Sugar_Labs#Sugar_Labs:_a_community|Sugar Labs: a community]]===
[[Sugar_Labs#Sugar_Labs:_a_community|Sugar Labs®]] is a non-profit association, consisting entirely of the free contributions of volunteers. Please see our [[Sugar_Labs/Getting_Involved|Getting Involved]] page for how you might contribute. Financial [[Sugar_Labs/Donate|donations]] are used to support grassroots learning innovations and face-to-face meetings between developers and educators.

[[Category:Proposal]]

Marketing Team/Website

2011-03-29T21:05:03Z

SeanDaly: /* Website 2 */

====http://www.sugarlabs.org====
In the beginning, the Sugar Labs wiki was the homepage. Then, we prepared a small static HTML intro section to give a high-level overview of the project useful for teachers, parents, and journalists and which would direct people to appropriate areas of the wiki and other sites such as the Activities Library.

Christian did the intro and is working on the sitewide navbar: [mailto:anything@christianmarcschmidt.com anything@christianmarcschmidt.com]

==Website 2==
In late 2010 and early 2011, agreement[http://www.mail-archive.com/marketing@lists.sugarlabs.org/msg01294.html] was reached to revamp the www.sugarlabs.org website. The MarketLab consultants and volunteers have stimulated important reconsideration of the messages we want to project on this public site. (See [[Marketing_Team#MIT_Sloan_MarketLab_Study]].)

The sections below are a place to explore and summarize ideas collected from our community on how best to market Sugar Labs through a web site for our primary target market, teachers.

===Collaboration===
''Collaboration'' is a prime distinguishing feature of Sugar that we should naturally project in the image of Sugar Labs.

* We must provide a means to collaborate on the public website.
* We must provide a means to build and maintain the website collaboratively.

The general public can collaborate effectively through blog-style comments and social group sites that link with www.sugarlabs.org. Creative tools are available for public expression and collaboration, and we must learn to put our public to "work" with them to properly engage them in the Sugar Labs Learning experience. This will help extend our Learning Platform into the world wide web.
: (A technical [[Collab mockup|collaboration proposal]] was drafted in January 2010.)

The second goal can be accomplished by starting a wiki version of the main content. Marketing volunteers and others can edit, integrate, and migrate the best submissions from the wiki sandbox and other sources to the main web site.

===Joyful learning===

Children and teachers ''delighted in their learning'' experience is another prime distinguishing feature of Sugar deployments. This results from Sugar's founding principles:

* everyone is a teacher and a learner
* humans by their nature are social beings
* humans by their nature are expressive
* we learn through doing, and
* love is a better master than duty

We can proudly point to visual evidence of this in our [http://www.laptop.org/ OLPC deployments] of Sugar.

The public can learn that it is the Sugar software that powers those computers; and it is people, dedicated to the Sugar principles, that drive the communities to collaborate for such joyful learning.

===A learning laboratory===

The public can learn that Sugar Labs is a learning laboratory, where the most important life skill is practiced and espoused. They can learn how we are a laboratory developing catalysts to revolutionize the field of education. We don't work exclusively in such a broad field, but we hope that we can spark others to recognize and advance some of our developments and to help in finding the most successful ways to stimulate others to join in the mission of advancing learning to the highest possible level.

Sugar Labs' role is to be a focus and lens for Learners to learn learning—as we are, and as we begin with the tools and communities we can assemble. We are not a global university, but the public should be able to recognize that we have some powerful ideas and tools, which are uniquely free, and which have great potential to advance learning and education.

===Learning software===

All the inspiring views of education provided by OLPC, XO, and Sugar images prompt all good-hearted souls to imagine wonderful possibilities for a better world. Technologists see similar possibilities in the Sugar software platform in the broad sense, including the style of development and the fundamentally free expression of human intentions to a world of machines.

Our technologists want to learn how to teach machines to learn to collaborate with humans, and our educators want to learn how to teach humans to learn to learn with machines that can let humans collaborate in their learning. Wow! that's a lot of learning. But the freedom to learn that comes from having such free and powerful ideas and the companion of tools is unlimited.

We need your help in unleashing that potential! If you love children and collaboration and learning, and if you can help us with learning technology and software or any of the important bits needed to enliven and liberate our human potential in a project like this, then please join with us and contribute some of those billions of ways that '''''you''''' might help to propel Sugar learning into the future.

===[[Sugar_Labs#Sugar_Labs:_a_community|Sugar Labs: a community]]===
[[Sugar_Labs#Sugar_Labs:_a_community|Sugar Labs®]] is a non-profit association, consisting entirely of the free contributions of volunteers. Please see our [[Sugar_Labs/Getting_Involved|Getting Involved]] page for how you might contribute. Financial [[Sugar_Labs/Donate|donations]] are used to support grassroots learning innovations and face-to-face meetings between developers and educators.

[[Category:Proposal]]

Marketing Team

2011-03-29T20:51:15Z

SeanDaly: /* Sugar Labs website */

<noinclude>{{ GoogleTrans-en}}{{TeamHeader|Marketing Team}}</noinclude>

<div style="font-size: 1.0em; background: #daffd5; padding: 10px; border: 1px solid #cde7a8" align=left>'''The Sugar Labs Marketing Team exists to spread the good word about Sugar.''' Sugar provides a simple yet powerful means of engaging young children in the world of learning that is opened up by computing and the Internet. It is the job of the Sugar Labs Marketing Team to promote the benefits of Sugar as widely as possible, and to recruit volunteers to help improve the Sugar experience.</div>

{{TOCright}}

== Mission ==
{{:Marketing Team/Mission}}
== Team Coordinator ==

{{:Marketing Team/Coordinator}} (sdaly at sugarlabs.org) is Marketing Coordinator and welcomes ideas and comments but most of all communicators interested in helping out!

== Mailing list ==

Please see our [http://lists.sugarlabs.org/listinfo/marketing Marketing Team mailing list] and its [http://lists.sugarlabs.org/archive/marketing/ archive].

== Projects ==

Deliverables and/or initiatives actively being worked on (with goals and deadlines).

=== MIT Sloan MarketLab Study ===
In late 2010, four students from the MIT Sloan MarketLab worked on a study of the Sugar Labs website. Their conclusions indicate the importance not only of revamping our website (launched two years ago when fewer visuals were available), but of addressing other aspects, in particular installation and support issues, as well as the technical orientation of our web presence.

The study wiki, with raw data, is here: https://sites.google.com/site/marketlabsugar

Of particular interest: the survey results from 85 respondents, here: [[Media:MarketLab_survey_results.pdf]]

A sample fundraising document by the MarketLab team is here: [[Media:Sugar_Fundraising_Text_Proposal.odt]]

The annotated final presentation is here: [[Media:MIT_MarketLab_Annotated_Presentation.odp]]

===[[Marketing_Team/Events|Events]]===
See [[Marketing Team/Events]] for a table of events we are targeting.

=== Press page ===

Our Press page is here: http://www.sugarlabs.org/index.php?template=press

Translator assistance welcomed!

=== Sugar stories ===

How Sugar motivates us: a series of profiles on contributors. [[Marketing Team/Sugar stories]]

=== Press contacts list ===

We're working on a [[Marketing Team/Press contacts]] list with education-oriented publications. This list is maintained by the Marketing Coordinator.

=== PR phone line ===

+1.857.265.1100

[[Marketing Team/Phone]] is a number that journalists can call for quotes, interviews, clarifications, etc. about Sugar. This is a VoIP number which at this time forwards either to the Marketing Coordinator, an Oversight Board member, or voicemail which is forwarded as a timestamped soundfile to pr AT sugarlabs DOT org, an account monitored through forwarding by the Marketing Coordinator and two others.

=== Sugar Labs website ===

Our polished static website as a landing page for Sugar Labs is in the process of being redone (March-May 2011). [[Marketing Team/Website]]

=== [[Marketing Team/Swag|Swag]] ===

To view, download, and contribute to swag designs (stickers, t-shirts, business cards, USB sticks, etc.) and coordinate purchasing swag from suppliers, see [[Marketing Team/Swag]].

== Discussions ==

Conversations that may one day turn into projects, or may have in the past been projects.

=== "Audited" Circulation ===

- [[User:Docdtv|Docdtv]]

While a small user community might discourage adoption of a tool,
a large user community can help encourage adoption. And of course,
small communities need always precede large ones! You know the old
expression: "Eat Sugar! 10**9 flies can't be wrong!" <G>

How do you measure the size of a community? A great way to do that
with automata connected to a global communication network is to
have them "phone home" now and then. Now, I hope what I am suggesting
does not break with any covenent, (implicit or explicit, moral or legal).
But would it be so harmful if, say once a day, a Sugar installation
would briefly tell Sugar Labs "Hey, I'm alive on a machine today!"

Some might agree to do this, but worry about a slippery slope.
Would the future of this humble audit parallel the course of the
United States decennial census, growing from a simple enumeration
into a ruthless and arrogant demographic strip-search?

Of course, audits could be of great benefit to end-users, especially
if they included Activity installation audits. For example, they could
evolve into a mechanism for warning the user about a terrible bug
that needs patching, or advertising a follow-on tool almost all users
adopt upon learning about the new existence of same. (I just now learn
that [http://wiki.laptop.org/go/Automatic_software_updates automatic software updates]
are a new feature of the latest ([http://wiki.laptop.org/go/Release_Notes/8.2.0 8.2.0])
OLPC software release.) By "factoring" the audit mechanism into a
system-wide facility, Activity developers would be spared the need
to code such support on their own.

As a courtesy to Sugar users, cooperation in audits should be voluntary.
But every user should be told why such an audit can help him and others.

Naturally, all this is limited by the fact that not every last machine
on which Sugar will be run will be attached to the Internet.

=== Video channels ===

- [[User:Docdtv|Docdtv]]

1. Does a YouTube channel exist? If not, why not?
There already is a channel at Dailymotion with 19 videos as we write:
http://www.dailymotion.com/sugarlabs/1
YouTube may not use an open source codec, but it is an
incredibly popular search engine and affiliate-propagation tool, see:

http://graphics8.nytimes.com/images/2009/12/31/technology/internet/31tubeGrfx/articleInline.jpg

2. First video would be a 60-second TV-style ad explaining

... what Sugar is (leverage OLPC brand-awareness!)

... that it is free

... what you need to run it

... how you get a copy to install

3. Every time a pitch (q.v. below) is created, a YouTube video record of same is made.
The YouTube version can add stills or short video clips to a talking head.

=== Pitches ===

Short, 1-page elevator pitches to sell Sugar to various audiences. Not formalized, but the homepage (www.sugarlabs.org) is the best starting point. [[Marketing Team/Pitches]]

=== Logo ===

See [[Marketing Team/Logo]].

=== Name ===

Ongoing discussion. See [[Marketing Team/Name]]

=== Slogans ===

Several slogan options are available at [[Marketing Team/Slogan]].

== Subpages ==

{{Special:PrefixIndex/Marketing_Team/}}

[[Category:Marketing Team]]
[[Category:Team]]

Marketing Team

2011-03-29T20:49:52Z

SeanDaly: /* Sugar Labs website */

<noinclude>{{ GoogleTrans-en}}{{TeamHeader|Marketing Team}}</noinclude>

<div style="font-size: 1.0em; background: #daffd5; padding: 10px; border: 1px solid #cde7a8" align=left>'''The Sugar Labs Marketing Team exists to spread the good word about Sugar.''' Sugar provides a simple yet powerful means of engaging young children in the world of learning that is opened up by computing and the Internet. It is the job of the Sugar Labs Marketing Team to promote the benefits of Sugar as widely as possible, and to recruit volunteers to help improve the Sugar experience.</div>

{{TOCright}}

== Mission ==
{{:Marketing Team/Mission}}
== Team Coordinator ==

{{:Marketing Team/Coordinator}} (sdaly at sugarlabs.org) is Marketing Coordinator and welcomes ideas and comments but most of all communicators interested in helping out!

== Mailing list ==

Please see our [http://lists.sugarlabs.org/listinfo/marketing Marketing Team mailing list] and its [http://lists.sugarlabs.org/archive/marketing/ archive].

== Projects ==

Deliverables and/or initiatives actively being worked on (with goals and deadlines).

=== MIT Sloan MarketLab Study ===
In late 2010, four students from the MIT Sloan MarketLab worked on a study of the Sugar Labs website. Their conclusions indicate the importance not only of revamping our website (launched two years ago when fewer visuals were available), but of addressing other aspects, in particular installation and support issues, as well as the technical orientation of our web presence.

The study wiki, with raw data, is here: https://sites.google.com/site/marketlabsugar

Of particular interest: the survey results from 85 respondents, here: [[Media:MarketLab_survey_results.pdf]]

A sample fundraising document by the MarketLab team is here: [[Media:Sugar_Fundraising_Text_Proposal.odt]]

The annotated final presentation is here: [[Media:MIT_MarketLab_Annotated_Presentation.odp]]

===[[Marketing_Team/Events|Events]]===
See [[Marketing Team/Events]] for a table of events we are targeting.

=== Press page ===

Our Press page is here: http://www.sugarlabs.org/index.php?template=press

Translator assistance welcomed!

=== Sugar stories ===

How Sugar motivates us: a series of profiles on contributors. [[Marketing Team/Sugar stories]]

=== Press contacts list ===

We're working on a [[Marketing Team/Press contacts]] list with education-oriented publications. This list is maintained by the Marketing Coordinator.

=== PR phone line ===

+1.857.265.1100

[[Marketing Team/Phone]] is a number that journalists can call for quotes, interviews, clarifications, etc. about Sugar. This is a VoIP number which at this time forwards either to the Marketing Coordinator, an Oversight Board member, or voicemail which is forwarded as a timestamped soundfile to pr AT sugarlabs DOT org, an account monitored through forwarding by the Marketing Coordinator and two others.

=== Sugar Labs website ===

Our polished static website as a landing page for Sugar Labs is in the process of being redone. [[Marketing Team/Website]]

=== [[Marketing Team/Swag|Swag]] ===

To view, download, and contribute to swag designs (stickers, t-shirts, business cards, USB sticks, etc.) and coordinate purchasing swag from suppliers, see [[Marketing Team/Swag]].

== Discussions ==

Conversations that may one day turn into projects, or may have in the past been projects.

=== "Audited" Circulation ===

- [[User:Docdtv|Docdtv]]

While a small user community might discourage adoption of a tool,
a large user community can help encourage adoption. And of course,
small communities need always precede large ones! You know the old
expression: "Eat Sugar! 10**9 flies can't be wrong!" <G>

How do you measure the size of a community? A great way to do that
with automata connected to a global communication network is to
have them "phone home" now and then. Now, I hope what I am suggesting
does not break with any covenent, (implicit or explicit, moral or legal).
But would it be so harmful if, say once a day, a Sugar installation
would briefly tell Sugar Labs "Hey, I'm alive on a machine today!"

Some might agree to do this, but worry about a slippery slope.
Would the future of this humble audit parallel the course of the
United States decennial census, growing from a simple enumeration
into a ruthless and arrogant demographic strip-search?

Of course, audits could be of great benefit to end-users, especially
if they included Activity installation audits. For example, they could
evolve into a mechanism for warning the user about a terrible bug
that needs patching, or advertising a follow-on tool almost all users
adopt upon learning about the new existence of same. (I just now learn
that [http://wiki.laptop.org/go/Automatic_software_updates automatic software updates]
are a new feature of the latest ([http://wiki.laptop.org/go/Release_Notes/8.2.0 8.2.0])
OLPC software release.) By "factoring" the audit mechanism into a
system-wide facility, Activity developers would be spared the need
to code such support on their own.

As a courtesy to Sugar users, cooperation in audits should be voluntary.
But every user should be told why such an audit can help him and others.

Naturally, all this is limited by the fact that not every last machine
on which Sugar will be run will be attached to the Internet.

=== Video channels ===

- [[User:Docdtv|Docdtv]]

1. Does a YouTube channel exist? If not, why not?
There already is a channel at Dailymotion with 19 videos as we write:
http://www.dailymotion.com/sugarlabs/1
YouTube may not use an open source codec, but it is an
incredibly popular search engine and affiliate-propagation tool, see:

http://graphics8.nytimes.com/images/2009/12/31/technology/internet/31tubeGrfx/articleInline.jpg

2. First video would be a 60-second TV-style ad explaining

... what Sugar is (leverage OLPC brand-awareness!)

... that it is free

... what you need to run it

... how you get a copy to install

3. Every time a pitch (q.v. below) is created, a YouTube video record of same is made.
The YouTube version can add stills or short video clips to a talking head.

=== Pitches ===

Short, 1-page elevator pitches to sell Sugar to various audiences. Not formalized, but the homepage (www.sugarlabs.org) is the best starting point. [[Marketing Team/Pitches]]

=== Logo ===

See [[Marketing Team/Logo]].

=== Name ===

Ongoing discussion. See [[Marketing Team/Name]]

=== Slogans ===

Several slogan options are available at [[Marketing Team/Slogan]].

== Subpages ==

{{Special:PrefixIndex/Marketing_Team/}}

[[Category:Marketing Team]]
[[Category:Team]]

Marketing Team

2011-03-29T20:48:34Z

SeanDaly: /* MIT Sloan MarketLab Study */

<noinclude>{{ GoogleTrans-en}}{{TeamHeader|Marketing Team}}</noinclude>

<div style="font-size: 1.0em; background: #daffd5; padding: 10px; border: 1px solid #cde7a8" align=left>'''The Sugar Labs Marketing Team exists to spread the good word about Sugar.''' Sugar provides a simple yet powerful means of engaging young children in the world of learning that is opened up by computing and the Internet. It is the job of the Sugar Labs Marketing Team to promote the benefits of Sugar as widely as possible, and to recruit volunteers to help improve the Sugar experience.</div>

{{TOCright}}

== Mission ==
{{:Marketing Team/Mission}}
== Team Coordinator ==

{{:Marketing Team/Coordinator}} (sdaly at sugarlabs.org) is Marketing Coordinator and welcomes ideas and comments but most of all communicators interested in helping out!

== Mailing list ==

Please see our [http://lists.sugarlabs.org/listinfo/marketing Marketing Team mailing list] and its [http://lists.sugarlabs.org/archive/marketing/ archive].

== Projects ==

Deliverables and/or initiatives actively being worked on (with goals and deadlines).

=== MIT Sloan MarketLab Study ===
In late 2010, four students from the MIT Sloan MarketLab worked on a study of the Sugar Labs website. Their conclusions indicate the importance not only of revamping our website (launched two years ago when fewer visuals were available), but of addressing other aspects, in particular installation and support issues, as well as the technical orientation of our web presence.

The study wiki, with raw data, is here: https://sites.google.com/site/marketlabsugar

Of particular interest: the survey results from 85 respondents, here: [[Media:MarketLab_survey_results.pdf]]

A sample fundraising document by the MarketLab team is here: [[Media:Sugar_Fundraising_Text_Proposal.odt]]

The annotated final presentation is here: [[Media:MIT_MarketLab_Annotated_Presentation.odp]]

===[[Marketing_Team/Events|Events]]===
See [[Marketing Team/Events]] for a table of events we are targeting.

=== Press page ===

Our Press page is here: http://www.sugarlabs.org/index.php?template=press

Translator assistance welcomed!

=== Sugar stories ===

How Sugar motivates us: a series of profiles on contributors. [[Marketing Team/Sugar stories]]

=== Press contacts list ===

We're working on a [[Marketing Team/Press contacts]] list with education-oriented publications. This list is maintained by the Marketing Coordinator.

=== PR phone line ===

+1.857.265.1100

[[Marketing Team/Phone]] is a number that journalists can call for quotes, interviews, clarifications, etc. about Sugar. This is a VoIP number which at this time forwards either to the Marketing Coordinator, an Oversight Board member, or voicemail which is forwarded as a timestamped soundfile to pr AT sugarlabs DOT org, an account monitored through forwarding by the Marketing Coordinator and two others.

=== Sugar Labs website ===

Our polished static website as a landing page for Sugar Labs is live and the new Activities section too. We are currently working on a common navigation bar for all the site sections to simplify navigation for first-time visitors. [[Marketing Team/Website]]

=== [[Marketing Team/Swag|Swag]] ===

To view, download, and contribute to swag designs (stickers, t-shirts, business cards, USB sticks, etc.) and coordinate purchasing swag from suppliers, see [[Marketing Team/Swag]].

== Discussions ==

Conversations that may one day turn into projects, or may have in the past been projects.

=== "Audited" Circulation ===

- [[User:Docdtv|Docdtv]]

While a small user community might discourage adoption of a tool,
a large user community can help encourage adoption. And of course,
small communities need always precede large ones! You know the old
expression: "Eat Sugar! 10**9 flies can't be wrong!" <G>

How do you measure the size of a community? A great way to do that
with automata connected to a global communication network is to
have them "phone home" now and then. Now, I hope what I am suggesting
does not break with any covenent, (implicit or explicit, moral or legal).
But would it be so harmful if, say once a day, a Sugar installation
would briefly tell Sugar Labs "Hey, I'm alive on a machine today!"

Some might agree to do this, but worry about a slippery slope.
Would the future of this humble audit parallel the course of the
United States decennial census, growing from a simple enumeration
into a ruthless and arrogant demographic strip-search?

Of course, audits could be of great benefit to end-users, especially
if they included Activity installation audits. For example, they could
evolve into a mechanism for warning the user about a terrible bug
that needs patching, or advertising a follow-on tool almost all users
adopt upon learning about the new existence of same. (I just now learn
that [http://wiki.laptop.org/go/Automatic_software_updates automatic software updates]
are a new feature of the latest ([http://wiki.laptop.org/go/Release_Notes/8.2.0 8.2.0])
OLPC software release.) By "factoring" the audit mechanism into a
system-wide facility, Activity developers would be spared the need
to code such support on their own.

As a courtesy to Sugar users, cooperation in audits should be voluntary.
But every user should be told why such an audit can help him and others.

Naturally, all this is limited by the fact that not every last machine
on which Sugar will be run will be attached to the Internet.

=== Video channels ===

- [[User:Docdtv|Docdtv]]

1. Does a YouTube channel exist? If not, why not?
There already is a channel at Dailymotion with 19 videos as we write:
http://www.dailymotion.com/sugarlabs/1
YouTube may not use an open source codec, but it is an
incredibly popular search engine and affiliate-propagation tool, see:

http://graphics8.nytimes.com/images/2009/12/31/technology/internet/31tubeGrfx/articleInline.jpg

2. First video would be a 60-second TV-style ad explaining

... what Sugar is (leverage OLPC brand-awareness!)

... that it is free

... what you need to run it

... how you get a copy to install

3. Every time a pitch (q.v. below) is created, a YouTube video record of same is made.
The YouTube version can add stills or short video clips to a talking head.

=== Pitches ===

Short, 1-page elevator pitches to sell Sugar to various audiences. Not formalized, but the homepage (www.sugarlabs.org) is the best starting point. [[Marketing Team/Pitches]]

=== Logo ===

See [[Marketing Team/Logo]].

=== Name ===

Ongoing discussion. See [[Marketing Team/Name]]

=== Slogans ===

Several slogan options are available at [[Marketing Team/Slogan]].

== Subpages ==

{{Special:PrefixIndex/Marketing_Team/}}

[[Category:Marketing Team]]
[[Category:Team]]

Marketing Team

2011-03-29T20:47:14Z

SeanDaly: /* MIT Sloan MarketLab Study */

<noinclude>{{ GoogleTrans-en}}{{TeamHeader|Marketing Team}}</noinclude>

<div style="font-size: 1.0em; background: #daffd5; padding: 10px; border: 1px solid #cde7a8" align=left>'''The Sugar Labs Marketing Team exists to spread the good word about Sugar.''' Sugar provides a simple yet powerful means of engaging young children in the world of learning that is opened up by computing and the Internet. It is the job of the Sugar Labs Marketing Team to promote the benefits of Sugar as widely as possible, and to recruit volunteers to help improve the Sugar experience.</div>

{{TOCright}}

== Mission ==
{{:Marketing Team/Mission}}
== Team Coordinator ==

{{:Marketing Team/Coordinator}} (sdaly at sugarlabs.org) is Marketing Coordinator and welcomes ideas and comments but most of all communicators interested in helping out!

== Mailing list ==

Please see our [http://lists.sugarlabs.org/listinfo/marketing Marketing Team mailing list] and its [http://lists.sugarlabs.org/archive/marketing/ archive].

== Projects ==

Deliverables and/or initiatives actively being worked on (with goals and deadlines).

=== MIT Sloan MarketLab Study ===
Four students from the MIT Sloan MarketLab have prepared a study of the Sugar Labs website. The conclusions indicate the importance not only of revamping our website (launched two years ago when fewer visuals were available), but of addressing other aspects, in particular installation and support issues.

The study wiki, with raw data, is here: https://sites.google.com/site/marketlabsugar

Of particular interest: the survey results from 85 respondents, here: [[Media:MarketLab_survey_results.pdf]]

A sample fundraising document by the MarketLab team is here: [[Media:Sugar_Fundraising_Text_Proposal.odt]]

The annotated final presentation is here: [[Media:MIT_MarketLab_Annotated_Presentation.odp]]

===[[Marketing_Team/Events|Events]]===
See [[Marketing Team/Events]] for a table of events we are targeting.

=== Press page ===

Our Press page is here: http://www.sugarlabs.org/index.php?template=press

Translator assistance welcomed!

=== Sugar stories ===

How Sugar motivates us: a series of profiles on contributors. [[Marketing Team/Sugar stories]]

=== Press contacts list ===

We're working on a [[Marketing Team/Press contacts]] list with education-oriented publications. This list is maintained by the Marketing Coordinator.

=== PR phone line ===

+1.857.265.1100

[[Marketing Team/Phone]] is a number that journalists can call for quotes, interviews, clarifications, etc. about Sugar. This is a VoIP number which at this time forwards either to the Marketing Coordinator, an Oversight Board member, or voicemail which is forwarded as a timestamped soundfile to pr AT sugarlabs DOT org, an account monitored through forwarding by the Marketing Coordinator and two others.

=== Sugar Labs website ===

Our polished static website as a landing page for Sugar Labs is live and the new Activities section too. We are currently working on a common navigation bar for all the site sections to simplify navigation for first-time visitors. [[Marketing Team/Website]]

=== [[Marketing Team/Swag|Swag]] ===

To view, download, and contribute to swag designs (stickers, t-shirts, business cards, USB sticks, etc.) and coordinate purchasing swag from suppliers, see [[Marketing Team/Swag]].

== Discussions ==

Conversations that may one day turn into projects, or may have in the past been projects.

=== "Audited" Circulation ===

- [[User:Docdtv|Docdtv]]

While a small user community might discourage adoption of a tool,
a large user community can help encourage adoption. And of course,
small communities need always precede large ones! You know the old
expression: "Eat Sugar! 10**9 flies can't be wrong!" <G>

How do you measure the size of a community? A great way to do that
with automata connected to a global communication network is to
have them "phone home" now and then. Now, I hope what I am suggesting
does not break with any covenent, (implicit or explicit, moral or legal).
But would it be so harmful if, say once a day, a Sugar installation
would briefly tell Sugar Labs "Hey, I'm alive on a machine today!"

Some might agree to do this, but worry about a slippery slope.
Would the future of this humble audit parallel the course of the
United States decennial census, growing from a simple enumeration
into a ruthless and arrogant demographic strip-search?

Of course, audits could be of great benefit to end-users, especially
if they included Activity installation audits. For example, they could
evolve into a mechanism for warning the user about a terrible bug
that needs patching, or advertising a follow-on tool almost all users
adopt upon learning about the new existence of same. (I just now learn
that [http://wiki.laptop.org/go/Automatic_software_updates automatic software updates]
are a new feature of the latest ([http://wiki.laptop.org/go/Release_Notes/8.2.0 8.2.0])
OLPC software release.) By "factoring" the audit mechanism into a
system-wide facility, Activity developers would be spared the need
to code such support on their own.

As a courtesy to Sugar users, cooperation in audits should be voluntary.
But every user should be told why such an audit can help him and others.

Naturally, all this is limited by the fact that not every last machine
on which Sugar will be run will be attached to the Internet.

=== Video channels ===

- [[User:Docdtv|Docdtv]]

1. Does a YouTube channel exist? If not, why not?
There already is a channel at Dailymotion with 19 videos as we write:
http://www.dailymotion.com/sugarlabs/1
YouTube may not use an open source codec, but it is an
incredibly popular search engine and affiliate-propagation tool, see:

http://graphics8.nytimes.com/images/2009/12/31/technology/internet/31tubeGrfx/articleInline.jpg

2. First video would be a 60-second TV-style ad explaining

... what Sugar is (leverage OLPC brand-awareness!)

... that it is free

... what you need to run it

... how you get a copy to install

3. Every time a pitch (q.v. below) is created, a YouTube video record of same is made.
The YouTube version can add stills or short video clips to a talking head.

=== Pitches ===

Short, 1-page elevator pitches to sell Sugar to various audiences. Not formalized, but the homepage (www.sugarlabs.org) is the best starting point. [[Marketing Team/Pitches]]

=== Logo ===

See [[Marketing Team/Logo]].

=== Name ===

Ongoing discussion. See [[Marketing Team/Name]]

=== Slogans ===

Several slogan options are available at [[Marketing Team/Slogan]].

== Subpages ==

{{Special:PrefixIndex/Marketing_Team/}}

[[Category:Marketing Team]]
[[Category:Team]]

Marketing Team

2011-03-29T20:44:55Z

SeanDaly: /* MIT Sloan MarketLab Study */

<noinclude>{{ GoogleTrans-en}}{{TeamHeader|Marketing Team}}</noinclude>

<div style="font-size: 1.0em; background: #daffd5; padding: 10px; border: 1px solid #cde7a8" align=left>'''The Sugar Labs Marketing Team exists to spread the good word about Sugar.''' Sugar provides a simple yet powerful means of engaging young children in the world of learning that is opened up by computing and the Internet. It is the job of the Sugar Labs Marketing Team to promote the benefits of Sugar as widely as possible, and to recruit volunteers to help improve the Sugar experience.</div>

{{TOCright}}

== Mission ==
{{:Marketing Team/Mission}}
== Team Coordinator ==

{{:Marketing Team/Coordinator}} (sdaly at sugarlabs.org) is Marketing Coordinator and welcomes ideas and comments but most of all communicators interested in helping out!

== Mailing list ==

Please see our [http://lists.sugarlabs.org/listinfo/marketing Marketing Team mailing list] and its [http://lists.sugarlabs.org/archive/marketing/ archive].

== Projects ==

Deliverables and/or initiatives actively being worked on (with goals and deadlines).

=== MIT Sloan MarketLab Study ===
Four students from the MIT Sloan MarketLab have prepared a study of the Sugar Labs website. The conclusions indicate the importance not only of revamping our website (launched two years ago when fewer visuals were available), but of addressing other aspects, in particular installation and support issues.

The study wiki, with raw data, is here: https://sites.google.com/site/marketlabsugar. Of particular interest: the survey results from 85 respondents, here: [[Media:MarketLab_survey_results.pdf]]

A sample fundraising document by the MarketLab team is here: [[Media:Sugar_Fundraising_Text_Proposal.odt]]

The annotated final presentation is here: [[Media:MIT_MarketLab_Annotated_Presentation.odp]]

===[[Marketing_Team/Events|Events]]===
See [[Marketing Team/Events]] for a table of events we are targeting.

=== Press page ===

Our Press page is here: http://www.sugarlabs.org/index.php?template=press

Translator assistance welcomed!

=== Sugar stories ===

How Sugar motivates us: a series of profiles on contributors. [[Marketing Team/Sugar stories]]

=== Press contacts list ===

We're working on a [[Marketing Team/Press contacts]] list with education-oriented publications. This list is maintained by the Marketing Coordinator.

=== PR phone line ===

+1.857.265.1100

[[Marketing Team/Phone]] is a number that journalists can call for quotes, interviews, clarifications, etc. about Sugar. This is a VoIP number which at this time forwards either to the Marketing Coordinator, an Oversight Board member, or voicemail which is forwarded as a timestamped soundfile to pr AT sugarlabs DOT org, an account monitored through forwarding by the Marketing Coordinator and two others.

=== Sugar Labs website ===

Our polished static website as a landing page for Sugar Labs is live and the new Activities section too. We are currently working on a common navigation bar for all the site sections to simplify navigation for first-time visitors. [[Marketing Team/Website]]

=== [[Marketing Team/Swag|Swag]] ===

To view, download, and contribute to swag designs (stickers, t-shirts, business cards, USB sticks, etc.) and coordinate purchasing swag from suppliers, see [[Marketing Team/Swag]].

== Discussions ==

Conversations that may one day turn into projects, or may have in the past been projects.

=== "Audited" Circulation ===

- [[User:Docdtv|Docdtv]]

While a small user community might discourage adoption of a tool,
a large user community can help encourage adoption. And of course,
small communities need always precede large ones! You know the old
expression: "Eat Sugar! 10**9 flies can't be wrong!" <G>

How do you measure the size of a community? A great way to do that
with automata connected to a global communication network is to
have them "phone home" now and then. Now, I hope what I am suggesting
does not break with any covenent, (implicit or explicit, moral or legal).
But would it be so harmful if, say once a day, a Sugar installation
would briefly tell Sugar Labs "Hey, I'm alive on a machine today!"

Some might agree to do this, but worry about a slippery slope.
Would the future of this humble audit parallel the course of the
United States decennial census, growing from a simple enumeration
into a ruthless and arrogant demographic strip-search?

Of course, audits could be of great benefit to end-users, especially
if they included Activity installation audits. For example, they could
evolve into a mechanism for warning the user about a terrible bug
that needs patching, or advertising a follow-on tool almost all users
adopt upon learning about the new existence of same. (I just now learn
that [http://wiki.laptop.org/go/Automatic_software_updates automatic software updates]
are a new feature of the latest ([http://wiki.laptop.org/go/Release_Notes/8.2.0 8.2.0])
OLPC software release.) By "factoring" the audit mechanism into a
system-wide facility, Activity developers would be spared the need
to code such support on their own.

As a courtesy to Sugar users, cooperation in audits should be voluntary.
But every user should be told why such an audit can help him and others.

Naturally, all this is limited by the fact that not every last machine
on which Sugar will be run will be attached to the Internet.

=== Video channels ===

- [[User:Docdtv|Docdtv]]

1. Does a YouTube channel exist? If not, why not?
There already is a channel at Dailymotion with 19 videos as we write:
http://www.dailymotion.com/sugarlabs/1
YouTube may not use an open source codec, but it is an
incredibly popular search engine and affiliate-propagation tool, see:

http://graphics8.nytimes.com/images/2009/12/31/technology/internet/31tubeGrfx/articleInline.jpg

2. First video would be a 60-second TV-style ad explaining

... what Sugar is (leverage OLPC brand-awareness!)

... that it is free

... what you need to run it

... how you get a copy to install

3. Every time a pitch (q.v. below) is created, a YouTube video record of same is made.
The YouTube version can add stills or short video clips to a talking head.

=== Pitches ===

Short, 1-page elevator pitches to sell Sugar to various audiences. Not formalized, but the homepage (www.sugarlabs.org) is the best starting point. [[Marketing Team/Pitches]]

=== Logo ===

See [[Marketing Team/Logo]].

=== Name ===

Ongoing discussion. See [[Marketing Team/Name]]

=== Slogans ===

Several slogan options are available at [[Marketing Team/Slogan]].

== Subpages ==

{{Special:PrefixIndex/Marketing_Team/}}

[[Category:Marketing Team]]
[[Category:Team]]

Marketing Team

2011-03-29T20:44:07Z

SeanDaly: /* MIT Sloan MarketLab Study */

<noinclude>{{ GoogleTrans-en}}{{TeamHeader|Marketing Team}}</noinclude>

<div style="font-size: 1.0em; background: #daffd5; padding: 10px; border: 1px solid #cde7a8" align=left>'''The Sugar Labs Marketing Team exists to spread the good word about Sugar.''' Sugar provides a simple yet powerful means of engaging young children in the world of learning that is opened up by computing and the Internet. It is the job of the Sugar Labs Marketing Team to promote the benefits of Sugar as widely as possible, and to recruit volunteers to help improve the Sugar experience.</div>

{{TOCright}}

== Mission ==
{{:Marketing Team/Mission}}
== Team Coordinator ==

{{:Marketing Team/Coordinator}} (sdaly at sugarlabs.org) is Marketing Coordinator and welcomes ideas and comments but most of all communicators interested in helping out!

== Mailing list ==

Please see our [http://lists.sugarlabs.org/listinfo/marketing Marketing Team mailing list] and its [http://lists.sugarlabs.org/archive/marketing/ archive].

== Projects ==

Deliverables and/or initiatives actively being worked on (with goals and deadlines).

=== MIT Sloan MarketLab Study ===
Four students from the MIT Sloan MarketLab have prepared a study of the Sugar Labs website. The conclusions indicate the importance not only of redoing our website (launched two years ago when fewer visuals were available), but of addressing other aspects, in particular installation and support issues.

The study wiki, with raw data, is here: https://sites.google.com/site/marketlabsugar. Of particular interest: the survey results from 85 respondents, here: [[Media:MarketLab_survey_results.pdf]]

A sample fundraising document by the MarketLab team is here: [[Media:Sugar_Fundraising_Text_Proposal.odt]]

The annotated final presentation is here: [[Media:MIT_MarketLab_Annotated_Presentation.odp]]

===[[Marketing_Team/Events|Events]]===
See [[Marketing Team/Events]] for a table of events we are targeting.

=== Press page ===

Our Press page is here: http://www.sugarlabs.org/index.php?template=press

Translator assistance welcomed!

=== Sugar stories ===

How Sugar motivates us: a series of profiles on contributors. [[Marketing Team/Sugar stories]]

=== Press contacts list ===

We're working on a [[Marketing Team/Press contacts]] list with education-oriented publications. This list is maintained by the Marketing Coordinator.

=== PR phone line ===

+1.857.265.1100

[[Marketing Team/Phone]] is a number that journalists can call for quotes, interviews, clarifications, etc. about Sugar. This is a VoIP number which at this time forwards either to the Marketing Coordinator, an Oversight Board member, or voicemail which is forwarded as a timestamped soundfile to pr AT sugarlabs DOT org, an account monitored through forwarding by the Marketing Coordinator and two others.

=== Sugar Labs website ===

Our polished static website as a landing page for Sugar Labs is live and the new Activities section too. We are currently working on a common navigation bar for all the site sections to simplify navigation for first-time visitors. [[Marketing Team/Website]]

=== [[Marketing Team/Swag|Swag]] ===

To view, download, and contribute to swag designs (stickers, t-shirts, business cards, USB sticks, etc.) and coordinate purchasing swag from suppliers, see [[Marketing Team/Swag]].

== Discussions ==

Conversations that may one day turn into projects, or may have in the past been projects.

=== "Audited" Circulation ===

- [[User:Docdtv|Docdtv]]

While a small user community might discourage adoption of a tool,
a large user community can help encourage adoption. And of course,
small communities need always precede large ones! You know the old
expression: "Eat Sugar! 10**9 flies can't be wrong!" <G>

How do you measure the size of a community? A great way to do that
with automata connected to a global communication network is to
have them "phone home" now and then. Now, I hope what I am suggesting
does not break with any covenent, (implicit or explicit, moral or legal).
But would it be so harmful if, say once a day, a Sugar installation
would briefly tell Sugar Labs "Hey, I'm alive on a machine today!"

Some might agree to do this, but worry about a slippery slope.
Would the future of this humble audit parallel the course of the
United States decennial census, growing from a simple enumeration
into a ruthless and arrogant demographic strip-search?

Of course, audits could be of great benefit to end-users, especially
if they included Activity installation audits. For example, they could
evolve into a mechanism for warning the user about a terrible bug
that needs patching, or advertising a follow-on tool almost all users
adopt upon learning about the new existence of same. (I just now learn
that [http://wiki.laptop.org/go/Automatic_software_updates automatic software updates]
are a new feature of the latest ([http://wiki.laptop.org/go/Release_Notes/8.2.0 8.2.0])
OLPC software release.) By "factoring" the audit mechanism into a
system-wide facility, Activity developers would be spared the need
to code such support on their own.

As a courtesy to Sugar users, cooperation in audits should be voluntary.
But every user should be told why such an audit can help him and others.

Naturally, all this is limited by the fact that not every last machine
on which Sugar will be run will be attached to the Internet.

=== Video channels ===

- [[User:Docdtv|Docdtv]]

1. Does a YouTube channel exist? If not, why not?
There already is a channel at Dailymotion with 19 videos as we write:
http://www.dailymotion.com/sugarlabs/1
YouTube may not use an open source codec, but it is an
incredibly popular search engine and affiliate-propagation tool, see:

http://graphics8.nytimes.com/images/2009/12/31/technology/internet/31tubeGrfx/articleInline.jpg

2. First video would be a 60-second TV-style ad explaining

... what Sugar is (leverage OLPC brand-awareness!)

... that it is free

... what you need to run it

... how you get a copy to install

3. Every time a pitch (q.v. below) is created, a YouTube video record of same is made.
The YouTube version can add stills or short video clips to a talking head.

=== Pitches ===

Short, 1-page elevator pitches to sell Sugar to various audiences. Not formalized, but the homepage (www.sugarlabs.org) is the best starting point. [[Marketing Team/Pitches]]

=== Logo ===

See [[Marketing Team/Logo]].

=== Name ===

Ongoing discussion. See [[Marketing Team/Name]]

=== Slogans ===

Several slogan options are available at [[Marketing Team/Slogan]].

== Subpages ==

{{Special:PrefixIndex/Marketing_Team/}}

[[Category:Marketing Team]]
[[Category:Team]]

File:MarketLab survey results.pdf

2011-03-29T20:42:55Z

SeanDaly: MIT Sloan MarketLab survey results from 85 respondents in the community.

MIT Sloan MarketLab survey results from 85 respondents in the community.

Marketing Team

2011-03-29T20:38:09Z

SeanDaly: /* MIT Sloan MarketLab Study */

<noinclude>{{ GoogleTrans-en}}{{TeamHeader|Marketing Team}}</noinclude>

<div style="font-size: 1.0em; background: #daffd5; padding: 10px; border: 1px solid #cde7a8" align=left>'''The Sugar Labs Marketing Team exists to spread the good word about Sugar.''' Sugar provides a simple yet powerful means of engaging young children in the world of learning that is opened up by computing and the Internet. It is the job of the Sugar Labs Marketing Team to promote the benefits of Sugar as widely as possible, and to recruit volunteers to help improve the Sugar experience.</div>

{{TOCright}}

== Mission ==
{{:Marketing Team/Mission}}
== Team Coordinator ==

{{:Marketing Team/Coordinator}} (sdaly at sugarlabs.org) is Marketing Coordinator and welcomes ideas and comments but most of all communicators interested in helping out!

== Mailing list ==

Please see our [http://lists.sugarlabs.org/listinfo/marketing Marketing Team mailing list] and its [http://lists.sugarlabs.org/archive/marketing/ archive].

== Projects ==

Deliverables and/or initiatives actively being worked on (with goals and deadlines).

=== MIT Sloan MarketLab Study ===
Four students from the MIT Sloan MarketLab have prepared a study of the Sugar Labs website. The conclusions indicate the importance not only of redoing our website (launched two years ago when fewer visuals were available), but of addressing other aspects, in particular installation and support issues.

The study wiki, with raw data, is here: https://sites.google.com/site/marketlabsugar

A sample fundraising document by the MarketLab team is here: [[Media:Sugar_Fundraising_Text_Proposal.odt]]

The annotated final presentation is here: [[Media:MIT_MarketLab_Annotated_Presentation.odp]]

===[[Marketing_Team/Events|Events]]===
See [[Marketing Team/Events]] for a table of events we are targeting.

=== Press page ===

Our Press page is here: http://www.sugarlabs.org/index.php?template=press

Translator assistance welcomed!

=== Sugar stories ===

How Sugar motivates us: a series of profiles on contributors. [[Marketing Team/Sugar stories]]

=== Press contacts list ===

We're working on a [[Marketing Team/Press contacts]] list with education-oriented publications. This list is maintained by the Marketing Coordinator.

=== PR phone line ===

+1.857.265.1100

[[Marketing Team/Phone]] is a number that journalists can call for quotes, interviews, clarifications, etc. about Sugar. This is a VoIP number which at this time forwards either to the Marketing Coordinator, an Oversight Board member, or voicemail which is forwarded as a timestamped soundfile to pr AT sugarlabs DOT org, an account monitored through forwarding by the Marketing Coordinator and two others.

=== Sugar Labs website ===

Our polished static website as a landing page for Sugar Labs is live and the new Activities section too. We are currently working on a common navigation bar for all the site sections to simplify navigation for first-time visitors. [[Marketing Team/Website]]

=== [[Marketing Team/Swag|Swag]] ===

To view, download, and contribute to swag designs (stickers, t-shirts, business cards, USB sticks, etc.) and coordinate purchasing swag from suppliers, see [[Marketing Team/Swag]].

== Discussions ==

Conversations that may one day turn into projects, or may have in the past been projects.

=== "Audited" Circulation ===

- [[User:Docdtv|Docdtv]]

While a small user community might discourage adoption of a tool,
a large user community can help encourage adoption. And of course,
small communities need always precede large ones! You know the old
expression: "Eat Sugar! 10**9 flies can't be wrong!" <G>

How do you measure the size of a community? A great way to do that
with automata connected to a global communication network is to
have them "phone home" now and then. Now, I hope what I am suggesting
does not break with any covenent, (implicit or explicit, moral or legal).
But would it be so harmful if, say once a day, a Sugar installation
would briefly tell Sugar Labs "Hey, I'm alive on a machine today!"

Some might agree to do this, but worry about a slippery slope.
Would the future of this humble audit parallel the course of the
United States decennial census, growing from a simple enumeration
into a ruthless and arrogant demographic strip-search?

Of course, audits could be of great benefit to end-users, especially
if they included Activity installation audits. For example, they could
evolve into a mechanism for warning the user about a terrible bug
that needs patching, or advertising a follow-on tool almost all users
adopt upon learning about the new existence of same. (I just now learn
that [http://wiki.laptop.org/go/Automatic_software_updates automatic software updates]
are a new feature of the latest ([http://wiki.laptop.org/go/Release_Notes/8.2.0 8.2.0])
OLPC software release.) By "factoring" the audit mechanism into a
system-wide facility, Activity developers would be spared the need
to code such support on their own.

As a courtesy to Sugar users, cooperation in audits should be voluntary.
But every user should be told why such an audit can help him and others.

Naturally, all this is limited by the fact that not every last machine
on which Sugar will be run will be attached to the Internet.

=== Video channels ===

- [[User:Docdtv|Docdtv]]

1. Does a YouTube channel exist? If not, why not?
There already is a channel at Dailymotion with 19 videos as we write:
http://www.dailymotion.com/sugarlabs/1
YouTube may not use an open source codec, but it is an
incredibly popular search engine and affiliate-propagation tool, see:

http://graphics8.nytimes.com/images/2009/12/31/technology/internet/31tubeGrfx/articleInline.jpg

2. First video would be a 60-second TV-style ad explaining

... what Sugar is (leverage OLPC brand-awareness!)

... that it is free

... what you need to run it

... how you get a copy to install

3. Every time a pitch (q.v. below) is created, a YouTube video record of same is made.
The YouTube version can add stills or short video clips to a talking head.

=== Pitches ===

Short, 1-page elevator pitches to sell Sugar to various audiences. Not formalized, but the homepage (www.sugarlabs.org) is the best starting point. [[Marketing Team/Pitches]]

=== Logo ===

See [[Marketing Team/Logo]].

=== Name ===

Ongoing discussion. See [[Marketing Team/Name]]

=== Slogans ===

Several slogan options are available at [[Marketing Team/Slogan]].

== Subpages ==

{{Special:PrefixIndex/Marketing_Team/}}

[[Category:Marketing Team]]
[[Category:Team]]

Marketing Team

2011-03-29T20:36:42Z

SeanDaly: /* MIT Sloan MarketLab Study */

<noinclude>{{ GoogleTrans-en}}{{TeamHeader|Marketing Team}}</noinclude>

<div style="font-size: 1.0em; background: #daffd5; padding: 10px; border: 1px solid #cde7a8" align=left>'''The Sugar Labs Marketing Team exists to spread the good word about Sugar.''' Sugar provides a simple yet powerful means of engaging young children in the world of learning that is opened up by computing and the Internet. It is the job of the Sugar Labs Marketing Team to promote the benefits of Sugar as widely as possible, and to recruit volunteers to help improve the Sugar experience.</div>

{{TOCright}}

== Mission ==
{{:Marketing Team/Mission}}
== Team Coordinator ==

{{:Marketing Team/Coordinator}} (sdaly at sugarlabs.org) is Marketing Coordinator and welcomes ideas and comments but most of all communicators interested in helping out!

== Mailing list ==

Please see our [http://lists.sugarlabs.org/listinfo/marketing Marketing Team mailing list] and its [http://lists.sugarlabs.org/archive/marketing/ archive].

== Projects ==

Deliverables and/or initiatives actively being worked on (with goals and deadlines).

=== MIT Sloan MarketLab Study ===
Four students from the MIT Sloan MarketLab have prepared a study of the Sugar Labs website. The conclusions indicate the importance not only of redoing our website (launched two years ago when fewer visuals were available), but of addressing other aspects, in particular installation and support issues.

The study wiki, with raw data, is here: https://sites.google.com/site/marketlabsugar

A sample fundraising document by the MarketLab team is here: [[Media:Sugar_Fundraising_Text_Proposal.odt]]

===[[Marketing_Team/Events|Events]]===
See [[Marketing Team/Events]] for a table of events we are targeting.

=== Press page ===

Our Press page is here: http://www.sugarlabs.org/index.php?template=press

Translator assistance welcomed!

=== Sugar stories ===

How Sugar motivates us: a series of profiles on contributors. [[Marketing Team/Sugar stories]]

=== Press contacts list ===

We're working on a [[Marketing Team/Press contacts]] list with education-oriented publications. This list is maintained by the Marketing Coordinator.

=== PR phone line ===

+1.857.265.1100

[[Marketing Team/Phone]] is a number that journalists can call for quotes, interviews, clarifications, etc. about Sugar. This is a VoIP number which at this time forwards either to the Marketing Coordinator, an Oversight Board member, or voicemail which is forwarded as a timestamped soundfile to pr AT sugarlabs DOT org, an account monitored through forwarding by the Marketing Coordinator and two others.

=== Sugar Labs website ===

Our polished static website as a landing page for Sugar Labs is live and the new Activities section too. We are currently working on a common navigation bar for all the site sections to simplify navigation for first-time visitors. [[Marketing Team/Website]]

=== [[Marketing Team/Swag|Swag]] ===

To view, download, and contribute to swag designs (stickers, t-shirts, business cards, USB sticks, etc.) and coordinate purchasing swag from suppliers, see [[Marketing Team/Swag]].

== Discussions ==

Conversations that may one day turn into projects, or may have in the past been projects.

=== "Audited" Circulation ===

- [[User:Docdtv|Docdtv]]

While a small user community might discourage adoption of a tool,
a large user community can help encourage adoption. And of course,
small communities need always precede large ones! You know the old
expression: "Eat Sugar! 10**9 flies can't be wrong!" <G>

How do you measure the size of a community? A great way to do that
with automata connected to a global communication network is to
have them "phone home" now and then. Now, I hope what I am suggesting
does not break with any covenent, (implicit or explicit, moral or legal).
But would it be so harmful if, say once a day, a Sugar installation
would briefly tell Sugar Labs "Hey, I'm alive on a machine today!"

Some might agree to do this, but worry about a slippery slope.
Would the future of this humble audit parallel the course of the
United States decennial census, growing from a simple enumeration
into a ruthless and arrogant demographic strip-search?

Of course, audits could be of great benefit to end-users, especially
if they included Activity installation audits. For example, they could
evolve into a mechanism for warning the user about a terrible bug
that needs patching, or advertising a follow-on tool almost all users
adopt upon learning about the new existence of same. (I just now learn
that [http://wiki.laptop.org/go/Automatic_software_updates automatic software updates]
are a new feature of the latest ([http://wiki.laptop.org/go/Release_Notes/8.2.0 8.2.0])
OLPC software release.) By "factoring" the audit mechanism into a
system-wide facility, Activity developers would be spared the need
to code such support on their own.

As a courtesy to Sugar users, cooperation in audits should be voluntary.
But every user should be told why such an audit can help him and others.

Naturally, all this is limited by the fact that not every last machine
on which Sugar will be run will be attached to the Internet.

=== Video channels ===

- [[User:Docdtv|Docdtv]]

1. Does a YouTube channel exist? If not, why not?
There already is a channel at Dailymotion with 19 videos as we write:
http://www.dailymotion.com/sugarlabs/1
YouTube may not use an open source codec, but it is an
incredibly popular search engine and affiliate-propagation tool, see:

http://graphics8.nytimes.com/images/2009/12/31/technology/internet/31tubeGrfx/articleInline.jpg

2. First video would be a 60-second TV-style ad explaining

... what Sugar is (leverage OLPC brand-awareness!)

... that it is free

... what you need to run it

... how you get a copy to install

3. Every time a pitch (q.v. below) is created, a YouTube video record of same is made.
The YouTube version can add stills or short video clips to a talking head.

=== Pitches ===

Short, 1-page elevator pitches to sell Sugar to various audiences. Not formalized, but the homepage (www.sugarlabs.org) is the best starting point. [[Marketing Team/Pitches]]

=== Logo ===

See [[Marketing Team/Logo]].

=== Name ===

Ongoing discussion. See [[Marketing Team/Name]]

=== Slogans ===

Several slogan options are available at [[Marketing Team/Slogan]].

== Subpages ==

{{Special:PrefixIndex/Marketing_Team/}}

[[Category:Marketing Team]]
[[Category:Team]]

File:MIT MarketLab Annotated Presentation.odp

2011-03-29T20:35:14Z

SeanDaly: MIT Sloan MarketLab study of Sugar Labs website late 2010 - early 2011.

MIT Sloan MarketLab study of Sugar Labs website late 2010 - early 2011.

Marketing Team

2011-03-29T20:32:02Z

SeanDaly: /* MIT Sloan MarketLab Study */

<noinclude>{{ GoogleTrans-en}}{{TeamHeader|Marketing Team}}</noinclude>

<div style="font-size: 1.0em; background: #daffd5; padding: 10px; border: 1px solid #cde7a8" align=left>'''The Sugar Labs Marketing Team exists to spread the good word about Sugar.''' Sugar provides a simple yet powerful means of engaging young children in the world of learning that is opened up by computing and the Internet. It is the job of the Sugar Labs Marketing Team to promote the benefits of Sugar as widely as possible, and to recruit volunteers to help improve the Sugar experience.</div>

{{TOCright}}

== Mission ==
{{:Marketing Team/Mission}}
== Team Coordinator ==

{{:Marketing Team/Coordinator}} (sdaly at sugarlabs.org) is Marketing Coordinator and welcomes ideas and comments but most of all communicators interested in helping out!

== Mailing list ==

Please see our [http://lists.sugarlabs.org/listinfo/marketing Marketing Team mailing list] and its [http://lists.sugarlabs.org/archive/marketing/ archive].

== Projects ==

Deliverables and/or initiatives actively being worked on (with goals and deadlines).

=== MIT Sloan MarketLab Study ===
Four students from the MIT Sloan MarketLab have prepared a study of the Sugar Labs website. The conclusions indicate the importance not only of redoing our website (launched two years ago when fewer visuals were available), but of addressing other aspects, in particular installation and support issues.

The study wiki, with raw data, is here: https://sites.google.com/site/marketlabsugar

A sample fundraising document by the MarketLab team is [http://wiki.sugarlabs.org/images/e/e3/Sugar_Fundraising_Text_Proposal.odt here.]

===[[Marketing_Team/Events|Events]]===
See [[Marketing Team/Events]] for a table of events we are targeting.

=== Press page ===

Our Press page is here: http://www.sugarlabs.org/index.php?template=press

Translator assistance welcomed!

=== Sugar stories ===

How Sugar motivates us: a series of profiles on contributors. [[Marketing Team/Sugar stories]]

=== Press contacts list ===

We're working on a [[Marketing Team/Press contacts]] list with education-oriented publications. This list is maintained by the Marketing Coordinator.

=== PR phone line ===

+1.857.265.1100

[[Marketing Team/Phone]] is a number that journalists can call for quotes, interviews, clarifications, etc. about Sugar. This is a VoIP number which at this time forwards either to the Marketing Coordinator, an Oversight Board member, or voicemail which is forwarded as a timestamped soundfile to pr AT sugarlabs DOT org, an account monitored through forwarding by the Marketing Coordinator and two others.

=== Sugar Labs website ===

Our polished static website as a landing page for Sugar Labs is live and the new Activities section too. We are currently working on a common navigation bar for all the site sections to simplify navigation for first-time visitors. [[Marketing Team/Website]]

=== [[Marketing Team/Swag|Swag]] ===

To view, download, and contribute to swag designs (stickers, t-shirts, business cards, USB sticks, etc.) and coordinate purchasing swag from suppliers, see [[Marketing Team/Swag]].

== Discussions ==

Conversations that may one day turn into projects, or may have in the past been projects.

=== "Audited" Circulation ===

- [[User:Docdtv|Docdtv]]

While a small user community might discourage adoption of a tool,
a large user community can help encourage adoption. And of course,
small communities need always precede large ones! You know the old
expression: "Eat Sugar! 10**9 flies can't be wrong!" <G>

How do you measure the size of a community? A great way to do that
with automata connected to a global communication network is to
have them "phone home" now and then. Now, I hope what I am suggesting
does not break with any covenent, (implicit or explicit, moral or legal).
But would it be so harmful if, say once a day, a Sugar installation
would briefly tell Sugar Labs "Hey, I'm alive on a machine today!"

Some might agree to do this, but worry about a slippery slope.
Would the future of this humble audit parallel the course of the
United States decennial census, growing from a simple enumeration
into a ruthless and arrogant demographic strip-search?

Of course, audits could be of great benefit to end-users, especially
if they included Activity installation audits. For example, they could
evolve into a mechanism for warning the user about a terrible bug
that needs patching, or advertising a follow-on tool almost all users
adopt upon learning about the new existence of same. (I just now learn
that [http://wiki.laptop.org/go/Automatic_software_updates automatic software updates]
are a new feature of the latest ([http://wiki.laptop.org/go/Release_Notes/8.2.0 8.2.0])
OLPC software release.) By "factoring" the audit mechanism into a
system-wide facility, Activity developers would be spared the need
to code such support on their own.

As a courtesy to Sugar users, cooperation in audits should be voluntary.
But every user should be told why such an audit can help him and others.

Naturally, all this is limited by the fact that not every last machine
on which Sugar will be run will be attached to the Internet.

=== Video channels ===

- [[User:Docdtv|Docdtv]]

1. Does a YouTube channel exist? If not, why not?
There already is a channel at Dailymotion with 19 videos as we write:
http://www.dailymotion.com/sugarlabs/1
YouTube may not use an open source codec, but it is an
incredibly popular search engine and affiliate-propagation tool, see:

http://graphics8.nytimes.com/images/2009/12/31/technology/internet/31tubeGrfx/articleInline.jpg

2. First video would be a 60-second TV-style ad explaining

... what Sugar is (leverage OLPC brand-awareness!)

... that it is free

... what you need to run it

... how you get a copy to install

3. Every time a pitch (q.v. below) is created, a YouTube video record of same is made.
The YouTube version can add stills or short video clips to a talking head.

=== Pitches ===

Short, 1-page elevator pitches to sell Sugar to various audiences. Not formalized, but the homepage (www.sugarlabs.org) is the best starting point. [[Marketing Team/Pitches]]

=== Logo ===

See [[Marketing Team/Logo]].

=== Name ===

Ongoing discussion. See [[Marketing Team/Name]]

=== Slogans ===

Several slogan options are available at [[Marketing Team/Slogan]].

== Subpages ==

{{Special:PrefixIndex/Marketing_Team/}}

[[Category:Marketing Team]]
[[Category:Team]]

Marketing Team

2011-03-29T20:30:14Z

SeanDaly: /* MIT Sloan MarketLab Study */

<noinclude>{{ GoogleTrans-en}}{{TeamHeader|Marketing Team}}</noinclude>

<div style="font-size: 1.0em; background: #daffd5; padding: 10px; border: 1px solid #cde7a8" align=left>'''The Sugar Labs Marketing Team exists to spread the good word about Sugar.''' Sugar provides a simple yet powerful means of engaging young children in the world of learning that is opened up by computing and the Internet. It is the job of the Sugar Labs Marketing Team to promote the benefits of Sugar as widely as possible, and to recruit volunteers to help improve the Sugar experience.</div>

{{TOCright}}

== Mission ==
{{:Marketing Team/Mission}}
== Team Coordinator ==

{{:Marketing Team/Coordinator}} (sdaly at sugarlabs.org) is Marketing Coordinator and welcomes ideas and comments but most of all communicators interested in helping out!

== Mailing list ==

Please see our [http://lists.sugarlabs.org/listinfo/marketing Marketing Team mailing list] and its [http://lists.sugarlabs.org/archive/marketing/ archive].

== Projects ==

Deliverables and/or initiatives actively being worked on (with goals and deadlines).

=== MIT Sloan MarketLab Study ===
Four students from the MIT Sloan MarketLab have prepared a study of the Sugar Labs website. The conclusions indicate the importance not only of redoing our website (launched two years ago when fewer visuals were available), but of addressing other aspects, in particular installation and support issues.

The study wiki, with raw data, is here: https://sites.google.com/site/marketlabsugar

A sample fundraising document by the MarketLab team is here: [[File:Sugar_Fundraising_Text_Proposal.odt]]

===[[Marketing_Team/Events|Events]]===
See [[Marketing Team/Events]] for a table of events we are targeting.

=== Press page ===

Our Press page is here: http://www.sugarlabs.org/index.php?template=press

Translator assistance welcomed!

=== Sugar stories ===

How Sugar motivates us: a series of profiles on contributors. [[Marketing Team/Sugar stories]]

=== Press contacts list ===

We're working on a [[Marketing Team/Press contacts]] list with education-oriented publications. This list is maintained by the Marketing Coordinator.

=== PR phone line ===

+1.857.265.1100

[[Marketing Team/Phone]] is a number that journalists can call for quotes, interviews, clarifications, etc. about Sugar. This is a VoIP number which at this time forwards either to the Marketing Coordinator, an Oversight Board member, or voicemail which is forwarded as a timestamped soundfile to pr AT sugarlabs DOT org, an account monitored through forwarding by the Marketing Coordinator and two others.

=== Sugar Labs website ===

Our polished static website as a landing page for Sugar Labs is live and the new Activities section too. We are currently working on a common navigation bar for all the site sections to simplify navigation for first-time visitors. [[Marketing Team/Website]]

=== [[Marketing Team/Swag|Swag]] ===

To view, download, and contribute to swag designs (stickers, t-shirts, business cards, USB sticks, etc.) and coordinate purchasing swag from suppliers, see [[Marketing Team/Swag]].

== Discussions ==

Conversations that may one day turn into projects, or may have in the past been projects.

=== "Audited" Circulation ===

- [[User:Docdtv|Docdtv]]

While a small user community might discourage adoption of a tool,
a large user community can help encourage adoption. And of course,
small communities need always precede large ones! You know the old
expression: "Eat Sugar! 10**9 flies can't be wrong!" <G>

How do you measure the size of a community? A great way to do that
with automata connected to a global communication network is to
have them "phone home" now and then. Now, I hope what I am suggesting
does not break with any covenent, (implicit or explicit, moral or legal).
But would it be so harmful if, say once a day, a Sugar installation
would briefly tell Sugar Labs "Hey, I'm alive on a machine today!"

Some might agree to do this, but worry about a slippery slope.
Would the future of this humble audit parallel the course of the
United States decennial census, growing from a simple enumeration
into a ruthless and arrogant demographic strip-search?

Of course, audits could be of great benefit to end-users, especially
if they included Activity installation audits. For example, they could
evolve into a mechanism for warning the user about a terrible bug
that needs patching, or advertising a follow-on tool almost all users
adopt upon learning about the new existence of same. (I just now learn
that [http://wiki.laptop.org/go/Automatic_software_updates automatic software updates]
are a new feature of the latest ([http://wiki.laptop.org/go/Release_Notes/8.2.0 8.2.0])
OLPC software release.) By "factoring" the audit mechanism into a
system-wide facility, Activity developers would be spared the need
to code such support on their own.

As a courtesy to Sugar users, cooperation in audits should be voluntary.
But every user should be told why such an audit can help him and others.

Naturally, all this is limited by the fact that not every last machine
on which Sugar will be run will be attached to the Internet.

=== Video channels ===

- [[User:Docdtv|Docdtv]]

1. Does a YouTube channel exist? If not, why not?
There already is a channel at Dailymotion with 19 videos as we write:
http://www.dailymotion.com/sugarlabs/1
YouTube may not use an open source codec, but it is an
incredibly popular search engine and affiliate-propagation tool, see:

http://graphics8.nytimes.com/images/2009/12/31/technology/internet/31tubeGrfx/articleInline.jpg

2. First video would be a 60-second TV-style ad explaining

... what Sugar is (leverage OLPC brand-awareness!)

... that it is free

... what you need to run it

... how you get a copy to install

3. Every time a pitch (q.v. below) is created, a YouTube video record of same is made.
The YouTube version can add stills or short video clips to a talking head.

=== Pitches ===

Short, 1-page elevator pitches to sell Sugar to various audiences. Not formalized, but the homepage (www.sugarlabs.org) is the best starting point. [[Marketing Team/Pitches]]

=== Logo ===

See [[Marketing Team/Logo]].

=== Name ===

Ongoing discussion. See [[Marketing Team/Name]]

=== Slogans ===

Several slogan options are available at [[Marketing Team/Slogan]].

== Subpages ==

{{Special:PrefixIndex/Marketing_Team/}}

[[Category:Marketing Team]]
[[Category:Team]]

File:Sugar Fundraising Text Proposal.odt

2011-03-29T20:22:29Z

SeanDaly: MIT Sloan MarketLab proposed example document for fundraising

MIT Sloan MarketLab proposed example document for fundraising

Marketing Team

2011-03-29T20:13:02Z

SeanDaly: /* MIT Sloan MarketLab Study */

<noinclude>{{ GoogleTrans-en}}{{TeamHeader|Marketing Team}}</noinclude>

<div style="font-size: 1.0em; background: #daffd5; padding: 10px; border: 1px solid #cde7a8" align=left>'''The Sugar Labs Marketing Team exists to spread the good word about Sugar.''' Sugar provides a simple yet powerful means of engaging young children in the world of learning that is opened up by computing and the Internet. It is the job of the Sugar Labs Marketing Team to promote the benefits of Sugar as widely as possible, and to recruit volunteers to help improve the Sugar experience.</div>

{{TOCright}}

== Mission ==
{{:Marketing Team/Mission}}
== Team Coordinator ==

{{:Marketing Team/Coordinator}} (sdaly at sugarlabs.org) is Marketing Coordinator and welcomes ideas and comments but most of all communicators interested in helping out!

== Mailing list ==

Please see our [http://lists.sugarlabs.org/listinfo/marketing Marketing Team mailing list] and its [http://lists.sugarlabs.org/archive/marketing/ archive].

== Projects ==

Deliverables and/or initiatives actively being worked on (with goals and deadlines).

=== MIT Sloan MarketLab Study ===
Four students from the MIT Sloan MarketLab have prepared a study of the Sugar Labs website. The conclusions indicate the importance not only of redoing our website (launched two years ago when fewer visuals were available), but of addressing other aspects, in particular installation and support issues.

The study wiki, with raw data, is here: https://sites.google.com/site/marketlabsugar

===[[Marketing_Team/Events|Events]]===
See [[Marketing Team/Events]] for a table of events we are targeting.

=== Press page ===

Our Press page is here: http://www.sugarlabs.org/index.php?template=press

Translator assistance welcomed!

=== Sugar stories ===

How Sugar motivates us: a series of profiles on contributors. [[Marketing Team/Sugar stories]]

=== Press contacts list ===

We're working on a [[Marketing Team/Press contacts]] list with education-oriented publications. This list is maintained by the Marketing Coordinator.

=== PR phone line ===

+1.857.265.1100

[[Marketing Team/Phone]] is a number that journalists can call for quotes, interviews, clarifications, etc. about Sugar. This is a VoIP number which at this time forwards either to the Marketing Coordinator, an Oversight Board member, or voicemail which is forwarded as a timestamped soundfile to pr AT sugarlabs DOT org, an account monitored through forwarding by the Marketing Coordinator and two others.

=== Sugar Labs website ===

Our polished static website as a landing page for Sugar Labs is live and the new Activities section too. We are currently working on a common navigation bar for all the site sections to simplify navigation for first-time visitors. [[Marketing Team/Website]]

=== [[Marketing Team/Swag|Swag]] ===

To view, download, and contribute to swag designs (stickers, t-shirts, business cards, USB sticks, etc.) and coordinate purchasing swag from suppliers, see [[Marketing Team/Swag]].

== Discussions ==

Conversations that may one day turn into projects, or may have in the past been projects.

=== "Audited" Circulation ===

- [[User:Docdtv|Docdtv]]

While a small user community might discourage adoption of a tool,
a large user community can help encourage adoption. And of course,
small communities need always precede large ones! You know the old
expression: "Eat Sugar! 10**9 flies can't be wrong!" <G>

How do you measure the size of a community? A great way to do that
with automata connected to a global communication network is to
have them "phone home" now and then. Now, I hope what I am suggesting
does not break with any covenent, (implicit or explicit, moral or legal).
But would it be so harmful if, say once a day, a Sugar installation
would briefly tell Sugar Labs "Hey, I'm alive on a machine today!"

Some might agree to do this, but worry about a slippery slope.
Would the future of this humble audit parallel the course of the
United States decennial census, growing from a simple enumeration
into a ruthless and arrogant demographic strip-search?

Of course, audits could be of great benefit to end-users, especially
if they included Activity installation audits. For example, they could
evolve into a mechanism for warning the user about a terrible bug
that needs patching, or advertising a follow-on tool almost all users
adopt upon learning about the new existence of same. (I just now learn
that [http://wiki.laptop.org/go/Automatic_software_updates automatic software updates]
are a new feature of the latest ([http://wiki.laptop.org/go/Release_Notes/8.2.0 8.2.0])
OLPC software release.) By "factoring" the audit mechanism into a
system-wide facility, Activity developers would be spared the need
to code such support on their own.

As a courtesy to Sugar users, cooperation in audits should be voluntary.
But every user should be told why such an audit can help him and others.

Naturally, all this is limited by the fact that not every last machine
on which Sugar will be run will be attached to the Internet.

=== Video channels ===

- [[User:Docdtv|Docdtv]]

1. Does a YouTube channel exist? If not, why not?
There already is a channel at Dailymotion with 19 videos as we write:
http://www.dailymotion.com/sugarlabs/1
YouTube may not use an open source codec, but it is an
incredibly popular search engine and affiliate-propagation tool, see:

http://graphics8.nytimes.com/images/2009/12/31/technology/internet/31tubeGrfx/articleInline.jpg

2. First video would be a 60-second TV-style ad explaining

... what Sugar is (leverage OLPC brand-awareness!)

... that it is free

... what you need to run it

... how you get a copy to install

3. Every time a pitch (q.v. below) is created, a YouTube video record of same is made.
The YouTube version can add stills or short video clips to a talking head.

=== Pitches ===

Short, 1-page elevator pitches to sell Sugar to various audiences. Not formalized, but the homepage (www.sugarlabs.org) is the best starting point. [[Marketing Team/Pitches]]

=== Logo ===

See [[Marketing Team/Logo]].

=== Name ===

Ongoing discussion. See [[Marketing Team/Name]]

=== Slogans ===

Several slogan options are available at [[Marketing Team/Slogan]].

== Subpages ==

{{Special:PrefixIndex/Marketing_Team/}}

[[Category:Marketing Team]]
[[Category:Team]]

Marketing Team

2011-03-29T20:10:40Z

SeanDaly: /* Projects */

<noinclude>{{ GoogleTrans-en}}{{TeamHeader|Marketing Team}}</noinclude>

<div style="font-size: 1.0em; background: #daffd5; padding: 10px; border: 1px solid #cde7a8" align=left>'''The Sugar Labs Marketing Team exists to spread the good word about Sugar.''' Sugar provides a simple yet powerful means of engaging young children in the world of learning that is opened up by computing and the Internet. It is the job of the Sugar Labs Marketing Team to promote the benefits of Sugar as widely as possible, and to recruit volunteers to help improve the Sugar experience.</div>

{{TOCright}}

== Mission ==
{{:Marketing Team/Mission}}
== Team Coordinator ==

{{:Marketing Team/Coordinator}} (sdaly at sugarlabs.org) is Marketing Coordinator and welcomes ideas and comments but most of all communicators interested in helping out!

== Mailing list ==

Please see our [http://lists.sugarlabs.org/listinfo/marketing Marketing Team mailing list] and its [http://lists.sugarlabs.org/archive/marketing/ archive].

== Projects ==

Deliverables and/or initiatives actively being worked on (with goals and deadlines).

=== MIT Sloan MarketLab Study ===
Four students from the MIT Sloan MarketLab have prepared a study of the Sugar Labs website. The conclusions indicate the importance not only of redoing our website (launched two years ago when fewer visuals were available), but of addressing other aspects, in particular installation and support issues.

===[[Marketing_Team/Events|Events]]===
See [[Marketing Team/Events]] for a table of events we are targeting.

=== Press page ===

Our Press page is here: http://www.sugarlabs.org/index.php?template=press

Translator assistance welcomed!

=== Sugar stories ===

How Sugar motivates us: a series of profiles on contributors. [[Marketing Team/Sugar stories]]

=== Press contacts list ===

We're working on a [[Marketing Team/Press contacts]] list with education-oriented publications. This list is maintained by the Marketing Coordinator.

=== PR phone line ===

+1.857.265.1100

[[Marketing Team/Phone]] is a number that journalists can call for quotes, interviews, clarifications, etc. about Sugar. This is a VoIP number which at this time forwards either to the Marketing Coordinator, an Oversight Board member, or voicemail which is forwarded as a timestamped soundfile to pr AT sugarlabs DOT org, an account monitored through forwarding by the Marketing Coordinator and two others.

=== Sugar Labs website ===

Our polished static website as a landing page for Sugar Labs is live and the new Activities section too. We are currently working on a common navigation bar for all the site sections to simplify navigation for first-time visitors. [[Marketing Team/Website]]

=== [[Marketing Team/Swag|Swag]] ===

To view, download, and contribute to swag designs (stickers, t-shirts, business cards, USB sticks, etc.) and coordinate purchasing swag from suppliers, see [[Marketing Team/Swag]].

== Discussions ==

Conversations that may one day turn into projects, or may have in the past been projects.

=== "Audited" Circulation ===

- [[User:Docdtv|Docdtv]]

While a small user community might discourage adoption of a tool,
a large user community can help encourage adoption. And of course,
small communities need always precede large ones! You know the old
expression: "Eat Sugar! 10**9 flies can't be wrong!" <G>

How do you measure the size of a community? A great way to do that
with automata connected to a global communication network is to
have them "phone home" now and then. Now, I hope what I am suggesting
does not break with any covenent, (implicit or explicit, moral or legal).
But would it be so harmful if, say once a day, a Sugar installation
would briefly tell Sugar Labs "Hey, I'm alive on a machine today!"

Some might agree to do this, but worry about a slippery slope.
Would the future of this humble audit parallel the course of the
United States decennial census, growing from a simple enumeration
into a ruthless and arrogant demographic strip-search?

Of course, audits could be of great benefit to end-users, especially
if they included Activity installation audits. For example, they could
evolve into a mechanism for warning the user about a terrible bug
that needs patching, or advertising a follow-on tool almost all users
adopt upon learning about the new existence of same. (I just now learn
that [http://wiki.laptop.org/go/Automatic_software_updates automatic software updates]
are a new feature of the latest ([http://wiki.laptop.org/go/Release_Notes/8.2.0 8.2.0])
OLPC software release.) By "factoring" the audit mechanism into a
system-wide facility, Activity developers would be spared the need
to code such support on their own.

As a courtesy to Sugar users, cooperation in audits should be voluntary.
But every user should be told why such an audit can help him and others.

Naturally, all this is limited by the fact that not every last machine
on which Sugar will be run will be attached to the Internet.

=== Video channels ===

- [[User:Docdtv|Docdtv]]

1. Does a YouTube channel exist? If not, why not?
There already is a channel at Dailymotion with 19 videos as we write:
http://www.dailymotion.com/sugarlabs/1
YouTube may not use an open source codec, but it is an
incredibly popular search engine and affiliate-propagation tool, see:

http://graphics8.nytimes.com/images/2009/12/31/technology/internet/31tubeGrfx/articleInline.jpg

2. First video would be a 60-second TV-style ad explaining

... what Sugar is (leverage OLPC brand-awareness!)

... that it is free

... what you need to run it

... how you get a copy to install

3. Every time a pitch (q.v. below) is created, a YouTube video record of same is made.
The YouTube version can add stills or short video clips to a talking head.

=== Pitches ===

Short, 1-page elevator pitches to sell Sugar to various audiences. Not formalized, but the homepage (www.sugarlabs.org) is the best starting point. [[Marketing Team/Pitches]]

=== Logo ===

See [[Marketing Team/Logo]].

=== Name ===

Ongoing discussion. See [[Marketing Team/Name]]

=== Slogans ===

Several slogan options are available at [[Marketing Team/Slogan]].

== Subpages ==

{{Special:PrefixIndex/Marketing_Team/}}

[[Category:Marketing Team]]
[[Category:Team]]

Marketing Team/Meetings

2011-03-29T19:57:08Z

SeanDaly: /* Meeting Logs */

<noinclude>{{TeamHeader|Marketing Team}}</noinclude>
__NOTOC__
<div style="font-size: 1.0em; background: #daffd5; padding: 10px; border: 1px solid #cde7a8" align=left>The Marketing team will be holding regular weekly meetings on Tuesdays at 15 UTC on irc.freenode.net (channel: #sugar-meeting).
Please add to the agenda below and please join in with your ideas.

Hint: You can use an [http://www.timeanddate.com/worldclock/converter.html online time calculator] to convert from UTC to your local time zone or back. Help: [[Sugar_Labs/Communication channels#IRC.2C_Internet_Relay_Chat |Using IRC]]

The Sugar Labs Meetings calendar is available in a variety of formats at these links: [[File:XML.gif|link=http://www.google.com/calendar/feeds/h9cfuk10894em7a8moemquusmg%40group.calendar.google.com/public/basic]] [[File:ICal.gif|link=http://www.google.com/calendar/ical/h9cfuk10894em7a8moemquusmg%40group.calendar.google.com/public/basic.ics]] [[File:HTML.gif|link=http://www.google.com/calendar/embed?src=h9cfuk10894em7a8moemquusmg%40group.calendar.google.com&ctz=America/New_York]].
</div><br>

: Please consult the [http://lists.sugarlabs.org/archive/marketing/ Marketing list archives] and IRC meeting transcripts [[#Meeting Logs|below]] for the latest initiatives.

===[[Marketing_Team/Events|Events]]===
:See [[Marketing Team/Events]] for special Meeting Events.

===Upcoming Agenda for on-line Meeting===
* [[Marketing Team/Events/Tour of Uruguay]]

===Previous Agenda===

== Meeting Logs ==
* [http://meeting.sugarlabs.org/sugar-meeting/meetings/2011-03-29T14:16:49 2011-03-29]
* [http://meeting.sugarlabs.org/sugar-meeting/meetings/2011-03-15T16:04:05 2011-03-15]
* [http://meeting.sugarlabs.org/sugar-meeting/2011-03-08#i_2641710 2011-03-08]
* [http://meeting.sugarlabs.org/sugar-meeting/meetings/2011-03-01T15:05:46 2011-03-01]
* [[/2011-02-22|2011-02-22]]
* [http://meeting.sugarlabs.org/sugar-meeting/meetings/2011-02-15T15:05:53 2011-02-15]

* [http://meeting.sugarlabs.org/sugar-meeting.log.20100601_1009.html 06-01-2010]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20100525_1009.html 05-25-2010]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20100504_1010.html 05-04-2010]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20100223_1003.html 02-23-2010]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20100216_1008.html 02-16-2010]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20100210_1005.html 02-10-2010]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20100127_1017.html 01-27-2010]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20100119_1010.html 01-19-2010]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20100112_1005.html 01-12-2010]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20091215_1003.html 12-15-2009]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20091201_1002.html 12-01-2009]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20091125_1003.html 11-25-2009]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20091111_1118.html 11-11-2009]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20091103_1002.html 11-03-2009]
* [http://lists.sugarlabs.org/archive/marketing/2009-October/002328.html 10-27-2009]
* [http://lists.sugarlabs.org/archive/marketing/2009-October/002269.html 10-20-2009]
* [http://lists.sugarlabs.org/archive/marketing/2009-October/002207.html 10-13-2009]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20091006_1006.html 10-06-2009]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20090929_1005.html 09-29-2009]
* [http://lists.sugarlabs.org/archive/marketing/2009-September/002086.html 09-22-2009]
* [http://lists.sugarlabs.org/archive/marketing/2009-September/002060.html 09-15-2009]
* [http://lists.sugarlabs.org/archive/marketing/2009-September/002021.html 09-08-2009]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20090630_1105.html 06-30-2009]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20090623_1119.html 06-23-2009]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20090616_1104.html 06-16-2009]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20090609_1104.html 06-09-2009]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20090602_1106.html 06-02-2009]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20090526_1108.html 05-26-2009]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20090519_1105.html 05-19-2009]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20090512_1103.html 05-12-2009]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20090505_1101.html 05-05-2009]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20090429_1101.html 04-29-2009]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20090414_1101.html 04-14-2009]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20090407_1002.html 04-07-2009]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20090324_1102.html 03-24-2009]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20090317_1102.html 03-17-2009]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20090313_1205.html 03-13-2009]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20090310_1100.html 03-10-2009]
* [[Marketing Team/Meetings/03-03-2009]]
* [[Marketing Team/Meetings/02-25-2009]]
* [[Marketing Team/Meetings/02-10-2009]]
* [[Marketing Team/Meetings/12-23-2008]]
* [[Marketing Team/Meetings/12-16-2008]]
* [[Marketing Team/Meetings/12-9-2008]]
* [[Marketing Team/Meetings/12-2-2008]]

[[Category:Marketing Team]]
[[Category:Meetings]]

Sugar on a Stick

2010-06-10T10:38:22Z

SeanDaly: /* What is Sugar on a Stick? */

<noinclude>
[[Category:Project]]
[[Category:Live USB]]
[[Category:Sugar on a Stick]]
</noinclude>

== What is Sugar on a Stick? ==

{|
|-
| style="border: 0; border-width: 0; width: 350px;" | [[File:SugaronastickMirabelle.png |300px|left|link=http://spins.fedoraproject.org/soas]]
| style="border: 0; border-width: 0;" | '''[[Sugar on a Stick]]''' is a [http://fedoraproject.org Fedora-based] [[wikipedia:Live USB|Live USB]] operating system featuring the award-winning [[What is Sugar?|Sugar Learning Platform]] and designed to fit on an ordinary USB thumbdrive ("stick"). Learn more about [http://spins.fedoraproject.org/soas/#home the project] and the [http://spins.fedoraproject.org/soas/#about principles] behind it at our [http://spins.fedoraproject.org/soas Spin webpage]. The most recent version is version 3, code-named '''[[Sugar on a Stick/Mirabelle|Mirabelle]]''' and was released on '''May 25, 2010.''' The '''[[Sugar_on_a_Stick/Installation/Variations#SugarCreationKit_DVD|Sugar Creation Kit]]''' is a downloadable DVD which includes Mirabelle, previous versions of Sugar on a Stick, Activities for children, documentation, and tools.
|}

__TOC__

=== Want to use Sugar on a Stick? ===

{|
|-
| rowspan="3" style="border: 0; border-width: 0; width: 350px;" | [[File:Cici-maze.jpg |300px|left|link=http://spins.fedoraproject.org/soas]]
|-
|
|style="border: 0; border-width: 0;" align="center" | [[File:Download Mirabell.png|center|link=http://spins.fedoraproject.org/soas/#downloads]]
|-
|
|If you'd like to try out Sugar on a Stick, check out the [http://spins.fedoraproject.org/soas Sugar on a Stick Spin Page] - it's where our software downloads, installation and usage instructions, and support information lives.

After you've tried out Sugar on a Stick, we hope you'll come back here and join our community of contributors to help us make the next release even better.
|}

=== Want to contribute to Sugar on a Stick? ===

{|
|-
| style="border: 0; border-width: 0; width: 350px;" | [[File:SoaS-contributors.jpg |300px|left|link=Sugar_on_a_Stick]]
| style="border: 0; border-width: 0;" |
You're in the right place! This page is a contributors portal to the project, and contains everything you need to get started in becoming part of the Sugar on a Stick community.
|}

== New contributors start here! ==

Welcome! We're excited that you want to help us bring the Sugar Learning Platform to children around the world. No prior experience with computers or educational technology is required - in fact, we actively encourage a diversity of backgrounds, ages, and perspectives. See the [[Joining Sugar on a Stick]] page for instructions on how to get started. You may also want to check out the [http://openhatch.org/+projects/Sugar%20on%20a%20Stick Sugar on a Stick project page] on [http://openhatch.org OpenHatch], or attend one of our [[Sugar on a Stick meetings]].

== What can you do? ==

There are three main ways you can contribute to the Sugar on a Stick community. We work closely with our upstreams, [http://sugarlabs.org Sugar Labs] and [http://fedoraproject.org the Fedora Project].

=== Get Activities on the Stick ===

{|
|-
| style="border: 0; border-width: 0;" |

We're always looking for help with all aspects of the [[Sugar on a Stick release process]]. Here are a few things you can do:

* [[Sugar on a Stick QA|Test Sugar on a Stick]] and help us find bugs and think of ways the project could be better. When you find a bug or think of an enhancement, [[How to file a ticket|file a ticket!]] ''No technical experience required.''
* Help make it easier for others to test Sugar on a Stick by writing [[Sugar on a Stick QA#Test cases|test cases]]. ''If you've run a test case, you can write a test case.''
* [http://bugs.sugarlabs.org Fix a bug or add a feature] to an existing Activity, to [[Development Team|sugar-core itself]], or to [http://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=SoaS&order=priority&col=id&col=summary&col=status&col=type&col=priority&col=milestone&col=component Sugar on a Stick]. See [[How to fix an Activity bug]] and [[How to fix a sugar-core bug]] to get started. ''Basic Python programming skills - or the desire to learn - are all that's needed.''
* [https://fedoraproject.org/wiki/Sugar_Activities Package Sugar Activities for Fedora]. ''If you're a [https://fedoraproject.org/wiki/PackageMaintainers/Join Fedora Packager] or want to become one, help in this area is something we desperately need - it's a trickier thing to learn, but rewarding once you get the hang of it.''
* [[Sugar on a Stick release process#Review|Review Activities for inclusion in the build]] - check submitted Activities against our [[SoaS Activity Criteria]] and help us choose what gets included in the next release! ''No prior experience needed - we do reviews during our [[Sugar on a Stick meetings|weekly meetings]] and will teach you how.''
* Have an idea for a technical feature that isn't an Activity? Check out our [[Sugar on a Stick release process#Feature process|feature process]].

| style="border: 0; border-width: 0; width: 150px;" |[[Image:SoaS-netbook-1.jpg|150px|right|link=http://wiki.sugarlabs.org/go/Sugar_on_a_Stick_release_process]][[Image:SoaS-netbook-2.jpg|150px|right|link=http://wiki.sugarlabs.org/go/Sugar_on_a_Stick_release_process]][[Image:SoaS-netbook-3.jpg|150px|right|link=http://wiki.sugarlabs.org/go/Sugar_on_a_Stick_release_process]]
|}

=== Get Sticks into Schools ===

{|
|-
| style="border: 0; border-width: 0; width: 250px;" | [[File:Cici-stick.jpg |200px|left|link=Sugar_on_a_Stick_deployment_process]]
| style="border: 0; border-width: 0;" |
Deployments all over the world need many different types of help as they work through the [[Sugar on a Stick deployment process]] - we need help building resources for all deployments to use, supporting those deployments, and helping new deployments start, as well as gathering stories and feedback from deployments so that we can make the next version of Sugar on a Stick even better.

Some things you can do to help:

* ''"It's a wiki: Edit away!"'' is often said in open source communities. Almost nothing is set in stone and can't be undone. So if you've got ideas how to make instructions clearer and more accessible to our users, just go for it!
* We produce official documentation such as the [http://download.sugarlabs.org/soas/docs/creation-kit/ Creation Kit] or the [http://download.sugarlabs.org/soas/docs/customization-guide/ Customization Guide]. If you've an idea how to make them better, why don't you jump in and create a patch? Creating these nifty text files is simple - instructions live in the [[Sugar_on_a_Stick/Documentation_SOP|Documentation SOP]].
* Unofficial documentation for unsupported workarounds for [[Sugar on a Stick/Installation|installation]] and [[Sugar on a Stick/Sugar Clone|customization]] need to be edited, tested, and submitted for approval for official support. Check them out and leave comments and improvements; just jump in and edit the page.
* Interested in starting a deployment or helping a specific one (with anything from pedagogical design to technical support to funding logistics)? Introduce yourself on the deployment lists for [http://lists.sugarlabs.org/ Sugar Labs] and [http://lists.laptop.org/listinfo/ One Laptop Per Child] and we'll get you connected with some teachers on the ground.
* We're looking for some people to help us assemble tools for our support team to use. Email the [http://lists.sugarlabs.org/listinfo/soas Sugar on a Stick mailing list] if you're interested.
|}

=== Get Contributors ===

{|
|-
| style="border: 0; border-width: 0;" |

Contributors are the lifeblood of the Sugar on a Stick community - we work hard to bring a playful mindset of teaching, learning, and meaningful work to the children we aim to reach, and we aim to keep that mindset in our own work and community as well. Welcoming and teaching new contributors or all types, building the resources they need, and teaching them how to empower others in their turn is one of the most important things you can do; it is ''everyone's'' responsibility to help build our community, one person at a time.

Some things you can do:

* Edit this page and [[Joining Sugar on a Stick]]. Is there something we could do to make the "getting started" process easier? You don't have to ask permission to edit; just do it!
* Help us fill in our remaining task-starter pages: [[Sugar on a Stick release process]], [[How to fix an Activity bug]], [[How to fix a sugar-core bug]], and [[Sugar on a Stick deployment process]]/
* [http://openhatch.org/+projects/Sugar%20on%20a%20Stick Point out starter tasks on OpenHatch] - fill in questions and ideas for beginner jobs, and point newcomers towards them.
* [http://lists.sugarlabs.org/listinfo/soas Watch for introductions on the mailing list], and send welcome emails to new contributors (copy the list, so we can see what advice a newcomer has gotten so far).
* Hang out with us on IRC: [http://webchat.freenode.net?channels=sugar #sugar]. This is the place where users join when using [http://activities.sugarlabs.org/en-US/sugar/addon/4029 IRC Activity]. Help them past initial trouble and provide instant help!
* Add to our collection of otherwise tricky-to-find FAQs at [[The undiscoverable]].

| style="border: 0; border-width: 0; width: 200px;" |[[Image:Cici-netbook.jpg|200px|right|link=http://wiki.sugarlabs.org/go/Sugar_on_a_Stick]]
|}

== What's happening? ==

=== Meetings ===

We have weekly meetings on IRC - see [[Sugar on a Stick meetings]] for more information, including logs from past meetings. Attending a meeting is a great way for newcomers to get started.

=== Release schedule ===

Our release schedule is based on the [[fedora:Releases/Schedule | Fedora release schedule]]. The most recent release was v.3, code-named [[Mirabelle]], shipped on '''May 25, 2010''' and based on the Fedora 13 release schedule. The next Sugar on a Stick version will be based on the [[fedora:Releases/14/Schedule | Fedora 14 release schedule]].

{|border="1" cellspacing="0" width="100%"
|-
|rowspan="2"| 2010-05-25 || Sugar on a Stick v.3.0 Mirabelle released
|-
| Planning & Development Begins
|-
| 2010-07-27 || Feature Freeze (all features have to be ''approved'' and in a satisfying state.)
|-
| 2010-08-03 || Alpha Change deadline (all changes will have to be ''pushed'' by this time. pending submissions are insufficient.)
|-
| 2010-08-17 || Alpha Release
|-
| 2010-09-07 || Beta Change deadline (all changes will have to be ''pushed'' by this time. pending submissions are insufficient.)
|-
| 2010-09-21 || Beta Release
|-
| 2010-10-12 || Final Freeze (all changes have to be ''pushed''. no further changes permitted.)
|-
| 2010-10-14 || Compose Release Candidate
|-
| 2010-10-26 || Sugar on a Stick v.4.0 Final Release
|-
|}

=== Contributor stories ===

To find out what other contributors are doing, check out [http://planet.sugarlabs.org Planet Sugar Labs], where contributors to Sugar Labs and the Sugar on a Stick project aggregate their blogs. You can also [[Sysadmin/Planet syndication request|add your own blog to the Planet]].

== Related work ==

While the projects listed below are not part of Sugar on a Stick, we watch them closely and try to work with them when possible (or at least we're trying to learn!)

* [[Sugar_on_a_Stick/Installation/Variations#SugarCreationKit_DVD|SugarCreationKit DVD]] - Complete DVD containing all the resources required to create all 3 versions of Sugar-on-a-Stick without requiring Internet access
* Other [[:Category:Live USB|portable Sugar distributions]] - Live USB work based on other Linux distributions.

== Previous versions and subpage index ==
{{Show|Earlier versions of Sugar on a Stick can be reviewed at these pages: |{{Special:PrefixIndex/Sugar on a Stick/}}}}

Sugar on a Stick

2010-06-10T10:37:37Z

SeanDaly: /* What is Sugar on a Stick? */

<noinclude>
[[Category:Project]]
[[Category:Live USB]]
[[Category:Sugar on a Stick]]
</noinclude>

== What is Sugar on a Stick? ==

{|
|-
| style="border: 0; border-width: 0; width: 350px;" | [[File:SugaronastickMirabelle.png |300px|left|link=http://spins.fedoraproject.org/soas]]
| style="border: 0; border-width: 0;" | '''[[Sugar on a Stick]]''' is a [http://fedoraproject.org Fedora-based] [[wikipedia:Live USB|Live USB]] operating system featuring the award-winning [[What is Sugar?|Sugar Learning Platform]] and designed to fit on an ordinary USB thumbdrive ("stick"). Learn more about [http://spins.fedoraproject.org/soas/#home the project] and the [http://spins.fedoraproject.org/soas/#about principles] behind it at our [http://spins.fedoraproject.org/soas Spin webpage]. The most recent version is version 3, code-named '''[[Sugar on a Stick/Mirabelle|Mirabelle]]''' and was released on '''May 25, 2010.''' The [[Sugar_on_a_Stick/Installation/Variations#SugarCreationKit_DVD|Sugar Creation Kit]] is a downloadable DVD which includes Mirabelle, previous versions of Sugar on a Stick, Activities for children, documentation, and tools.
|}

__TOC__

=== Want to use Sugar on a Stick? ===

{|
|-
| rowspan="3" style="border: 0; border-width: 0; width: 350px;" | [[File:Cici-maze.jpg |300px|left|link=http://spins.fedoraproject.org/soas]]
|-
|
|style="border: 0; border-width: 0;" align="center" | [[File:Download Mirabell.png|center|link=http://spins.fedoraproject.org/soas/#downloads]]
|-
|
|If you'd like to try out Sugar on a Stick, check out the [http://spins.fedoraproject.org/soas Sugar on a Stick Spin Page] - it's where our software downloads, installation and usage instructions, and support information lives.

After you've tried out Sugar on a Stick, we hope you'll come back here and join our community of contributors to help us make the next release even better.
|}

=== Want to contribute to Sugar on a Stick? ===

{|
|-
| style="border: 0; border-width: 0; width: 350px;" | [[File:SoaS-contributors.jpg |300px|left|link=Sugar_on_a_Stick]]
| style="border: 0; border-width: 0;" |
You're in the right place! This page is a contributors portal to the project, and contains everything you need to get started in becoming part of the Sugar on a Stick community.
|}

== New contributors start here! ==

Welcome! We're excited that you want to help us bring the Sugar Learning Platform to children around the world. No prior experience with computers or educational technology is required - in fact, we actively encourage a diversity of backgrounds, ages, and perspectives. See the [[Joining Sugar on a Stick]] page for instructions on how to get started. You may also want to check out the [http://openhatch.org/+projects/Sugar%20on%20a%20Stick Sugar on a Stick project page] on [http://openhatch.org OpenHatch], or attend one of our [[Sugar on a Stick meetings]].

== What can you do? ==

There are three main ways you can contribute to the Sugar on a Stick community. We work closely with our upstreams, [http://sugarlabs.org Sugar Labs] and [http://fedoraproject.org the Fedora Project].

=== Get Activities on the Stick ===

{|
|-
| style="border: 0; border-width: 0;" |

We're always looking for help with all aspects of the [[Sugar on a Stick release process]]. Here are a few things you can do:

* [[Sugar on a Stick QA|Test Sugar on a Stick]] and help us find bugs and think of ways the project could be better. When you find a bug or think of an enhancement, [[How to file a ticket|file a ticket!]] ''No technical experience required.''
* Help make it easier for others to test Sugar on a Stick by writing [[Sugar on a Stick QA#Test cases|test cases]]. ''If you've run a test case, you can write a test case.''
* [http://bugs.sugarlabs.org Fix a bug or add a feature] to an existing Activity, to [[Development Team|sugar-core itself]], or to [http://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=SoaS&order=priority&col=id&col=summary&col=status&col=type&col=priority&col=milestone&col=component Sugar on a Stick]. See [[How to fix an Activity bug]] and [[How to fix a sugar-core bug]] to get started. ''Basic Python programming skills - or the desire to learn - are all that's needed.''
* [https://fedoraproject.org/wiki/Sugar_Activities Package Sugar Activities for Fedora]. ''If you're a [https://fedoraproject.org/wiki/PackageMaintainers/Join Fedora Packager] or want to become one, help in this area is something we desperately need - it's a trickier thing to learn, but rewarding once you get the hang of it.''
* [[Sugar on a Stick release process#Review|Review Activities for inclusion in the build]] - check submitted Activities against our [[SoaS Activity Criteria]] and help us choose what gets included in the next release! ''No prior experience needed - we do reviews during our [[Sugar on a Stick meetings|weekly meetings]] and will teach you how.''
* Have an idea for a technical feature that isn't an Activity? Check out our [[Sugar on a Stick release process#Feature process|feature process]].

| style="border: 0; border-width: 0; width: 150px;" |[[Image:SoaS-netbook-1.jpg|150px|right|link=http://wiki.sugarlabs.org/go/Sugar_on_a_Stick_release_process]][[Image:SoaS-netbook-2.jpg|150px|right|link=http://wiki.sugarlabs.org/go/Sugar_on_a_Stick_release_process]][[Image:SoaS-netbook-3.jpg|150px|right|link=http://wiki.sugarlabs.org/go/Sugar_on_a_Stick_release_process]]
|}

=== Get Sticks into Schools ===

{|
|-
| style="border: 0; border-width: 0; width: 250px;" | [[File:Cici-stick.jpg |200px|left|link=Sugar_on_a_Stick_deployment_process]]
| style="border: 0; border-width: 0;" |
Deployments all over the world need many different types of help as they work through the [[Sugar on a Stick deployment process]] - we need help building resources for all deployments to use, supporting those deployments, and helping new deployments start, as well as gathering stories and feedback from deployments so that we can make the next version of Sugar on a Stick even better.

Some things you can do to help:

* ''"It's a wiki: Edit away!"'' is often said in open source communities. Almost nothing is set in stone and can't be undone. So if you've got ideas how to make instructions clearer and more accessible to our users, just go for it!
* We produce official documentation such as the [http://download.sugarlabs.org/soas/docs/creation-kit/ Creation Kit] or the [http://download.sugarlabs.org/soas/docs/customization-guide/ Customization Guide]. If you've an idea how to make them better, why don't you jump in and create a patch? Creating these nifty text files is simple - instructions live in the [[Sugar_on_a_Stick/Documentation_SOP|Documentation SOP]].
* Unofficial documentation for unsupported workarounds for [[Sugar on a Stick/Installation|installation]] and [[Sugar on a Stick/Sugar Clone|customization]] need to be edited, tested, and submitted for approval for official support. Check them out and leave comments and improvements; just jump in and edit the page.
* Interested in starting a deployment or helping a specific one (with anything from pedagogical design to technical support to funding logistics)? Introduce yourself on the deployment lists for [http://lists.sugarlabs.org/ Sugar Labs] and [http://lists.laptop.org/listinfo/ One Laptop Per Child] and we'll get you connected with some teachers on the ground.
* We're looking for some people to help us assemble tools for our support team to use. Email the [http://lists.sugarlabs.org/listinfo/soas Sugar on a Stick mailing list] if you're interested.
|}

=== Get Contributors ===

{|
|-
| style="border: 0; border-width: 0;" |

Contributors are the lifeblood of the Sugar on a Stick community - we work hard to bring a playful mindset of teaching, learning, and meaningful work to the children we aim to reach, and we aim to keep that mindset in our own work and community as well. Welcoming and teaching new contributors or all types, building the resources they need, and teaching them how to empower others in their turn is one of the most important things you can do; it is ''everyone's'' responsibility to help build our community, one person at a time.

Some things you can do:

* Edit this page and [[Joining Sugar on a Stick]]. Is there something we could do to make the "getting started" process easier? You don't have to ask permission to edit; just do it!
* Help us fill in our remaining task-starter pages: [[Sugar on a Stick release process]], [[How to fix an Activity bug]], [[How to fix a sugar-core bug]], and [[Sugar on a Stick deployment process]]/
* [http://openhatch.org/+projects/Sugar%20on%20a%20Stick Point out starter tasks on OpenHatch] - fill in questions and ideas for beginner jobs, and point newcomers towards them.
* [http://lists.sugarlabs.org/listinfo/soas Watch for introductions on the mailing list], and send welcome emails to new contributors (copy the list, so we can see what advice a newcomer has gotten so far).
* Hang out with us on IRC: [http://webchat.freenode.net?channels=sugar #sugar]. This is the place where users join when using [http://activities.sugarlabs.org/en-US/sugar/addon/4029 IRC Activity]. Help them past initial trouble and provide instant help!
* Add to our collection of otherwise tricky-to-find FAQs at [[The undiscoverable]].

| style="border: 0; border-width: 0; width: 200px;" |[[Image:Cici-netbook.jpg|200px|right|link=http://wiki.sugarlabs.org/go/Sugar_on_a_Stick]]
|}

== What's happening? ==

=== Meetings ===

We have weekly meetings on IRC - see [[Sugar on a Stick meetings]] for more information, including logs from past meetings. Attending a meeting is a great way for newcomers to get started.

=== Release schedule ===

Our release schedule is based on the [[fedora:Releases/Schedule | Fedora release schedule]]. The most recent release was v.3, code-named [[Mirabelle]], shipped on '''May 25, 2010''' and based on the Fedora 13 release schedule. The next Sugar on a Stick version will be based on the [[fedora:Releases/14/Schedule | Fedora 14 release schedule]].

{|border="1" cellspacing="0" width="100%"
|-
|rowspan="2"| 2010-05-25 || Sugar on a Stick v.3.0 Mirabelle released
|-
| Planning & Development Begins
|-
| 2010-07-27 || Feature Freeze (all features have to be ''approved'' and in a satisfying state.)
|-
| 2010-08-03 || Alpha Change deadline (all changes will have to be ''pushed'' by this time. pending submissions are insufficient.)
|-
| 2010-08-17 || Alpha Release
|-
| 2010-09-07 || Beta Change deadline (all changes will have to be ''pushed'' by this time. pending submissions are insufficient.)
|-
| 2010-09-21 || Beta Release
|-
| 2010-10-12 || Final Freeze (all changes have to be ''pushed''. no further changes permitted.)
|-
| 2010-10-14 || Compose Release Candidate
|-
| 2010-10-26 || Sugar on a Stick v.4.0 Final Release
|-
|}

=== Contributor stories ===

To find out what other contributors are doing, check out [http://planet.sugarlabs.org Planet Sugar Labs], where contributors to Sugar Labs and the Sugar on a Stick project aggregate their blogs. You can also [[Sysadmin/Planet syndication request|add your own blog to the Planet]].

== Related work ==

While the projects listed below are not part of Sugar on a Stick, we watch them closely and try to work with them when possible (or at least we're trying to learn!)

* [[Sugar_on_a_Stick/Installation/Variations#SugarCreationKit_DVD|SugarCreationKit DVD]] - Complete DVD containing all the resources required to create all 3 versions of Sugar-on-a-Stick without requiring Internet access
* Other [[:Category:Live USB|portable Sugar distributions]] - Live USB work based on other Linux distributions.

== Previous versions and subpage index ==
{{Show|Earlier versions of Sugar on a Stick can be reviewed at these pages: |{{Special:PrefixIndex/Sugar on a Stick/}}}}

Sugar on a Stick

2010-06-09T23:24:54Z

SeanDaly: /* Want to use Sugar on a Stick? */

<noinclude>
[[Category:Project]]
[[Category:Live USB]]
[[Category:Sugar on a Stick]]
</noinclude>

== What is Sugar on a Stick? ==

{|
|-
| style="border: 0; border-width: 0; width: 350px;" | [[File:SugaronastickMirabelle.png |300px|left|link=http://spins.fedoraproject.org/soas]]
| style="border: 0; border-width: 0;" | '''[[Sugar on a Stick]]''' is a [http://fedoraproject.org Fedora-based] [[wikipedia:Live USB|Live USB]] operating system featuring the award-winning [[What is Sugar?|Sugar Learning Platform]] and designed to fit on an ordinary USB thumbdrive ("stick"). Learn more about [http://spins.fedoraproject.org/soas/#home the project] and the [http://spins.fedoraproject.org/soas/#about principles] behind it at our [http://spins.fedoraproject.org/soas Spin webpage]. The most recent version is version 3, code-named '''[[Sugar on a Stick/Mirabelle|Mirabelle]]''' and was released on '''May 25, 2010.'''
|}

__TOC__

=== Want to use Sugar on a Stick? ===

{|
|-
| rowspan="3" style="border: 0; border-width: 0; width: 350px;" | [[File:Cici-maze.jpg |300px|left|link=http://spins.fedoraproject.org/soas]]
|-
|
|style="border: 0; border-width: 0;" align="center" | [[File:Download Mirabell.png|center|link=http://spins.fedoraproject.org/soas/#downloads]]
|-
|
|If you'd like to try out Sugar on a Stick, check out the [http://spins.fedoraproject.org/soas Sugar on a Stick Spin Page] - it's where our software downloads, installation and usage instructions, and support information lives.

After you've tried out Sugar on a Stick, we hope you'll come back here and join our community of contributors to help us make the next release even better.
|}

=== Want to contribute to Sugar on a Stick? ===

{|
|-
| style="border: 0; border-width: 0; width: 350px;" | [[File:SoaS-contributors.jpg |300px|left|link=Sugar_on_a_Stick]]
| style="border: 0; border-width: 0;" |
You're in the right place! This page is a contributors portal to the project, and contains everything you need to get started in becoming part of the Sugar on a Stick community.
|}

== New contributors start here! ==

Welcome! We're excited that you want to help us bring the Sugar Learning Platform to children around the world. No prior experience with computers or educational technology is required - in fact, we actively encourage a diversity of backgrounds, ages, and perspectives. See the [[Joining Sugar on a Stick]] page for instructions on how to get started. You may also want to check out the [http://openhatch.org/+projects/Sugar%20on%20a%20Stick Sugar on a Stick project page] on [http://openhatch.org OpenHatch], or attend one of our [[Sugar on a Stick meetings]].

== What can you do? ==

There are three main ways you can contribute to the Sugar on a Stick community. We work closely with our upstreams, [http://sugarlabs.org Sugar Labs] and [http://fedoraproject.org the Fedora Project].

=== Get Activities on the Stick ===

{|
|-
| style="border: 0; border-width: 0;" |

We're always looking for help with all aspects of the [[Sugar on a Stick release process]]. Here are a few things you can do:

* [[Sugar on a Stick QA|Test Sugar on a Stick]] and help us find bugs and think of ways the project could be better. When you find a bug or think of an enhancement, [[How to file a ticket|file a ticket!]] ''No technical experience required.''
* Help make it easier for others to test Sugar on a Stick by writing [[Sugar on a Stick QA#Test cases|test cases]]. ''If you've run a test case, you can write a test case.''
* [http://bugs.sugarlabs.org Fix a bug or add a feature] to an existing Activity, to [[Development Team|sugar-core itself]], or to [http://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=SoaS&order=priority&col=id&col=summary&col=status&col=type&col=priority&col=milestone&col=component Sugar on a Stick]. See [[How to fix an Activity bug]] and [[How to fix a sugar-core bug]] to get started. ''Basic Python programming skills - or the desire to learn - are all that's needed.''
* [https://fedoraproject.org/wiki/Sugar_Activities Package Sugar Activities for Fedora]. ''If you're a [https://fedoraproject.org/wiki/PackageMaintainers/Join Fedora Packager] or want to become one, help in this area is something we desperately need - it's a trickier thing to learn, but rewarding once you get the hang of it.''
* [[Sugar on a Stick release process#Review|Review Activities for inclusion in the build]] - check submitted Activities against our [[SoaS Activity Criteria]] and help us choose what gets included in the next release! ''No prior experience needed - we do reviews during our [[Sugar on a Stick meetings|weekly meetings]] and will teach you how.''
* Have an idea for a technical feature that isn't an Activity? Check out our [[Sugar on a Stick release process#Feature process|feature process]].

| style="border: 0; border-width: 0; width: 150px;" |[[Image:SoaS-netbook-1.jpg|150px|right|link=http://wiki.sugarlabs.org/go/Sugar_on_a_Stick_release_process]][[Image:SoaS-netbook-2.jpg|150px|right|link=http://wiki.sugarlabs.org/go/Sugar_on_a_Stick_release_process]][[Image:SoaS-netbook-3.jpg|150px|right|link=http://wiki.sugarlabs.org/go/Sugar_on_a_Stick_release_process]]
|}

=== Get Sticks into Schools ===

{|
|-
| style="border: 0; border-width: 0; width: 250px;" | [[File:Cici-stick.jpg |200px|left|link=Sugar_on_a_Stick_deployment_process]]
| style="border: 0; border-width: 0;" |
Deployments all over the world need many different types of help as they work through the [[Sugar on a Stick deployment process]] - we need help building resources for all deployments to use, supporting those deployments, and helping new deployments start, as well as gathering stories and feedback from deployments so that we can make the next version of Sugar on a Stick even better.

Some things you can do to help:

* ''"It's a wiki: Edit away!"'' is often said in open source communities. Almost nothing is set in stone and can't be undone. So if you've got ideas how to make instructions clearer and more accessible to our users, just go for it!
* We produce official documentation such as the [http://download.sugarlabs.org/soas/docs/creation-kit/ Creation Kit] or the [http://download.sugarlabs.org/soas/docs/customization-guide/ Customization Guide]. If you've an idea how to make them better, why don't you jump in and create a patch? Creating these nifty text files is simple - instructions live in the [[Sugar_on_a_Stick/Documentation_SOP|Documentation SOP]].
* Unofficial documentation for unsupported workarounds for [[Sugar on a Stick/Installation|installation]] and [[Sugar on a Stick/Sugar Clone|customization]] need to be edited, tested, and submitted for approval for official support. Check them out and leave comments and improvements; just jump in and edit the page.
* Interested in starting a deployment or helping a specific one (with anything from pedagogical design to technical support to funding logistics)? Introduce yourself on the deployment lists for [http://lists.sugarlabs.org/ Sugar Labs] and [http://lists.laptop.org/listinfo/ One Laptop Per Child] and we'll get you connected with some teachers on the ground.
* We're looking for some people to help us assemble tools for our support team to use. Email the [http://lists.sugarlabs.org/listinfo/soas Sugar on a Stick mailing list] if you're interested.
|}

=== Get Contributors ===

{|
|-
| style="border: 0; border-width: 0;" |

Contributors are the lifeblood of the Sugar on a Stick community - we work hard to bring a playful mindset of teaching, learning, and meaningful work to the children we aim to reach, and we aim to keep that mindset in our own work and community as well. Welcoming and teaching new contributors or all types, building the resources they need, and teaching them how to empower others in their turn is one of the most important things you can do; it is ''everyone's'' responsibility to help build our community, one person at a time.

Some things you can do:

* Edit this page and [[Joining Sugar on a Stick]]. Is there something we could do to make the "getting started" process easier? You don't have to ask permission to edit; just do it!
* Help us fill in our remaining task-starter pages: [[Sugar on a Stick release process]], [[How to fix an Activity bug]], [[How to fix a sugar-core bug]], and [[Sugar on a Stick deployment process]]/
* [http://openhatch.org/+projects/Sugar%20on%20a%20Stick Point out starter tasks on OpenHatch] - fill in questions and ideas for beginner jobs, and point newcomers towards them.
* [http://lists.sugarlabs.org/listinfo/soas Watch for introductions on the mailing list], and send welcome emails to new contributors (copy the list, so we can see what advice a newcomer has gotten so far).
* Hang out with us on IRC: [http://webchat.freenode.net?channels=sugar #sugar]. This is the place where users join when using [http://activities.sugarlabs.org/en-US/sugar/addon/4029 IRC Activity]. Help them past initial trouble and provide instant help!
* For Help on hard to find answers look at The undiscoverable features of sugar: [http://wiki.sugarlabs.org/go/The_undiscoverable]
| style="border: 0; border-width: 0; width: 200px;" |[[Image:Cici-netbook.jpg|200px|right|link=http://wiki.sugarlabs.org/go/Sugar_on_a_Stick]]
|}

== What's happening? ==

=== Meetings ===

We have weekly meetings on IRC - see [[Sugar on a Stick meetings]] for more information, including logs from past meetings. Attending a meeting is a great way for newcomers to get started.

=== Release schedule ===

Our release schedule is based on the [[fedora:Releases/Schedule | Fedora release schedule]]. The most recent release was v.3, code-named [[Mirabelle]], shipped on '''May 25, 2010''' and based on the Fedora 13 release schedule. The next Sugar on a Stick version will be based on the [[fedora:Releases/14/Schedule | Fedora 14 release schedule]].

{|border="1" cellspacing="0" width="100%"
|-
|rowspan="2"| 2010-05-25 || Sugar on a Stick v.3.0 Mirabelle released
|-
| Planning & Development Begins
|-
| 2010-07-27 || Feature Freeze (all features have to be ''approved'' and in a satisfying state.)
|-
| 2010-08-03 || Alpha Change deadline (all changes will have to be ''pushed'' by this time. pending submissions are insufficient.)
|-
| 2010-08-17 || Alpha Release
|-
| 2010-09-07 || Beta Change deadline (all changes will have to be ''pushed'' by this time. pending submissions are insufficient.)
|-
| 2010-09-21 || Beta Release
|-
| 2010-10-12 || Final Freeze (all changes have to be ''pushed''. no further changes permitted.)
|-
| 2010-10-14 || Compose Release Candidate
|-
| 2010-10-26 || Sugar on a Stick v.4.0 Final Release
|-
|}

=== Contributor stories ===

To find out what other contributors are doing, check out [http://planet.sugarlabs.org Planet Sugar Labs], where contributors to Sugar Labs and the Sugar on a Stick project aggregate their blogs. You can also [[Sysadmin/Planet syndication request|add your own blog to the Planet]].

== Related work ==

While the projects listed below are not part of Sugar on a Stick, we watch them closely and try to work with them when possible (or at least we're trying to learn!)

* [[Sugar_on_a_Stick/Installation/Variations#SugarCreationKit_DVD|SugarCreationKit DVD]] - Complete DVD containing all the resources required to create all 3 versions of Sugar-on-a-Stick without requiring Internet access
* Other [[:Category:Live USB|portable Sugar distributions]] - Live USB work based on other Linux distributions.

== Previous versions and subpage index ==
{{Show|Earlier versions of Sugar on a Stick can be reviewed at these pages: |{{Special:PrefixIndex/Sugar on a Stick/}}}}

Sugar on a Stick

2010-06-09T23:24:10Z

SeanDaly: /* What is Sugar on a Stick? */

<noinclude>
[[Category:Project]]
[[Category:Live USB]]
[[Category:Sugar on a Stick]]
</noinclude>

== What is Sugar on a Stick? ==

{|
|-
| style="border: 0; border-width: 0; width: 350px;" | [[File:SugaronastickMirabelle.png |300px|left|link=http://spins.fedoraproject.org/soas]]
| style="border: 0; border-width: 0;" | '''[[Sugar on a Stick]]''' is a [http://fedoraproject.org Fedora-based] [[wikipedia:Live USB|Live USB]] operating system featuring the award-winning [[What is Sugar?|Sugar Learning Platform]] and designed to fit on an ordinary USB thumbdrive ("stick"). Learn more about [http://spins.fedoraproject.org/soas/#home the project] and the [http://spins.fedoraproject.org/soas/#about principles] behind it at our [http://spins.fedoraproject.org/soas Spin webpage]. The most recent version is version 3, code-named '''[[Sugar on a Stick/Mirabelle|Mirabelle]]''' and was released on '''May 25, 2010.'''
|}

__TOC__

=== Want to use Sugar on a Stick? ===

{|
|-
| rowspan="3" style="border: 0; border-width: 0; width: 350px;" | [[File:Cici-maze.jpg |300px|left|link=http://spins.fedoraproject.org/soas]]
|-
|
|style="border: 0; border-width: 0;" align="center" | [[File:Download Mirabell.png|center|link=http://spins.fedoraproject.org/soas/#downloads]]
|-
|
|If you'd like to try out Sugar on a Stick, check out the main [http://spins.fedoraproject.org/soas Sugar on a Stick Spin Page] - it's where our software downloads, installation and usage instructions, and support information lives.

After you've tried out Sugar on a Stick, we hope you'll come back here and join our community of contributors to help us make the next release even better.
|}

=== Want to contribute to Sugar on a Stick? ===

{|
|-
| style="border: 0; border-width: 0; width: 350px;" | [[File:SoaS-contributors.jpg |300px|left|link=Sugar_on_a_Stick]]
| style="border: 0; border-width: 0;" |
You're in the right place! This page is a contributors portal to the project, and contains everything you need to get started in becoming part of the Sugar on a Stick community.
|}

== New contributors start here! ==

Welcome! We're excited that you want to help us bring the Sugar Learning Platform to children around the world. No prior experience with computers or educational technology is required - in fact, we actively encourage a diversity of backgrounds, ages, and perspectives. See the [[Joining Sugar on a Stick]] page for instructions on how to get started. You may also want to check out the [http://openhatch.org/+projects/Sugar%20on%20a%20Stick Sugar on a Stick project page] on [http://openhatch.org OpenHatch], or attend one of our [[Sugar on a Stick meetings]].

== What can you do? ==

There are three main ways you can contribute to the Sugar on a Stick community. We work closely with our upstreams, [http://sugarlabs.org Sugar Labs] and [http://fedoraproject.org the Fedora Project].

=== Get Activities on the Stick ===

{|
|-
| style="border: 0; border-width: 0;" |

We're always looking for help with all aspects of the [[Sugar on a Stick release process]]. Here are a few things you can do:

* [[Sugar on a Stick QA|Test Sugar on a Stick]] and help us find bugs and think of ways the project could be better. When you find a bug or think of an enhancement, [[How to file a ticket|file a ticket!]] ''No technical experience required.''
* Help make it easier for others to test Sugar on a Stick by writing [[Sugar on a Stick QA#Test cases|test cases]]. ''If you've run a test case, you can write a test case.''
* [http://bugs.sugarlabs.org Fix a bug or add a feature] to an existing Activity, to [[Development Team|sugar-core itself]], or to [http://bugs.sugarlabs.org/query?status=accepted&status=assigned&status=new&status=reopened&component=SoaS&order=priority&col=id&col=summary&col=status&col=type&col=priority&col=milestone&col=component Sugar on a Stick]. See [[How to fix an Activity bug]] and [[How to fix a sugar-core bug]] to get started. ''Basic Python programming skills - or the desire to learn - are all that's needed.''
* [https://fedoraproject.org/wiki/Sugar_Activities Package Sugar Activities for Fedora]. ''If you're a [https://fedoraproject.org/wiki/PackageMaintainers/Join Fedora Packager] or want to become one, help in this area is something we desperately need - it's a trickier thing to learn, but rewarding once you get the hang of it.''
* [[Sugar on a Stick release process#Review|Review Activities for inclusion in the build]] - check submitted Activities against our [[SoaS Activity Criteria]] and help us choose what gets included in the next release! ''No prior experience needed - we do reviews during our [[Sugar on a Stick meetings|weekly meetings]] and will teach you how.''
* Have an idea for a technical feature that isn't an Activity? Check out our [[Sugar on a Stick release process#Feature process|feature process]].

| style="border: 0; border-width: 0; width: 150px;" |[[Image:SoaS-netbook-1.jpg|150px|right|link=http://wiki.sugarlabs.org/go/Sugar_on_a_Stick_release_process]][[Image:SoaS-netbook-2.jpg|150px|right|link=http://wiki.sugarlabs.org/go/Sugar_on_a_Stick_release_process]][[Image:SoaS-netbook-3.jpg|150px|right|link=http://wiki.sugarlabs.org/go/Sugar_on_a_Stick_release_process]]
|}

=== Get Sticks into Schools ===

{|
|-
| style="border: 0; border-width: 0; width: 250px;" | [[File:Cici-stick.jpg |200px|left|link=Sugar_on_a_Stick_deployment_process]]
| style="border: 0; border-width: 0;" |
Deployments all over the world need many different types of help as they work through the [[Sugar on a Stick deployment process]] - we need help building resources for all deployments to use, supporting those deployments, and helping new deployments start, as well as gathering stories and feedback from deployments so that we can make the next version of Sugar on a Stick even better.

Some things you can do to help:

* ''"It's a wiki: Edit away!"'' is often said in open source communities. Almost nothing is set in stone and can't be undone. So if you've got ideas how to make instructions clearer and more accessible to our users, just go for it!
* We produce official documentation such as the [http://download.sugarlabs.org/soas/docs/creation-kit/ Creation Kit] or the [http://download.sugarlabs.org/soas/docs/customization-guide/ Customization Guide]. If you've an idea how to make them better, why don't you jump in and create a patch? Creating these nifty text files is simple - instructions live in the [[Sugar_on_a_Stick/Documentation_SOP|Documentation SOP]].
* Unofficial documentation for unsupported workarounds for [[Sugar on a Stick/Installation|installation]] and [[Sugar on a Stick/Sugar Clone|customization]] need to be edited, tested, and submitted for approval for official support. Check them out and leave comments and improvements; just jump in and edit the page.
* Interested in starting a deployment or helping a specific one (with anything from pedagogical design to technical support to funding logistics)? Introduce yourself on the deployment lists for [http://lists.sugarlabs.org/ Sugar Labs] and [http://lists.laptop.org/listinfo/ One Laptop Per Child] and we'll get you connected with some teachers on the ground.
* We're looking for some people to help us assemble tools for our support team to use. Email the [http://lists.sugarlabs.org/listinfo/soas Sugar on a Stick mailing list] if you're interested.
|}

=== Get Contributors ===

{|
|-
| style="border: 0; border-width: 0;" |

Contributors are the lifeblood of the Sugar on a Stick community - we work hard to bring a playful mindset of teaching, learning, and meaningful work to the children we aim to reach, and we aim to keep that mindset in our own work and community as well. Welcoming and teaching new contributors or all types, building the resources they need, and teaching them how to empower others in their turn is one of the most important things you can do; it is ''everyone's'' responsibility to help build our community, one person at a time.

Some things you can do:

* Edit this page and [[Joining Sugar on a Stick]]. Is there something we could do to make the "getting started" process easier? You don't have to ask permission to edit; just do it!
* Help us fill in our remaining task-starter pages: [[Sugar on a Stick release process]], [[How to fix an Activity bug]], [[How to fix a sugar-core bug]], and [[Sugar on a Stick deployment process]]/
* [http://openhatch.org/+projects/Sugar%20on%20a%20Stick Point out starter tasks on OpenHatch] - fill in questions and ideas for beginner jobs, and point newcomers towards them.
* [http://lists.sugarlabs.org/listinfo/soas Watch for introductions on the mailing list], and send welcome emails to new contributors (copy the list, so we can see what advice a newcomer has gotten so far).
* Hang out with us on IRC: [http://webchat.freenode.net?channels=sugar #sugar]. This is the place where users join when using [http://activities.sugarlabs.org/en-US/sugar/addon/4029 IRC Activity]. Help them past initial trouble and provide instant help!
* For Help on hard to find answers look at The undiscoverable features of sugar: [http://wiki.sugarlabs.org/go/The_undiscoverable]
| style="border: 0; border-width: 0; width: 200px;" |[[Image:Cici-netbook.jpg|200px|right|link=http://wiki.sugarlabs.org/go/Sugar_on_a_Stick]]
|}

== What's happening? ==

=== Meetings ===

We have weekly meetings on IRC - see [[Sugar on a Stick meetings]] for more information, including logs from past meetings. Attending a meeting is a great way for newcomers to get started.

=== Release schedule ===

Our release schedule is based on the [[fedora:Releases/Schedule | Fedora release schedule]]. The most recent release was v.3, code-named [[Mirabelle]], shipped on '''May 25, 2010''' and based on the Fedora 13 release schedule. The next Sugar on a Stick version will be based on the [[fedora:Releases/14/Schedule | Fedora 14 release schedule]].

{|border="1" cellspacing="0" width="100%"
|-
|rowspan="2"| 2010-05-25 || Sugar on a Stick v.3.0 Mirabelle released
|-
| Planning & Development Begins
|-
| 2010-07-27 || Feature Freeze (all features have to be ''approved'' and in a satisfying state.)
|-
| 2010-08-03 || Alpha Change deadline (all changes will have to be ''pushed'' by this time. pending submissions are insufficient.)
|-
| 2010-08-17 || Alpha Release
|-
| 2010-09-07 || Beta Change deadline (all changes will have to be ''pushed'' by this time. pending submissions are insufficient.)
|-
| 2010-09-21 || Beta Release
|-
| 2010-10-12 || Final Freeze (all changes have to be ''pushed''. no further changes permitted.)
|-
| 2010-10-14 || Compose Release Candidate
|-
| 2010-10-26 || Sugar on a Stick v.4.0 Final Release
|-
|}

=== Contributor stories ===

To find out what other contributors are doing, check out [http://planet.sugarlabs.org Planet Sugar Labs], where contributors to Sugar Labs and the Sugar on a Stick project aggregate their blogs. You can also [[Sysadmin/Planet syndication request|add your own blog to the Planet]].

== Related work ==

While the projects listed below are not part of Sugar on a Stick, we watch them closely and try to work with them when possible (or at least we're trying to learn!)

* [[Sugar_on_a_Stick/Installation/Variations#SugarCreationKit_DVD|SugarCreationKit DVD]] - Complete DVD containing all the resources required to create all 3 versions of Sugar-on-a-Stick without requiring Internet access
* Other [[:Category:Live USB|portable Sugar distributions]] - Live USB work based on other Linux distributions.

== Previous versions and subpage index ==
{{Show|Earlier versions of Sugar on a Stick can be reviewed at these pages: |{{Special:PrefixIndex/Sugar on a Stick/}}}}

Marketing Team/Meetings

2010-06-01T15:29:27Z

SeanDaly: /* Meeting Logs */

<noinclude>{{TeamHeader|Marketing Team}}</noinclude>
__NOTOC__
<div style="font-size: 1.0em; background: #daffd5; padding: 10px; border: 1px solid #cde7a8" align=left>The Marketing team will be holding regular weekly meetings on Tuesdays at 15 UTC on irc.freenode.net (channel: #sugar-meeting).
Please add to the agenda below and please join in with your ideas.

Hint: You can use an [http://www.timeanddate.com/worldclock/converter.html online time calculator] to convert from UTC to your local time zone or back. Help: [[Sugar_Labs/Communication channels#IRC.2C_Internet_Relay_Chat |Using IRC]]

The Sugar Labs Meetings calendar is available in a variety of formats at these links: [[File:XML.gif|link=http://www.google.com/calendar/feeds/h9cfuk10894em7a8moemquusmg%40group.calendar.google.com/public/basic]] [[File:ICal.gif|link=http://www.google.com/calendar/ical/h9cfuk10894em7a8moemquusmg%40group.calendar.google.com/public/basic.ics]] [[File:HTML.gif|link=http://www.google.com/calendar/embed?src=h9cfuk10894em7a8moemquusmg%40group.calendar.google.com&ctz=America/New_York]].
</div><br>

: Please consult the [http://lists.sugarlabs.org/archive/marketing/ Marketing list archives] and IRC meeting transcripts [[#Meeting Logs|below]] for the latest initiatives.

===[[Marketing_Team/Events|Events]]===
:See [[Marketing Team/Events]] for special Meeting Events.

===Upcoming Agenda for on-line Meeting===

===Previous Agenda===

== Meeting Logs ==

* [http://meeting.sugarlabs.org/sugar-meeting.log.20100601_1009.html 06-01-2010]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20100525_1009.html 05-25-2010]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20100504_1010.html 05-04-2010]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20100223_1003.html 02-23-2010]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20100216_1008.html 02-16-2010]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20100210_1005.html 02-10-2010]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20100127_1017.html 01-27-2010]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20100119_1010.html 01-19-2010]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20100112_1005.html 01-12-2010]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20091215_1003.html 12-15-2009]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20091201_1002.html 12-01-2009]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20091125_1003.html 11-25-2009]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20091111_1118.html 11-11-2009]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20091103_1002.html 11-03-2009]
* [http://lists.sugarlabs.org/archive/marketing/2009-October/002328.html 10-27-2009]
* [http://lists.sugarlabs.org/archive/marketing/2009-October/002269.html 10-20-2009]
* [http://lists.sugarlabs.org/archive/marketing/2009-October/002207.html 10-13-2009]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20091006_1006.html 10-06-2009]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20090929_1005.html 09-29-2009]
* [http://lists.sugarlabs.org/archive/marketing/2009-September/002086.html 09-22-2009]
* [http://lists.sugarlabs.org/archive/marketing/2009-September/002060.html 09-15-2009]
* [http://lists.sugarlabs.org/archive/marketing/2009-September/002021.html 09-08-2009]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20090630_1105.html 06-30-2009]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20090623_1119.html 06-23-2009]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20090616_1104.html 06-16-2009]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20090609_1104.html 06-09-2009]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20090602_1106.html 06-02-2009]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20090526_1108.html 05-26-2009]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20090519_1105.html 05-19-2009]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20090512_1103.html 05-12-2009]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20090505_1101.html 05-05-2009]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20090429_1101.html 04-29-2009]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20090414_1101.html 04-14-2009]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20090407_1002.html 04-07-2009]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20090324_1102.html 03-24-2009]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20090317_1102.html 03-17-2009]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20090313_1205.html 03-13-2009]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20090310_1100.html 03-10-2009]
* [[Marketing Team/Meetings/03-03-2009]]
* [[Marketing Team/Meetings/02-25-2009]]
* [[Marketing Team/Meetings/02-10-2009]]
* [[Marketing Team/Meetings/12-23-2008]]
* [[Marketing Team/Meetings/12-16-2008]]
* [[Marketing Team/Meetings/12-9-2008]]
* [[Marketing Team/Meetings/12-2-2008]]

[[Category:Marketing Team]]
[[Category:Meetings]]

Marketing Team/Meetings

2010-05-25T17:04:56Z

SeanDaly: /* Meeting Logs */

<noinclude>{{TeamHeader|Marketing Team}}</noinclude>
__NOTOC__
<div style="font-size: 1.0em; background: #daffd5; padding: 10px; border: 1px solid #cde7a8" align=left>The Marketing team will be holding regular weekly meetings on Tuesdays at 15 UTC on irc.freenode.net (channel: #sugar-meeting).
Please add to the agenda below and please join in with your ideas.

Hint: You can use an [http://www.timeanddate.com/worldclock/converter.html online time calculator] to convert from UTC to your local time zone or back. Help: [[Sugar_Labs/Communication channels#IRC.2C_Internet_Relay_Chat |Using IRC]]

The Sugar Labs Meetings calendar is available in a variety of formats at these links: [[File:XML.gif|link=http://www.google.com/calendar/feeds/h9cfuk10894em7a8moemquusmg%40group.calendar.google.com/public/basic]] [[File:ICal.gif|link=http://www.google.com/calendar/ical/h9cfuk10894em7a8moemquusmg%40group.calendar.google.com/public/basic.ics]] [[File:HTML.gif|link=http://www.google.com/calendar/embed?src=h9cfuk10894em7a8moemquusmg%40group.calendar.google.com&ctz=America/New_York]].
</div><br>

: Please consult the [http://lists.sugarlabs.org/archive/marketing/ Marketing list archives] and IRC meeting transcripts [[#Meeting Logs|below]] for the latest initiatives.

===[[Marketing_Team/Events|Events]]===
:See [[Marketing Team/Events]] for special Meeting Events.

===Upcoming Agenda for on-line Meeting===

===Previous Agenda===

== Meeting Logs ==

* [http://meeting.sugarlabs.org/sugar-meeting.log.20100525_1009.html 05-25-2010]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20100504_1010.html 05-04-2010]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20100223_1003.html 02-23-2010]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20100216_1008.html 02-16-2010]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20100210_1005.html 02-10-2010]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20100127_1017.html 01-27-2010]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20100119_1010.html 01-19-2010]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20100112_1005.html 01-12-2010]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20091215_1003.html 12-15-2009]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20091201_1002.html 12-01-2009]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20091125_1003.html 11-25-2009]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20091111_1118.html 11-11-2009]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20091103_1002.html 11-03-2009]
* [http://lists.sugarlabs.org/archive/marketing/2009-October/002328.html 10-27-2009]
* [http://lists.sugarlabs.org/archive/marketing/2009-October/002269.html 10-20-2009]
* [http://lists.sugarlabs.org/archive/marketing/2009-October/002207.html 10-13-2009]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20091006_1006.html 10-06-2009]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20090929_1005.html 09-29-2009]
* [http://lists.sugarlabs.org/archive/marketing/2009-September/002086.html 09-22-2009]
* [http://lists.sugarlabs.org/archive/marketing/2009-September/002060.html 09-15-2009]
* [http://lists.sugarlabs.org/archive/marketing/2009-September/002021.html 09-08-2009]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20090630_1105.html 06-30-2009]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20090623_1119.html 06-23-2009]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20090616_1104.html 06-16-2009]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20090609_1104.html 06-09-2009]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20090602_1106.html 06-02-2009]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20090526_1108.html 05-26-2009]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20090519_1105.html 05-19-2009]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20090512_1103.html 05-12-2009]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20090505_1101.html 05-05-2009]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20090429_1101.html 04-29-2009]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20090414_1101.html 04-14-2009]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20090407_1002.html 04-07-2009]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20090324_1102.html 03-24-2009]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20090317_1102.html 03-17-2009]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20090313_1205.html 03-13-2009]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20090310_1100.html 03-10-2009]
* [[Marketing Team/Meetings/03-03-2009]]
* [[Marketing Team/Meetings/02-25-2009]]
* [[Marketing Team/Meetings/02-10-2009]]
* [[Marketing Team/Meetings/12-23-2008]]
* [[Marketing Team/Meetings/12-16-2008]]
* [[Marketing Team/Meetings/12-9-2008]]
* [[Marketing Team/Meetings/12-2-2008]]

[[Category:Marketing Team]]
[[Category:Meetings]]

Sugar on a Stick

2010-05-25T09:56:33Z

SeanDaly:

<noinclude>{{ Translations | [[Sugar_on_a_Stick|english]] | [[Sugar_on_a_Stick/lang-es|español]] | [[Sugar_on_a_Stick/lang-fr|français]]}}{{TeamHeader|Sugar on a Stick|home=Project Home|xbgColor=ffe792|join_label=Get Involved}}
[[Category:Project]]
[[Category:Live USB]]</noinclude>

{{/Pancake page}}

{{TOCright}}
Please Note: Sugar on a Stick v2 Blueberry will be superseded by the Mirabelle release as of 25 May 2010!

== Introduction ==
Sugar on a Stick (SoaS) enables children to reclaim computers. SoaS aims to make it easy for children, parents, or local deployers to provide each student with a small device (USB stick or thumbdrive) that can starts any computer with the student's personalized Sugar environment. We would like to see [[Sugar]]'s presence, journal, and clarity principles usable on any machine — at school, at home, and anywhere there is a suitable computing device. Sugar on a Stick starts up ("boots") the host computer directly, without touching the hard disk; however, it may be necessary to adjust the computer's settings to look for a USB device before the hard disk.

{| border="0"
|[[Image:Soas-1.png|180px|link=0.86/Notes]]
|
'''What exactly is on the Stick?''': The Sugar Learning Platform and Sugar Activities for children over Fedora GNU/Linux. Taking advantage of [[wikipedia:Live USB|Live USB]] technology, it's possible to store everything you need to run Sugar on a single, [[wikipedia:USB flash drive|USB flash memory stick]]. Compressed file systems are used to save space, and [[LiveOS image|persistent overlay]] files are used to save changes to the system and the learner's work. See our [[Sugar on a Stick/Resources| '''resources page''']] to learn about different component configurations we are designing to offer the option to use [[wikipedia:Virtual machine|virtual machines]] on existing computers to host Sugar from a portable Stick and save the [[Human Interface Guidelines/The Laptop Experience/The Journal|Sugar Journal]] (the learner's work) and personal settings on the Stick for use at another workstation - for example, a computer in the home.
|}

== Project Principles ==
* ''Portability'' - One's Sugar environment, saved Activities, and Journal are available wherever one has access to suitable computing devices, at home, school, library, clubhouse in order to permit resumable, extended, and deep exploration of concepts and phenomena.
* ''Customizability'' - Deployments, as well as users, can build their own SoaS easily.
* ''Deployability'' - SoaS is easy to deploy, both for individual sticks and for multiple-instances deployed in computer labs.

'''Would you like to help?''' ...this is entirely a volunteer-run effort. Please [[/Getting Involved| get involved]]!

== Getting Sugar on a Stick ==

* [[Sugar on a Stick/Mirabelle]] is nearing its release on 25 May 2010.<br>It is quite stable, and may be downloaded from the [[File:Soas-mirabelle-logo.png|120px|link=http://alt.fedoraproject.org/pub/alt/nightly-composes/soas/]] [http://alt.fedoraproject.org/pub/alt/nightly-composes/soas/ Nightly builds] site.<br>Please see the instructions at [[Sugar on a Stick/Beta]]. The release candidate images will be released on the [http://alt.fedoraproject.org/pub/alt/stage/13.RC2/Spins/ Fedora F13 Spins RC images] location once they are built.
* [[Sugar on a Stick/Blueberry]] was released on 03 December 2009.
* [[Sugar on a Stick/Strawberry]] was released on 22 June 2009.

Developers and testers can help us debug Beta test builds. See [[Sugar on a Stick/Beta]].

Please let us know how it goes. You can always [[Sugar on a Stick/Contacts| get in touch]] with us!

== E-Books ==

For licensing reasons, Sugar on a Stick does not contain e-books with NC (noncommercial) licensing. To get teachers and parents started with finding, downloading, and reading e-books with Sugar, see our [[Sugar on a Stick/E-Books| E-Books page]].

== More information ==

For general questions, please see the [[/FAQ|Frequently Asked Questions (FAQ) page for Sugar on a Stick]]. You can learn more from [http://www.xconomy.com/boston/2009/02/05/sugar-beyond-the-xo-laptop-walter-bender-on-olpc-sucrose-084-and-sugar-on-a-stick/ Walter Bender's interview with Xconomy], [http://www.olpcnews.com/software/sugar/sugar_on_a_stick_netbooks.html Wayan Vota's video] and [http://www.flickr.com/photos/curiouslee/sets/72157613785006745/ Mike Lee's pictures].

== Problems? ==

Please file bug reports in [http://bugs.sugarlabs.org The Sugar on a Stick bug tracker].
* Here are [[BugSquad/Bug Report|some instructions for using the bug tracker]].
* This link will [https://bugs.sugarlabs.org/query?component=SoaS&status=accepted&status=assigned&status=new&status=reopened query the database for all tickets designated with the SoaS component/tag].
* You must [https://bugs.sugarlabs.org/register register an account] to enter new bugs.
* This link will take you to a [http://bugs.sugarlabs.org/newticket?component=SoaS new bug/ticket form for SoaS] (once you are logged in).

Sugar developers can often be found in IRC at irc.freenode.net, channel #sugar

Or, send e-mail to feedback AT sugarlabs DOT org.

See the '''Get Help!''' section of the [[Sugar_on_a_Stick/Blueberry|Blueberry release notes page]] for further information.

== Related work ==

See these other [[:Category:Live USB|portable Sugar distributions]] that share some of these goals.

<div class="NavFrame collapsed"><div class="NavHead">'''Subpage index''' </div><div class="NavContent">{{Special:PrefixIndex/{{PAGENAME}}/}}</div></div>

Marketing Team/Meetings

2010-05-11T14:05:02Z

SeanDaly: /* Meeting Logs */

<noinclude>{{TeamHeader|Marketing Team}}</noinclude>
__NOTOC__
<div style="font-size: 1.0em; background: #daffd5; padding: 10px; border: 1px solid #cde7a8" align=left>The Marketing team will be holding regular weekly meetings on Tuesdays at 15 UTC on irc.freenode.net (channel: #sugar-meeting).
Please add to the agenda below and please join in with your ideas.

Hint: You can use an [http://www.timeanddate.com/worldclock/converter.html online time calculator] to convert from UTC to your local time zone or back. Help: [[Sugar_Labs/Communication channels#IRC.2C_Internet_Relay_Chat |Using IRC]]

The Sugar Labs Meetings calendar is available in a variety of formats at these links: [[File:XML.gif|link=http://www.google.com/calendar/feeds/h9cfuk10894em7a8moemquusmg%40group.calendar.google.com/public/basic]] [[File:ICal.gif|link=http://www.google.com/calendar/ical/h9cfuk10894em7a8moemquusmg%40group.calendar.google.com/public/basic.ics]] [[File:HTML.gif|link=http://www.google.com/calendar/embed?src=h9cfuk10894em7a8moemquusmg%40group.calendar.google.com&ctz=America/New_York]].
</div><br>

: Please consult the [http://lists.sugarlabs.org/archive/marketing/ Marketing list archives] and IRC meeting transcripts [[#Meeting Logs|below]] for the latest initiatives.

===[[Marketing_Team/Events|Events]]===
:See [[Marketing Team/Events]] for special Meeting Events.

===Upcoming Agenda for on-line Meeting===

===Previous Agenda===

== Meeting Logs ==

* [http://meeting.sugarlabs.org/sugar-meeting.log.20100504_1010.html 05-04-2010]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20100223_1003.html 02-23-2010]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20100216_1008.html 02-16-2010]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20100210_1005.html 02-10-2010]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20100127_1017.html 01-27-2010]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20100119_1010.html 01-19-2010]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20100112_1005.html 01-12-2010]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20091215_1003.html 12-15-2009]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20091201_1002.html 12-01-2009]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20091125_1003.html 11-25-2009]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20091111_1118.html 11-11-2009]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20091103_1002.html 11-03-2009]
* [http://lists.sugarlabs.org/archive/marketing/2009-October/002328.html 10-27-2009]
* [http://lists.sugarlabs.org/archive/marketing/2009-October/002269.html 10-20-2009]
* [http://lists.sugarlabs.org/archive/marketing/2009-October/002207.html 10-13-2009]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20091006_1006.html 10-06-2009]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20090929_1005.html 09-29-2009]
* [http://lists.sugarlabs.org/archive/marketing/2009-September/002086.html 09-22-2009]
* [http://lists.sugarlabs.org/archive/marketing/2009-September/002060.html 09-15-2009]
* [http://lists.sugarlabs.org/archive/marketing/2009-September/002021.html 09-08-2009]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20090630_1105.html 06-30-2009]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20090623_1119.html 06-23-2009]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20090616_1104.html 06-16-2009]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20090609_1104.html 06-09-2009]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20090602_1106.html 06-02-2009]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20090526_1108.html 05-26-2009]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20090519_1105.html 05-19-2009]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20090512_1103.html 05-12-2009]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20090505_1101.html 05-05-2009]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20090429_1101.html 04-29-2009]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20090414_1101.html 04-14-2009]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20090407_1002.html 04-07-2009]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20090324_1102.html 03-24-2009]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20090317_1102.html 03-17-2009]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20090313_1205.html 03-13-2009]
* [http://meeting.sugarlabs.org/sugar-meeting.log.20090310_1100.html 03-10-2009]
* [[Marketing Team/Meetings/03-03-2009]]
* [[Marketing Team/Meetings/02-25-2009]]
* [[Marketing Team/Meetings/02-10-2009]]
* [[Marketing Team/Meetings/12-23-2008]]
* [[Marketing Team/Meetings/12-16-2008]]
* [[Marketing Team/Meetings/12-9-2008]]
* [[Marketing Team/Meetings/12-2-2008]]

[[Category:Marketing Team]]
[[Category:Meetings]]

Talk:Trademark

2010-05-07T15:28:25Z

SeanDaly: /* Sugar Trademark Policy */

==Sugar Labs association/organization conflated with Sugar software==
:2a & b, and elsewhere suggest that the full name of our product is 'Sugar Labs' rather than Sugar or some form of Sugar. Yes, 5e suggests that Sugar is short for Sugar Labs. This would be a new practice. Why conflate the terms?

:Why not register [[What is Sugar?|Sugar]] as a mark for our software, and [[Sugar Labs]] for our association?

::--[[User:FGrose|FGrose]] 23:18, 7 July 2009 (UTC)
==Logo==
: In paragraph 1, "(our trademark registration application for the logo is still pending)", is a separate statement, right? Sugar Labs is already registered, but the logos (colors and typeface) are pending registration, no? If so, this would be more clear as a separate sentence in the introduction, as it is currently too closely associated with the Sugar Labs name.
::--[[User:FGrose|FGrose]] 23:45, 7 July 2009 (UTC)
::AFAIK, the logo is not registered. It seemed that the name "Sugar Labs" was enough. --[[User:Walter|Walter]] 00:00, 8 July 2009 (UTC)

==Section 5a==

:It has been suggested that we certify distributions as "Sugar on a Stick". "Otherwise nothing stops anyone from creating a lousy version which hardly works and calls it Sugar on a Stick Peanut Butter release, etc."

:Comments? --[[User:Walter|Walter]] 22:23, 7 July 2009 (UTC)

::We have our hands full verifying and testing our own release. Our best defense is focusing on making the best release and so being able to market it as such. --[[User:FGrose|FGrose]] 23:28, 7 July 2009 (UTC)
::I agree. It adds yet another thing to worry about that can better be handled downstream. --[[User:Walter|Walter]] 23:34, 7 July 2009 (UTC)

::: This line of judgement needs revisiting. "our own release" means Strawberry? If SL lets anyone use "Sugar on a Stick", then it's probably giving up the rights to the trademark "Sugar on a Stick", right?

==[[Sugar Labs/Legal/Logo and trademark policy]]==
: This older page needs updating. --[[User:FGrose|FGrose]] 18:31, 4 September 2009 (UTC)
{{Merge|Sugar Labs/Legal/Logo and trademark_policy}}

== Sugar on a Stick Guidelines ==

I am herewith proposing the following changes to the section 5a. This has been derived from Fedora's [http://fedoraproject.org/wiki/Legal/TrademarkGuidelines trademark guidelines] and might need to be adjusted to cover more cases, as listed in those guidelines. By referring to Sugar on a Stick, the following draft means the project [[Sugar_on_a_Stick| located]] and [http://git.sugarlabs.org/projects/soas hosted] here.

* You '''may''' use the term ''Sugar on a Stick'' whenever referring to the official Sugar on a Stick product and its releases, as well as when distributing ''unmodified'' copies of it.
** However, this usage '''must not''' imply any endorsement by Sugar Labs or the Sugar on a Stick project, unless this is case and an appropriate agreement has been reached.
* You '''may''' modify Sugar on a Stick and create ''remixes'' of it.
** However, when distributing or selling this modified version, you '''must not''' call it Sugar on a Stick.
** When not exposing the resulting product to the public, you '''may''' still call it Sugar on a Stick, though. A deployment might adjust Sugar on a Stick for its needs and still say it deployed Sugar on a Stick, as long as the modified version is not distributed publicly.

== substantially unmodified ==

We discuss examples of "substantially unmodified" in [[Sugar Labs/Governance/Trademark|Section 2]] of the policy: "including but not limited to: the enabling or disabling of certain features by default, changes required for compatibility with a particular operating system distribution, or the inclusion of bug-fix patches." But it would be instructive to give some examples of changes that would not qualify as substantially unmodified: including but not limited to adding of non-free drivers. (We need to build consensus around this issue.) --[[User:Walter|Walter]] 20:44, 18 December 2009 (UTC)

== How to make modifications ==
There is a discussion [[Features/Feature_SoaS_customization|here]] about making a systemic process for most trivial modifications. --[[User:Walter|Walter]] 20:44, 18 December 2009 (UTC)

==Sugar Trademark Policy==

DRAFT: 7 May 2010

The purpose of this policy is to ensure that the identity, provenance, and free and open-source nature of Sugar Labs<sup>®</sup> remain clear '''to the public. This is in keeping with''' our objective to spread the use of the Sugar Learning Platform while protecting our trademarks. It is our intention to be liberal and responsive in the enforcement of our trademarks: '''we want our Marks to be widely used to represent our learning mission to the public, but we also need to ensure clarity regarding the relationship between Sugar Labs and the individual or organization using our Marks in order to both protect Sugar Labs and the public.''' As part of our marketing effort to make Sugar better known, we have developed a label program with the objective of simplifying and streamlining permission to use Sugar Labs marks by projects and businesses. '''We encourage you to contact us at trademark at sugarlabs.org if you have any questions about this policy or the label program.''' Throughout this document, the word "Marks" refers to the Sugar Labs name and logo, individually or together. Note that Section 5 provides guidelines for other marks used by Sugar Labs. Sugar Labs is a member project of the Software Freedom Conservancy, which is the holder of the [http://tess2.uspto.gov/bin/showfield?f=doc&state=4006:qq173k.3.1 registered mark].

Guidelines for using the Marks

1.

The first or most prominent mention of the name should be immediately followed by a symbol for registered trademark: "®" or "(r)". For example: "Sugar Labs<sup>®</sup>".

This requirement is waived in all contexts where such marks are not normally included: email, on-line discussion, non-graphical advertisements (when permitted), and academic papers. We encourage the use of the symbol whenever possible, but recognize that many non-commercial and informal uses will omit it.

2.

:a.

:You may use the Sugar Labs Marks without prior written permission for the following purposes (subject to the other sections):

:To refer to the Sugar Labs software in substantially unmodified form. "Substantially unmodified" means built from the source code provided by the Sugar Labs project, possibly with minor modifications including but not limited to: the enabling or disabling of certain features by default, translations into other languages, changes required for compatibility with a particular operating system distribution, or the inclusion of bug-fix patches). All such minor modifications must be released under an [[Oversight_Board/Meeting_Minutes-2009-12-11#Non-FOSS_content|approved license]].

:To identify Sugar Labs software as a distinct component of a software offering. Please note however that we prefer that Sugar be described as a "learning environment", not a "desktop", and its programs as "Activities", not "applications".

:b.

:You may use the Sugar Labs Marks with prior written permission for the following purposes (subject to the other sections):

:If you are producing a new product which is based on Sugar Labs software but which has more substantial changes than those described in the previous paragraph, you may refer to your product as "derived from", "based on", or "a derivative of" a Sugar Labs mark.

:Please refer to our [[Sugar_Labs/Governance/Transactions#License_request|License Request]] procedure for details regarding obtaining a license to use the Sugar Marks.

:c.

:You do not need written permission to refer to the Sugar Labs project itself, its products, or its protocols.

3.

You may use the Sugar Labs Marks as part of the name of a product designed to work with Sugar Labs, so long as the name as a whole (via its other components) clearly and unambiguously distinguishes the product from Sugar Labs software itself, and the general presentation of the product does not imply any official association or identity with Sugar Labs. Because it would be awkward to attach a trademark symbol to a portion of a larger name whose other portions might themselves be trademarked, the requirement to display the symbol is waived for this circumstance.

4.

You may not use the Marks in the following ways:

:a.

:In any way likely to cause confusion as to the identity of the Sugar Labs project, the provenance of its software, or the software's license (the Sugar Labs marks should be secondary in advertising and promotional materials, including graphics on websites, etc.);

:b.

:In any way that indicates a greater degree of association between you and the Sugar Labs project than actually exists;

:c.

:In any way that implies a designated successor to Sugar Labs (e.g., "Sugar Labs++" is not permitted).

:d.

:In a way that indicates that Sugar Labs [[Oversight_Board/Meeting_Minutes-2009-12-18|favors one distribution, platform, product, etc. over another]].

5.

Sugar Labs also uses the following other marks:

:a.

:Sugar on a Stick:
::The "Sugar on a Stick" name and mark is associated with a specific [[Sugar on a Stick|Sugar Labs liveUSB project]]. You may produce and distribute Sugar Labs software on a USB key or other device, but you are required choose a different name to avoid confusion.

:b.

:Sugar Labs Partner:
::"Sugar Labs Partner" should only be used to refer to a person or entity that is officially affiliated with the Sugar Labs project. Sugar Labs is happy to designate partners, so please [[#Contact information|contact us]] if you are interested in becoming a Sugar Labs Partner.

:c.

:Sugar Ready:
::"Sugar Ready" may be used to refer to software certified by Sugar Labs to run on top of an official version of Sugar Labs, please [[#Contact information|contact us]] if you are interested in receiving a certification.

:d.

:Sugar Learning Platform
::"Sugar Learning Platform" should be used to refer to the software created by Sugar Labs and should be used under the same guidelines as per Sections 2 and 3 of this policy.

:e.

:Sugar
::We sometimes use this term as a shortened way to refer to software and other things created by Sugar Labs. Please use this policy as guidance for use of these terms as well and [[#Contact information|contact us]] if you are uncertain.

:f.

:local Sugar Lab:
::We have affiliated local and regional Sugar Labs that are referred to Sugar Labs <Region Name>, e.g., Sugar Labs Colombia. Sugar Labs is happy to designate local lab partners, so please [[#Contact information|contact us]] if you are interested in establishing a local Sugar Lab.

6.

You may create and sell merchandise using the Sugar Labs name and logo without additional permission provided that you use only unmodified graphics from the logo page on the Sugar Labs website. Please [[#Contact information|contact us]] if you would like to sell any other merchandise containing Sugar Labs Marks. This section is subject to the provisions contained in Sections 2 and 3 of this policy.

7.

The Software Freedom Conservancy reserves the sole right to:

:a.

:Determine compliance with this policy;

:b.

:Modify this policy in ways consistent with its mission of protecting the public;

:c.

:Grant exceptions to this policy, of any kind and for any reason whatsoever, other clauses notwithstanding.

===Contact information===

If you have questions about using the Marks, or if you think you should be able to use the Marks for any purpose not allowed by this policy and would like permission for that use, please contact Sugar Labs by emailing [trademark@sugarlabs.org] '''or by writing to [[Sugar_Labs/Contacts#Mail|Sugar Labs c/o Software Freedom Conservancy, 1995 BROADWAY FL 17, NEW YORK NY 10023-5882 USA]].'''

===Usage examples===

Usage examples can be found [[Sugar Labs/Governance/Trademark/Guidelines|on the Guidelines page]].

= Trademark case studies =

As the next step in working on the trademark, we are preparing case studies. The below text is taken from the [[Trademark case studies]] page - please [http://wiki.sugarlabs.org/index.php?title=Trademark_case_studies&action=edit edit that page directly] to contribute.

{{:Trademark case studies}}

Talk:Trademark

2010-05-07T15:00:36Z

SeanDaly: /* Sugar Trademark Policy */

==Sugar Labs association/organization conflated with Sugar software==
:2a & b, and elsewhere suggest that the full name of our product is 'Sugar Labs' rather than Sugar or some form of Sugar. Yes, 5e suggests that Sugar is short for Sugar Labs. This would be a new practice. Why conflate the terms?

:Why not register [[What is Sugar?|Sugar]] as a mark for our software, and [[Sugar Labs]] for our association?

::--[[User:FGrose|FGrose]] 23:18, 7 July 2009 (UTC)
==Logo==
: In paragraph 1, "(our trademark registration application for the logo is still pending)", is a separate statement, right? Sugar Labs is already registered, but the logos (colors and typeface) are pending registration, no? If so, this would be more clear as a separate sentence in the introduction, as it is currently too closely associated with the Sugar Labs name.
::--[[User:FGrose|FGrose]] 23:45, 7 July 2009 (UTC)
::AFAIK, the logo is not registered. It seemed that the name "Sugar Labs" was enough. --[[User:Walter|Walter]] 00:00, 8 July 2009 (UTC)

==Section 5a==

:It has been suggested that we certify distributions as "Sugar on a Stick". "Otherwise nothing stops anyone from creating a lousy version which hardly works and calls it Sugar on a Stick Peanut Butter release, etc."

:Comments? --[[User:Walter|Walter]] 22:23, 7 July 2009 (UTC)

::We have our hands full verifying and testing our own release. Our best defense is focusing on making the best release and so being able to market it as such. --[[User:FGrose|FGrose]] 23:28, 7 July 2009 (UTC)
::I agree. It adds yet another thing to worry about that can better be handled downstream. --[[User:Walter|Walter]] 23:34, 7 July 2009 (UTC)

::: This line of judgement needs revisiting. "our own release" means Strawberry? If SL lets anyone use "Sugar on a Stick", then it's probably giving up the rights to the trademark "Sugar on a Stick", right?

==[[Sugar Labs/Legal/Logo and trademark policy]]==
: This older page needs updating. --[[User:FGrose|FGrose]] 18:31, 4 September 2009 (UTC)
{{Merge|Sugar Labs/Legal/Logo and trademark_policy}}

== Sugar on a Stick Guidelines ==

I am herewith proposing the following changes to the section 5a. This has been derived from Fedora's [http://fedoraproject.org/wiki/Legal/TrademarkGuidelines trademark guidelines] and might need to be adjusted to cover more cases, as listed in those guidelines. By referring to Sugar on a Stick, the following draft means the project [[Sugar_on_a_Stick| located]] and [http://git.sugarlabs.org/projects/soas hosted] here.

* You '''may''' use the term ''Sugar on a Stick'' whenever referring to the official Sugar on a Stick product and its releases, as well as when distributing ''unmodified'' copies of it.
** However, this usage '''must not''' imply any endorsement by Sugar Labs or the Sugar on a Stick project, unless this is case and an appropriate agreement has been reached.
* You '''may''' modify Sugar on a Stick and create ''remixes'' of it.
** However, when distributing or selling this modified version, you '''must not''' call it Sugar on a Stick.
** When not exposing the resulting product to the public, you '''may''' still call it Sugar on a Stick, though. A deployment might adjust Sugar on a Stick for its needs and still say it deployed Sugar on a Stick, as long as the modified version is not distributed publicly.

== substantially unmodified ==

We discuss examples of "substantially unmodified" in [[Sugar Labs/Governance/Trademark|Section 2]] of the policy: "including but not limited to: the enabling or disabling of certain features by default, changes required for compatibility with a particular operating system distribution, or the inclusion of bug-fix patches." But it would be instructive to give some examples of changes that would not qualify as substantially unmodified: including but not limited to adding of non-free drivers. (We need to build consensus around this issue.) --[[User:Walter|Walter]] 20:44, 18 December 2009 (UTC)

== How to make modifications ==
There is a discussion [[Features/Feature_SoaS_customization|here]] about making a systemic process for most trivial modifications. --[[User:Walter|Walter]] 20:44, 18 December 2009 (UTC)

==Sugar Trademark Policy==

DRAFT: 7 May 2010

The purpose of this policy is to ensure that the identity, provenance, and free and open-source nature of Sugar Labs<sup>®</sup> remain clear '''to the public. This is in keeping with''' our objective to spread the use of the Sugar Learning Platform while protecting our trademarks. It is our intention to be liberal and responsive in the enforcement of our trademarks: '''we want our Marks to be widely used to represent our learning mission to the public, but we also need to ensure clarity regarding the relationship between Sugar Labs and the individual or organization using our Marks in order to both protect Sugar Labs and the public.''' As part of our marketing effort to make Sugar better known, we have developed a label program with the objective of simplifying and streamlining permission to use Sugar Labs marks by projects and businesses. '''We encourage you to contact us at trademark at sugarlabs.org if you have any questions about this policy or the label program.''' Throughout this document, the word "Marks" refers to the Sugar Labs name and logo, individually or together. Note that Section 5 provides guidelines for other marks used by Sugar Labs. Sugar Labs is a member project of the Software Freedom Conservancy, which is the holder of the [http://tess2.uspto.gov/bin/showfield?f=doc&state=4006:qq173k.3.1 registered mark].

Guidelines for using the Marks

1.

The first or most prominent mention of the name should be immediately followed by a symbol for registered trademark: "®" or "(r)". For example: "Sugar Labs<sup>®</sup>".

This requirement is waived in all contexts where such marks are not normally included: email, on-line discussion, non-graphical advertisements (when permitted), and academic papers. We encourage the use of the symbol whenever possible, but recognize that many non-commercial and informal uses will omit it.

2.

:a.

:You may use the Sugar Labs Marks without prior written permission for the following purposes (subject to the other sections):

:To refer to the Sugar Labs software in substantially unmodified form. "Substantially unmodified" means built from the source code provided by the Sugar Labs project, possibly with minor modifications including but not limited to: the enabling or disabling of certain features by default, translations into other languages, changes required for compatibility with a particular operating system distribution, or the inclusion of bug-fix patches). All such minor modifications must be released under an [[Oversight_Board/Meeting_Minutes-2009-12-11#Non-FOSS_content|approved license]].

:To identify Sugar Labs software as a distinct component of a software offering. For example, "MyDistro, sweetened by Sugar" or other "<product>, <joined with> Sugar" language would be a use that does not require explicit written permission.

:b.

:You may use the Sugar Labs Marks with prior written permission for the following purposes (subject to the other sections):

:If you are producing a new product which is based on Sugar Labs software but which has more substantial changes than those described in the previous paragraph, you may refer to your product as "derived from", "based on", or "a derivative of" a Sugar Labs mark.

:Please refer to our [[http://wiki.sugarlabs.org/go/Sugar_Labs/Governance/Transactions#License_request|License Request]] procedure for details regarding obtaining a license to use the Sugar Marks.

:c.

:You do not need written permission to refer to the Sugar Labs project itself, its products, or its protocols.

3.

You may use the Sugar Labs Marks as part of the name of a product designed to work with Sugar Labs, so long as the name as a whole (via its other components) clearly and unambiguously distinguishes the product from Sugar Labs software itself, and the general presentation of the product does not imply any official association or identity with Sugar Labs. Because it would be awkward to attach a trademark symbol to a portion of a larger name whose other portions might themselves be trademarked, the requirement to display the symbol is waived for this circumstance.

4.

You may not use the Marks in the following ways:

:a.

:In any way likely to cause confusion as to the identity of the Sugar Labs project, the provenance of its software, or the software's license (the Sugar Labs marks should be secondary in advertising and promotional materials, including graphics on websites, etc.);

:b.

:In any way that indicates a greater degree of association between you and the Sugar Labs project than actually exists;

:c.

:In any way that implies a designated successor to Sugar Labs (e.g., "Sugar Labs++" is not permitted).

:d.

:In a way that indicates that Sugar Labs [[Oversight_Board/Meeting_Minutes-2009-12-18|favors one distribution, platform, product, etc. over another]].

5.

Sugar Labs also uses the following other marks:

:a.

:Sugar on a Stick:
::The "Sugar on a Stick" name and mark is associated with a specific [[Sugar on a Stick|Sugar Labs liveUSB project]]. You may produce and distribute Sugar Labs software on a USB key or other device, but you are required choose a different name to avoid confusion.

:b.

:Sugar Labs Partner:
::"Sugar Labs Partner" should only be used to refer to a person or entity that is officially affiliated with the Sugar Labs project. Sugar Labs is happy to designate partners, so please [[#Contact information|contact us]] if you are interested in becoming a Sugar Labs Partner.

:c.

:Sugar Ready:
::"Sugar Ready" may be used to refer to software certified by Sugar Labs to run on top of an official version of Sugar Labs, please [[#Contact information|contact us]] if you are interested in receiving a certification.

:d.

:Sugar Learning Platform
::"Sugar Learning Platform" should be used to refer to the software created by Sugar Labs and should be used under the same guidelines as per Sections 2 and 3 of this policy.

:e.

:Sugar
::We sometimes use this term as a shortened way to refer to software and other things created by Sugar Labs. Please use this policy as guidance for use of these terms as well and [[#Contact information|contact us]] if you are uncertain.

:f.

:local Sugar Lab:
::We have affiliated local and regional Sugar Labs that are referred to Sugar Labs <Region Name>, e.g., Sugar Labs Colombia. Sugar Labs is happy to designate local lab partners, so please [[#Contact information|contact us]] if you are interested in establishing a local Sugar Lab.

6.

You may create and sell merchandise using the Sugar Labs name and logo without additional permission provided that you use only unmodified graphics from the logo page on the Sugar Labs website. Please [[#Contact information|contact us]] if you would like to sell any other merchandise containing Sugar Labs Marks. This section is subject to the provisions contained in Sections 2 and 3 of this policy.

7.

The Software Freedom Conservancy reserves the sole right to:

:a.

:Determine compliance with this policy;

:b.

:Modify this policy in ways consistent with its mission of protecting the public;

:c.

:Grant exceptions to this policy, of any kind and for any reason whatsoever, other clauses notwithstanding.

===Contact information===

If you have questions about using the Marks, or if you think you should be able to use the Marks for any purpose not allowed by this policy and would like permission for that use, please contact Sugar Labs by emailing [trademark@sugarlabs.org] '''or by writing to [[Sugar_Labs/Contacts#Mail|Sugar Labs c/o Software Freedom Conservancy, 1995 BROADWAY FL 17, NEW YORK NY 10023-5882 USA]].'''

===Usage examples===

Usage examples can be found [[Sugar Labs/Governance/Trademark/Guidelines|on the Guidelines page]].

= Trademark case studies =

As the next step in working on the trademark, we are preparing case studies. The below text is taken from the [[Trademark case studies]] page - please [http://wiki.sugarlabs.org/index.php?title=Trademark_case_studies&action=edit edit that page directly] to contribute.

{{:Trademark case studies}}

Talk:Trademark

2010-05-07T14:57:27Z

SeanDaly: /* Sugar Trademark Policy */

==Sugar Labs association/organization conflated with Sugar software==
:2a & b, and elsewhere suggest that the full name of our product is 'Sugar Labs' rather than Sugar or some form of Sugar. Yes, 5e suggests that Sugar is short for Sugar Labs. This would be a new practice. Why conflate the terms?

:Why not register [[What is Sugar?|Sugar]] as a mark for our software, and [[Sugar Labs]] for our association?

::--[[User:FGrose|FGrose]] 23:18, 7 July 2009 (UTC)
==Logo==
: In paragraph 1, "(our trademark registration application for the logo is still pending)", is a separate statement, right? Sugar Labs is already registered, but the logos (colors and typeface) are pending registration, no? If so, this would be more clear as a separate sentence in the introduction, as it is currently too closely associated with the Sugar Labs name.
::--[[User:FGrose|FGrose]] 23:45, 7 July 2009 (UTC)
::AFAIK, the logo is not registered. It seemed that the name "Sugar Labs" was enough. --[[User:Walter|Walter]] 00:00, 8 July 2009 (UTC)

==Section 5a==

:It has been suggested that we certify distributions as "Sugar on a Stick". "Otherwise nothing stops anyone from creating a lousy version which hardly works and calls it Sugar on a Stick Peanut Butter release, etc."

:Comments? --[[User:Walter|Walter]] 22:23, 7 July 2009 (UTC)

::We have our hands full verifying and testing our own release. Our best defense is focusing on making the best release and so being able to market it as such. --[[User:FGrose|FGrose]] 23:28, 7 July 2009 (UTC)
::I agree. It adds yet another thing to worry about that can better be handled downstream. --[[User:Walter|Walter]] 23:34, 7 July 2009 (UTC)

::: This line of judgement needs revisiting. "our own release" means Strawberry? If SL lets anyone use "Sugar on a Stick", then it's probably giving up the rights to the trademark "Sugar on a Stick", right?

==[[Sugar Labs/Legal/Logo and trademark policy]]==
: This older page needs updating. --[[User:FGrose|FGrose]] 18:31, 4 September 2009 (UTC)
{{Merge|Sugar Labs/Legal/Logo and trademark_policy}}

== Sugar on a Stick Guidelines ==

I am herewith proposing the following changes to the section 5a. This has been derived from Fedora's [http://fedoraproject.org/wiki/Legal/TrademarkGuidelines trademark guidelines] and might need to be adjusted to cover more cases, as listed in those guidelines. By referring to Sugar on a Stick, the following draft means the project [[Sugar_on_a_Stick| located]] and [http://git.sugarlabs.org/projects/soas hosted] here.

* You '''may''' use the term ''Sugar on a Stick'' whenever referring to the official Sugar on a Stick product and its releases, as well as when distributing ''unmodified'' copies of it.
** However, this usage '''must not''' imply any endorsement by Sugar Labs or the Sugar on a Stick project, unless this is case and an appropriate agreement has been reached.
* You '''may''' modify Sugar on a Stick and create ''remixes'' of it.
** However, when distributing or selling this modified version, you '''must not''' call it Sugar on a Stick.
** When not exposing the resulting product to the public, you '''may''' still call it Sugar on a Stick, though. A deployment might adjust Sugar on a Stick for its needs and still say it deployed Sugar on a Stick, as long as the modified version is not distributed publicly.

== substantially unmodified ==

We discuss examples of "substantially unmodified" in [[Sugar Labs/Governance/Trademark|Section 2]] of the policy: "including but not limited to: the enabling or disabling of certain features by default, changes required for compatibility with a particular operating system distribution, or the inclusion of bug-fix patches." But it would be instructive to give some examples of changes that would not qualify as substantially unmodified: including but not limited to adding of non-free drivers. (We need to build consensus around this issue.) --[[User:Walter|Walter]] 20:44, 18 December 2009 (UTC)

== How to make modifications ==
There is a discussion [[Features/Feature_SoaS_customization|here]] about making a systemic process for most trivial modifications. --[[User:Walter|Walter]] 20:44, 18 December 2009 (UTC)

==Sugar Trademark Policy==

DRAFT: 7 May 2010

The purpose of this policy is to ensure that the identity, provenance, and free and open-source nature of Sugar Labs<sup>®</sup> remain clear '''to the public. This is in keeping with''' our objective to spread the use of the Sugar Learning Platform while protecting our trademarks. It is our intention to be liberal and responsive in the enforcement of our trademarks: '''we want our Marks to be widely used to represent our learning mission to the public, but we also need to ensure clarity regarding the relationship between Sugar Labs and the individual or organization using our Marks in order to both protect Sugar Labs and the public.''' As part of our marketing effort to make Sugar better known, we have developed a label program with the objective of simplifying and streamlining permission to use Sugar Labs marks by projects and businesses. '''We encourage you to contact us at trademark at sugarlabs.org if you have any questions about this policy or the label program.''' Throughout this document, the word "Marks" refers to the Sugar Labs name and logo, individually or together. Note that Section 5 provides guidelines for other marks used by Sugar Labs. Sugar Labs is a member project of the Software Freedom Conservancy, which is the holder of the [http://tess2.uspto.gov/bin/showfield?f=doc&state=4006:qq173k.3.1 registered mark].

Guidelines for using the Marks

1.

The first or most prominent mention of the name should be immediately followed by a symbol for registered trademark: "®" or "(r)". For example: "Sugar Labs<sup>®</sup>".

This requirement is waived in all contexts where such marks are not normally included: email, on-line discussion, non-graphical advertisements (when permitted), and academic papers. We encourage the use of the symbol whenever possible, but recognize that many non-commercial and informal uses will omit it.

2.

:a.

:You may use the Sugar Labs Marks without prior written permission for the following purposes (subject to the other sections):

:To refer to the Sugar Labs software in substantially unmodified form. "Substantially unmodified" means built from the source code provided by the Sugar Labs project, possibly with minor modifications including but not limited to: the enabling or disabling of certain features by default, translations into other languages, changes required for compatibility with a particular operating system distribution, or the inclusion of bug-fix patches). All such minor modifications must be released under an [[Oversight_Board/Meeting_Minutes-2009-12-11#Non-FOSS_content|approved license]].

:To identify Sugar Labs software as a distinct component of a software offering. For example, "MyDistro, sweetened by Sugar" or other "<product>, <joined with> Sugar" language would be a use that does not require explicit written permission.

:b.

:You may use the Sugar Labs Marks with prior written permission for the following purposes (subject to the other sections):

:If you are producing a new product which is based on Sugar Labs software but which has more substantial changes than those described in the previous paragraph, you may refer to your product as "derived from", "based on", or "a derivative of" a Sugar Labs mark.

:Please refer to our [[http://wiki.sugarlabs.org/go/Sugar_Labs/Governance/Transactions#License_request|License Request]] procedure for details regarding obtaining a license to use the Sugar Marks.

:c.

:You do not need written permission to refer to the Sugar Labs project itself, its products, or its protocols.

3.

You may use the Sugar Labs Marks as part of the name of a product designed to work with Sugar Labs, so long as the name as a whole (via its other components) clearly and unambiguously distinguishes the product from Sugar Labs software itself, and the general presentation of the product does not imply any official association or identity with Sugar Labs. Because it would be awkward to attach a trademark symbol to a portion of a larger name whose other portions might themselves be trademarked, the requirement to display the symbol is waived for this circumstance.

4.

You may not use the Marks in the following ways:

:a.

:In any way likely to cause confusion as to the identity of the Sugar Labs project, the provenance of its software, or the software's license (the Sugar Labs Marks should be secondary in advertising materials, including graphics on websites, etc.);

:b.

:In any way that indicates a greater degree of association between you and the Sugar Labs project than actually exists;

:c.

:In any way that implies a designated successor to Sugar Labs (e.g., "Sugar Labs++" is not permitted).

:d.

:In a way that indicates that Sugar Labs [[Oversight_Board/Meeting_Minutes-2009-12-18|favors one distribution, platform, product, etc. over another]].

5.

Sugar Labs also uses the following other marks:

:a.

:Sugar on a Stick:
::The "Sugar on a Stick" name and mark is associated with a specific [[Sugar on a Stick|Sugar Labs liveUSB project]]. You may produce and distribute Sugar Labs software on a USB key or other device, but you are required choose a different name to avoid confusion.

:b.

:Sugar Labs Partner:
::"Sugar Labs Partner" should only be used to refer to a person or entity that is officially affiliated with the Sugar Labs project. Sugar Labs is happy to designate partners, so please [[#Contact information|contact us]] if you are interested in becoming a Sugar Labs Partner.

:c.

:Sugar Ready:
::"Sugar Ready" may be used to refer to software certified by Sugar Labs to run on top of an official version of Sugar Labs, please [[#Contact information|contact us]] if you are interested in receiving a certification.

:d.

:Sugar Learning Platform
::"Sugar Learning Platform" should be used to refer to the software created by Sugar Labs and should be used under the same guidelines as per Sections 2 and 3 of this policy.

:e.

:Sugar
::We sometimes use this term as a shortened way to refer to software and other things created by Sugar Labs. Please use this policy as guidance for use of these terms as well and [[#Contact information|contact us]] if you are uncertain.

:f.

:local Sugar Lab:
::We have affiliated local and regional Sugar Labs that are referred to Sugar Labs <Region Name>, e.g., Sugar Labs Colombia. Sugar Labs is happy to designate local lab partners, so please [[#Contact information|contact us]] if you are interested in establishing a local Sugar Lab.

6.

You may create and sell merchandise using the Sugar Labs name and logo without additional permission provided that you use only unmodified graphics from the logo page on the Sugar Labs website. Please [[#Contact information|contact us]] if you would like to sell any other merchandise containing Sugar Labs Marks. This section is subject to the provisions contained in Sections 2 and 3 of this policy.

7.

The Software Freedom Conservancy reserves the sole right to:

:a.

:Determine compliance with this policy;

:b.

:Modify this policy in ways consistent with its mission of protecting the public;

:c.

:Grant exceptions to this policy, of any kind and for any reason whatsoever, other clauses notwithstanding.

===Contact information===

If you have questions about using the Marks, or if you think you should be able to use the Marks for any purpose not allowed by this policy and would like permission for that use, please contact Sugar Labs by emailing [trademark@sugarlabs.org] '''or by writing to [[Sugar_Labs/Contacts#Mail|Sugar Labs c/o Software Freedom Conservancy, 1995 BROADWAY FL 17, NEW YORK NY 10023-5882 USA]].'''

===Usage examples===

Usage examples can be found [[Sugar Labs/Governance/Trademark/Guidelines|on the Guidelines page]].

= Trademark case studies =

As the next step in working on the trademark, we are preparing case studies. The below text is taken from the [[Trademark case studies]] page - please [http://wiki.sugarlabs.org/index.php?title=Trademark_case_studies&action=edit edit that page directly] to contribute.

{{:Trademark case studies}}

Talk:Trademark

2010-05-07T14:56:57Z

SeanDaly: /* Sugar Trademark Policy */

==Sugar Labs association/organization conflated with Sugar software==
:2a & b, and elsewhere suggest that the full name of our product is 'Sugar Labs' rather than Sugar or some form of Sugar. Yes, 5e suggests that Sugar is short for Sugar Labs. This would be a new practice. Why conflate the terms?

:Why not register [[What is Sugar?|Sugar]] as a mark for our software, and [[Sugar Labs]] for our association?

::--[[User:FGrose|FGrose]] 23:18, 7 July 2009 (UTC)
==Logo==
: In paragraph 1, "(our trademark registration application for the logo is still pending)", is a separate statement, right? Sugar Labs is already registered, but the logos (colors and typeface) are pending registration, no? If so, this would be more clear as a separate sentence in the introduction, as it is currently too closely associated with the Sugar Labs name.
::--[[User:FGrose|FGrose]] 23:45, 7 July 2009 (UTC)
::AFAIK, the logo is not registered. It seemed that the name "Sugar Labs" was enough. --[[User:Walter|Walter]] 00:00, 8 July 2009 (UTC)

==Section 5a==

:It has been suggested that we certify distributions as "Sugar on a Stick". "Otherwise nothing stops anyone from creating a lousy version which hardly works and calls it Sugar on a Stick Peanut Butter release, etc."

:Comments? --[[User:Walter|Walter]] 22:23, 7 July 2009 (UTC)

::We have our hands full verifying and testing our own release. Our best defense is focusing on making the best release and so being able to market it as such. --[[User:FGrose|FGrose]] 23:28, 7 July 2009 (UTC)
::I agree. It adds yet another thing to worry about that can better be handled downstream. --[[User:Walter|Walter]] 23:34, 7 July 2009 (UTC)

::: This line of judgement needs revisiting. "our own release" means Strawberry? If SL lets anyone use "Sugar on a Stick", then it's probably giving up the rights to the trademark "Sugar on a Stick", right?

==[[Sugar Labs/Legal/Logo and trademark policy]]==
: This older page needs updating. --[[User:FGrose|FGrose]] 18:31, 4 September 2009 (UTC)
{{Merge|Sugar Labs/Legal/Logo and trademark_policy}}

== Sugar on a Stick Guidelines ==

I am herewith proposing the following changes to the section 5a. This has been derived from Fedora's [http://fedoraproject.org/wiki/Legal/TrademarkGuidelines trademark guidelines] and might need to be adjusted to cover more cases, as listed in those guidelines. By referring to Sugar on a Stick, the following draft means the project [[Sugar_on_a_Stick| located]] and [http://git.sugarlabs.org/projects/soas hosted] here.

* You '''may''' use the term ''Sugar on a Stick'' whenever referring to the official Sugar on a Stick product and its releases, as well as when distributing ''unmodified'' copies of it.
** However, this usage '''must not''' imply any endorsement by Sugar Labs or the Sugar on a Stick project, unless this is case and an appropriate agreement has been reached.
* You '''may''' modify Sugar on a Stick and create ''remixes'' of it.
** However, when distributing or selling this modified version, you '''must not''' call it Sugar on a Stick.
** When not exposing the resulting product to the public, you '''may''' still call it Sugar on a Stick, though. A deployment might adjust Sugar on a Stick for its needs and still say it deployed Sugar on a Stick, as long as the modified version is not distributed publicly.

== substantially unmodified ==

We discuss examples of "substantially unmodified" in [[Sugar Labs/Governance/Trademark|Section 2]] of the policy: "including but not limited to: the enabling or disabling of certain features by default, changes required for compatibility with a particular operating system distribution, or the inclusion of bug-fix patches." But it would be instructive to give some examples of changes that would not qualify as substantially unmodified: including but not limited to adding of non-free drivers. (We need to build consensus around this issue.) --[[User:Walter|Walter]] 20:44, 18 December 2009 (UTC)

== How to make modifications ==
There is a discussion [[Features/Feature_SoaS_customization|here]] about making a systemic process for most trivial modifications. --[[User:Walter|Walter]] 20:44, 18 December 2009 (UTC)

==Sugar Trademark Policy==

DRAFT: 7 May 2010

The purpose of this policy is to ensure that the identity, provenance, and free and open-source nature of Sugar Labs<sup>®</sup> remain clear '''to the public. This is in keeping with''' our objective to spread the use of the Sugar Learning Platform while protecting our trademarks. It is our intention to be liberal and responsive in the enforcement of our trademarks: '''we want our Marks to be widely used to represent our learning mission to the public, but we also need to ensure clarity regarding the relationship between Sugar Labs and the individual or organization using our Marks in order to both protect Sugar Labs and the public.''' As part of our marketing effort to make Sugar better known, we have developed a label program with the objective of simplifying and streamlining permission to use Sugar Labs marks by projects and businesses. '''We encourage you to contact us at trademark@sugarlabs.org if you have any questions about this policy or the label program.''' Throughout this document, the word "Marks" refers to the Sugar Labs name and logo, individually or together. Note that Section 5 provides guidelines for other marks used by Sugar Labs. Sugar Labs is a member project of the Software Freedom Conservancy, which is the holder of the [http://tess2.uspto.gov/bin/showfield?f=doc&state=4006:qq173k.3.1 registered mark].

Guidelines for using the Marks

1.

The first or most prominent mention of the name should be immediately followed by a symbol for registered trademark: "®" or "(r)". For example: "Sugar Labs<sup>®</sup>".

This requirement is waived in all contexts where such marks are not normally included: email, on-line discussion, non-graphical advertisements (when permitted), and academic papers. We encourage the use of the symbol whenever possible, but recognize that many non-commercial and informal uses will omit it.

2.

:a.

:You may use the Sugar Labs Marks without prior written permission for the following purposes (subject to the other sections):

:To refer to the Sugar Labs software in substantially unmodified form. "Substantially unmodified" means built from the source code provided by the Sugar Labs project, possibly with minor modifications including but not limited to: the enabling or disabling of certain features by default, translations into other languages, changes required for compatibility with a particular operating system distribution, or the inclusion of bug-fix patches). All such minor modifications must be released under an [[Oversight_Board/Meeting_Minutes-2009-12-11#Non-FOSS_content|approved license]].

:To identify Sugar Labs software as a distinct component of a software offering. For example, "MyDistro, sweetened by Sugar" or other "<product>, <joined with> Sugar" language would be a use that does not require explicit written permission.

:b.

:You may use the Sugar Labs Marks with prior written permission for the following purposes (subject to the other sections):

:If you are producing a new product which is based on Sugar Labs software but which has more substantial changes than those described in the previous paragraph, you may refer to your product as "derived from", "based on", or "a derivative of" a Sugar Labs mark.

:Please refer to our [[http://wiki.sugarlabs.org/go/Sugar_Labs/Governance/Transactions#License_request|License Request]] procedure for details regarding obtaining a license to use the Sugar Marks.

:c.

:You do not need written permission to refer to the Sugar Labs project itself, its products, or its protocols.

3.

You may use the Sugar Labs Marks as part of the name of a product designed to work with Sugar Labs, so long as the name as a whole (via its other components) clearly and unambiguously distinguishes the product from Sugar Labs software itself, and the general presentation of the product does not imply any official association or identity with Sugar Labs. Because it would be awkward to attach a trademark symbol to a portion of a larger name whose other portions might themselves be trademarked, the requirement to display the symbol is waived for this circumstance.

4.

You may not use the Marks in the following ways:

:a.

:In any way likely to cause confusion as to the identity of the Sugar Labs project, the provenance of its software, or the software's license (the Sugar Labs Marks should be secondary in advertising materials, including graphics on websites, etc.);

:b.

:In any way that indicates a greater degree of association between you and the Sugar Labs project than actually exists;

:c.

:In any way that implies a designated successor to Sugar Labs (e.g., "Sugar Labs++" is not permitted).

:d.

:In a way that indicates that Sugar Labs [[Oversight_Board/Meeting_Minutes-2009-12-18|favors one distribution, platform, product, etc. over another]].

5.

Sugar Labs also uses the following other marks:

:a.

:Sugar on a Stick:
::The "Sugar on a Stick" name and mark is associated with a specific [[Sugar on a Stick|Sugar Labs liveUSB project]]. You may produce and distribute Sugar Labs software on a USB key or other device, but you are required choose a different name to avoid confusion.

:b.

:Sugar Labs Partner:
::"Sugar Labs Partner" should only be used to refer to a person or entity that is officially affiliated with the Sugar Labs project. Sugar Labs is happy to designate partners, so please [[#Contact information|contact us]] if you are interested in becoming a Sugar Labs Partner.

:c.

:Sugar Ready:
::"Sugar Ready" may be used to refer to software certified by Sugar Labs to run on top of an official version of Sugar Labs, please [[#Contact information|contact us]] if you are interested in receiving a certification.

:d.

:Sugar Learning Platform
::"Sugar Learning Platform" should be used to refer to the software created by Sugar Labs and should be used under the same guidelines as per Sections 2 and 3 of this policy.

:e.

:Sugar
::We sometimes use this term as a shortened way to refer to software and other things created by Sugar Labs. Please use this policy as guidance for use of these terms as well and [[#Contact information|contact us]] if you are uncertain.

:f.

:local Sugar Lab:
::We have affiliated local and regional Sugar Labs that are referred to Sugar Labs <Region Name>, e.g., Sugar Labs Colombia. Sugar Labs is happy to designate local lab partners, so please [[#Contact information|contact us]] if you are interested in establishing a local Sugar Lab.

6.

You may create and sell merchandise using the Sugar Labs name and logo without additional permission provided that you use only unmodified graphics from the logo page on the Sugar Labs website. Please [[#Contact information|contact us]] if you would like to sell any other merchandise containing Sugar Labs Marks. This section is subject to the provisions contained in Sections 2 and 3 of this policy.

7.

The Software Freedom Conservancy reserves the sole right to:

:a.

:Determine compliance with this policy;

:b.

:Modify this policy in ways consistent with its mission of protecting the public;

:c.

:Grant exceptions to this policy, of any kind and for any reason whatsoever, other clauses notwithstanding.

===Contact information===

If you have questions about using the Marks, or if you think you should be able to use the Marks for any purpose not allowed by this policy and would like permission for that use, please contact Sugar Labs by emailing [trademark@sugarlabs.org] '''or by writing to [[Sugar_Labs/Contacts#Mail|Sugar Labs c/o Software Freedom Conservancy, 1995 BROADWAY FL 17, NEW YORK NY 10023-5882 USA]].'''

===Usage examples===

Usage examples can be found [[Sugar Labs/Governance/Trademark/Guidelines|on the Guidelines page]].

= Trademark case studies =

As the next step in working on the trademark, we are preparing case studies. The below text is taken from the [[Trademark case studies]] page - please [http://wiki.sugarlabs.org/index.php?title=Trademark_case_studies&action=edit edit that page directly] to contribute.

{{:Trademark case studies}}

Talk:Trademark

2010-05-07T14:54:58Z

SeanDaly: /* Sugar Trademark Policy */

==Sugar Labs association/organization conflated with Sugar software==
:2a & b, and elsewhere suggest that the full name of our product is 'Sugar Labs' rather than Sugar or some form of Sugar. Yes, 5e suggests that Sugar is short for Sugar Labs. This would be a new practice. Why conflate the terms?

:Why not register [[What is Sugar?|Sugar]] as a mark for our software, and [[Sugar Labs]] for our association?

::--[[User:FGrose|FGrose]] 23:18, 7 July 2009 (UTC)
==Logo==
: In paragraph 1, "(our trademark registration application for the logo is still pending)", is a separate statement, right? Sugar Labs is already registered, but the logos (colors and typeface) are pending registration, no? If so, this would be more clear as a separate sentence in the introduction, as it is currently too closely associated with the Sugar Labs name.
::--[[User:FGrose|FGrose]] 23:45, 7 July 2009 (UTC)
::AFAIK, the logo is not registered. It seemed that the name "Sugar Labs" was enough. --[[User:Walter|Walter]] 00:00, 8 July 2009 (UTC)

==Section 5a==

:It has been suggested that we certify distributions as "Sugar on a Stick". "Otherwise nothing stops anyone from creating a lousy version which hardly works and calls it Sugar on a Stick Peanut Butter release, etc."

:Comments? --[[User:Walter|Walter]] 22:23, 7 July 2009 (UTC)

::We have our hands full verifying and testing our own release. Our best defense is focusing on making the best release and so being able to market it as such. --[[User:FGrose|FGrose]] 23:28, 7 July 2009 (UTC)
::I agree. It adds yet another thing to worry about that can better be handled downstream. --[[User:Walter|Walter]] 23:34, 7 July 2009 (UTC)

::: This line of judgement needs revisiting. "our own release" means Strawberry? If SL lets anyone use "Sugar on a Stick", then it's probably giving up the rights to the trademark "Sugar on a Stick", right?

==[[Sugar Labs/Legal/Logo and trademark policy]]==
: This older page needs updating. --[[User:FGrose|FGrose]] 18:31, 4 September 2009 (UTC)
{{Merge|Sugar Labs/Legal/Logo and trademark_policy}}

== Sugar on a Stick Guidelines ==

I am herewith proposing the following changes to the section 5a. This has been derived from Fedora's [http://fedoraproject.org/wiki/Legal/TrademarkGuidelines trademark guidelines] and might need to be adjusted to cover more cases, as listed in those guidelines. By referring to Sugar on a Stick, the following draft means the project [[Sugar_on_a_Stick| located]] and [http://git.sugarlabs.org/projects/soas hosted] here.

* You '''may''' use the term ''Sugar on a Stick'' whenever referring to the official Sugar on a Stick product and its releases, as well as when distributing ''unmodified'' copies of it.
** However, this usage '''must not''' imply any endorsement by Sugar Labs or the Sugar on a Stick project, unless this is case and an appropriate agreement has been reached.
* You '''may''' modify Sugar on a Stick and create ''remixes'' of it.
** However, when distributing or selling this modified version, you '''must not''' call it Sugar on a Stick.
** When not exposing the resulting product to the public, you '''may''' still call it Sugar on a Stick, though. A deployment might adjust Sugar on a Stick for its needs and still say it deployed Sugar on a Stick, as long as the modified version is not distributed publicly.

== substantially unmodified ==

We discuss examples of "substantially unmodified" in [[Sugar Labs/Governance/Trademark|Section 2]] of the policy: "including but not limited to: the enabling or disabling of certain features by default, changes required for compatibility with a particular operating system distribution, or the inclusion of bug-fix patches." But it would be instructive to give some examples of changes that would not qualify as substantially unmodified: including but not limited to adding of non-free drivers. (We need to build consensus around this issue.) --[[User:Walter|Walter]] 20:44, 18 December 2009 (UTC)

== How to make modifications ==
There is a discussion [[Features/Feature_SoaS_customization|here]] about making a systemic process for most trivial modifications. --[[User:Walter|Walter]] 20:44, 18 December 2009 (UTC)

==Sugar Trademark Policy==

DRAFT: 7 May 2010

The purpose of this policy is to ensure that the identity, provenance, and free and open-source nature of Sugar Labs<sup>®</sup> remain clear '''to the public. This is in keeping with''' our objective to spread the use of the Sugar Learning Platform while protecting our trademarks. It is our intention to be liberal and responsive in the enforcement of our trademarks: '''we want our Marks to be widely used to represent our learning mission to the public, but we also need to ensure clarity regarding the relationship between Sugar Labs and the individual or organization using our Marks in order to both protect Sugar Labs and the public.''' As part of our marketing effort to make Sugar better known, we have developed a label program with the objective of simplifying and streamlining permission to use Sugar Labs marks by projects and businesses. '''We encourage you to contact us if you have any questions about this policy.''' Throughout this document, the word "Marks" refers to the Sugar Labs name and logo, individually or together. Note that Section 5 provides guidelines for other marks used by Sugar Labs. Sugar Labs is a member project of the Software Freedom Conservancy, which is the holder of the [http://tess2.uspto.gov/bin/showfield?f=doc&state=4006:qq173k.3.1 registered mark].

Guidelines for using the Marks

1.

The first or most prominent mention of the name should be immediately followed by a symbol for registered trademark: "®" or "(r)". For example: "Sugar Labs<sup>®</sup>".

This requirement is waived in all contexts where such marks are not normally included: email, on-line discussion, non-graphical advertisements (when permitted), and academic papers. We encourage the use of the symbol whenever possible, but recognize that many non-commercial and informal uses will omit it.

2.

:a.

:You may use the Sugar Labs Marks without prior written permission for the following purposes (subject to the other sections):

:To refer to the Sugar Labs software in substantially unmodified form. "Substantially unmodified" means built from the source code provided by the Sugar Labs project, possibly with minor modifications including but not limited to: the enabling or disabling of certain features by default, translations into other languages, changes required for compatibility with a particular operating system distribution, or the inclusion of bug-fix patches). All such minor modifications must be released under an [[Oversight_Board/Meeting_Minutes-2009-12-11#Non-FOSS_content|approved license]].

:To identify Sugar Labs software as a distinct component of a software offering. For example, "MyDistro, sweetened by Sugar" or other "<product>, <joined with> Sugar" language would be a use that does not require explicit written permission.

:b.

:You may use the Sugar Labs Marks with prior written permission for the following purposes (subject to the other sections):

:If you are producing a new product which is based on Sugar Labs software but which has more substantial changes than those described in the previous paragraph, you may refer to your product as "derived from", "based on", or "a derivative of" a Sugar Labs mark.

:Please refer to our [[http://wiki.sugarlabs.org/go/Sugar_Labs/Governance/Transactions#License_request|License Request]] procedure for details regarding obtaining a license to use the Sugar Marks.

:c.

:You do not need written permission to refer to the Sugar Labs project itself, its products, or its protocols.

3.

You may use the Sugar Labs Marks as part of the name of a product designed to work with Sugar Labs, so long as the name as a whole (via its other components) clearly and unambiguously distinguishes the product from Sugar Labs software itself, and the general presentation of the product does not imply any official association or identity with Sugar Labs. Because it would be awkward to attach a trademark symbol to a portion of a larger name whose other portions might themselves be trademarked, the requirement to display the symbol is waived for this circumstance.

4.

You may not use the Marks in the following ways:

:a.

:In any way likely to cause confusion as to the identity of the Sugar Labs project, the provenance of its software, or the software's license (the Sugar Labs Marks should be secondary in advertising materials, including graphics on websites, etc.);

:b.

:In any way that indicates a greater degree of association between you and the Sugar Labs project than actually exists;

:c.

:In any way that implies a designated successor to Sugar Labs (e.g., "Sugar Labs++" is not permitted).

:d.

:In a way that indicates that Sugar Labs [[Oversight_Board/Meeting_Minutes-2009-12-18|favors one distribution, platform, product, etc. over another]].

5.

Sugar Labs also uses the following other marks:

:a.

:Sugar on a Stick:
::The "Sugar on a Stick" name and mark is associated with a specific [[Sugar on a Stick|Sugar Labs liveUSB project]]. You may produce and distribute Sugar Labs software on a USB key or other device, but you are required choose a different name to avoid confusion.

:b.

:Sugar Labs Partner:
::"Sugar Labs Partner" should only be used to refer to a person or entity that is officially affiliated with the Sugar Labs project. Sugar Labs is happy to designate partners, so please [[#Contact information|contact us]] if you are interested in becoming a Sugar Labs Partner.

:c.

:Sugar Ready:
::"Sugar Ready" may be used to refer to software certified by Sugar Labs to run on top of an official version of Sugar Labs, please [[#Contact information|contact us]] if you are interested in receiving a certification.

:d.

:Sugar Learning Platform
::"Sugar Learning Platform" should be used to refer to the software created by Sugar Labs and should be used under the same guidelines as per Sections 2 and 3 of this policy.

:e.

:Sugar
::We sometimes use this term as a shortened way to refer to software and other things created by Sugar Labs. Please use this policy as guidance for use of these terms as well and [[#Contact information|contact us]] if you are uncertain.

:f.

:local Sugar Lab:
::We have affiliated local and regional Sugar Labs that are referred to Sugar Labs <Region Name>, e.g., Sugar Labs Colombia. Sugar Labs is happy to designate local lab partners, so please [[#Contact information|contact us]] if you are interested in establishing a local Sugar Lab.

6.

You may create and sell merchandise using the Sugar Labs name and logo without additional permission provided that you use only unmodified graphics from the logo page on the Sugar Labs website. Please [[#Contact information|contact us]] if you would like to sell any other merchandise containing Sugar Labs Marks. This section is subject to the provisions contained in Sections 2 and 3 of this policy.

7.

The Software Freedom Conservancy reserves the sole right to:

:a.

:Determine compliance with this policy;

:b.

:Modify this policy in ways consistent with its mission of protecting the public;

:c.

:Grant exceptions to this policy, of any kind and for any reason whatsoever, other clauses notwithstanding.

===Contact information===

If you have questions about using the Marks, or if you think you should be able to use the Marks for any purpose not allowed by this policy and would like permission for that use, please contact Sugar Labs by emailing [trademark@sugarlabs.org] '''or by writing to [[Sugar_Labs/Contacts#Mail|Sugar Labs c/o Software Freedom Conservancy, 1995 BROADWAY FL 17, NEW YORK NY 10023-5882 USA]].'''

===Usage examples===

Usage examples can be found [[Sugar Labs/Governance/Trademark/Guidelines|on the Guidelines page]].

= Trademark case studies =

As the next step in working on the trademark, we are preparing case studies. The below text is taken from the [[Trademark case studies]] page - please [http://wiki.sugarlabs.org/index.php?title=Trademark_case_studies&action=edit edit that page directly] to contribute.

{{:Trademark case studies}}

Talk:Trademark

2010-05-07T14:53:47Z

SeanDaly: /* Sugar Trademark Policy */

==Sugar Labs association/organization conflated with Sugar software==
:2a & b, and elsewhere suggest that the full name of our product is 'Sugar Labs' rather than Sugar or some form of Sugar. Yes, 5e suggests that Sugar is short for Sugar Labs. This would be a new practice. Why conflate the terms?

:Why not register [[What is Sugar?|Sugar]] as a mark for our software, and [[Sugar Labs]] for our association?

::--[[User:FGrose|FGrose]] 23:18, 7 July 2009 (UTC)
==Logo==
: In paragraph 1, "(our trademark registration application for the logo is still pending)", is a separate statement, right? Sugar Labs is already registered, but the logos (colors and typeface) are pending registration, no? If so, this would be more clear as a separate sentence in the introduction, as it is currently too closely associated with the Sugar Labs name.
::--[[User:FGrose|FGrose]] 23:45, 7 July 2009 (UTC)
::AFAIK, the logo is not registered. It seemed that the name "Sugar Labs" was enough. --[[User:Walter|Walter]] 00:00, 8 July 2009 (UTC)

==Section 5a==

:It has been suggested that we certify distributions as "Sugar on a Stick". "Otherwise nothing stops anyone from creating a lousy version which hardly works and calls it Sugar on a Stick Peanut Butter release, etc."

:Comments? --[[User:Walter|Walter]] 22:23, 7 July 2009 (UTC)

::We have our hands full verifying and testing our own release. Our best defense is focusing on making the best release and so being able to market it as such. --[[User:FGrose|FGrose]] 23:28, 7 July 2009 (UTC)
::I agree. It adds yet another thing to worry about that can better be handled downstream. --[[User:Walter|Walter]] 23:34, 7 July 2009 (UTC)

::: This line of judgement needs revisiting. "our own release" means Strawberry? If SL lets anyone use "Sugar on a Stick", then it's probably giving up the rights to the trademark "Sugar on a Stick", right?

==[[Sugar Labs/Legal/Logo and trademark policy]]==
: This older page needs updating. --[[User:FGrose|FGrose]] 18:31, 4 September 2009 (UTC)
{{Merge|Sugar Labs/Legal/Logo and trademark_policy}}

== Sugar on a Stick Guidelines ==

I am herewith proposing the following changes to the section 5a. This has been derived from Fedora's [http://fedoraproject.org/wiki/Legal/TrademarkGuidelines trademark guidelines] and might need to be adjusted to cover more cases, as listed in those guidelines. By referring to Sugar on a Stick, the following draft means the project [[Sugar_on_a_Stick| located]] and [http://git.sugarlabs.org/projects/soas hosted] here.

* You '''may''' use the term ''Sugar on a Stick'' whenever referring to the official Sugar on a Stick product and its releases, as well as when distributing ''unmodified'' copies of it.
** However, this usage '''must not''' imply any endorsement by Sugar Labs or the Sugar on a Stick project, unless this is case and an appropriate agreement has been reached.
* You '''may''' modify Sugar on a Stick and create ''remixes'' of it.
** However, when distributing or selling this modified version, you '''must not''' call it Sugar on a Stick.
** When not exposing the resulting product to the public, you '''may''' still call it Sugar on a Stick, though. A deployment might adjust Sugar on a Stick for its needs and still say it deployed Sugar on a Stick, as long as the modified version is not distributed publicly.

== substantially unmodified ==

We discuss examples of "substantially unmodified" in [[Sugar Labs/Governance/Trademark|Section 2]] of the policy: "including but not limited to: the enabling or disabling of certain features by default, changes required for compatibility with a particular operating system distribution, or the inclusion of bug-fix patches." But it would be instructive to give some examples of changes that would not qualify as substantially unmodified: including but not limited to adding of non-free drivers. (We need to build consensus around this issue.) --[[User:Walter|Walter]] 20:44, 18 December 2009 (UTC)

== How to make modifications ==
There is a discussion [[Features/Feature_SoaS_customization|here]] about making a systemic process for most trivial modifications. --[[User:Walter|Walter]] 20:44, 18 December 2009 (UTC)

==Sugar Trademark Policy==

DRAFT: 7 May 2010

The purpose of this policy is to ensure that the identity, provenance, and free and open-source nature of Sugar Labs<sup>®</sup> remain clear '''to the public. This is in keeping with''' our objective to spread the use of the Sugar Learning Platform while protecting our trademarks. It is our intention to be liberal and responsive in the enforcement of our trademarks: '''we want our Marks to be widely used to represent our learning mission to the public, but we also need to ensure clarity regarding the relationship between Sugar Labs and the individual or organization using our Marks in order to both protect Sugar Labs and the public. As part of our marketing effort to make Sugar better known, we have developed a label program with the objective of simplifying and streamlining permission to use Sugar Labs marks by projects and businesses. We encourage you to contact us if you have any questions about this policy.''' Throughout this document, the word "Marks" refers to the Sugar Labs name and logo, individually or together. Note that Section 5 provides guidelines for other marks used by Sugar Labs. Sugar Labs is a member project of the Software Freedom Conservancy, which is the holder of the [http://tess2.uspto.gov/bin/showfield?f=doc&state=4006:qq173k.3.1 registered mark].

Guidelines for using the Marks

1.

The first or most prominent mention of the name should be immediately followed by a symbol for registered trademark: "®" or "(r)". For example: "Sugar Labs<sup>®</sup>".

This requirement is waived in all contexts where such marks are not normally included: email, on-line discussion, non-graphical advertisements (when permitted), and academic papers. We encourage the use of the symbol whenever possible, but recognize that many non-commercial and informal uses will omit it.

2.

:a.

:You may use the Sugar Labs Marks without prior written permission for the following purposes (subject to the other sections):

:To refer to the Sugar Labs software in substantially unmodified form. "Substantially unmodified" means built from the source code provided by the Sugar Labs project, possibly with minor modifications including but not limited to: the enabling or disabling of certain features by default, translations into other languages, changes required for compatibility with a particular operating system distribution, or the inclusion of bug-fix patches). All such minor modifications must be released under an [[Oversight_Board/Meeting_Minutes-2009-12-11#Non-FOSS_content|approved license]].

:To identify Sugar Labs software as a distinct component of a software offering. For example, "MyDistro, sweetened by Sugar" or other "<product>, <joined with> Sugar" language would be a use that does not require explicit written permission.

:b.

:You may use the Sugar Labs Marks with prior written permission for the following purposes (subject to the other sections):

:If you are producing a new product which is based on Sugar Labs software but which has more substantial changes than those described in the previous paragraph, you may refer to your product as "derived from", "based on", or "a derivative of" a Sugar Labs mark.

:Please refer to our [[http://wiki.sugarlabs.org/go/Sugar_Labs/Governance/Transactions#License_request|License Request]] procedure for details regarding obtaining a license to use the Sugar Marks.

:c.

:You do not need written permission to refer to the Sugar Labs project itself, its products, or its protocols.

3.

You may use the Sugar Labs Marks as part of the name of a product designed to work with Sugar Labs, so long as the name as a whole (via its other components) clearly and unambiguously distinguishes the product from Sugar Labs software itself, and the general presentation of the product does not imply any official association or identity with Sugar Labs. Because it would be awkward to attach a trademark symbol to a portion of a larger name whose other portions might themselves be trademarked, the requirement to display the symbol is waived for this circumstance.

4.

You may not use the Marks in the following ways:

:a.

:In any way likely to cause confusion as to the identity of the Sugar Labs project, the provenance of its software, or the software's license (the Sugar Labs Marks should be secondary in advertising materials, including graphics on websites, etc.);

:b.

:In any way that indicates a greater degree of association between you and the Sugar Labs project than actually exists;

:c.

:In any way that implies a designated successor to Sugar Labs (e.g., "Sugar Labs++" is not permitted).

:d.

:In a way that indicates that Sugar Labs [[Oversight_Board/Meeting_Minutes-2009-12-18|favors one distribution, platform, product, etc. over another]].

5.

Sugar Labs also uses the following other marks:

:a.

:Sugar on a Stick:
::The "Sugar on a Stick" name and mark is associated with a specific [[Sugar on a Stick|Sugar Labs liveUSB project]]. You may produce and distribute Sugar Labs software on a USB key or other device, but you are required choose a different name to avoid confusion.

:b.

:Sugar Labs Partner:
::"Sugar Labs Partner" should only be used to refer to a person or entity that is officially affiliated with the Sugar Labs project. Sugar Labs is happy to designate partners, so please [[#Contact information|contact us]] if you are interested in becoming a Sugar Labs Partner.

:c.

:Sugar Ready:
::"Sugar Ready" may be used to refer to software certified by Sugar Labs to run on top of an official version of Sugar Labs, please [[#Contact information|contact us]] if you are interested in receiving a certification.

:d.

:Sugar Learning Platform
::"Sugar Learning Platform" should be used to refer to the software created by Sugar Labs and should be used under the same guidelines as per Sections 2 and 3 of this policy.

:e.

:Sugar
::We sometimes use this term as a shortened way to refer to software and other things created by Sugar Labs. Please use this policy as guidance for use of these terms as well and [[#Contact information|contact us]] if you are uncertain.

:f.

:local Sugar Lab:
::We have affiliated local and regional Sugar Labs that are referred to Sugar Labs <Region Name>, e.g., Sugar Labs Colombia. Sugar Labs is happy to designate local lab partners, so please [[#Contact information|contact us]] if you are interested in establishing a local Sugar Lab.

6.

You may create and sell merchandise using the Sugar Labs name and logo without additional permission provided that you use only unmodified graphics from the logo page on the Sugar Labs website. Please [[#Contact information|contact us]] if you would like to sell any other merchandise containing Sugar Labs Marks. This section is subject to the provisions contained in Sections 2 and 3 of this policy.

7.

The Software Freedom Conservancy reserves the sole right to:

:a.

:Determine compliance with this policy;

:b.

:Modify this policy in ways consistent with its mission of protecting the public;

:c.

:Grant exceptions to this policy, of any kind and for any reason whatsoever, other clauses notwithstanding.

===Contact information===

If you have questions about using the Marks, or if you think you should be able to use the Marks for any purpose not allowed by this policy and would like permission for that use, please contact Sugar Labs by emailing [trademark@sugarlabs.org] '''or by writing to [[Sugar_Labs/Contacts#Mail|Sugar Labs c/o Software Freedom Conservancy, 1995 BROADWAY FL 17, NEW YORK NY 10023-5882 USA]].'''

===Usage examples===

Usage examples can be found [[Sugar Labs/Governance/Trademark/Guidelines|on the Guidelines page]].

= Trademark case studies =

As the next step in working on the trademark, we are preparing case studies. The below text is taken from the [[Trademark case studies]] page - please [http://wiki.sugarlabs.org/index.php?title=Trademark_case_studies&action=edit edit that page directly] to contribute.

{{:Trademark case studies}}

Talk:Trademark

2010-05-07T14:53:01Z

SeanDaly: /* Sugar Trademark Policy */

==Sugar Labs association/organization conflated with Sugar software==
:2a & b, and elsewhere suggest that the full name of our product is 'Sugar Labs' rather than Sugar or some form of Sugar. Yes, 5e suggests that Sugar is short for Sugar Labs. This would be a new practice. Why conflate the terms?

:Why not register [[What is Sugar?|Sugar]] as a mark for our software, and [[Sugar Labs]] for our association?

::--[[User:FGrose|FGrose]] 23:18, 7 July 2009 (UTC)
==Logo==
: In paragraph 1, "(our trademark registration application for the logo is still pending)", is a separate statement, right? Sugar Labs is already registered, but the logos (colors and typeface) are pending registration, no? If so, this would be more clear as a separate sentence in the introduction, as it is currently too closely associated with the Sugar Labs name.
::--[[User:FGrose|FGrose]] 23:45, 7 July 2009 (UTC)
::AFAIK, the logo is not registered. It seemed that the name "Sugar Labs" was enough. --[[User:Walter|Walter]] 00:00, 8 July 2009 (UTC)

==Section 5a==

:It has been suggested that we certify distributions as "Sugar on a Stick". "Otherwise nothing stops anyone from creating a lousy version which hardly works and calls it Sugar on a Stick Peanut Butter release, etc."

:Comments? --[[User:Walter|Walter]] 22:23, 7 July 2009 (UTC)

::We have our hands full verifying and testing our own release. Our best defense is focusing on making the best release and so being able to market it as such. --[[User:FGrose|FGrose]] 23:28, 7 July 2009 (UTC)
::I agree. It adds yet another thing to worry about that can better be handled downstream. --[[User:Walter|Walter]] 23:34, 7 July 2009 (UTC)

::: This line of judgement needs revisiting. "our own release" means Strawberry? If SL lets anyone use "Sugar on a Stick", then it's probably giving up the rights to the trademark "Sugar on a Stick", right?

==[[Sugar Labs/Legal/Logo and trademark policy]]==
: This older page needs updating. --[[User:FGrose|FGrose]] 18:31, 4 September 2009 (UTC)
{{Merge|Sugar Labs/Legal/Logo and trademark_policy}}

== Sugar on a Stick Guidelines ==

I am herewith proposing the following changes to the section 5a. This has been derived from Fedora's [http://fedoraproject.org/wiki/Legal/TrademarkGuidelines trademark guidelines] and might need to be adjusted to cover more cases, as listed in those guidelines. By referring to Sugar on a Stick, the following draft means the project [[Sugar_on_a_Stick| located]] and [http://git.sugarlabs.org/projects/soas hosted] here.

* You '''may''' use the term ''Sugar on a Stick'' whenever referring to the official Sugar on a Stick product and its releases, as well as when distributing ''unmodified'' copies of it.
** However, this usage '''must not''' imply any endorsement by Sugar Labs or the Sugar on a Stick project, unless this is case and an appropriate agreement has been reached.
* You '''may''' modify Sugar on a Stick and create ''remixes'' of it.
** However, when distributing or selling this modified version, you '''must not''' call it Sugar on a Stick.
** When not exposing the resulting product to the public, you '''may''' still call it Sugar on a Stick, though. A deployment might adjust Sugar on a Stick for its needs and still say it deployed Sugar on a Stick, as long as the modified version is not distributed publicly.

== substantially unmodified ==

We discuss examples of "substantially unmodified" in [[Sugar Labs/Governance/Trademark|Section 2]] of the policy: "including but not limited to: the enabling or disabling of certain features by default, changes required for compatibility with a particular operating system distribution, or the inclusion of bug-fix patches." But it would be instructive to give some examples of changes that would not qualify as substantially unmodified: including but not limited to adding of non-free drivers. (We need to build consensus around this issue.) --[[User:Walter|Walter]] 20:44, 18 December 2009 (UTC)

== How to make modifications ==
There is a discussion [[Features/Feature_SoaS_customization|here]] about making a systemic process for most trivial modifications. --[[User:Walter|Walter]] 20:44, 18 December 2009 (UTC)

==Sugar Trademark Policy==

DRAFT: 7 May 2010

The purpose of this policy is to ensure that the identity, provenance, and free and open-source nature of Sugar Labs<sup>®</sup> remain clear '''to the public. This is in keeping with''' our objective to spread the use of the Sugar Learning Platform while protecting our trademarks. It is our intention to be liberal and responsive in the enforcement of our trademarks: '''we want our Marks to be widely used to represent our learning mission to the public, but we also need to ensure clarity regarding the relationship between Sugar Labs and the individual or organization using our Marks in order to both protect Sugar Labs and the public. As part of our marketing effort to make Sugar better known, we have developed a label program with the objective of simplifying and streamlining use of Sugar Labs marks by projects and businesses. We encourage you to contact us if you have any questions about this policy.''' Throughout this document, the word "Marks" refers to the Sugar Labs name and logo, individually or together. Note that Section 5 provides guidelines for other marks used by Sugar Labs. Sugar Labs is a member project of the Software Freedom Conservancy, which is the holder of the [http://tess2.uspto.gov/bin/showfield?f=doc&state=4006:qq173k.3.1 registered mark].

Guidelines for using the Marks

1.

The first or most prominent mention of the name should be immediately followed by a symbol for registered trademark: "®" or "(r)". For example: "Sugar Labs<sup>®</sup>".

This requirement is waived in all contexts where such marks are not normally included: email, on-line discussion, non-graphical advertisements (when permitted), and academic papers. We encourage the use of the symbol whenever possible, but recognize that many non-commercial and informal uses will omit it.

2.

:a.

:You may use the Sugar Labs Marks without prior written permission for the following purposes (subject to the other sections):

:To refer to the Sugar Labs software in substantially unmodified form. "Substantially unmodified" means built from the source code provided by the Sugar Labs project, possibly with minor modifications including but not limited to: the enabling or disabling of certain features by default, translations into other languages, changes required for compatibility with a particular operating system distribution, or the inclusion of bug-fix patches). All such minor modifications must be released under an [[Oversight_Board/Meeting_Minutes-2009-12-11#Non-FOSS_content|approved license]].

:To identify Sugar Labs software as a distinct component of a software offering. For example, "MyDistro, sweetened by Sugar" or other "<product>, <joined with> Sugar" language would be a use that does not require explicit written permission.

:b.

:You may use the Sugar Labs Marks with prior written permission for the following purposes (subject to the other sections):

:If you are producing a new product which is based on Sugar Labs software but which has more substantial changes than those described in the previous paragraph, you may refer to your product as "derived from", "based on", or "a derivative of" a Sugar Labs mark.

:Please refer to our [[http://wiki.sugarlabs.org/go/Sugar_Labs/Governance/Transactions#License_request|License Request]] procedure for details regarding obtaining a license to use the Sugar Marks.

:c.

:You do not need written permission to refer to the Sugar Labs project itself, its products, or its protocols.

3.

You may use the Sugar Labs Marks as part of the name of a product designed to work with Sugar Labs, so long as the name as a whole (via its other components) clearly and unambiguously distinguishes the product from Sugar Labs software itself, and the general presentation of the product does not imply any official association or identity with Sugar Labs. Because it would be awkward to attach a trademark symbol to a portion of a larger name whose other portions might themselves be trademarked, the requirement to display the symbol is waived for this circumstance.

4.

You may not use the Marks in the following ways:

:a.

:In any way likely to cause confusion as to the identity of the Sugar Labs project, the provenance of its software, or the software's license (the Sugar Labs Marks should be secondary in advertising materials, including graphics on websites, etc.);

:b.

:In any way that indicates a greater degree of association between you and the Sugar Labs project than actually exists;

:c.

:In any way that implies a designated successor to Sugar Labs (e.g., "Sugar Labs++" is not permitted).

:d.

:In a way that indicates that Sugar Labs [[Oversight_Board/Meeting_Minutes-2009-12-18|favors one distribution, platform, product, etc. over another]].

5.

Sugar Labs also uses the following other marks:

:a.

:Sugar on a Stick:
::The "Sugar on a Stick" name and mark is associated with a specific [[Sugar on a Stick|Sugar Labs liveUSB project]]. You may produce and distribute Sugar Labs software on a USB key or other device, but you are required choose a different name to avoid confusion.

:b.

:Sugar Labs Partner:
::"Sugar Labs Partner" should only be used to refer to a person or entity that is officially affiliated with the Sugar Labs project. Sugar Labs is happy to designate partners, so please [[#Contact information|contact us]] if you are interested in becoming a Sugar Labs Partner.

:c.

:Sugar Ready:
::"Sugar Ready" may be used to refer to software certified by Sugar Labs to run on top of an official version of Sugar Labs, please [[#Contact information|contact us]] if you are interested in receiving a certification.

:d.

:Sugar Learning Platform
::"Sugar Learning Platform" should be used to refer to the software created by Sugar Labs and should be used under the same guidelines as per Sections 2 and 3 of this policy.

:e.

:Sugar
::We sometimes use this term as a shortened way to refer to software and other things created by Sugar Labs. Please use this policy as guidance for use of these terms as well and [[#Contact information|contact us]] if you are uncertain.

:f.

:local Sugar Lab:
::We have affiliated local and regional Sugar Labs that are referred to Sugar Labs <Region Name>, e.g., Sugar Labs Colombia. Sugar Labs is happy to designate local lab partners, so please [[#Contact information|contact us]] if you are interested in establishing a local Sugar Lab.

6.

You may create and sell merchandise using the Sugar Labs name and logo without additional permission provided that you use only unmodified graphics from the logo page on the Sugar Labs website. Please [[#Contact information|contact us]] if you would like to sell any other merchandise containing Sugar Labs Marks. This section is subject to the provisions contained in Sections 2 and 3 of this policy.

7.

The Software Freedom Conservancy reserves the sole right to:

:a.

:Determine compliance with this policy;

:b.

:Modify this policy in ways consistent with its mission of protecting the public;

:c.

:Grant exceptions to this policy, of any kind and for any reason whatsoever, other clauses notwithstanding.

===Contact information===

If you have questions about using the Marks, or if you think you should be able to use the Marks for any purpose not allowed by this policy and would like permission for that use, please contact Sugar Labs by emailing [trademark@sugarlabs.org] '''or by writing to [[Sugar_Labs/Contacts#Mail|Sugar Labs c/o Software Freedom Conservancy, 1995 BROADWAY FL 17, NEW YORK NY 10023-5882 USA]].'''

===Usage examples===

Usage examples can be found [[Sugar Labs/Governance/Trademark/Guidelines|on the Guidelines page]].

= Trademark case studies =

As the next step in working on the trademark, we are preparing case studies. The below text is taken from the [[Trademark case studies]] page - please [http://wiki.sugarlabs.org/index.php?title=Trademark_case_studies&action=edit edit that page directly] to contribute.

{{:Trademark case studies}}

Talk:Trademark

2010-05-07T14:39:12Z

SeanDaly: /* Sugar Trademark Policy */

==Sugar Labs association/organization conflated with Sugar software==
:2a & b, and elsewhere suggest that the full name of our product is 'Sugar Labs' rather than Sugar or some form of Sugar. Yes, 5e suggests that Sugar is short for Sugar Labs. This would be a new practice. Why conflate the terms?

:Why not register [[What is Sugar?|Sugar]] as a mark for our software, and [[Sugar Labs]] for our association?

::--[[User:FGrose|FGrose]] 23:18, 7 July 2009 (UTC)
==Logo==
: In paragraph 1, "(our trademark registration application for the logo is still pending)", is a separate statement, right? Sugar Labs is already registered, but the logos (colors and typeface) are pending registration, no? If so, this would be more clear as a separate sentence in the introduction, as it is currently too closely associated with the Sugar Labs name.
::--[[User:FGrose|FGrose]] 23:45, 7 July 2009 (UTC)
::AFAIK, the logo is not registered. It seemed that the name "Sugar Labs" was enough. --[[User:Walter|Walter]] 00:00, 8 July 2009 (UTC)

==Section 5a==

:It has been suggested that we certify distributions as "Sugar on a Stick". "Otherwise nothing stops anyone from creating a lousy version which hardly works and calls it Sugar on a Stick Peanut Butter release, etc."

:Comments? --[[User:Walter|Walter]] 22:23, 7 July 2009 (UTC)

::We have our hands full verifying and testing our own release. Our best defense is focusing on making the best release and so being able to market it as such. --[[User:FGrose|FGrose]] 23:28, 7 July 2009 (UTC)
::I agree. It adds yet another thing to worry about that can better be handled downstream. --[[User:Walter|Walter]] 23:34, 7 July 2009 (UTC)

::: This line of judgement needs revisiting. "our own release" means Strawberry? If SL lets anyone use "Sugar on a Stick", then it's probably giving up the rights to the trademark "Sugar on a Stick", right?

==[[Sugar Labs/Legal/Logo and trademark policy]]==
: This older page needs updating. --[[User:FGrose|FGrose]] 18:31, 4 September 2009 (UTC)
{{Merge|Sugar Labs/Legal/Logo and trademark_policy}}

== Sugar on a Stick Guidelines ==

I am herewith proposing the following changes to the section 5a. This has been derived from Fedora's [http://fedoraproject.org/wiki/Legal/TrademarkGuidelines trademark guidelines] and might need to be adjusted to cover more cases, as listed in those guidelines. By referring to Sugar on a Stick, the following draft means the project [[Sugar_on_a_Stick| located]] and [http://git.sugarlabs.org/projects/soas hosted] here.

* You '''may''' use the term ''Sugar on a Stick'' whenever referring to the official Sugar on a Stick product and its releases, as well as when distributing ''unmodified'' copies of it.
** However, this usage '''must not''' imply any endorsement by Sugar Labs or the Sugar on a Stick project, unless this is case and an appropriate agreement has been reached.
* You '''may''' modify Sugar on a Stick and create ''remixes'' of it.
** However, when distributing or selling this modified version, you '''must not''' call it Sugar on a Stick.
** When not exposing the resulting product to the public, you '''may''' still call it Sugar on a Stick, though. A deployment might adjust Sugar on a Stick for its needs and still say it deployed Sugar on a Stick, as long as the modified version is not distributed publicly.

== substantially unmodified ==

We discuss examples of "substantially unmodified" in [[Sugar Labs/Governance/Trademark|Section 2]] of the policy: "including but not limited to: the enabling or disabling of certain features by default, changes required for compatibility with a particular operating system distribution, or the inclusion of bug-fix patches." But it would be instructive to give some examples of changes that would not qualify as substantially unmodified: including but not limited to adding of non-free drivers. (We need to build consensus around this issue.) --[[User:Walter|Walter]] 20:44, 18 December 2009 (UTC)

== How to make modifications ==
There is a discussion [[Features/Feature_SoaS_customization|here]] about making a systemic process for most trivial modifications. --[[User:Walter|Walter]] 20:44, 18 December 2009 (UTC)

==Sugar Trademark Policy==

DRAFT: 7 May 2010

The purpose of this policy is to ensure that the identity, provenance, and free and open-source nature of Sugar Labs<sup>®</sup> remain clear '''to the public. This is in keeping with''' our objective to spread the use of the Sugar Learning Platform while protecting our trademarks. It is our intention to be liberal and responsive in the enforcement of our trademarks: '''we want our Marks to be widely used to represent our learning mission to the public, but we also need to ensure clarity regarding the relationship between Sugar Labs and the individual or organization using our Marks in order to both protect Sugar Labs and the public. We encourage you to contact us if you have any questions about this policy.''' Throughout this document, the word "Marks" refers to the Sugar Labs name and logo, individually or together. Note that Section 5 provides guidelines for other marks used by Sugar Labs. Sugar Labs is a member project of the Software Freedom Conservancy, which is the holder of the [http://tess2.uspto.gov/bin/showfield?f=doc&state=4006:qq173k.3.1 registered mark].

Guidelines for using the Marks

1.

The first or most prominent mention of the name should be immediately followed by a symbol for registered trademark: "®" or "(r)". For example: "Sugar Labs<sup>®</sup>".

This requirement is waived in all contexts where such marks are not normally included: email, on-line discussion, non-graphical advertisements (when permitted), and academic papers. We encourage the use of the symbol whenever possible, but recognize that many non-commercial and informal uses will omit it.

2.

:a.

:You may use the Sugar Labs Marks without prior written permission for the following purposes (subject to the other sections):

:To refer to the Sugar Labs software in substantially unmodified form. "Substantially unmodified" means built from the source code provided by the Sugar Labs project, possibly with minor modifications including but not limited to: the enabling or disabling of certain features by default, translations into other languages, changes required for compatibility with a particular operating system distribution, or the inclusion of bug-fix patches). All such minor modifications must be released under an [[Oversight_Board/Meeting_Minutes-2009-12-11#Non-FOSS_content|approved license]].

:To identify Sugar Labs software as a distinct component of a software offering. For example, "MyDistro, sweetened by Sugar" or other "<product>, <joined with> Sugar" language would be a use that does not require explicit written permission.

:b.

:You may use the Sugar Labs Marks with prior written permission for the following purposes (subject to the other sections):

:If you are producing a new product which is based on Sugar Labs software but which has more substantial changes than those described in the previous paragraph, you may refer to your product as "derived from", "based on", or "a derivative of" a Sugar Labs mark.

:Please refer to our [[http://wiki.sugarlabs.org/go/Sugar_Labs/Governance/Transactions#License_request|License Request]] procedure for details regarding obtaining a license to use the Sugar Marks.

:c.

:You do not need written permission to refer to the Sugar Labs project itself, its products, or its protocols.

3.

You may use the Sugar Labs Marks as part of the name of a product designed to work with Sugar Labs, so long as the name as a whole (via its other components) clearly and unambiguously distinguishes the product from Sugar Labs software itself, and the general presentation of the product does not imply any official association or identity with Sugar Labs. Because it would be awkward to attach a trademark symbol to a portion of a larger name whose other portions might themselves be trademarked, the requirement to display the symbol is waived for this circumstance.

4.

You may not use the Marks in the following ways:

:a.

:In any way likely to cause confusion as to the identity of the Sugar Labs project, the provenance of its software, or the software's license (the Sugar Labs Marks should be secondary in advertising materials, including graphics on websites, etc.);

:b.

:In any way that indicates a greater degree of association between you and the Sugar Labs project than actually exists;

:c.

:In any way that implies a designated successor to Sugar Labs (e.g., "Sugar Labs++" is not permitted).

:d.

:In a way that indicates that Sugar Labs [[Oversight_Board/Meeting_Minutes-2009-12-18|favors one distribution, platform, product, etc. over another]].

5.

Sugar Labs also uses the following other marks:

:a.

:Sugar on a Stick:
::The "Sugar on a Stick" name and mark is associated with a specific [[Sugar on a Stick|Sugar Labs liveUSB project]]. You may produce and distribute Sugar Labs software on a USB key or other device, but you are required choose a different name to avoid confusion.

:b.

:Sugar Labs Partner:
::"Sugar Labs Partner" should only be used to refer to a person or entity that is officially affiliated with the Sugar Labs project. Sugar Labs is happy to designate partners, so please [[#Contact information|contact us]] if you are interested in becoming a Sugar Labs Partner.

:c.

:Sugar Ready:
::"Sugar Ready" may be used to refer to software certified by Sugar Labs to run on top of an official version of Sugar Labs, please [[#Contact information|contact us]] if you are interested in receiving a certification.

:d.

:Sugar Learning Platform
::"Sugar Learning Platform" should be used to refer to the software created by Sugar Labs and should be used under the same guidelines as per Sections 2 and 3 of this policy.

:e.

:Sugar
::We sometimes use this term as a shortened way to refer to software and other things created by Sugar Labs. Please use this policy as guidance for use of these terms as well and [[#Contact information|contact us]] if you are uncertain.

:f.

:local Sugar Lab:
::We have affiliated local and regional Sugar Labs that are referred to Sugar Labs <Region Name>, e.g., Sugar Labs Colombia. Sugar Labs is happy to designate local lab partners, so please [[#Contact information|contact us]] if you are interested in establishing a local Sugar Lab.

6.

You may create and sell merchandise using the Sugar Labs name and logo without additional permission provided that you use only unmodified graphics from the logo page on the Sugar Labs website. Please [[#Contact information|contact us]] if you would like to sell any other merchandise containing Sugar Labs Marks. This section is subject to the provisions contained in Sections 2 and 3 of this policy.

7.

The Software Freedom Conservancy reserves the sole right to:

:a.

:Determine compliance with this policy;

:b.

:Modify this policy in ways consistent with its mission of protecting the public;

:c.

:Grant exceptions to this policy, of any kind and for any reason whatsoever, other clauses notwithstanding.

===Contact information===

If you have questions about using the Marks, or if you think you should be able to use the Marks for any purpose not allowed by this policy and would like permission for that use, please contact Sugar Labs by emailing [trademark@sugarlabs.org] '''or by writing to [[Sugar_Labs/Contacts#Mail|Sugar Labs c/o Software Freedom Conservancy, 1995 BROADWAY FL 17, NEW YORK NY 10023-5882 USA]].'''

===Usage examples===

Usage examples can be found [[Sugar Labs/Governance/Trademark/Guidelines|on the Guidelines page]].

= Trademark case studies =

As the next step in working on the trademark, we are preparing case studies. The below text is taken from the [[Trademark case studies]] page - please [http://wiki.sugarlabs.org/index.php?title=Trademark_case_studies&action=edit edit that page directly] to contribute.

{{:Trademark case studies}}