User Tools

Site Tools


best_practices

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
best_practices [2012/02/20 15:14]
127.0.0.1 external edit
best_practices [2012/02/22 18:56] (current)
kokr link cleanup
Line 3: Line 3:
 2010 is the third year in which the gEDA Project has participated in Google'​s Summer of Code program. ​ Through our experience, we have learned a couple of things about running a successful program. ​ Here are the things we ask of our students to help make the GSoC experience a success for everybody. 2010 is the third year in which the gEDA Project has participated in Google'​s Summer of Code program. ​ Through our experience, we have learned a couple of things about running a successful program. ​ Here are the things we ask of our students to help make the GSoC experience a success for everybody.
  
-  *  Please get involved with the gEDA Project **before** the summer begins. ​ We are more interested in having new developers join (and stay with) our community than we are in simply giving away easy summer jobs.  Therefore, get involved **now!** ​ Join our [[http://geda.seul.org/​mailinglist/​index.html ​| mailing lists]], check the code out of git, and fiddle around with it.  We will rate your application more highly if you are already a participant,​ and not just a new face when GSoC application time rolls around.+  *  Please get involved with the gEDA Project **before** the summer begins. ​ We are more interested in having new developers join (and stay with) our community than we are in simply giving away easy summer jobs.  Therefore, get involved **now!** ​ Join our [[geda:​mailinglists|mailing lists]], check the code out of git, and fiddle around with it.  We will rate your application more highly if you are already a participant,​ and not just a new face when GSoC application time rolls around.
   *  Participating in Google Summer of Code is meant to be a **full time job**. ​ We expect that you will work on your project 8 hours/day from Monday to Friday. ​ Summer of Code is not meant to be a side job.  Please do not try to work on both Summer of Code and a different job during the summer -- you will tire yourself out, your work quality will suffer, and you won't enjoy the experience at all.   *  Participating in Google Summer of Code is meant to be a **full time job**. ​ We expect that you will work on your project 8 hours/day from Monday to Friday. ​ Summer of Code is not meant to be a side job.  Please do not try to work on both Summer of Code and a different job during the summer -- you will tire yourself out, your work quality will suffer, and you won't enjoy the experience at all.
-  *  Students and mentors should use the [[http://​www.seul.org/​cgi-bin/​mailman/​listinfo/​geda-dev|geda-dev mailing list]] for (almost) all communication about their GSoC project. ​ There are several reasons for this: +  *  Students and mentors should use the [[geda:mailinglists|geda-developer ​mailing list]] for (almost) all communication about their GSoC project. ​ There are several reasons for this: 
      * Oftentimes, a different developer on the list can answer a question before the  mentor even realizes that he's been asked.      * Oftentimes, a different developer on the list can answer a question before the  mentor even realizes that he's been asked.
      * It increases the sense of community for both the GSoC student, and the rest of the gEDA developers. ​ And the gEDA Project is a community of developers, so community building is a benefit to all.      * It increases the sense of community for both the GSoC student, and the rest of the gEDA developers. ​ And the gEDA Project is a community of developers, so community building is a benefit to all.
best_practices.1329768896.txt.gz ยท Last modified: 2012/02/22 18:56 (external edit)