Difference between revisions of "Talk:Sugar Labs/Roadmap"
Jump to navigation
Jump to search
(12 intermediate revisions by 3 users not shown) | |||
Line 1: | Line 1: | ||
− | <noinclude> | + | <noinclude> <small>[[Sugar Labs/Roadmap|< Sugar Labs/Roadmap]]</small>{{GoogleTrans-en}}{{TOCright}}</noinclude> |
− | [[Sugar Labs/Roadmap|< Sugar Labs/Roadmap]] | + | Please share your thoughts. See also comments in this mailing list [http://www.mail-archive.com/iaep@lists.sugarlabs.org/msg05698.html thread]. |
− | </noinclude> | ||
− | Please share your thoughts. | ||
==How is Sugar Labs different from other FOSS projects?== | ==How is Sugar Labs different from other FOSS projects?== | ||
Line 12: | Line 10: | ||
: We also aspire to transfer aspects of the culture of the FOSS community to the learning community—the culture of sharing and the culture of critique. Learners must have ready access to powerful ideas and to a community that engages in constructive criticism of ideas. "Show me the code." | : We also aspire to transfer aspects of the culture of the FOSS community to the learning community—the culture of sharing and the culture of critique. Learners must have ready access to powerful ideas and to a community that engages in constructive criticism of ideas. "Show me the code." | ||
+ | ::-Caroline- Are we a FOSS project or are we an Education Project that uses FOSS and takes our inspiration from FOSS? | ||
+ | |||
+ | :::What if we are an education project whose software projects are FOSS? [[User:Tomeu|Tomeu]] 18:43, 21 July 2009 (UTC) | ||
+ | |||
+ | ==How and why does FOSS development work best for Sugar Labs?== | ||
+ | |||
+ | -Caroline's Brainstorming- We don't have an alternative??? :) There is much to love and that is coherent with our mission about FOSS development. But maybe we should rephrase the question, this one sounds like we sat around and thought about different alternatives. Actually, I personally did so in 1999. I realized there was no way to educate the world with per-user-seat business model, the only thing that could work was open source. [This is a lousy answer but maybe it will insprire other people to brainstorm.] | ||
+ | |||
+ | Perhaps someone should propose alternatives? ;) [[User:Tomeu|Tomeu]] 18:44, 21 July 2009 (UTC) | ||
+ | |||
+ | : The intent of this question was to draw out a description of some of the features of [[wikipedia:Free_and_open_source_software|FLOSS]] development—and how and why they are best employed. Tomeu started some of this in the [http://meeting.sugarlabs.org/sugar-meeting.log.20090713_1034.html SoaS meeting of 13 July 2009], and it deserves a fuller treatment (or, at least, a good summary). Caroline provides a practical answer that is sobering and a useful reference point. One believes that you and others could help educate our diverse community to become more familiar with those features that you find most practical, beautiful, and inspiring. Like the previous question, we are not one or the other, or just both. We can evolve to something more than both, based on the strength of hybrids and the contributions of our diverse communities. --[[User:FGrose|FGrose]] 00:25, 22 July 2009 (UTC) | ||
==What are Sugar Labs [[:Category:Project|Projects]]?== | ==What are Sugar Labs [[:Category:Project|Projects]]?== | ||
:[[:Category:Project|Projects]] in Sugar Labs are learning experiments generally focused on delivering specific goals within a defined time period and learning how to advance the Sugar Labs vision. They often require services from multiple specialties. Project members may be active in multiple areas. Projects may have a home page with links in a project header to pages for participation, contacts, resources, FAQs, a roadmap or their vision, tasks, and meetings. | :[[:Category:Project|Projects]] in Sugar Labs are learning experiments generally focused on delivering specific goals within a defined time period and learning how to advance the Sugar Labs vision. They often require services from multiple specialties. Project members may be active in multiple areas. Projects may have a home page with links in a project header to pages for participation, contacts, resources, FAQs, a roadmap or their vision, tasks, and meetings. | ||
+ | |||
:Projects are where the Sugar principles and software may be developed, tested, and deployed for the purpose of better integrating Sugar software with community needs and aspirations. | :Projects are where the Sugar principles and software may be developed, tested, and deployed for the purpose of better integrating Sugar software with community needs and aspirations. | ||
+ | |||
:Projects take on a further meaning in the context of learning. Sugar Labs promotes the pedagogy of guided discovery—many Sugar Labs Project include guides to teachers and structure for learners to help launch them into a discovery process that they subsequently appropriate. Guides are most often in the form of open-ended problems and challenges. Many Sugar Labs Projects go so far as to include guides to modifying the Project itself, including the software. | :Projects take on a further meaning in the context of learning. Sugar Labs promotes the pedagogy of guided discovery—many Sugar Labs Project include guides to teachers and structure for learners to help launch them into a discovery process that they subsequently appropriate. Guides are most often in the form of open-ended problems and challenges. Many Sugar Labs Projects go so far as to include guides to modifying the Project itself, including the software. | ||
+ | |||
+ | ::What if we rename the above as "Learning projects"? Sugar is a quite traditional FOSS project that exists outside the projects mentioned above. [[User:Tomeu|Tomeu]] 18:47, 21 July 2009 (UTC) |
Latest revision as of 19:13, 15 September 2009
Please share your thoughts. See also comments in this mailing list thread.
How is Sugar Labs different from other FOSS projects?
- Sugar Labs attracts a very broad spectrum of people interested not only in software but for the humanitarian products of software. While a humanitarian FOSS project (we need the powerful, foundational tools of software), we are different because we are participating in the invention of a new society with more powerful tools, social objects, and more freedom to learn. The potential resulting from the combination of these powers is enormous. Sugar Labs is about building those powers. It's an Education Project is a moniker we have adopted to remind us of that breadth of purpose.
How is Sugar Labs a FOSS project?
- Sugar Labs recognizes free and open source software as the powerful ingredient in our technological future. Our success is based on a powerful vision and working software. A large part of our investments must be dedicated to the delivery of powerful software designs and working code—software that is used powerfully and productively.
- We also aspire to transfer aspects of the culture of the FOSS community to the learning community—the culture of sharing and the culture of critique. Learners must have ready access to powerful ideas and to a community that engages in constructive criticism of ideas. "Show me the code."
- -Caroline- Are we a FOSS project or are we an Education Project that uses FOSS and takes our inspiration from FOSS?
- What if we are an education project whose software projects are FOSS? Tomeu 18:43, 21 July 2009 (UTC)
How and why does FOSS development work best for Sugar Labs?
-Caroline's Brainstorming- We don't have an alternative??? :) There is much to love and that is coherent with our mission about FOSS development. But maybe we should rephrase the question, this one sounds like we sat around and thought about different alternatives. Actually, I personally did so in 1999. I realized there was no way to educate the world with per-user-seat business model, the only thing that could work was open source. [This is a lousy answer but maybe it will insprire other people to brainstorm.]
Perhaps someone should propose alternatives? ;) Tomeu 18:44, 21 July 2009 (UTC)
- The intent of this question was to draw out a description of some of the features of FLOSS development—and how and why they are best employed. Tomeu started some of this in the SoaS meeting of 13 July 2009, and it deserves a fuller treatment (or, at least, a good summary). Caroline provides a practical answer that is sobering and a useful reference point. One believes that you and others could help educate our diverse community to become more familiar with those features that you find most practical, beautiful, and inspiring. Like the previous question, we are not one or the other, or just both. We can evolve to something more than both, based on the strength of hybrids and the contributions of our diverse communities. --FGrose 00:25, 22 July 2009 (UTC)
What are Sugar Labs Projects?
- Projects in Sugar Labs are learning experiments generally focused on delivering specific goals within a defined time period and learning how to advance the Sugar Labs vision. They often require services from multiple specialties. Project members may be active in multiple areas. Projects may have a home page with links in a project header to pages for participation, contacts, resources, FAQs, a roadmap or their vision, tasks, and meetings.
- Projects are where the Sugar principles and software may be developed, tested, and deployed for the purpose of better integrating Sugar software with community needs and aspirations.
- Projects take on a further meaning in the context of learning. Sugar Labs promotes the pedagogy of guided discovery—many Sugar Labs Project include guides to teachers and structure for learners to help launch them into a discovery process that they subsequently appropriate. Guides are most often in the form of open-ended problems and challenges. Many Sugar Labs Projects go so far as to include guides to modifying the Project itself, including the software.
- What if we rename the above as "Learning projects"? Sugar is a quite traditional FOSS project that exists outside the projects mentioned above. Tomeu 18:47, 21 July 2009 (UTC)