Google Code In 2017/background - Revision history

Quozl at 22:13, 1 December 2017

2017-12-01T22:13:13Z

← Older revision		Revision as of 18:13, 1 December 2017
Line 5:		Line 5:
	=== Setting up a Sugarizer environment ===		=== Setting up a Sugarizer environment ===

	Use your computer.		Use your computer. See also [[#Getting started with Sugarizer]].

	=== Setting up a Sugar desktop environment ===		=== Setting up a Sugar desktop environment ===

Quozl: lionel points out that setting up sugar desktop environment not necessary for sugarizer, so move that to separate section.

2017-12-01T22:12:03Z

lionel points out that setting up sugar desktop environment not necessary for sugarizer, so move that to separate section.

← Older revision		Revision as of 18:12, 1 December 2017
Line 3:		Line 3:
	Read [[Attribution and Licensing]], as both are important for all submissions.		Read [[Attribution and Licensing]], as both are important for all submissions.

	=== Setting up ~~the Sugar~~ environment ===		=== Setting up a Sugarizer environment ===

	There are several options for setting up the Sugar environment for development, depending on what equipment you have;		Use your computer.

			=== Setting up a Sugar desktop environment ===

			There are several options for setting up the Sugar desktop environment for development, depending on what equipment you have;

	{\| class="wikitable"		{\| class="wikitable"
Line 14:		Line 18:
	\| Linux, Windows, macOS, or iOS		\| Linux, Windows, macOS, or iOS
	\| Install virtualisation software, make a new virtual machine and install [[Live Build\|Sugar Live Build]], [[SoaS\|Sugar on a Stick]], [[Ubuntu]], [[Fedora]], or [[Debian]].		\| Install virtualisation software, make a new virtual machine and install [[Live Build\|Sugar Live Build]], [[SoaS\|Sugar on a Stick]], [[Ubuntu]], [[Fedora]], or [[Debian]].
	~~For Sugarizer, your could use your computer.~~
	\|-		\|-
	\| Linux		\| Linux
Line 44:		Line 47:
	! Works as a Virtual Machine		! Works as a Virtual Machine
	\| yes \|\| yes \|\| yes		\| yes \|\| yes \|\| yes
	\|-
	~~! Good for Sugarizer development~~
	~~\| colspan="3" \| no, use your normal computer~~
	\|}		\|}

Llaske: Specify Sugarizer pre-requisite

2017-12-01T21:10:25Z

Specify Sugarizer pre-requisite

← Older revision		Revision as of 17:10, 1 December 2017
Line 13:		Line 13:
	\| rowspan="2" \| You have only one computer and don't want to erase it		\| rowspan="2" \| You have only one computer and don't want to erase it
	\| Linux, Windows, macOS, or iOS		\| Linux, Windows, macOS, or iOS
	\| Install virtualisation software, make a new virtual machine and install [[Live Build\|Sugar Live Build]], [[SoaS\|Sugar on a Stick]], [[Ubuntu]], [[Fedora]], or [[Debian]].		\| Install virtualisation software, make a new virtual machine and install [[Live Build\|Sugar Live Build]], [[SoaS\|Sugar on a Stick]], [[Ubuntu]], [[Fedora]], or [[Debian]].
			For Sugarizer, your could use your computer.
	\|-		\|-
	\| Linux		\| Linux

Quozl: simplify contribution and use proper wiki page link

2017-12-01T03:52:18Z

simplify contribution and use proper wiki page link

← Older revision		Revision as of 23:52, 30 November 2017
Line 1:		Line 1:
	=== Basics: Attribution and Licensing ===		=== Basics: Attribution and Licensing ===

	Read ~~the informative wiki article on attribution and licensing at https://wiki.sugarlabs.org/go/Attribution_and_Licensing~~ Attribution and ~~licensing is~~ important for ~~both documentation (i.e. text, media) and code~~ submissions.		Read [[Attribution and Licensing]], as both are important for all submissions.

	=== Setting up the Sugar environment ===		=== Setting up the Sugar environment ===

Pikurasa: Added info on licensing and attribution

2017-11-29T21:16:10Z

Added info on licensing and attribution

← Older revision		Revision as of 17:16, 29 November 2017
Line 1:		Line 1:
			=== Basics: Attribution and Licensing ===

			Read the informative wiki article on attribution and licensing at https://wiki.sugarlabs.org/go/Attribution_and_Licensing Attribution and licensing is important for both documentation (i.e. text, media) and code submissions.

	=== Setting up the Sugar environment ===		=== Setting up the Sugar environment ===

Quozl at 00:11, 28 November 2017

2017-11-28T00:11:45Z

← Older revision		Revision as of 20:11, 27 November 2017
Line 5:		Line 5:
	{\| class="wikitable"		{\| class="wikitable"
	\|-		\|-
	! Equipment !! Operating System !! Recommendation		! Your Equipment !! Your Operating System !! Our Recommendation
	\|-		\|-
	\| rowspan="2" \| You have only one computer and don't want to erase it		\| rowspan="2" \| You have only one computer and don't want to erase it

Quozl: rewrite setting up environment to better illustrate the choices, and simplify decision-making by students

2017-11-28T00:10:58Z

rewrite setting up environment to better illustrate the choices, and simplify decision-making by students

@@ Line 1: / Line 1: @@
 === Setting up the Sugar environment ===
-There are several options for setting up the Sugar environment for development.
+There are several options for setting up the Sugar environment for development, depending on what equipment you have;
-* Install Sugar on [[Ubuntu]], [[Fedora]], or [[Debian]], using apt or dnf;
-* From Windows. macOS or iOS, run Sugar in a virtual machine;
+{| class="wikitable"
-* Live boot from [[SoaS|Sugar on a Stick]];
+|-
-* or ''better yet'', use Sugar Live Build containing Sugar 0.112, which can be booted from hard drive, flash drive, and optical media, automatically starting Sugar without persistence; or can be installed as a virtual machine, with persistence and password protection, and contains all build dependencies, configured source trees (git clones in /usr/src), and binaries (make install) for Sugar 0.112 (Download from [http://people.sugarlabs.org/~quozl/sugar-live-build-20171009/ our server]).
+! Equipment !! Operating System !! Recommendation
 See also [https://developer.sugarlabs.org/dev-environment.md.html Setup a development environment].

Walter at 22:47, 27 November 2017

2017-11-27T22:47:38Z

← Older revision		Revision as of 18:47, 27 November 2017
Line 41:		Line 41:

	Sugar Web Framework is the [https://github.com/sugarlabs/sugar-docs/blob/master/web-architecture.md JavaScript Framework for Sugar]. [http://sugarizer.org Sugarizer] is a subset of Sugar that allow running activities developed with Sugar Web Framework on any web browser. Sugarizer is also available as Android, iOS, Firefox OS and Chrome Web App.		Sugar Web Framework is the [https://github.com/sugarlabs/sugar-docs/blob/master/web-architecture.md JavaScript Framework for Sugar]. [http://sugarizer.org Sugarizer] is a subset of Sugar that allow running activities developed with Sugar Web Framework on any web browser. Sugarizer is also available as Android, iOS, Firefox OS and Chrome Web App.

			=== Getting a wiki account ===

			Some tasks require that you make edits to this wiki for which you'll need an account. Please email walter @ sugarlabs . org to request an account.

	=== Getting help ===		=== Getting help ===

Quozl at 00:58, 22 November 2017

2017-11-22T00:58:35Z

← Older revision		Revision as of 20:58, 21 November 2017
Line 41:		Line 41:

	Sugar Web Framework is the [https://github.com/sugarlabs/sugar-docs/blob/master/web-architecture.md JavaScript Framework for Sugar]. [http://sugarizer.org Sugarizer] is a subset of Sugar that allow running activities developed with Sugar Web Framework on any web browser. Sugarizer is also available as Android, iOS, Firefox OS and Chrome Web App.		Sugar Web Framework is the [https://github.com/sugarlabs/sugar-docs/blob/master/web-architecture.md JavaScript Framework for Sugar]. [http://sugarizer.org Sugarizer] is a subset of Sugar that allow running activities developed with Sugar Web Framework on any web browser. Sugarizer is also available as Android, iOS, Firefox OS and Chrome Web App.

			=== Getting help ===

			Got a problem? Ask your mentors, ask other students, or ask the Sugar Labs community.

			The Sugar Labs community is large, and there are people who are not mentors in the contest. Mentors are [[Google_Code_In_2017#Mentors\|listed]]. Everyone else you talk with may be a non-mentor.

			As part of Sugar Labs community, non-mentors are to treat students in accord with the [[Sugar_Labs/Legal/Code_of_Conduct\|Code of Conduct]], and as if they are new to Sugar Labs.

			Students should keep in mind that some people are non-mentors, and cannot see the contest tasks, contest progress, dates, or information about students. When communicating widely, be sure to;

			* introduce yourself, the first time;
			* tell us what your task is, without relying on a link to the task (because we probably can't see it);
			* talk about the task as if you want to do it yourself, not because of the contest; and,
			* defend your technical decisions without using the contest as a defence.

			Non-mentors may give good guidance on technical decisions, but bad guidance on how they think a task is judged. Always consult with your mentors as well.

Quozl: /* Getting started with coding in Sugar */

2017-11-22T00:48:32Z

Getting started with coding in Sugar

← Older revision		Revision as of 20:48, 21 November 2017
Line 24:		Line 24:
	** the [https://python-gtk-3-tutorial.readthedocs.org/en/latest/ Python bindings] for [https://www.gtk.org/ GTK+ 3]; and		** the [https://python-gtk-3-tutorial.readthedocs.org/en/latest/ Python bindings] for [https://www.gtk.org/ GTK+ 3]; and
	** the [https://lazka.github.io/pgi-docs/#Gtk-3.0 Gtk-3.0 section of the PyGObject API Reference].		** the [https://lazka.github.io/pgi-docs/#Gtk-3.0 Gtk-3.0 section of the PyGObject API Reference].
	* For both, you will need knowledge ~~the basics~~ of Sugar development, see the book [http://www.flossmanuals.net/make-your-own-sugar-activities/ Make Your Own Sugar Activities!]		* For both, you will need knowledge of Sugar activity development, see the book [http://www.flossmanuals.net/make-your-own-sugar-activities/ Make Your Own Sugar Activities!]

	Python programmers, you must run [http://legacy.python.org/dev/peps/pep-0008/#introduction pep8] and pyflakes on your code ''before'' submitting your patches.		Python programmers, you must run [http://legacy.python.org/dev/peps/pep-0008/#introduction pep8] and pyflakes on your code ''before'' submitting your patches.