GSoC Mentor App - 2008

From Audacity Wiki
Revision as of 04:38, 12 March 2008 by Vaughan (talk | contribs)
Jump to: navigation, search

This is a draft of the text to send to Google to apply for mentoring status:


1. Organization's Name: Audacity

2. Organization's Homepage:

3. Describe your organization.

We are developers of the Audacity(R) sound editor which runs on Linux, Windows, and Mac.

Audacity is widely used:

  • around 15 million downloads in the past year, and a total of more than 37 million, from Sourceforge. Consistently in the top 10 downloads on Sourceforge, which hosts more than 100,000 projects.

Audacity won Best Project for Multimedia in the Sourceforge 2007 Community Choice Awards, and Project of the Month for July 2004. Audacity was chosen as Audio Authoring Application of the Year in the 2007 Members Choice poll. Audacity has been featured widely in the media, including CNN.coma reference in a New York Times article.

Audacity is a flagship application of the wxWidgets cross-platform toolkit and has an active developer community. Care has been taken to make Audacity work with screen readers for visually impaired users. Audacity has been translated into almost 30 languages.

4. Why is your organization applying to participate in GSoC 2008? What do you hope to gain by participating?

GSoC looks to be a very effective way to get a developer giving full time attention to Audacity, coding on a focused task. It looks to be win-win, good for the student and good for us. As well as the direct improvements to Audacity from the student, which would be hugely welcome, we also hope to interest more people in contributing, through the publicity around GSoC.

5. Did your organization participate in GSoC 2005, 2006 or 2007? If so, please summarize your involvement and the successes and failures of your student projects.


6. If your organization has not previously participated in GSoC, have you applied in the past? If so, for what year(s)?

Yes. We applied in 2007, but we didn't make the cut. This time round we're getting more of the developer community involved in the application process so as to make a better and hopefully successful pitch.

7. What license does your project use?

  • All of it is GNU GPL V2 compatible. We deliberately release some framework code under the wxWidgets license so that it can migrate to wxWidgets in due course and so be of benefit to other projects.

8. URL for your ideas page

9. What is the main development mailing list for your organization?

[email protected]

10. Where is the main IRC channel for your organization?

TBD. Currently, we just use the mail list and forums (

11. Does your organization have an application template you would like to see students use? If so, please provide it now.

Yes. See GSoC Student draft.

12. Who will be your backup organization administrator? Please include Google Account information.

Alexandre Proukoudine, Richard Ash.


1. What criteria did you use to select these individuals as mentors? Please be as specific as possible.

All of our mentors have extensive experience in Audacity and software in general. More information available at "".

2. Who will your mentors be? Please include Google Account Information.

   * Dominic Mazzoni
   * Federico Grau (need Google Account/gmail address)
   * James Crook
   * Leland Lucius? (If so, need Google Account/gmail address.)
   * Markus Meyer? (If so, need Google Account/gmail address.)
   * Richard Ash
   * Roger Dannenberg
   * Vaughan Johnson
   * (backup) Martyn Shaw

About the Program

1. What is your plan for dealing with disappearing students?

Certainly repeated pinging is the first response. We plan to target a ratio of 4 mentors to 3 students. If we have student applicants we have to exclude for the reason of maintaining that ratio, and the disappearing students disappear early, we might be able to replace them.

2. What is your plan for dealing with disappearing mentors?

Our targeted ratio of 4 mentors to 3 students should provide sufficient backup.

3. What steps will you take to encourage students to interact with your project's community before, during and after the program?

  • (Before) We already have a few students talking with us about possible projects. This happened through having several pages on our Wiki relating to GSoC and an invitation to start discussion on the devel list.
  • We are discussing a hackathon (social) for early in the GSoC process, so that we meet some of the potential students face to face.

4. What will you do to ensure that your accepted students stick with the project after GSoC concludes?

At student selection stage, we look for evidence that the student has a real interest in our project, 'Do they actually use it?' rather than just choosing some project that is part of GSoC. That should be somewhat predictive.

Afterward, we will stay in touch with them, possibly provide a new forum (, and more hackathon meetings.