Difference between revisions of "GSoC FAQ"

From Audacity Wiki
Jump to: navigation, search
(Answers to some questions asked by e-mail.)
 
(just tidied a bit / capitalised etc.)
Line 1: Line 1:
This page has answers to some questions posted to our [email protected] address.
+
{{Intro|1=This page answers some common questions posted to our {{external|[mailto:[email protected] Summer of Code e-mail address.]}} Please e-mail us if this FAQ does not answer your query. |2=
 
+
{{external|http://code.google.com/soc/2008/}} has comprehensive details of the current GSoC program. Some questions we have been asked are also answered there, though not always on their FAQ pages.}}
Comprehensive details of the GSoC program can be found at:
 
 
 
http://code.google.com/soc/2008/
 
 
 
Some questions we have been asked are answered there, though not always on their FAQ pages.
 
  
  
 
* '''What level of technical expertise is required to participate in GSoC?'''
 
* '''What level of technical expertise is required to participate in GSoC?'''
  
The level that could reasonably be expected of better than average computer science degree students after their first year.  Realistically, given that the program is fairly competitive, programming skill to the level of having completed some programming project of 1000+ lines as part of coursework would I see being the minimum. Applicants should mention at least one significant program they have completed on their application.   
+
The level that could reasonably be expected of better than average computer science degree students after their first year.  Realistically, given that GSoC is fairly competitive, we'd regard the minimum programming skill to be such that at least one programming project of 1000+ lines should have been completed as part of coursework. Applicants should mention at least one significant program they have completed on their application.   
  
 
We're not expecting students to already be familiar with the speciality of sound processing for Audacity work.  However students should have some familiarity with writing GUI code or they will be at a distinct disadvantage.
 
We're not expecting students to already be familiar with the speciality of sound processing for Audacity work.  However students should have some familiarity with writing GUI code or they will be at a distinct disadvantage.
 +
  
 
* '''What sort of projects can be chosen?'''
 
* '''What sort of projects can be chosen?'''
 
The organisations and projects that were offered in 2007 can be found here:
 
The organisations and projects that were offered in 2007 can be found here:
  
http://code.google.com/soc/2007
+
{{external|http://code.google.com/soc/2007}}
  
For Audacity we welcome new ideas.  Some suggestions can be found at:
+
For Audacity we welcome new ideas that may enhance the program's functionality.  Some suggestions can be found on our [[GSoC Ideas|GSoC ideas page]].
  
http://www.audacityteam.org/wiki/index.php?title=GSoC_Ideas
 
  
* '''What is the role of mentoring oragnizations?'''
+
* '''What is the role of mentoring organizations?'''
 +
 
 +
See the Google pages for precise details.<br>
 +
- We select the applications we like the best.<br>
 +
- We provide a mentor.  The mentor is there to advise on implementation choices, making sure that the student has the information they need.<br>
 +
- We, particularly the mentor, evaluate the work and confirm to Google that the student has done the work satisfactorily, which is the basis on which Google pay the student.
  
See the google pages for precise details.
 
* We select the applications we like the best.
 
* We provide a mentor.  The mentor is there to advise on implementation choices, making sure that the student has the information they need.
 
* We, particularly the mentor, evaluate the work and confirms to google that the student has done the work satisfactorily, which is the basis on which google pay the student.
 
  
 
* '''How do I make a "good" application?'''
 
* '''How do I make a "good" application?'''
  
Whatever mentoring organisation you choose, the best way is to get in contact with the developers and discuss what you would like to do as a project with them.  Do this well in advance of sending in your application. The results of that discussion will lead to a much stronger application.   
+
Whatever mentoring organization you choose, the best way is to get in contact with its developers and discuss what you would like to do as a project with them.  Do this well in advance of sending in your application. The results of that discussion will lead to a much stronger application.  To discuss your ideas with the Audacity developers, please {{external|[http://lists.sourceforge.net/lists/listinfo/audacity-devel subscribe to our developers' mailing list]}}.
 
 
For Audacity that is {{external|[http://lists.sourceforge.net/lists/listinfo/audacity-devel here]}}
 
  
Your application will also be stronger if you have already tried using the Audacity codebase.  If you have compiled Audacity and made some small experimental change that gives us confidence that you will be able to do more.
+
Your application will also be stronger if you have already tried using the Audacity codebase.  If you have compiled Audacity and made some small experimental change, that gives us confidence that you will be able to do more.
  
  

Revision as of 18:42, 1 March 2008

This page answers some common questions posted to our Summer of Code e-mail address.  Please e-mail us if this FAQ does not answer your query.
http://code.google.com/soc/2008/  has comprehensive details of the current GSoC program. Some questions we have been asked are also answered there, though not always on their FAQ pages.


  • What level of technical expertise is required to participate in GSoC?

The level that could reasonably be expected of better than average computer science degree students after their first year. Realistically, given that GSoC is fairly competitive, we'd regard the minimum programming skill to be such that at least one programming project of 1000+ lines should have been completed as part of coursework. Applicants should mention at least one significant program they have completed on their application.

We're not expecting students to already be familiar with the speciality of sound processing for Audacity work. However students should have some familiarity with writing GUI code or they will be at a distinct disadvantage.


  • What sort of projects can be chosen?

The organisations and projects that were offered in 2007 can be found here:

http://code.google.com/soc/2007 

For Audacity we welcome new ideas that may enhance the program's functionality. Some suggestions can be found on our GSoC ideas page.


  • What is the role of mentoring organizations?

See the Google pages for precise details.
- We select the applications we like the best.
- We provide a mentor. The mentor is there to advise on implementation choices, making sure that the student has the information they need.
- We, particularly the mentor, evaluate the work and confirm to Google that the student has done the work satisfactorily, which is the basis on which Google pay the student.


  • How do I make a "good" application?

Whatever mentoring organization you choose, the best way is to get in contact with its developers and discuss what you would like to do as a project with them. Do this well in advance of sending in your application. The results of that discussion will lead to a much stronger application. To discuss your ideas with the Audacity developers, please subscribe to our developers' mailing list .

Your application will also be stronger if you have already tried using the Audacity codebase. If you have compiled Audacity and made some small experimental change, that gives us confidence that you will be able to do more.