Activity Library/Editors/Policy - Revision history

FGrose: categorize

2011-11-01T15:11:08Z

categorize

← Older revision		Revision as of 11:11, 1 November 2011
Line 1:		Line 1:
	{{draft}}		<noinclude>[[Category:Policy]]</noinclude>{{draft}}

	== Technical policy ==		== Technical policy ==

Alsroot: /* Guidelines for accepting an activity */

2011-09-26T11:29:38Z

Guidelines for accepting an activity

← Older revision		Revision as of 07:29, 26 September 2011
Line 46:		Line 46:
	* Must have I18n support (i.e gettext generated .POT with ./setup.py genpot)		* Must have I18n support (i.e gettext generated .POT with ./setup.py genpot)
	--[[User:RafaelOrtiz\|RafaelOrtiz]] 20:48, 18 February 2011 (EST) We must focus in testing for diferent versions of sugar, olpc. soas an use different sugar versions, generally newer than Sugar 0.82		--[[User:RafaelOrtiz\|RafaelOrtiz]] 20:48, 18 February 2011 (EST) We must focus in testing for diferent versions of sugar, olpc. soas an use different sugar versions, generally newer than Sugar 0.82

			----

			Sorry, but keeping all these "Must"s, what ASLO is supposed to be? A place to host activities developed by well skilled coders, QAed by well skilled engineers, released by well skilled project managers? Is it about Sugar or something else? If I got Sugar purpose right, Sugar is about learning via doing, it is mostly impossible to do something well formed right after starting. ASLO should respect experimenters and their decision about quality (ready to share) of the code. At the same time, there are bunch of side ways how to mark activities that satisfy all these "Must"s - editors pick up and special collections. [[User:Alsroot\|alsroot]] 07:29, 26 September 2011 (EDT)

	== Non-technical policy ==		== Non-technical policy ==

Alsroot: /* Technical policy */ Thats a draft, so it is all about new workflows

2011-09-15T12:46:43Z

Technical policy: Thats a draft, so it is all about new workflows

