Skip to content

Latest commit

 

History

History
100 lines (62 loc) · 5.51 KB

ProposalTemplate.md

File metadata and controls

100 lines (62 loc) · 5.51 KB

Please use this template to organize your GSoC application. You can use an editor of your choice. Please keep the section headings exaclty as they are. Everything but the headings are notes, and you should replace these with your proposal materials!

Section 1: Introduction

The whole introduction section should be about 1 page, including the bio and project summary below.

First, please list your:

  • Name
  • GitHub handle
  • Discourse handle
  • Discord handle
  • Pronouns
  • Optional: website, portfolio, blog, etc

Important

If you have not already said hello in one of the online community spaces, make sure you do so before the application deadline on March 31st. The recommended place to start is this Discourse thread. Merged GitHub PRs are not required, and if you make Pull Requests on GitHub, ensure they follow contributor guidelines. PRs (and any other activity in online community spaces) that consistently ignore contribution and community guidelines can actually make your proposal less likely to succeed.

Short bio

100-200 words

Project abstract

100-200 words

Interests & skills

Briefly describe:

  • What do you find most interesting about this project?
  • What skills and perspectives do you bring to this GSoC project? Technical and non-technical
  • What skills and perspectives do you want to develop through GSoC? Technical and non-technical

Section 2: Contribution & Open Source

This section should be about 1 page.

Be sure to answer all the below questions in your reflection:

  1. Share a contribution in p5/processing you are most proud of. What did you learn? Contributions include: active, helpful participation in online spaces; code (pull requests); bug reports and investigation; ideas; sketches shared in a public forum, like Discord, Discourse, your own blog, social media, etc. (No need to list everything - we will review your public GitHub, Discourse, and Discord activity. Here, we‘re interested in getting your reflections. But include a link to the specific highlight described.)
  2. Share a p5/Processing sketch/project that you made that you are most satisfied with and why. Include a link.
  3. Share a p5/Processing sketch/project that someone else made that inspires you. Include a link.
  4. Share an open source project that you use regularly. Include a link.
  5. In your words, what is most important to make open source accessible?

Section 3: Proposed work

This section should be no more than 3 pages. Although you can add additional information in an appendix, we expect in this section a clear, thorough, and not overly verbose description of the proposed project.

  1. What problem does this project solve? Be specific and make sure there is more detail about this in the Research section.
  2. To describe how the project solves the problem, please be sure to address each of these areas:
    1. Detailed approach to the problem (potentially include diagram(s))
    2. Technical details of the implementation (including proposed tech stack, libraries, and tools to be used)
    3. 1-3 potential roadblocks that might come up
    4. Plan for integration of solution within existing codebase and ecosystem
  3. Does this project increase access and inclusion? Be as specific as possible.

Section 4: Timeline

This section should be 1-3 pages, but it can vary.

  • Please include an overview timeline of your proposed project, including overall number of hours. Please also indicate when you'd like to receive community feedback on your work, and how, such as through Discourse, Discord, social media, GitHub. Your mentor can help coordinate this, but it's up to you how to structure and use community feedback to inform your development work.
  • Timeline should be week by week
  • For each week, be sure to list an expected minimum technical outcome, as well as the additional work that will be done as long as there are no roadblocks)

Section 5: Research

This section can be 1 or more pages.

  • Briefly describe your thought process and journey when researching the project. We would like to know not only the final result, but how you approach the project.
  • Share any user research, market research, or technical research you did in creating the proposal. Please mention any contributors or maintainers you’ve already had conversations with (including in open Discourse or Discord discussions or GitHub issues)
  • More detailed research can be in an appendix.

Section 6: Practicalities

Very important - don't skip this!

  • Please carefully review the GSoC Rules 7.1 and confirm eligibility. Write explicitly that you have read the program rules, and are eligible.
  • AI disclosure - if LLMs were used in this proposal, please describe precisely they were used in: code generation, research, community engagement, or writing.
  • Availability (your preferences do NOT affect chances of being selected, but some availability to connect with mentor(s) and other contributors is important)
    • Indicate which days/times you’d be able to meet for audio or video calls (such as over Zoom, Discord, or other platform).
    • Any other preferences on communication style (e.g., written or calls)?

Good luck!

Tip

Recent GSoC contributors share what helped their applications stand out, and how they approached the process in this video: "It's not a Competition": How to Apply for GSoC with the Processing Foundation