Features/Host Version - Revision history

FGrose at 05:56, 18 October 2009

2009-10-18T05:56:45Z

← Older revision		Revision as of 01:56, 18 October 2009
Line 1:		Line 1:
	<noinclude>{{GoogleTrans-en}}{{TOCright}}</noinclude>		<noinclude>{{GoogleTrans-en}}{{TOCright}}
			[[Category:Feature Page Incomplete]]
			[[Category:Feature\|Host Version]]</noinclude>

	== Summary ==		== Summary ==
Line 14:		Line 16:

	== Detailed Description ==		== Detailed Description ==
	With 0.86 being on the ~~horizont~~, 0.84 being used on SoaS, 0.82 being widely used among the G1G1 community and some deployments and many deployment still using pre-0.82 software I think the issue of activity compatibility deserves some serious attention. Otherwise this has the potential to create '''a lot of confusion''' and frustration further down the road (especially with things like the XO-1.5 that supports 3D acceleration on the ~~horizont~~).		With 0.86 being on the horizon, 0.84 being used on SoaS, 0.82 being widely used among the G1G1 community and some deployments and many deployment still using pre-0.82 software I think the issue of activity compatibility deserves some serious attention. Otherwise this has the potential to create '''a lot of confusion''' and frustration further down the road (especially with things like the XO-1.5 that supports 3D acceleration on the horizon).

	: Not sure what the original plans wrt the technical implemention of this feature were but I would assume the harder part of solving this problem is spreading the word among activity developers to update their .xo bundles accordingly.		: Not sure what the original plans wrt the technical implemention of this feature were but I would assume the harder part of solving this problem is spreading the word among activity developers to update their .xo bundles accordingly.
Line 24:		Line 26:
	== Benefit to Sugar ==		== Benefit to Sugar ==
	* avoid user confusion as to why some activities might potentially not work on the currently installed OS.		* avoid user confusion as to why some activities might potentially not work on the currently installed OS.
	* identify activity ~~developres~~ who don't know about compatibility issues and the importance of testing on specific versions of Sugar (they won't have updated their default .info file)		* identify activity developers who don't know about compatibility issues and the importance of testing on specific versions of Sugar (they won't have updated their default .info file)


Line 53:		Line 55:
	* See [[{{TALKPAGENAME}}\|discussion tab for this feature]]		* See [[{{TALKPAGENAME}}\|discussion tab for this feature]]

	~~[[Category:Feature Page Incomplete]]~~
	~~[[Category:Feature]]~~
	----		----
	''You can add categories to tie features back to real deployments/schools requesting them, for example <nowiki>[[</nowiki>Category:Features requested by School Xyz]]''		''You can add categories to tie features back to real deployments/schools requesting them, for example <nowiki>[[</nowiki>Category:Features requested by School Xyz]]''

ChristophD at 09:15, 21 July 2009

2009-07-21T09:15:52Z

← Older revision		Revision as of 05:15, 21 July 2009
Line 18:		Line 18:
	: Not sure what the original plans wrt the technical implemention of this feature were but I would assume the harder part of solving this problem is spreading the word among activity developers to update their .xo bundles accordingly.		: Not sure what the original plans wrt the technical implemention of this feature were but I would assume the harder part of solving this problem is spreading the word among activity developers to update their .xo bundles accordingly.
	:: iirc, the original idea was roughly to have a monotonically increasing series of host #s which would define the point in the sugar devolution when the activity was finished and tested, with the idea that a later version of Sugar would be likely to run an older activity but not vice versa. If you are thinking in terms of 'on which of six platforms has this been tested' then this .info field may not be ideally suited to the task. [[User:Sj\|+sj]] [[User Talk:Sj\|<font color="#ff6996">+</font>]]		:: iirc, the original idea was roughly to have a monotonically increasing series of host #s which would define the point in the sugar devolution when the activity was finished and tested, with the idea that a later version of Sugar would be likely to run an older activity but not vice versa. If you are thinking in terms of 'on which of six platforms has this been tested' then this .info field may not be ideally suited to the task. [[User:Sj\|+sj]] [[User Talk:Sj\|<font color="#ff6996">+</font>]]
	::: Mmm, that's a very good point. Do we want to distinguish just between progressing versions or also between different flavors of the same version?		::: Mmm, that's a very good point. Do we want to distinguish just between progressing versions or also between different flavors of the same version? [[User:ChristophD\|ChristophD]]]
	[[User:ChristophD\|ChristophD]]]

	Someone, preferably the activity authors themselves, would need to check activities against the various Sugar versions which are in use and document their findings. This however could also be a nice entry-level task for people who want to start contributing to Sugar.		Someone, preferably the activity authors themselves, would need to check activities against the various Sugar versions which are in use and document their findings. This however could also be a nice entry-level task for people who want to start contributing to Sugar.