← Older revision		Revision as of 08:46, 15 September 2011
Line 3:		Line 3:
	== Technical policy ==		== Technical policy ==

	All technical checks will happen [[Platform_Team/Recipe_Lint\|automatically]] while uploading activities.~~(But for now ASLO doesn't check them all.)~~		All technical checks will happen [[Platform_Team/Recipe_Lint\|automatically]] while uploading activities.

	== Guidelines for accepting an activity ==		== Guidelines for accepting an activity ==

RafaelOrtiz: /* Guidelines for accepting an activity */

2011-02-22T18:36:19Z

Guidelines for accepting an activity

← Older revision		Revision as of 14:36, 22 February 2011
Line 44:		Line 44:
	** Who tests on SoaS and what version?		** Who tests on SoaS and what version?
	* Must tell user if the activity is using web? collecting user data?		* Must tell user if the activity is using web? collecting user data?
			* Must have I18n support (i.e gettext generated .POT with ./setup.py genpot)
	--[[User:RafaelOrtiz\|RafaelOrtiz]] 20:48, 18 February 2011 (EST) We must focus in testing for diferent versions of sugar, olpc. soas an use different sugar versions, generally newer than Sugar 0.82		--[[User:RafaelOrtiz\|RafaelOrtiz]] 20:48, 18 February 2011 (EST) We must focus in testing for diferent versions of sugar, olpc. soas an use different sugar versions, generally newer than Sugar 0.82

RafaelOrtiz: /* Guidelines for accepting an activity */

2011-02-19T01:48:57Z

Guidelines for accepting an activity

← Older revision		Revision as of 21:48, 18 February 2011
Line 40:		Line 40:
	** Must be categorised correctly		** Must be categorised correctly
	* Versions of Sugar		* Versions of Sugar
	** Do we assume the developer has tested on all versions they say it works on?		** Do we assume the developer has tested on all versions they say it works on? --[[User:RafaelOrtiz\|RafaelOrtiz]] 20:48, 18 February 2011 (EST) At least that he sets the flag correctly on ASLO.
	** Tester approving activity tests on olpc stable builds?		** Tester approving activity tests on olpc stable builds?
	** Who tests on SoaS and what version?		** Who tests on SoaS and what version?
	* Must tell user if the activity is using web? collecting user data?		* Must tell user if the activity is using web? collecting user data?
			--[[User:RafaelOrtiz\|RafaelOrtiz]] 20:48, 18 February 2011 (EST) We must focus in testing for diferent versions of sugar, olpc. soas an use different sugar versions, generally newer than Sugar 0.82

	== Non-technical policy ==		== Non-technical policy ==

RafaelOrtiz: /* Guidelines for accepting an activity */

2011-02-19T01:37:02Z

Guidelines for accepting an activity

← Older revision		Revision as of 21:37, 18 February 2011
Line 7:		Line 7:
	== Guidelines for accepting an activity ==		== Guidelines for accepting an activity ==

	* Must Start/Stop cleanly		* ''Must Start/Stop cleanly''
	** When stopping must stop gracefully - not stay in memory.		** When stopping must stop gracefully - not stay in memory.
	* CPU and Memory usage		* ''CPU and Memory usage''
	** Usage must be proportional to functionality		** Usage must be proportional to functionality
	** Must not completely tie up the machine		** Must not completely tie up the machine
	* Interface		* ''Interface''
	** Conform to Sugar standards?		** Conform to Sugar standards?
	** Icons to meet sugar colour guidelines		** Icons to meet sugar colour guidelines
	** Frame key must work from within the activity		** Frame key must work from within the activity
	** Must fit within screen size of the XO’s		** Must fit within screen size of the XO’s
	* Journal		* ''Journal''
	** Is there save functionality and does it interact with the Journal well?		** Is there save functionality and does it interact with the Journal well?
	** Are file types registered with SugarOS correctly?		** Are file types registered with SugarOS correctly?
	* Checks		* ''Checks''
	** Black and white (high contrast screen)		** Black and white (high contrast screen)
	** Sound		** Sound
Line 30:		Line 30:
	***Maximum number of collaborators		***Maximum number of collaborators
	***Test with 3 or more?		***Test with 3 or more?
	* Bugs (for updated activities)		* ''Bugs (for updated activities)''
	** Are there any regressions in old functionality?		** Are there any regressions in old functionality?
	** How functional is new functionality?		** How functional is new functionality?
	* Download size of application must be reasonable compared to		* ''Download size of application must be reasonable compared to similar applications''
	** similar applications
	** functionality		** functionality
	* For activities webpage		* ''For activities webpage''
	** Must have reasonable explanation of purpose for the “more about this activity” field		** Must have reasonable explanation of purpose for the “more about this activity” field
	** Must have release notes		** Must have release notes

RafaelOrtiz: /* Technical policy */

2011-02-19T01:07:33Z

Technical policy

@@ Line 3: / Line 3: @@
 == Technical policy ==
-All technical checks will happen [[Platform_Team/Recipe_Lint|automatically]] while uploading activities.
+All technical checks will happen [[Platform_Team/Recipe_Lint|automatically]] while uploading activities.(But for now ASLO doesn't check them all.)
 == Non-technical policy ==

RafaelOrtiz: /* Guidelines for accepting an activity */

2011-02-19T01:06:02Z

Guidelines for accepting an activity

@@ Line 7: / Line 7: @@
 == Non-technical policy ==
 {{:{{PAGENAME}}/Non-Technical}}
 == Resources ==

Tabitha: /* Guidelines for accepting an activity */

2011-02-19T00:29:29Z

Guidelines for accepting an activity

← Older revision		Revision as of 20:29, 18 February 2011
Line 26:		Line 26:
	** Black and white (high contrast screen)		** Black and white (high contrast screen)
	** Sound		** Sound
	+ Does sound behave?		***Does sound behave?
	# Stutter		****Stutter
	# lock up sound card		****lock up sound card
	** Collaboration		** Collaboration
	+ Must work if button is there		***Must work if button is there
	+ Maximum number of collaborators		***Maximum number of collaborators
	+ Test with 3 or more?		***Test with 3 or more?
	* Bugs (for updated activities)		* Bugs (for updated activities)
	** Are there any regressions in old functionality?		** Are there any regressions in old functionality?

Tabitha: /* Guidelines for accepting an activity */

2011-02-19T00:27:02Z

Guidelines for accepting an activity

← Older revision		Revision as of 20:27, 18 February 2011
Line 11:		Line 11:

	* Must Start/Stop cleanly		* Must Start/Stop cleanly
	oo When stopping must stop gracefully - not stay in memory.		** When stopping must stop gracefully - not stay in memory.
	* CPU and Memory usage		* CPU and Memory usage
	oo Usage must be proportional to functionality		** Usage must be proportional to functionality
	oo Must not completely tie up the machine		** Must not completely tie up the machine
	* Interface		* Interface
	oo Conform to Sugar standards?		** Conform to Sugar standards?
	oo Icons to meet sugar colour guidelines		** Icons to meet sugar colour guidelines
	oo Frame key must work from within the activity		** Frame key must work from within the activity
	oo Must fit within screen size of the XO’s		** Must fit within screen size of the XO’s
	* Journal		* Journal
	oo Is there save functionality and does it interact with the Journal well?		** Is there save functionality and does it interact with the Journal well?
	oo Are file types registered with SugarOS correctly?		** Are file types registered with SugarOS correctly?
	* Checks		* Checks
	oo Black and white (high contrast screen)		** Black and white (high contrast screen)
	oo Sound		** Sound
	+ Does sound behave?		+ Does sound behave?
	# Stutter		# Stutter
	# lock up sound card		# lock up sound card
	oo Collaboration		** Collaboration
	+ Must work if button is there		+ Must work if button is there
	+ Maximum number of collaborators		+ Maximum number of collaborators
	+ Test with 3 or more?		+ Test with 3 or more?
	* Bugs (for updated activities)		* Bugs (for updated activities)
	oo Are there any regressions in old functionality?		** Are there any regressions in old functionality?
	oo How functional is new functionality?		** How functional is new functionality?
	* Download size of application must be reasonable compared to		* Download size of application must be reasonable compared to
	oo similar applications		** similar applications
	oo functionality		** functionality
	* For activities webpage		* For activities webpage
	oo Must have reasonable explanation of purpose for the “more about this activity” field		** Must have reasonable explanation of purpose for the “more about this activity” field
	oo Must have release notes		** Must have release notes
	oo Must be categorised correctly		** Must be categorised correctly
	* Versions of Sugar		* Versions of Sugar
	oo Do we assume the developer has tested on all versions they say it works on?		** Do we assume the developer has tested on all versions they say it works on?
	oo Tester approving activity tests on olpc stable builds?		** Tester approving activity tests on olpc stable builds?
	oo Who tests on SoaS and what version?		** Who tests on SoaS and what version?
	* Must tell user if the activity is using web? collecting user data?		* Must tell user if the activity is using web? collecting user data?