<!DOCTYPE html> <html> <head> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> </head> <body> Hi, I finally had a chance to skim through every proposal that has been uploaded to the GSoC platform, and I want to start by giving some broad feedback for everyone. If you are interested in strengthening your proposal, here are some things I recommend: <ul> <li>Upload your proposal!!! I've received requests -- sometimes multiple requests -- for review privately from some folks who have yet to upload their proposal to GSoC. If you're one of those that have been contributing to Sugar Labs for months now, have submitted multiple PRs, and have a draft proposal, I recommend that you upload your latest draft!!!</li> <li>Make sure that your GitHub account ID is on your proposal.</li> <li>I recommend sharing a few links or screenshots to projects you've made with the Sugar Labs application that relates to your project (e.g. submitting links to Music Blocks projects you've made or a screenshot of a Sugar Activity you've recently used.) Basically, it's nice to know that you've used the program you are planning to spend the summer working on.</li> <li>Similarly, I recommend that you submit a few bug reports to the repository that relates to your project and reference this in your proposal. </li> <li>If you haven't submitted a pull request to a Sugar Labs repository, I highly recommend that you do so. This will make your proposal stronger.</li> <li>If you haven't joined a meeting, I highly recommend that you do so. We want to know who you are, how you work. Also, Google is giving us specific guidance to not accept proposals from applicants we haven't interacted with in some way.</li> <li>A few proposals lack any information on implementation. Your proposal should include some information on what you plan to implement over the summer and how. </li> <li>It may also be helpful to add your Matrix ID.</li> <li>We don't weigh the number of pages of a proposal as much as other criteria, but if your proposal is fewer than two pages it is probably too short. If this describes your proposal, please add the information suggested in the above bullets to fill it out. </li> </ul> At any rate, I hope this helps! Lastly, this subject of this email previously said the submission period "ends April 8 at 1000 UTC". This was copied from the body of an email I received from Google. It's an error that I've confirmed with them. The official deadline is ends April 8 at 1800 UTC. (I've fixed the subject for going forward.) Best, Devin <div class="moz-cite-prefix">Devin Ulibarri: </div> <blockquote type="cite" cite="mid:dde053c8-9d4c-467e-bd6b-4cc4bc064876@sugarlabs.org"> <meta http-equiv="content-type" content="text/html; charset=UTF-8"> Hi all, It's exciting to see all the activity around Google Summer of Code (GSoC). Now that the submission window is open, I encourage everyone who is considering applying to GSoC to do so as soon as possible. Please remember that the submission period ends April 8 at 1000 UTC. Also, there is no harm in uploading a "good enough" draft now and updating periodically before the submission period ends. Mentors can see, from their dashboard, all the submissions. It is convenient for us to view from the dashboard, and it ensures that you will not miss the deadline. I myself, for example, plan to review proposals in a batch over the weekend, and I'll be starting by looking at the proposal drafts that have been submitted. Lastly, if you have yet to make a PR, please know that it's important to do so. We weigh these quite a bit, since they show us how you will likely perform over the summer. Likewise, if you haven't done so already, you should join the conversation in our Matrix chat and join a live meeting: <a class="moz-txt-link-freetext" href="https://matrix.to/#/#sugar:matrix.org" moz-do-not-send="true">https://matrix.to/#/#sugar:matrix.org</a> (bi-weekly meeting info is in the room description). Google is recommending that we get to know all the contributors, not just by their applications but by interactions within the community. More info: <ul> <li>GSoC Rules: <a href="https://summerofcode.withgoogle.com/rules" class="moz-txt-link-freetext" moz-do-not-send="true">https://summerofcode.withgoogle.com/rules</a></li> <li>GSoC Contributor guide: <a href="https://google.github.io/gsocguides/student/" class="moz-txt-link-freetext" moz-do-not-send="true">https://google.github.io/gsocguides/student/</a></li> <li>GSoC FAQ: <a href="https://developers.google.com/open-source/gsoc/faq" class="moz-txt-link-freetext" moz-do-not-send="true">https://developers.google.com/open-source/gsoc/faq</a></li> <li>Sugar Labs's Ideas list: <a href="https://github.com/sugarlabs/GSoC/blob/master/Ideas-2025.md" class="moz-txt-link-freetext" moz-do-not-send="true">https://github.com/sugarlabs/GSoC/blob/master/Ideas-2025.md</a></li> </ul> Again, we're excited by all the activity, and we're looking forward to reviewing your proposals! Best, Devin <div class="moz-signature">-- Learn more: <a href="https://sugarlabs.org" class="moz-txt-link-freetext" moz-do-not-send="true">https://sugarlabs.org</a> Help us grow: <a href="https://www.every.org/sugar-labs" class="moz-txt-link-freetext" moz-do-not-send="true">https://www.every.org/sugar-labs</a> </div> </blockquote> <div class="moz-signature">-- Learn more: <a href="https://sugarlabs.org" class="moz-txt-link-freetext">https://sugarlabs.org</a> Help us grow: <a href="https://www.every.org/sugar-labs" class="moz-txt-link-freetext">https://www.every.org/sugar-labs</a> </div> </body> </html>