Talk:Sugar Labs/Roadmap - Revision history

FGrose at 00:13, 16 September 2009

2009-09-16T00:13:44Z

← Older revision		Revision as of 20:13, 15 September 2009
Line 10:		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?		::-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)		:::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?==		==How and why does FOSS development work best for Sugar Labs?==
Line 19:		Line 19:

	Perhaps someone should propose alternatives? ;) [[User:Tomeu\|Tomeu]] 18:44, 21 July 2009 (UTC)		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)		: 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)		::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)

FGrose at 00:25, 22 July 2009

2009-07-22T00:25:03Z

← Older revision		Revision as of 20:25, 21 July 2009
Line 19:		Line 19:

	Perhaps someone should propose alternatives? ;) [[User:Tomeu\|Tomeu]] 18:44, 21 July 2009 (UTC)		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.

Tomeu: /* What are Sugar Labs Projects? */

2009-07-21T18:47:26Z

What are Sugar Labs Projects?

← Older revision		Revision as of 14:47, 21 July 2009
Line 24:		Line 24:
	: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)

Tomeu: /* How and why does FOSS development work best for Sugar Labs? */

2009-07-21T18:44:23Z

How and why does FOSS development work best for Sugar Labs?

← Older revision		Revision as of 14:44, 21 July 2009
Line 17:		Line 17:

	-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.]		-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)

	==What are Sugar Labs [[:Category:Project\|Projects]]?==		==What are Sugar Labs [[:Category:Project\|Projects]]?==

Tomeu: /* How is Sugar Labs a FOSS project? */

2009-07-21T18:43:46Z

How is Sugar Labs a FOSS project?

← Older revision		Revision as of 14:43, 21 July 2009
Line 11:		Line 11:

	-Caroline- Are we a FOSS project or are we an Education Project that uses FOSS and takes our inspiration from FOSS?		-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?==		==How and why does FOSS development work best for Sugar Labs?==

FGrose at 20:49, 17 July 2009

2009-07-17T20:49:55Z

← Older revision		Revision as of 16:49, 17 July 2009
Line 1:		Line 1:
	<noinclude>  <small>[[Sugar Labs/Roadmap\|< Sugar Labs/Roadmap]]</small>{{GoogleTrans-en}}{{TOCright}}</noinclude>		<noinclude>  <small>[[Sugar Labs/Roadmap\|< Sugar Labs/Roadmap]]</small>{{GoogleTrans-en}}{{TOCright}}</noinclude>
	Please share your thoughts.		Please share your thoughts. See also comments in this mailing list [http://www.mail-archive.com/iaep@lists.sugarlabs.org/msg05698.html thread].

	==How is Sugar Labs different from other FOSS projects?==		==How is Sugar Labs different from other FOSS projects?==

CarolineM: /* How and why does FOSS development work best for Sugar Labs? */

2009-07-16T12:29:02Z

How and why does FOSS development work best for Sugar Labs?

← Older revision		Revision as of 08:29, 16 July 2009
Line 13:		Line 13:

	==How and why does FOSS development work best for Sugar Labs?==		==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.]
	: ...		: ...

CarolineM: /* How is Sugar Labs a FOSS project? */

2009-07-16T12:23:07Z

How is Sugar Labs a FOSS project?

← Older revision		Revision as of 08:23, 16 July 2009
Line 9:		Line 9:

	: 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?

	==How and why does FOSS development work best for Sugar Labs?==		==How and why does FOSS development work best for Sugar Labs?==
	: ...		: ...

FGrose: /* How and why does FOSS development work best for Sugar Labs? */

2009-07-13T17:31:01Z

How and why does FOSS development work best for Sugar Labs?

← Older revision		Revision as of 13:31, 13 July 2009
Line 10:		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."
	==How and why does FOSS development work best for Sugar Labs?==		==How and why does FOSS development work best for Sugar Labs?==
	:		: ...

	==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.

FGrose at 17:26, 13 July 2009

2009-07-13T17:26:55Z

← Older revision		Revision as of 13:26, 13 July 2009
Line 1:		Line 1:
	<noinclude>  <small>[[Sugar Labs/Roadmap\|< Sugar Labs/Roadmap]]</small>{{GoogleTrans-en}}</noinclude>		<noinclude>  <small>[[Sugar Labs/Roadmap\|< Sugar Labs/Roadmap]]</small>{{GoogleTrans-en}}{{TOCright}}</noinclude>
	Please share your thoughts.		Please share your thoughts.

← Older revision		Revision as of 20:25, 21 July 2009
Line 19:		Line 19:

	Perhaps someone should propose alternatives? ;) [[User:Tomeu\|Tomeu]] 18:44, 21 July 2009 (UTC)		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.