ChristophD: added comment

2009-07-21T09:13:12Z

added comment

← Older revision		Revision as of 05:13, 21 July 2009
Line 18:		Line 18:
	: Not sure what the original plans wrt the technical implemention of this feature were but I would assume the harder part of solving this problem is spreading the word among activity developers to update their .xo bundles accordingly.		: Not sure what the original plans wrt the technical implemention of this feature were but I would assume the harder part of solving this problem is spreading the word among activity developers to update their .xo bundles accordingly.
	:: iirc, the original idea was roughly to have a monotonically increasing series of host #s which would define the point in the sugar devolution when the activity was finished and tested, with the idea that a later version of Sugar would be likely to run an older activity but not vice versa. If you are thinking in terms of 'on which of six platforms has this been tested' then this .info field may not be ideally suited to the task. [[User:Sj\|+sj]] [[User Talk:Sj\|<font color="#ff6996">+</font>]]		:: iirc, the original idea was roughly to have a monotonically increasing series of host #s which would define the point in the sugar devolution when the activity was finished and tested, with the idea that a later version of Sugar would be likely to run an older activity but not vice versa. If you are thinking in terms of 'on which of six platforms has this been tested' then this .info field may not be ideally suited to the task. [[User:Sj\|+sj]] [[User Talk:Sj\|<font color="#ff6996">+</font>]]
			::: Mmm, that's a very good point. Do we want to distinguish just between progressing versions or also between different flavors of the same version?
			[[User:ChristophD\|ChristophD]]]

	Someone, preferably the activity authors themselves, would need to check activities against the various Sugar versions which are in use and document their findings. This however could also be a nice entry-level task for people who want to start contributing to Sugar.		Someone, preferably the activity authors themselves, would need to check activities against the various Sugar versions which are in use and document their findings. This however could also be a nice entry-level task for people who want to start contributing to Sugar.

Sj: notes

2009-07-21T09:03:47Z

notes

← Older revision		Revision as of 05:03, 21 July 2009
Line 2:		Line 2:

	== Summary ==		== Summary ==
	Using "hosts" variable in the activity.info ~~files~~ to ~~determine whether~~ an activity ~~runs on the specific Sugar installation~~.		Using the "hosts" variable in the activity.info file to define the Sugar version for which an activity was designed and tested.

	== Owner ==		== Owner ==
