Current Page -
Last modified Tue Mar 30 08:11:14 PDT 2021
Please use this template as a guide for information you send in any project application. Unless specifically stated otherwise, all information we request is required. Ensuring that your application is properly and fully filled out saves us all time, so please be thorough and accurate!
Please submit your application in plain text (or something more or less equivalent; Markdown is fine).
Students are encouraged to stop by #plan9-gsoc on Freenode (IRC) if they've got questions, or to mail 9fans (on our mailing lists page). They should also review the GSoC Student Expectations and be comfortable with what's described there.
We want to be sure you understand the basics of Plan 9 concepts and the environment you'll be working in. Pick something below and do it. We require something below. The first item is pretty easy, but is a good introduction to working with the tools; it is totally sufficient. The rest are above and beyond.
Tell us about the specific project you'd like to work on. If you've picked something from our ideas page, please make the title match what's on that page. Regardless, you should be able to describe the project in your own words (even if it's just to show us you understand what an existing idea is looking for). Especially if your proposal is your own idea, be sure to include enough detail so that we understand your idea.
Do **not** copy / paste an idea from the ideas page verbatim.
Part of effective engineering is being able to break a project down into component parts and evaluate those. Do so: tell us what the component parts of your project are and build a schedule for them.
We'd like you to break down your project into weekly (or smaller, if it makes sense) milestones. This will allow you to get a great feel for the work required for your project, and will give everyone involved a schedule to help guide project planning along the way. It will also help us evaluate the scope and complexity of your project, as well as how well-formed your idea is.
We understand that this schedule will change as the summer goes on, based on experience working on the project and discussions with your mentor. The objective here is not to hold you rigidly to what you say here, but rather to demonstrate your understanding of the project.
Summer of Code is a significant commitment. In 2021, the project is only expected to take up 175 hours over the course of the summer, which means it's important to figure out how those will be spread out.
Please tell us about any other commitments you have during the summer. Are you planning on fitting this in after work, throughout the summer, or are you dedicating a solid few weeks to it? Which weeks? Any set vacation time planned? Ideally, this should already be included in your proposed schedule above, but call out any vacation or similar "excluded" time here explicitly.
Summer of Code is a mentoring arrangement, and communication with your mentor is key. Please describe your expectations for communication with your mentor. Are you prepared to provide progress updates at least a few times a week while you're working? How are you most comfortable communicating (email, blog, IRC, so on)? While our mentors are making a commitment to give you time and attention over the summer, "stuff happens"; what would you do if your mentor disappeared for a week during the summer?
If you've spoken to someone in our community about this project, and they've agreed to mentor you for the summer, list them here. This is optional, but is particularly valuable if you're proposing a project not on our list. If it is on our ideas list, we can mostly figure this out.
