Google Summer of Code with Audacity

From Audacity Wiki
Revision as of 03:09, 17 February 2022 by Peter Jonas (talk | contribs) (Create page)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Introduction

Google Summer of Code (GSoC) is an annual program that offers money to contributors who successfully complete coding projects for open source "organisations" like Audacity. Applicants should be familiar with Google's requirements as well as our own.

Changes for 2022

For the first time this year:

  • The GSoC program is open to both students and non-students as long as you are at least 18 years old and fairly new to open source. See Google's FAQ for full eligibility requirements.
  • Projects can be medium (~175 hours) or large (~350 hours) in size, usually completed over a period of 12 weeks.
  • The 12 week coding period can optionally be extended up to 22 weeks, although this requires approval by both the contributor and their mentor.
    • We will consider extending the deadline to account for time when you are unavailable during the coding period, such as holidays or classes, but we do not advise using the extension as a way to attempt a larger project. The project should take 12 weeks to complete but the weeks do not have to be contiguous. Please be very clear about the expected end date in your proposal(s).

Applying to participate

Join the Discord server

Join the Audacity Dev Discord Server and introduce yourself in the GSoC channels. Use this opportunity to ask for help with the remaining parts of the application process, like compiling Audacity or writing a proposal.

Compile Audacity

See https://github.com/audacity/audacity/blob/master/BUILDING.md

Submit a pull request

Choose an open issue on GitHub and try to fix it in Audacity's code. Submit your fix as a pull request on GitHub and make any requested changed in order to get it merged.

Ideally you should submit multiple pull requests and make changes to code in several areas of the application, particularly in areas that relate to the project(s) you are applying for.

Write draft proposal(s)

Write your proposal in Google Docs and share a link with us via the GSoC Dashboard. Make sure sharing permissions on the proposal document are set to "Anyone with the link can comment". Ask potential mentors to review your draft proposal.

Draft proposals can be submitted via Google's GSoC interface from the start of the application period. We encourage you to submit early, as proposals can be revised based on comments from us. There won't be time for comments by us and revisions if you submit close to the deadline.

Here are some boilerplate comments we might have:

  • 'Please be clearer about what your new code will do for users.'
  • 'Have you looked at feature X already in Audacity?'
  • 'Where is the timeline?'
  • 'No, a project that only delivers anything useful at the very end of it isn't going to work'.

If your proposal is just a cut and paste from our ideas page, it won't get very far.

Your project timeline doesn't have to be super detailed, but it must show exams/internships/holidays that you plan to take during the coding period, or other known significant calls on your time, and you must distinguish between what you are planning to achieve by the mid term evaluation from what you plan for the part after. We look for a project plan that delivers something of some value to our end users by the mid term. That is an insurance for both you and for us. Planning for everything to come together only by the end of the project is too high risk.

Submit your final proposal(s)

Make sure you upload a final PDF version of your proposal(s) to the GSoC dashboard before the deadline. Proposals submitted after the deadline cannot be considered. Draft proposals cannot be considered regardless of when they were submitted.