Deployment Platform/Declaration of purpose - Revision history

Alsroot: moved Harmonic Distribution/Declaration of purpose to Deployment Platform/Declaration of purpose

2012-10-08T20:32:22Z

moved Harmonic Distribution/Declaration of purpose to Deployment Platform/Declaration of purpose

← Older revision	Revision as of 16:32, 8 October 2012
(No difference)

Alsroot at 05:31, 23 September 2012

2012-09-23T05:31:38Z

← Older revision		Revision as of 01:31, 23 September 2012
Line 22:		Line 22:
	''What's new in your approach, and why do you think it will be successful?''		''What's new in your approach, and why do you think it will be successful?''

	:* We use the [[Platform_Team/~~Open_Build_System~~\|Open Build ~~System~~]] for a systematic approach to provide the same ''Base software'':		:* We use the [[Platform_Team/Open_Build_Service\|Open Build Service]] for a systematic approach to provide the same ''Base software'':
	:** The same code base is being built for all supported [[wikipedia:GNU/Linux distribution\|GNU/Linux distributions]].		:** The same code base is being built for all supported [[wikipedia:GNU/Linux distribution\|GNU/Linux distributions]].
	:** Among the 6 months Sucrose releases, there will be Long Term Supported releases.		:** Among the 6 months Sucrose releases, there will be Long Term Supported releases.
	:* We provide the [[Sugar Network]] to systematically share a broad variety of ''Content''.		:* We provide the [[Sugar Network]] to systematically share a broad variety of ''Content''.
	:** This will include Sugar activities, [[Platform_Team/Sweets\|Sweets]] will take care about processing dependencies, and the [[Platform_Team/~~Open_Build_System~~\|Open Build ~~System~~]] will build binaries automatically.		:** This will include Sugar activities, [[Platform_Team/Sweets\|Sweets]] will take care about processing dependencies, and the [[Platform_Team/Open_Build_Service\|Open Build Service]] will build binaries automatically.
	:* [[Sugar Network]] is also an integrated approach to provide ''Social activity'' for the ''Content''.		:* [[Sugar Network]] is also an integrated approach to provide ''Social activity'' for the ''Content''.
	:* [[Sugar Network]] is designed to fulfill specific deployment needs like the following:		:* [[Sugar Network]] is designed to fulfill specific deployment needs like the following:

Alsroot: moved Platform Team/Harmonic Distribution/Declaration of purpose to Harmonic Distribution/Declaration of purpose

2012-07-27T06:33:27Z

moved Platform Team/Harmonic Distribution/Declaration of purpose to Harmonic Distribution/Declaration of purpose

← Older revision	Revision as of 02:33, 27 July 2012
(No difference)

FGrose at 03:03, 8 April 2012

2012-04-08T03:03:29Z

← Older revision		Revision as of 23:03, 7 April 2012
Line 22:		Line 22:
	''What's new in your approach, and why do you think it will be successful?''		''What's new in your approach, and why do you think it will be successful?''

	:* We use the[[Platform_Team/Open_Build_System\|Open Build System]] for a systematic approach to provide the same ''Base software'':		:* We use the [[Platform_Team/Open_Build_System\|Open Build System]] for a systematic approach to provide the same ''Base software'':
	:** The same code base is being built for all supported [[wikipedia:GNU/Linux distribution\|GNU/Linux distributions]].		:** The same code base is being built for all supported [[wikipedia:GNU/Linux distribution\|GNU/Linux distributions]].
	:** Among the 6 months Sucrose releases, there will be Long Term Supported releases.		:** Among the 6 months Sucrose releases, there will be Long Term Supported releases.

FGrose at 03:02, 8 April 2012

2012-04-08T03:02:35Z

