Status: Elixpo is applying to be a mentoring organisation for Google Summer of Code 2027. Google announces accepted organisations after the application period.

ElixpoGSoC 2027

Applying

Proposal template

Your proposal is your plan for one Elixpo project idea. Start with what Google provides, then use Elixpo's template below, in this order. Write it yourself; be specific and concise.

What Google provides

Google runs the application and publishes the official guidance. Read it first; the rest of this page adds what Elixpo asks for.

  1. Google's guide. Google's contributor guide explains writing a proposal: the formal requirements to check first, being clear about your time commitments, and the elements of a quality proposal.
  2. Where to submit. Proposals are submitted only through the official GSoC website, during the contributor application period. Proposals sent anywhere else are not considered.
  3. When. The dates are on Google's official timeline. Google has not announced the 2027 dates yet.

Before you write

  • Read the idea page in full, including its expected outcomes, out-of-scope items and success measures.
  • Complete at least one of the idea's warm-up tasks.
  • Read the selection criteria and the AI policy. Your proposal must be your own writing.
  • Send a draft to gsoc@elixpo.com before the deadline so that mentors can comment on it.
  • You must submit your final proposal through the official GSoC website.

The template

Elixpo's template: use these sections, in this order. Write each one yourself.

Title

Use this format:

Elixpo GSoC 2027: <idea title> — <your name>

For example: Elixpo GSoC 2027: Oreo badge desktop simulator — Jane Doe.

1. Contact details

  • Full name, email address, GitHub username and time zone.
  • Links to your other public profiles, if relevant.

2. About you

  • Your education or work background and relevant experience.
  • Links to code you have written.
  • Why you chose this idea and what you expect to learn.

3. Project title

The title of the idea as it appears on the idea page.

4. Synopsis

A short paragraph that summarises the problem and your proposed solution.

5. The problem in your own words

Explain the problem as you understand it after reading the code. Refer to the files, routes or modules involved. Do not copy the idea page.

6. Proposed approach and design decisions

  • How you intend to solve the problem.
  • The main design decisions, the options you considered and the reasons for your choice.
  • Open questions, and how you will resolve them.

7. Deliverables

List what will exist at the end of the project, mapped to the idea's expected outcomes. Mark any stretch goals separately.

8. Timeline

  • Divide the work into milestones of one to two weeks. Each milestone should end in a pull request that a mentor can review.
  • Include the community bonding period.
  • Mark a midterm checkpoint: the work that will be merged by the midterm evaluation.
  • State what you will drop first if the work falls behind.

9. Testing and evidence

Explain how you and your mentors will confirm the work is complete, with reference to the idea's "How success is measured" section. Include at least one test that fails before your change and passes after it.

10. Communication plan

  • How often you will report progress, and where. We prefer public channels, such as pull requests and issues in the project's repository.
  • How you will ask for help when you are blocked.

11. Availability and other commitments

  • The number of hours per week you can commit.
  • Examinations, travel, employment or other commitments during the programme.

12. Prior contributions to Elixpo

Link your pull requests, issues and discussions in Elixpo repositories, and state what you learned from review.

13. GSoC experience

State whether you have applied to or taken part in Google Summer of Code before, with which organisations, and the outcome.