Line 14:		Line 14:

	== Detailed Description ==		== Detailed Description ==
	With 0.86 being on the horizont, 0.84 being used on SoaS, 0.82 being widely used among the G1G1 community and some deployments and many deployment still using pre-0.82 software I think the issue of activity compatibility deserves some serious attention. Otherwise this has the potential to create _a lot ~~of_~~ confusion and frustration further down the road (especially with things like the XO-1.5 that supports 3D acceleration on the horizont).		With 0.86 being on the horizont, 0.84 being used on SoaS, 0.82 being widely used among the G1G1 community and some deployments and many deployment still using pre-0.82 software I think the issue of activity compatibility deserves some serious attention. Otherwise this has the potential to create '''a lot of confusion''' and frustration further down the road (especially with things like the XO-1.5 that supports 3D acceleration on the horizont).

	Not sure what the original plans wrt the technical implemention of this feature were but I would assume the harder part of solving this problem is spreading the word among activity developers to update their .xo bundles accordingly.		: Not sure what the original plans wrt the technical implemention of this feature were but I would assume the harder part of solving this problem is spreading the word among activity developers to update their .xo bundles accordingly.
			:: iirc, the original idea was roughly to have a monotonically increasing series of host #s which would define the point in the sugar devolution when the activity was finished and tested, with the idea that a later version of Sugar would be likely to run an older activity but not vice versa. If you are thinking in terms of 'on which of six platforms has this been tested' then this .info field may not be ideally suited to the task. [[User:Sj\|+sj]] [[User Talk:Sj\|<font color="#ff6996">+</font>]]

	Someone, preferably the activity authors themselves, would need to check activities against the various Sugar versions which are in use and document their findings. This however could also be a nice entry-level task for people who want to start contributing to Sugar.		Someone, preferably the activity authors themselves, would need to check activities against the various Sugar versions which are in use and document their findings. This however could also be a nice entry-level task for people who want to start contributing to Sugar.

	== Benefit to Sugar ==		== Benefit to Sugar ==
	~~Avoids~~ user confusion as to why some activities might potentially not work on the currently installed OS.		* avoid user confusion as to why some activities might potentially not work on the currently installed OS.
			* identify activity developres who don't know about compatibility issues and the importance of testing on specific versions of Sugar (they won't have updated their default .info file)


	== Scope ==		== Scope ==
Line 31:		Line 34:
	== User Experience ==		== User Experience ==
	Depends on the implementation but one way could be to fail gracefully by showing a warning when an activity that doesn't work on the specific Sugar version is downloaded/run. The warning message could also include information or a link to information on how to update the XO to the latest version.		Depends on the implementation but one way could be to fail gracefully by showing a warning when an activity that doesn't work on the specific Sugar version is downloaded/run. The warning message could also include information or a link to information on how to update the XO to the latest version.

			Also, the ability to sort a.sl.o activities by host.

	== Dependencies ==		== Dependencies ==

ChristophD at 08:54, 21 July 2009

2009-07-21T08:54:20Z

← Older revision		Revision as of 04:54, 21 July 2009
Line 14:		Line 14:

	== Detailed Description ==		== Detailed Description ==
	With 0.86 being on the horizont, 0.84 being used on SoaS, 0.82 being widely used among the G1G1 community and some deployments and many deployment still using pre-0.82 software I think the issue of activity compatibility deserves some serious attention. Otherwise this has the potential to create _a lot of_ confusion and frustration further down the road.		With 0.86 being on the horizont, 0.84 being used on SoaS, 0.82 being widely used among the G1G1 community and some deployments and many deployment still using pre-0.82 software I think the issue of activity compatibility deserves some serious attention. Otherwise this has the potential to create _a lot of_ confusion and frustration further down the road (especially with things like the XO-1.5 that supports 3D acceleration on the horizont).

	Not sure what the original plans wrt the technical implemention of this feature were but I would assume the harder part of solving this problem is spreading the word among activity developers to update their .xo bundles accordingly.		Not sure what the original plans wrt the technical implemention of this feature were but I would assume the harder part of solving this problem is spreading the word among activity developers to update their .xo bundles accordingly.
Line 21:		Line 21:

	== Benefit to Sugar ==		== Benefit to Sugar ==
			Avoids user confusion as to why some activities might potentially not work on the currently installed OS.

	~~''What is the benefit~~ to the platform? If this is a major capability update, what has changed? If this is a new feature, what capabilities does it bring? Why will Sugar become a better platform or project because of this feature?''

	== Scope ==		== Scope ==

ChristophD at 08:50, 21 July 2009

2009-07-21T08:50:21Z

← Older revision		Revision as of 04:50, 21 July 2009
Line 17:		Line 17:

	Not sure what the original plans wrt the technical implemention of this feature were but I would assume the harder part of solving this problem is spreading the word among activity developers to update their .xo bundles accordingly.		Not sure what the original plans wrt the technical implemention of this feature were but I would assume the harder part of solving this problem is spreading the word among activity developers to update their .xo bundles accordingly.

			Someone, preferably the activity authors themselves, would need to check activities against the various Sugar versions which are in use and document their findings. This however could also be a nice entry-level task for people who want to start contributing to Sugar.

	== Benefit to Sugar ==		== Benefit to Sugar ==