← Older revision		Revision as of 23:02, 7 April 2012
Line 1:		Line 1:
	''What are you trying to do?''		''What are you trying to do?''

	:* ~~The possibility~~ to launch ''Base Software'' in heterogeneous software and hardware environments.		:* Create the ability to launch ''Base Software'' within heterogeneous software and hardware environments.
	:* Using ''Base Software'', provide access to ~~various~~ ''Content'' (Sugar activities, artifacts ~~created by~~ Sugar activities, books, etc~~.) created within the Sugar community~~.		:* Using ''Base Software'', provide access to varieties of ''Content'' created within the Sugar community, such as Sugar activities, artifacts derived from Sugar activities, books, etc.
	:* Using ''Base Software'', provide collaborative functionality to support ''Social activity'' around the ''Content''.		:* Using ''Base Software'', provide the collaborative functionality to support community ''Social activity'' centered around the ''Content''.
	:* ~~Instruments~~ and workflows to adapt ''Content'' and ''Base Software'' to specific needs that Sugar ''Deployment'' might face, including ~~extreme ones~~ like off-line environments and restricting hardware.		:* Provide tools and workflows to adapt the ''Content'' and ''Base Software'' to specific needs that a Sugar ''Deployment'' might face, including limitations like off-line environments and restricting hardware.

	''How is it done today, and what are the limits of current practice?''		''How is it done today, and what are the limits of current practice?''

	:* There is no ~~system~~ approach to provide the same ''Base software'':		:* There is no systematic approach to provide the same ''Base software'':
	:** On different [[~~Wiki~~:GNU/Linux distribution\|GNU/Linux distributions]]. ~~That~~ makes ~~hard~~ coordination, on Sugar Labs level, of any efforts related to ''Base software''.		:** On different [[wikipedia:GNU/Linux distribution\|GNU/Linux distributions]]. This makes coordination difficult, on the Sugar Labs level, for any efforts related to ''Base software''.
	:** On Sugar Labs level, there are no [[~~Wiki~~:Long_Term_Support\|LTS]] Sucrose releases. It makes ~~hard~~ coordination between Sugar deployments.		:** On the Sugar Labs level, there are no Long Term Support, [[wikipedia:Long_Term_Support\|LTS]], Sucrose releases. It makes coordination difficult between Sugar deployments.
	:* ~~Current ways~~ to share ''Content'' is either too general or limited:		:* The current means to share ''Content'' is either too general or too limited:
	:** The [[Activity Library]] is ~~needless~~ centralized (by design of upstream project that [[Activity Library]] is based on) and, e.g., doesn't accept uploading experimental activities created by ~~not original~~ authors.		:** The Sugar [[Activity Library]] is needlessly centralized (by the design of the upstream project that [[Activity Library]] is based on) and, e.g., it doesn't accept uploading of experimental versions of existing activities created by any new authors.
	:** [[Activity Library]] is too ~~restricted (by upstream design, it was created to handle Firefox plugins)~~ in case of ~~not~~ trivial software, e.g., dependencies and binary based activities.		:** The [[Activity Library]] is too restrictive in the case of non-trivial software, e.g., dependencies and binary-based activities (by upstream design). It was created to handle Firefox plugins.
	:** No services~~, like~~ [[Activity Library]], to share something different to activities.		:** There are no services similar to [[Activity Library]] to share something different from activities.
	:* There is ~~not~~ centralized Sugar-way to support ''Social activity'' within the community:		:* There is no centralized Sugar-way to support ''Social activity'' within the community:
	:** There is a gap between developers and users in the field.		:** There is a communications gap between developers and users in the field.
	:** ~~Existing~~ social services either scattered or too technical.		:** The existing social services are either scattered or too technical.
	:* There is not ~~system~~ approach, on Sugar Labs level, to coordinate efforts within the Sugar deployments.		:* There is not a systems approach, on Sugar Labs' level, to coordinate efforts within the Sugar deployments.

	''What's new in your approach and why do you think it will be successful?''		''What's new in your approach, and why do you think it will be successful?''

	:* [[Platform_Team/Open_Build_System\|Open Build System]] for ~~system~~ approach to provide the same ''Base software'':		:* We use the[[Platform_Team/Open_Build_System\|Open Build System]] for a systematic approach to provide the same ''Base software'':
	:** The same code base is being built for all supported [[~~Wiki~~:GNU/Linux distribution\|GNU/Linux distributions]].		:** The same code base is being built for all supported [[wikipedia:GNU/Linux distribution\|GNU/Linux distributions]].
	:** Among 6 months Sucrose releases, there will be ~~supported LTS~~ releases.		:** Among the 6 months Sucrose releases, there will be Long Term Supported releases.
	:* [[Sugar Network]] ~~for system approach~~ to ~~provide~~ ''Content''.		:* We provide the [[Sugar Network]] to systematically share a broad variety of ''Content''.
	:** ~~That~~ will include Sugar activities, ~~the~~ [[Platform_Team/Sweets\|Sweets]] will take care about ~~treating~~ dependencies and [[Platform_Team/Open_Build_System\|Open Build System]] will build binaries ~~in automatic manner~~.		:** This will include Sugar activities, [[Platform_Team/Sweets\|Sweets]] will take care about processing dependencies, and the [[Platform_Team/Open_Build_System\|Open Build System]] will build binaries automatically.
	:* [[Sugar Network]] ~~for system~~ approach to provide ''Social activity'' for the ''Content''.		:* [[Sugar Network]] is also an integrated approach to provide ''Social activity'' for the ''Content''.
	:* [[Sugar Network]] is designed to fulfill deployment needs like:		:* [[Sugar Network]] is designed to fulfill specific deployment needs like the following:
	:** Supporting environments with limited, or ~~absent~~, access to the Internet;		:** Supporting environments with limited, or non-existent, access to the Internet;
	:** Adapt ''Content'' to local needs.		:** Adapt ''Content'' to local needs.

