Summer of Code/2015/GIT.JR: Difference between revisions

Line 44:

===You and the community===

* ~~If your~~ project is ~~successfully~~ completed, ~~what will its impact be~~ on ~~the Sugar Labs community? Give 3 answers~~, ~~each 1-3 paragraphs~~ in ~~length. The first one should be yours. The other two should be answers from members~~ of the ~~Sugar Labs community, at least one of whom should be a Sugar Labs GSoC mentor. Provide email contact information for non-GSoC mentors~~.

* Impact on the community:

**My Answer (Gabriel Cemaj)

*** Like i have stated above i dont think we are doing a good enough job of introducing kids that code how to code with people and how to share their code and how to document their code. I believe that when this project is completed it will serve as a learning tool that will enable kids to become better programmers with better code that is shareable. I this this is an huge investment in their future and their abilities, too many people come to university level Computer Science having never used a versioning system and having never shared their code. We are no longer in the 70's and 80's where one programmer could do a project on his own, we live in the era of colaboration and we need to include this as part of the curriculum.

* What will you do if you get stuck on your project and your mentor isn't around?

* How do you propose you will be keeping the community informed of your progress and any problems or questions you might have over the course of the project?

@@ Line 44: / Line 44: @@
 ===You and the community===
-* If your project is successfully completed, what will its impact be on the Sugar Labs community? Give 3 answers, each 1-3 paragraphs in length. The first one should be yours. The other two should be answers from members of the Sugar Labs community, at least one of whom should be a Sugar Labs GSoC mentor. Provide email contact information for non-GSoC mentors.
+* Impact on the community:
+**My Answer (Gabriel Cemaj)
+*** Like i have stated above i dont think we are doing a good enough job of introducing kids that code how to code with people and how to share their code and how to document their code. I believe that when this project is completed it will serve as a learning tool that will enable kids to become better programmers with better code that is shareable. I this this is an huge investment in their future and their abilities, too many people come to university level Computer Science having never used a versioning system and having never shared their code. We are no longer in the 70's and 80's where one programmer could do a project on his own, we live in the era of colaboration and we need to include this as part of the curriculum.
 * What will you do if you get stuck on your project and your mentor isn't around?
 * How do you propose you will be keeping the community informed of your progress and any problems or questions you might have over the course of the project?