Activity Team - Revision history

Quozl: /* A typical update cycle */

2018-03-07T03:41:05Z

A typical update cycle

@@ Line 220: / Line 220: @@
 === A typical update cycle ===
-Anyone can contribute a patch to a Sugar Activity. The typical work cycle involves an interaction with the activity (project) maintainer as follows:
+Moved to https://github.com/sugarlabs/sugar-docs/blob/master/src/contributing.md#modifying-activities
 === OLPC XO game buttons ===

Davelab6: Walter will graduate this

2016-05-14T20:18:10Z

Walter will graduate this

← Older revision		Revision as of 16:18, 14 May 2016
Line 1:		Line 1:
			{{Graduate\|Walterbender will move this to http://developer.sugarlabs.org in 2016}}

	<noinclude><div class="noprint">{{TeamHeader\|Activity Team}}</div></noinclude>		<noinclude><div class="noprint">{{TeamHeader\|Activity Team}}</div></noinclude>

FGrose: /* Testers */ update link

2015-12-29T19:59:40Z

Testers: update link

← Older revision		Revision as of 15:59, 29 December 2015
Line 136:		Line 136:
	== Testers ==		== Testers ==

	Please see the [[~~Features~~/~~Soas_V4/ASLOxo_Activity_Test_Table\|~~Activity Test~~-table page~~]] for tester information.		Please see the [[Testing/Activity Test Table]] for tester information.

	== Background information ==		== Background information ==

Ignacio Rodríguez: /* Move an activity */

2014-12-02T20:49:18Z

Move an activity

← Older revision		Revision as of 16:49, 2 December 2014
Line 25:		Line 25:
	===Move an activity===		===Move an activity===

	We need help moving activities over to Sugar Labs from GitHub servers. This is a great way to get started helping out the Activity Team. See [[Activity Team/How to migrate from ~~Sugar Labs~~]] for instructions, and [[Activity Team/Activity Status]] for the list of activities that need to be moved.		We need help moving activities over to Sugar Labs from GitHub servers. This is a great way to get started helping out the Activity Team. See [[Activity Team/How to migrate from Gitorious]] for instructions, and [[Activity Team/Activity Status]] for the list of activities that need to be moved.

	While moving activities, it would be great to check that the .pot files are up to date and the MANIFEST is correct. This will really help out the distro packagers.		While moving activities, it would be great to check that the .pot files are up to date and the MANIFEST is correct. This will really help out the distro packagers.

FGrose at 19:07, 2 December 2014

2014-12-02T19:07:40Z

← Older revision		Revision as of 15:07, 2 December 2014
Line 25:		Line 25:
	===Move an activity===		===Move an activity===

	We need help moving activities over to Sugar Labs from GitHub servers. This is a great way to get started helping out the Activity Team. See [[Activity Team/~~How_to_migrate_from_SugarLabs~~]] for instructions, and [[Activity Team/Activity Status]] for the list of activities that need to be moved.		We need help moving activities over to Sugar Labs from GitHub servers. This is a great way to get started helping out the Activity Team. See [[Activity Team/How to migrate from Sugar Labs]] for instructions, and [[Activity Team/Activity Status]] for the list of activities that need to be moved.

	While moving activities, it would be great to check that the .pot files are up to date and the MANIFEST is correct. This will really help out the distro packagers.		While moving activities, it would be great to check that the .pot files are up to date and the MANIFEST is correct. This will really help out the distro packagers.

	== Set up ~~SugarLabs~~ services ==		== Set up Sugar Labs services ==
	* '''Upload a xo bundle''' to [http://activities.sugarlabs.org/ activities.sugarlabs.org]. Be sure to include a couple of screenshots of your activity in action.		* '''Upload a xo bundle''' to [http://activities.sugarlabs.org/ activities.sugarlabs.org]. Be sure to include a couple of screenshots of your activity in action.
	* If your activity is part of Fructose, '''upload a .tar.bz2''' to [http://download.sugarlabs.org/ download.sugarlabs.org]. Request a shell account from the [[Infrastructure Team]] if you don't have one already.		* If your activity is part of Fructose, '''upload a .tar.bz2''' to [http://download.sugarlabs.org/ download.sugarlabs.org]. Request a shell account from the [[Infrastructure Team]] if you don't have one already.
Line 44:		Line 44:
	===Migrating from GTK2 to GTK3===		===Migrating from GTK2 to GTK3===

	The Sugar platform is migrating from GTK2 to GTK3 to stay relevant with upstream changes and benefit from their efforts. Sugar 0.96 (available in OLPC 12.1 development builds) includes support for a transition period, where both GTK2 and GTK3 activities can coexists, but new Sugar features will only be added to the GTK3 toolkit (e.g. improvements in touchscreen support). Have a read through the [~~http://wiki.sugarlabs.org/go/~~Features/GTK3/Porting migration notes], and the [http://python-gtk-3-tutorial.readthedocs.org/en/latest/index.html GTK3 Python tutorials] to get a feel for how things need to be changed. New activities should be developed with GTK3, unless you need to support an existing deployment today using an older build.		The Sugar platform is migrating from GTK2 to GTK3 to stay relevant with upstream changes and benefit from their efforts. Sugar 0.96 (available in OLPC 12.1 development builds) includes support for a transition period, where both GTK2 and GTK3 activities can coexists, but new Sugar features will only be added to the GTK3 toolkit (e.g., improvements in touchscreen support). Have a read through the [[Features/GTK3/Porting\|migration notes]], and the [http://python-gtk-3-tutorial.readthedocs.org/en/latest/index.html GTK3 Python tutorials] to get a feel for how things need to be changed. New activities should be developed with GTK3, unless you need to support an existing deployment today using an older build.

	===Modify Activities===		===Modify Activities===
Line 92:		Line 92:
	;gitorious: software for hosting git repositories, including a web interface for administration		;gitorious: software for hosting git repositories, including a web interface for administration
	;git.sugarlabs.org: server hosted by Sugar Labs running gitorious		;git.sugarlabs.org: server hosted by Sugar Labs running gitorious
	;~~github~~: ~~sugarlabs~~ is ~~moving all repositories~~ to ~~GitHub, github = gitorious~~		;GitHub: a web-based hosting service Git repository. Sugar Labs is migrating projects to this service.

	====Setup====		====Setup====
Line 119:		Line 119:
	So if you ever mess up and don't know how to fix it yourself, please		So if you ever mess up and don't know how to fix it yourself, please
	stop (at least for me that's usually the hardest part ;) ), try to		stop (at least for me that's usually the hardest part ;) ), try to
	recollect the exact sequence of actions (e.g. from shell history) and ask		recollect the exact sequence of actions (e.g., from shell history) and ask
	for help.		for help.

Line 169:		Line 169:
	===Mime types and file suffixes===		===Mime types and file suffixes===

	You can associate your activity with mime types by including a mime_types entry in the activity/activity.info file; e.g.		You can associate your activity with mime types by including a mime_types entry in the activity/activity.info file; e.g.,

	mime_types = text/plain;text/x-python;text/x-logo;text/x-svg;application/xml;text/html;text/xml;image/svg+xml		mime_types = text/plain;text/x-python;text/x-logo;text/x-svg;application/xml;text/html;text/xml;image/svg+xml

Ignacio Rodríguez: /* glossary */

2014-12-02T18:28:52Z

glossary

← Older revision		Revision as of 14:28, 2 December 2014
Line 92:		Line 92:
	;gitorious: software for hosting git repositories, including a web interface for administration		;gitorious: software for hosting git repositories, including a web interface for administration
	;git.sugarlabs.org: server hosted by Sugar Labs running gitorious		;git.sugarlabs.org: server hosted by Sugar Labs running gitorious
			;github: sugarlabs is moving all repositories to GitHub, github = gitorious

	====Setup====		====Setup====

Ignacio Rodríguez: /* Move an activity */

2014-12-02T18:26:03Z

Move an activity

← Older revision		Revision as of 14:26, 2 December 2014
Line 25:		Line 25:
	===Move an activity===		===Move an activity===

	We need help moving activities over to Sugar Labs from ~~OLPC's~~ servers. This is a great way to get started helping out the Activity Team. See [[Activity Team/~~How_to_migrate_from_OLPC~~]] for instructions, and [[Activity Team/Activity Status]] for the list of activities that need to be moved.		We need help moving activities over to Sugar Labs from GitHub servers. This is a great way to get started helping out the Activity Team. See [[Activity Team/How_to_migrate_from_SugarLabs]] for instructions, and [[Activity Team/Activity Status]] for the list of activities that need to be moved.

	While moving activities, it would be great to check that the .pot files are up to date and the MANIFEST is correct. This will really help out the distro packagers.		While moving activities, it would be great to check that the .pot files are up to date and the MANIFEST is correct. This will really help out the distro packagers.

			== Set up SugarLabs services ==
			* '''Upload a xo bundle''' to [http://activities.sugarlabs.org/ activities.sugarlabs.org]. Be sure to include a couple of screenshots of your activity in action.
			* If your activity is part of Fructose, '''upload a .tar.bz2''' to [http://download.sugarlabs.org/ download.sugarlabs.org]. Request a shell account from the [[Infrastructure Team]] if you don't have one already.
			* '''Update the OLPC wiki page''' for the Activity, noting the migration. Use the [http://wiki.laptop.org/go/Template:Migrated_to_sl.o Migrated to sl.o] template.
			* '''Change sugar-jhbuild''' to point to the new repository if this activity was included in sugar-jhbuild (enter a ticket in http://dev.sugarlabs.org if you have no access).
			* Ask an [[Activity Team/Contacts\|Activity Team Coordinator]] to create a '''Trac component''' for your activity.

	===Cross-platform compatibility===		===Cross-platform compatibility===

Ignacio Rodríguez: /* Problems logging in to Gitorious? */ <- NO problemas with GitHub.

2014-12-02T18:17:13Z

Problems logging in to Gitorious?: <- NO problemas with GitHub.

← Older revision		Revision as of 14:17, 2 December 2014
Line 18:		Line 18:

	See [[Automated Activity Testing]]		See [[Automated Activity Testing]]

	~~=== Problems logging in to Gitorious? ===~~

	Gitorious users are sometimes having their IP addresses incorrectly blacklisted at http://git.sugarlabs.org/. If your SSH key is rejected with the error "Access denied or bad repository path", please open a ticket by emailing git AT sugarlabs DOT org.

	===Port to GTK3===		===Port to GTK3===

Ignacio Rodríguez: /* Setup */ -> Github

2014-12-02T18:16:30Z

Setup: -> Github

← Older revision		Revision as of 14:16, 2 December 2014
Line 92:		Line 92:
	====Setup====		====Setup====
	(Once per machine you're working on)		(Once per machine you're working on)
	git clone git://~~git~~.~~sugarlabs.org~~/whatever/mainline.git whatever		git clone git://github.com/whatever/mainline.git whatever

	====Regular usage====		====Regular usage====

Svineet at 15:55, 7 January 2014

2014-01-07T15:55:19Z

← Older revision		Revision as of 11:55, 7 January 2014
Line 14:		Line 14:

	See [[Activity Team/Creating a New Activity\|Creating a New Activity]] and [[Activity Team/Resources\|Activity Team Resources]].		See [[Activity Team/Creating a New Activity\|Creating a New Activity]] and [[Activity Team/Resources\|Activity Team Resources]].

			=== Automated Testing ===

			See [[Automated Activity Testing]]

	=== Problems logging in to Gitorious? ===		=== Problems logging in to Gitorious? ===