Difference between revisions of "GSoC Student Guidelines"

From Audacity Wiki
Jump to: navigation, search
(very minor tidy/suggest call the Wiki project pages as per GSoC Ideas/More Ideas)
(Link to Developer_Guide#Tips_for_New_Developers.)
Line 12: Line 12:
 
* We encourage students to start a User: page on the Wiki (that is, "please introduce yourself"). Please also start a Wiki page for your project and call it as per the title on [[GSoC Ideas]] or [[More_GSoC_Ideas]]. See our [[GSoC News and Tips#Wiki Editing|Wiki editing tips]] on [[GSoC News and Tips]].
 
* We encourage students to start a User: page on the Wiki (that is, "please introduce yourself"). Please also start a Wiki page for your project and call it as per the title on [[GSoC Ideas]] or [[More_GSoC_Ideas]]. See our [[GSoC News and Tips#Wiki Editing|Wiki editing tips]] on [[GSoC News and Tips]].
  
 +
* Read the [[Developer_Guide | Developer Guide]], especially [[Developer_Guide#Tips_for_New_Developers | Tips for New Developers]].
  
 
== Requirements ==
 
== Requirements ==

Revision as of 17:50, 24 April 2008

These are Policy Guidelines and Requirements for Audacity Student Participants in Google Summer of Code.
Also bookmark GSoC News and Tips for handy hints and latest news.


  • Most discussion of your projects should be on the audacity-devel mailing list, but you can continue to use [email protected]  to contact all the mentors and admins directly.
  • When we need to contact you directly, we will use the gmail or googlemail address you gave us, so check those regularly.
  • Different mentors in Audacity will have different views on the exact same issues - it's part of the nature of open source. We have Vaughan as our Admin for GSoC 2008 and we have given him responsibilities and authority for the GSoC time. Partly this is because for some decisions it's more important to make a decision now than to reach the "optimum decision" but take too long about it. We hope this works as well for you as it does for us.

Requirements

  • Weekly status reports of the "this is going well... and this isn't...." kind to be sent to [email protected]  (so this will include your mentor). These should be brief and focused.
  • Keep a record of code you write so that you are ready to upload it to Google at the end of project. We'll ask for tarballs of your code at the mid-term as a practice run.
  • We'll build "kick-the-tires" betas every two weeks, for all three platforms. This means that on the designated bi-weekly dates, your latest code that's at least partially working should build without breaking anything.