Summer of Code/Resources: Difference between revisions

(4 intermediate revisions by 3 users not shown)

Line 1:

<noinclude>{{ GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show | ja =show | ko =show | no =show | pl =show | pt =show | ro =show | ru =show | sv =show }}{{TeamHeader|Summer of Code|home=Summer of Code Project Home|xbgColor=ffe792}}</noinclude>{{TOCright}}

<noinclude>{{TeamHeader|Summer of Code|home=Summer of Code Project Home|xbgColor=ffe792}}</noinclude>{{TOCright}}

Sugar Labs is a big project. Like all big projects, it has a big wiki. Here are some pointers:

Line 10:

=== Getting the Code ===

# Know git? Visit our [~~[Development_Team~~/~~Source_Code | source code]~~] ~~page~~ to see the repositories of all of the Sugar modules & core Activities

# Know git? Visit our [http://developer.sugarlabs.org resource page for developers] to see the repositories of all of the Sugar modules & core Activities

# You may wish to [[Taxonomy | learn the terms]] we use to describe Sugar's components

=== Fixing Bugs ===

Getting to work on bugs is a great way to start your introduction to the Sugar code base. Hint: Search for ''sugar-love'' in the bug tracker.

# Visit ~~http~~://dev.sugarlabs.org, also known as ~~http~~://bugs.sugarlabs.org/

# Visit https://dev.sugarlabs.org, also known as https://bugs.sugarlabs.org/

# Learn our [[BugSquad/Status_Fields | bug status codes]]

Line 30:

We are also very keen to have a student or two adopt a mature Activity. This would involve completing a set of non-trivial patches for a particular Activity. This is a great opportunity to get to know how others' code is written. You'll be able to show to your future employers that you're able to fit in nicely with a currenty software project.

=== Proposal Template ===

See [[Summer_of_Code/Template]].

==Further Resources==

Line 37:

Line 40:

===[[Activity Team]]===

* '''[[Activity Team/Resources|Resources]] is a portal of resources for the Activity team. The Activity team is focused on maintaining the individual Activities that sit within the Sugar Learning Platform.

* '''[[Activity Team/Resources|Resources]]''' is a portal of resources for the Activity team. The Activity team is focused on maintaining the individual Activities that sit within the Sugar Learning Platform.

===[[Sugar Labs]]===

* '''[[Sugar Labs/~~Contacts~~]]''' for communication channels

* '''[[Sugar Labs/Communication channels]]''' for communication channels

[[Category:Resource]]

[[Category:Idea]]

@@ Line 1: / Line 1: @@
-<noinclude>{{ GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show | ja =show | ko =show | no =show | pl =show | pt =show | ro =show | ru =show | sv =show }}{{TeamHeader|Summer of Code|home=Summer of Code Project Home|xbgColor=ffe792}}</noinclude>{{TOCright}}
+<noinclude>{{TeamHeader|Summer of Code|home=Summer of Code Project Home|xbgColor=ffe792}}</noinclude>{{TOCright}}
 Sugar Labs is a big project. Like all big projects, it has a big wiki. Here are some pointers:
@@ Line 10: / Line 10: @@
 === Getting the Code ===
-# Know git? Visit our [[Development_Team/Source_Code | source code]] page to see the repositories of all of the Sugar modules & core Activities
+# Know git? Visit our [http://developer.sugarlabs.org resource page for developers] to see the repositories of all of the Sugar modules & core Activities
 # You may wish to [[Taxonomy | learn the terms]] we use to describe Sugar's components
 === Fixing Bugs ===
 Getting to work on bugs is a great way to start your introduction to the Sugar code base. Hint: Search for ''sugar-love'' in the bug tracker.
-# Visit http://dev.sugarlabs.org, also known as http://bugs.sugarlabs.org/
+# Visit https://dev.sugarlabs.org, also known as https://bugs.sugarlabs.org/
 # Learn our [[BugSquad/Status_Fields | bug status codes]]
@@ Line 30: / Line 30: @@
 We are also very keen to have a student or two adopt a mature Activity. This would involve completing a set of non-trivial patches for a particular Activity. This is a great opportunity to get to know how others' code is written. You'll be able to show to your future employers that you're able to fit in nicely with a currenty software project.
+=== Proposal Template ===
+See [[Summer_of_Code/Template]].
 ==Further Resources==
@@ Line 37: / Line 40: @@
 ===[[Activity Team]]===
-* '''[[Activity Team/Resources|Resources]] is a portal of resources for the Activity team. The Activity team is focused on maintaining the individual Activities that sit within the Sugar Learning Platform.
+* '''[[Activity Team/Resources|Resources]]''' is a portal of resources for the Activity team. The Activity team is focused on maintaining the individual Activities that sit within the Sugar Learning Platform.
 ===[[Sugar Labs]]===
-* '''[[Sugar Labs/Contacts]]''' for communication channels
+* '''[[Sugar Labs/Communication channels]]''' for communication channels
 [[Category:Resource]]
 [[Category:Idea]]