Line 36:		Line 36:
	:* Individual users;		:* Individual users;
	:* Content creators and software developers;		:* Content creators and software developers;
	:* Existing and ~~potential~~ Sugar deployments.		:* Existing and future Sugar deployments.

	''If you're successful, what difference will it make?''		''If you're successful, what difference will it make?''

	:* ~~For individual~~ users:		:* Individual users will receive these benefits:
	:** reliable way to start Sugar on all mainstream platforms;		:** A reliable way to start Sugar on all mainstream platforms;
	:** environment to share content and ~~activities which is~~ well integrated to Sugar ~~workflow~~.		:** An environment to share content, activities, and collaborations that are well integrated with Sugar community workflows and learning.
	:* ~~For content~~ creators and software developers:		:* Content creators and software developers will obtain these services:
	:** ~~easy~~ sharing, e.g., system will handle issues like dependencies and building from sources automatically.		:** Easy sharing of software, e.g., the system will handle issues like dependencies and the building from sources automatically.
	:* ~~For existing~~ and ~~potential~~ Sugar deployments:		:* Existing and future Sugar deployments will enjoy these services:
	:** sharing space that will be common to all participants (but ~~it should support~~ tuning content for local needs);		:** A sharing space that will be common to all participants (but one that supports the tuning of content for local needs);
	:** more effectively ~~reusing~~ deployment experience~~, it~~ will be incarnate in solutions on community level to reuse in any deployment.		:** Accessible templates of deployment practices and procedures to more effectively reuse deployment experience. Such experience will be incarnate in solutions on the community level for reuse in any deployment.

Alsroot at 12:03, 21 March 2012

2012-03-21T12:03:51Z

