Difference between revisions of "Interns"

If you're an FD.io developer and you wish to participate as a Mentor, the easiest is to make a proposal in the ideas page. Take a look at what your FD.io project needs or what you feel FD.io should have. Feel free to submit ideas even if you cannot elaborate too much on them. However, the more detail you can provide, the more likely your potential interns will understand what you are looking for.

Your idea proposal should be a brief description of what the project is, what the desired goals would be, what the student should know and your email address for contact. The project ideas page has a template to aid in the creation of your project idea. Please note, though, that the students are not required to follow your idea to the letter, so regard your proposal as just a suggestion.

if you would like to get an idea of what is involved in being a good mentor, here are some excellent resources:

• Google Summer of Code Mentoring Guide.
• FOSS Outreach Program Guide For Mentors

Finally, know that we will never assign you to a project you do not want to work on. We will not assign you more projects than you can/want to take on either. And you will have a backup mentor, just in case something unforeseen takes place.

• Provide ample documentation for your proposed project, including a getting started guide.
• Prepare and test any packages or VMs prior to your Interns start date
• Verify all patches submitted by your Intern
• Ensure that you have sufficient bandwidth to meet with your Intern a minimum of once per week and respond to any questions that may arise.
• Share contact information with community members who may be able to help your Interns in case you are not available.
• Set expectations and milestones for your Intern each week and discuss outcome of expectations during evaluations.
  • Keep track of milestone progress to share with the Linux Foundation as midterm and final evaluations.
• Notify Internship Program Leadership of any Intern issues (Lack of participation, communication or vacations).
• Provide Midterm and Final evaluation reports within 1 week the perspective dates.

Students wishing to participate in any of the FD.io internships must realize this is more than a mere formality. You will be required to finish your work for FD.io in 3 months. You will also take some resources from FD.io developers, who will dedicate a portion of their time to mentoring you. Therefore, we'd like to have candidates who are committed to helping the FD.io Project.

You don't have to be a proven developer -- in fact, this whole program is meant to facilitate joining the FD.io project and other Open Source communities. However, experience in coding, C, and/or experience with networking concepts is welcome.

You should start familiarizing yourself with the components that you plan on working on before the start date. FD.io developers are available on mailing lists and on IRC for help. Note that the timeline for the intern program reserves a lot of time for bonding periods: use those periods wisely.

A project proposal is what you will be judged upon. So, as a general recommendation, write a clear proposal on what you plan to do, what your project is and what it is not, etc. Several websites now contain hints and other useful information on writing up such proposals.

FD.io does not require a specific format or specific list of information, but here are some specific points that you should address in your application:

• The project you are proposing.
• Why you’d like to execute on this particular project and the reason you’re the best individual to do so.
• Details of your academic, industry and/or open source development experience, as well as other details as you see fit.
• Provide links to the Gerrit URL(s) of your submitted patches to any project, at least one patch must be provided
• An explanation of your development methodology.
• Your contact information.
• One or two references.
• Regardless of what you include in your proposal, we recommend you speak to the FD.io project and/or mentor you are applying to about what they are looking for in a proposal to give you the best chance of success in your proposal.
• Interns can submit their own project proposals if desired. If you as an Intern submit your own proposal (here), please contact Casey Cain to request a mentor.
• Finally, please also include proof of current academic attendance (transcript, copy of student ID). You must be a current or graduating student in 2017 to be eligible.

After you have written your proposal, you should get it reviewed. Do not rely on the FD.io mentors to do it for you: they will only send back a proposal if they find it lacking. Instead, ask a colleague or a developer to do it for you. Once your proposal is ready send it here! A Linux Foundation staff member will get back to you shortly.

Basic Template

You can make a copy of and use this doc as a basic template to submit your Project Proposals. This can act as a living document to help track the progress of your internship. You are welcome to use other tools or services though. If you are having trouble reaching the document, please let your mentor know.

Hints

Submit your proposal early: early submissions get more attention from developers for the simple fact that they have more time to dedicate to reading them. The more people see it, the more it'll get known.

Do not leave it all to the last minute: Make sure you send your application before the final rush. Also, note that the applications submitted very late will get the least attention from mentors, so you may get a low vote because of that.

Keep it simple: we don't need a 10-page essay on the project and on you. You just need to be concise and precise.

Know what you are talking about: the last thing we need is for students to submit ideas that cannot be accomplished realistically or ideas that aren't even remotely related to FD.io or SDN. If your idea is unusual, be sure to explain why you have chosen FD.io as the best place to do your internship.

Aim wide: submit more than one proposal, to different areas of FD.io. You may also submit your proposal through more than one intern program.

• Please be prepared to work 40 hours per week for the entire duration of the Internship.
• Interns must show that they have at least 1 commit to any open source project before your internship starts.
  • You can work with your mentor during the application period to accomplish this goal.
• Attend at least 1 meeting per week with your assigned Mentor.
• Attend at least 1 meeting per week with your fellow Interns
• At least 1 commit to the FD.io repository by the end of your Internship.
• Provide a weekly project status update to the Interns group.