2017 Goals: Difference between revisions

Line 267:

===What is next for Sugar?===

We face several challenges at Sugar Labs. Since we are serving children's needs, with a particular focus on children in the developing world, we must adapt to their real needs as much as possible. Quality assurance for all our products must be an obsession~~. Frequent feedback from field, feeds developers and inspires them to upgrade their prototypes.~~.

We face several challenges at Sugar Labs. Since we are serving children's needs, with a particular focus on children in the developing world, we must adapt to their real needs as much as possible. Quality assurance for all our products must be an obsession.

With the ebb of OLPC, we have a contracting user base and the number of professional developers associated with the project is greatly diminished. How can we expand our user base? How can we keep our more experienced developers? Why would they want to work on Sugar as opposed to some other project? The meta issue is how do we keep Sugar relevant in a world of Apps and small, hand-held devices? Can we meet the expectations of learners living in a world of fast-paced, colorful interfaces? How do we ensure that it is fulfilling its potential as a learning environment? How do we ensure that it is fulfilling its potential as a collaboration tool?

@@ Line 267: / Line 267: @@
 ===What is next for Sugar?===
-We face several challenges at Sugar Labs. Since we are serving children's needs, with a particular focus on children in the developing world, we must adapt to their real needs as much as possible. Quality assurance for all our products must be an obsession. Frequent feedback from field, feeds developers and inspires them to upgrade their prototypes..
+We face several challenges at Sugar Labs. Since we are serving children's needs, with a particular focus on children in the developing world, we must adapt to their real needs as much as possible. Quality assurance for all our products must be an obsession.
 With the ebb of OLPC, we have a contracting user base and the number of professional developers associated with the project is greatly diminished. How can we expand our user base? How can we keep our more experienced developers? Why would they want to work on Sugar as opposed to some other project? The meta issue is how do we keep Sugar relevant in a world of Apps and small, hand-held devices? Can we meet the expectations of learners living in a world of fast-paced, colorful interfaces? How do we ensure that it is fulfilling its potential as a learning environment?  How do we ensure that it is fulfilling its potential as a collaboration tool?