← Older revision		Revision as of 08:03, 21 March 2012
Line 31:		Line 31:
	:** Supporting environments with limited, or absent, access to the Internet;		:** Supporting environments with limited, or absent, access to the Internet;
	:** Adapt ''Content'' to local needs.		:** Adapt ''Content'' to local needs.

			''Who cares?''

			:* Individual users;
			:* Content creators and software developers;
			:* Existing and potential Sugar deployments.

			''If you're successful, what difference will it make?''

			:* For individual users:
			:** reliable way to start Sugar on all mainstream platforms;
			:** environment to share content and activities which is well integrated to Sugar workflow.
			:* For content creators and software developers:
			:** easy sharing, e.g., system will handle issues like dependencies and building from sources automatically.
			:* For existing and potential Sugar deployments:
			:** sharing space that will be common to all participants (but it should support tuning content for local needs);
			:** more effectively reusing deployment experience, it will be incarnate in solutions on community level to reuse in any deployment.

Alsroot: moved Harmonic Distribution/Declaration of purpose to Platform Team/Harmonic Distribution/Declaration of purpose

2012-03-21T08:37:59Z

moved Harmonic Distribution/Declaration of purpose to Platform Team/Harmonic Distribution/Declaration of purpose

← Older revision	Revision as of 04:37, 21 March 2012
(No difference)

Alsroot: Created page with "''What are you trying to do?'' :* The possibility to launch ''Base Software'' in heterogeneous software and hardware environments. :* Using ''Base Software'', provide access to ..."

2012-03-21T08:33:21Z

Created page with "''What are you trying to do?'' :* The possibility to launch ''Base Software'' in heterogeneous software and hardware environments. :* Using ''Base Software'', provide access to ..."

New page

''What are you trying to do?''

:* The possibility to launch ''Base Software'' in heterogeneous software and hardware environments.
:* Using ''Base Software'', provide access to various ''Content'' (Sugar activities, artifacts created by Sugar activities, books, etc.) created within the Sugar community.
:* Using ''Base Software'', provide collaborative functionality to support ''Social activity'' around the ''Content''.
:* Instruments and workflows to adapt ''Content'' and ''Base Software'' to specific needs that Sugar ''Deployment'' might face, including extreme ones like off-line environments and restricting hardware.

''How is it done today, and what are the limits of current practice?''

:* There is no system approach to provide the same ''Base software'':
:** On different [[Wiki:GNU/Linux distribution|GNU/Linux distributions]]. That makes hard coordination, on Sugar Labs level, of any efforts related to ''Base software''.
:** On Sugar Labs level, there are no [[Wiki:Long_Term_Support|LTS]] Sucrose releases. It makes hard coordination between Sugar deployments.
:* Current ways to share ''Content'' is either too general or limited:
:** The [[Activity Library]] is needless centralized (by design of upstream project that [[Activity Library]] is based on) and, e.g., doesn't accept uploading experimental activities created by not original authors.
:** [[Activity Library]] is too restricted (by upstream design, it was created to handle Firefox plugins) in case of not trivial software, e.g., dependencies and binary based activities.
:** No services, like [[Activity Library]], to share something different to activities.
:* There is not centralized Sugar-way to support ''Social activity'' within the community:
:** There is a gap between developers and users in the field.
:** Existing social services either scattered or too technical.
:* There is not system approach, on Sugar Labs level, to coordinate efforts within the Sugar deployments.

''What's new in your approach and why do you think it will be successful?''

:* [[Platform_Team/Open_Build_System|Open Build System]] for system approach to provide the same ''Base software'':
:** The same code base is being built for all supported [[Wiki:GNU/Linux distribution|GNU/Linux distributions]].
:** Among 6 months Sucrose releases, there will be supported LTS releases.
:* [[Sugar Network]] for system approach to provide ''Content''.
:** That will include Sugar activities, the [[Platform_Team/Sweets|Sweets]] will take care about treating dependencies and [[Platform_Team/Open_Build_System|Open Build System]] will build binaries in automatic manner.
:* [[Sugar Network]] for system approach to provide ''Social activity'' for the ''Content''.
:* [[Sugar Network]] is designed to fulfill deployment needs like:
:** Supporting environments with limited, or absent, access to the Internet;
:** Adapt ''Content'' to local needs.