Line 24:		Line 26:

	== Scope ==		== Scope ==
	''What work do the developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?''		TBD

	== How To Test ==		== How To Test ==
	''This does not need to be a full-fledged document. Describe the dimensions of tests that this feature is expected to pass when it is done. If it needs to be tested with different hardware or software configurations, indicate them. The more specific you can be, the better the community testing can be.''		TBD

	''Remember that you are writing this how to for interested testers to use to check out your feature - documenting what you do for testing is OK, but it's much better to document what I can do to test your feature.''

	~~''A good "how to test" should answer these four questions:''~~

	* ''What special hardware / data / etc. is needed (if any)?
	* ''How do I prepare my system to test this feature? What packages need to be installed, config files edited, etc.?
	* ''What specific actions do I perform to check that the feature is working like it's supposed to?
	* ''What are the expected results of those actions?''

	== User Experience ==		== User Experience ==

ChristophD at 08:46, 21 July 2009

2009-07-21T08:46:04Z

← Older revision		Revision as of 04:46, 21 July 2009
Line 2:		Line 2:

	== Summary ==		== Summary ==
	~~''A sentence or two summarizing what this feature is and what it will do~~. ~~This information is used for~~ the ~~overall feature summary page for each release~~.''		Using "hosts" variable in the activity.info files to determine whether an activity runs on the specific Sugar installation.

	== Owner ==		== Owner ==
	* Name: [[User:ChristophD\| Christoph Derndorfer]]		* Name: [[User:ChristophD\| Christoph Derndorfer]]

	* Email: christoph AT olpcnews DOT com		* Email: christoph AT olpcnews DOT com

Line 15:		Line 14:

	== Detailed Description ==		== Detailed Description ==
	~~''Expand~~ on the ~~summary~~, ~~if appropriate~~. ~~A couple sentences suffices~~ to ~~explain~~ the ~~goal,~~ but the ~~more details you can provide~~ the ~~better~~.''		With 0.86 being on the horizont, 0.84 being used on SoaS, 0.82 being widely used among the G1G1 community and some deployments and many deployment still using pre-0.82 software I think the issue of activity compatibility deserves some serious attention. Otherwise this has the potential to create _a lot of_ confusion and frustration further down the road.

			Not sure what the original plans wrt the technical implemention of this feature were but I would assume the harder part of solving this problem is spreading the word among activity developers to update their .xo bundles accordingly.

	== Benefit to Sugar ==		== Benefit to Sugar ==


	''What is the benefit to the platform? If this is a major capability update, what has changed? If this is a new feature, what capabilities does it bring? Why will Sugar become a better platform or project because of this feature?''		''What is the benefit to the platform? If this is a major capability update, what has changed? If this is a new feature, what capabilities does it bring? Why will Sugar become a better platform or project because of this feature?''

Line 36:		Line 39:

	== User Experience ==		== User Experience ==
	'~~'If this feature~~ is ~~noticeable by its target audience,~~ how ~~will their experiences change as a result? Describe what they will see or notice~~.''		Depends on the implementation but one way could be to fail gracefully by showing a warning when an activity that doesn't work on the specific Sugar version is downloaded/run. The warning message could also include information or a link to information on how to update the XO to the latest version.

	== Dependencies ==		== Dependencies ==
	''What other packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this feature depends? In other words, completion of another feature owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate? Other upstream projects like python?''		TBD

	== Contingency Plan ==		== Contingency Plan ==
	~~''If you cannot complete your feature by the final development freeze, what is the backup plan? This might be as simple as "~~None ~~necessary, revert to previous release behaviour." Or it might not. If you feature is not completed in time we want to assure others that other parts of Sugar will not be in jeopardy.''~~		None yet

	== Documentation ==		== Documentation ==
	~~''Is there upstream documentation on this feature, or notes you have written yourself? Link to that material here so other interested developers can get involved.''~~		None yet

	== Release Notes ==		== Release Notes ==
	''The Sugar Release Notes inform end-users about what is new in the release. An Example is [[0.84/Notes]]. The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns. If there are any such changes involved in this feature, indicate them here. You can also link to upstream documentation if it satisfies this need. This information forms the basis of the release notes edited by the release team and shipped with the release.''		TBD

	== Comments and Discussion ==		== Comments and Discussion ==
	* See [[{{TALKPAGENAME}}\|discussion tab for this feature]] ~~<!-- This adds a link to the "discussion" tab associated with your page. This provides the ability to have ongoing comments or conversation without bogging down the main feature page -->~~		* See [[{{TALKPAGENAME}}\|discussion tab for this feature]]


	[[Category:Feature Page Incomplete]]		[[Category:Feature Page Incomplete]]

