GCI 2016 - Sugar Labs
Google Code-in is an annual programming
competition hosted by Google Inc. that allows pre-university students to complete tasks
specified by various, partnering open source organizations. The contest was
originally the Google Highly Open Participation Contest, but in 2010, the format was modified
into its current state. Students that complete tasks win certificates and
T-shirts. Each organization also selects two grand prize award winners who will
earn a trip to Google's Headquarters located in MountainView,
California.
Students must be
between 13 and 17 years old (inclusive) to participate. In addition, students
must upload parental consent forms as well as some documentation proving
enrollment in a pre-university program.
I joined GCI
from November 30, 2016. I joined it because of knowledges and
prizes . Students who complete one task earn a certificate. Students
who complete three tasks earn a T-shirt in addition to the certificate. There
is a maximum of one T-shirt and one certificate per student. At the end of
the competition, each organization will choose two students as the grand prize
award winners and they will visit Google's MountainView,
California, USA headquarters for a four-day trip with an awards ceremony, an
opportunity to meet with Google engineers, and a day of sightseeing in San
Francisco.
After this
program I hope to have more knowledge about different markings on GCI such as
GitHub, skill design, PHP code,...and have more beautiful T- shirts from GCI. Sugar
Labs is a software-development and learning community, which makes a
collection oftools that
learners use to explore, discover, create, and reflect. It distributes these
tools freely and encourages its users to appropriate them, taking ownership and
responsibility for their learning.. Helping learners all around the globe to
"learn how to learn".
Sugar Labs have Hundreds
of tools for discovery through exploring, expressing, and sharing: browsing,
writing, etc. Code style for Sugar HTML development is so good.
General
·
Avoid lines longer than 80
characters.
·
Don't use any form of
minification (neither in JS, HTML or CSS). All our source should be readable
using the Sugar "View Source" feature.
Javascript
·
Make your code conform to JSHint.
·
Use four spaces for indentation.
HTML
Use two spaces for
indentation. The rationale is that HTML tends to be very nested, and avoiding
lines longer than 80 characters becomes difficult.
The
js-beautify tool can be handy for indenting HTML as well.
CSS
·
Use two spaces for indentation.
·
Make it compliant with RECESS.
Tools
JSHint
Use JSHint http://jshint.com/ to
check for errors and make the source compatible with our coding conventions.
The jshint command is provided by sugar-build.
js-beautify
Use
js-beautify https://github.com/einars/js-beautify to make the sources compatible with
our indentation conventions. The js-beautify command is provided by sugar-build.
RECESS
RECESS https://github.com/twitter/recess keeps the order of CSS rules following
a convention, and protects us from different mistakes. The recess command is
provided by sugar-build.