ChristophD: Created page with '{{GoogleTrans-en}}{{TOCright}} == Summary == ''A sentence or two summarizing what this feature is and what it will do. This information is used for the ov…'

2009-07-21T08:35:12Z

Created page with '<noinclude>{{GoogleTrans-en}}{{TOCright}}</noinclude> == Summary == ''A sentence or two summarizing what this feature is and what it will do. This information is used for the ov…'

New page

<noinclude>{{GoogleTrans-en}}{{TOCright}}</noinclude>

== Summary ==
''A sentence or two summarizing what this feature is and what it will do. This information is used for the overall feature summary page for each release.''

== Owner ==
* Name: [[User:ChristophD| Christoph Derndorfer]]

* Email: christoph AT olpcnews DOT com

== Current status ==
* Targeted release: 0.86
* Last updated: 2009-07-21
* Percentage of completion: 0%

== Detailed Description ==
''Expand on the summary, if appropriate. A couple sentences suffices to explain the goal, but the more details you can provide the better.''

== Benefit to Sugar ==
''What is the benefit to the platform? If this is a major capability update, what has changed? If this is a new feature, what capabilities does it bring? Why will Sugar become a better platform or project because of this feature?''

== Scope ==
''What work do the developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?''

== How To Test ==
''This does not need to be a full-fledged document. Describe the dimensions of tests that this feature is expected to pass when it is done. If it needs to be tested with different hardware or software configurations, indicate them. The more specific you can be, the better the community testing can be.''

''Remember that you are writing this how to for interested testers to use to check out your feature - documenting what you do for testing is OK, but it's much better to document what *I* can do to test your feature.''

''A good "how to test" should answer these four questions:''

* ''What special hardware / data / etc. is needed (if any)?
* ''How do I prepare my system to test this feature? What packages need to be installed, config files edited, etc.?
* ''What specific actions do I perform to check that the feature is working like it's supposed to?
* ''What are the expected results of those actions?''

== User Experience ==
''If this feature is noticeable by its target audience, how will their experiences change as a result? Describe what they will see or notice.''

== Dependencies ==
''What other packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this feature depends? In other words, completion of another feature owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate? Other upstream projects like python?''

== Contingency Plan ==
''If you cannot complete your feature by the final development freeze, what is the backup plan? This might be as simple as "None necessary, revert to previous release behaviour." Or it might not. If you feature is not completed in time we want to assure others that other parts of Sugar will not be in jeopardy.''

== Documentation ==
''Is there upstream documentation on this feature, or notes you have written yourself? Link to that material here so other interested developers can get involved.''

== Release Notes ==
''The Sugar Release Notes inform end-users about what is new in the release. An Example is [[0.84/Notes]]. The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns. If there are any such changes involved in this feature, indicate them here. You can also link to upstream documentation if it satisfies this need. This information forms the basis of the release notes edited by the release team and shipped with the release.''

== Comments and Discussion ==
* See [[{{TALKPAGENAME}}|discussion tab for this feature]] 

[[Category:Feature Page Incomplete]]
[[Category:Feature]]
----
''You can add categories to tie features back to real deployments/schools requesting them, for example <nowiki>[[</nowiki>Category:Features requested by School Xyz]]''