View source for Google Summer of Code 2024

= Introduction =

QEMU is applying for [https://summerofcode.withgoogle.com/ Google Summer of Code 2024]. This page contains our ideas list and information for applicants and mentors. Google Summer of Code is an open source internship program offering paid remote work.

'''Status: QEMU was not accepted into GSoC 2024. If you would like to work with us on these project ideas outside of GSoC and without funding, please contact the mentors for the project idea you are interested in. We hope to participate in GSoC again next year.'''

= Application Process =

=== 1. Discuss the project idea with the mentor(s) ===

Read the project ideas list and choose one you are interested in. Read the links in the project idea description and start thinking about how you would approach this. Ask yourself:
* Do I have the necessary technical skills to complete this project?
* Will I be able to work independently without the physical presence of my mentor?

If you answer no to these questions, choose another project idea and/or organization that fits your skills.

Once you have identified a suitable project idea, email the mentor(s) your questions about the idea and explain your understanding of the project idea to them to verify that you are on the right track.

=== 2. Submit your proposal ===

Upload your proposal PDF file to the [https://summerofcode.withgoogle.com/ Google Summer of Code website] and notify your mentor(s) so they can give you feedback. You can make changes and upload the PDF again until the application deadline. Your proposal must include the following:
* Project idea (title)
* Your name and email address
* Outline of your solution
** Do some background research by looking at source code, browsing relevant specifications, etc in order to decide how to tackle the project. Discuss any questions with your mentor. This section will explain how your solution will work.
* Project schedule
** Create a week-by-week schedule of the coding period. Breaking down the project into tasks and estimate how many weeks they will take. The schedule can be adjusted during the summer so don't worry about getting everything right ahead of time.
* Relevant experience (programming language knowledge, hobby projects, etc)
* Are you available to work with no other commitments (jobs, university, vacation, etc) for the duration of your project? If not, please give details about the working hours and dates.

=== 3. Contribution task ===

Once you have submitted your proposal PDF, let your mentor know and request a contribution task. The task will be a real bug or small feature that should not take more than 1 or 2 days to complete. This will allow you to demonstrate your skills in a realistic setting. Your mentor will provide you the details and help you with any questions.

== Key Dates ==

From the [https://developers.google.com/open-source/gsoc/timeline timeline]:

* February 21 18:00 UTC - Organizations and project ideas announced
* March 18 - April 2 18:00 UTC - Application period
* April 21 - Contribution task deadline
* May 1 18:00 UTC - Accepted applicants announced
* May 27 - August 26 - Standard coding period (an extended timeline is possible depending on your project)

= Find Us =

* IRC (GSoC specific): [https://webchat.oftc.net/?channels=qemu-gsoc #qemu-gsoc on irc.oftc.net]

* IRC (development):
** QEMU: [https://webchat.oftc.net/?channels=qemu #qemu on irc.oftc.net]
** KVM: #kvm on chat.freenode.net

* Mailing lists:
** QEMU: [http://lists.nongnu.org/mailman/listinfo/qemu-devel qemu-devel]
** KVM: [http://www.linux-kvm.org/page/Lists,_IRC linux-kvm]

For general questions about QEMU in GSoC, please contact the following people:

* [[User:Stefanha|Stefan Hajnoczi]] <stefanha@gmail.com> (stefanha on IRC)

= Project Ideas =
This is the listing of suggested project ideas. Students are free to suggest their own projects, see [[#How to propose a custom project idea]] below.

{{:Internships/ProjectIdeas/RISCVVectorFrontendOptimization}}
{{:Internships/ProjectIdeas/GStreamerVhostDeviceSound}}
{{:Internships/ProjectIdeas/PackedShadowVirtqueue}}
{{:Internships/ProjectIdeas/VhostUserMemoryIsolation}}
{{:Internships/ProjectIdeas/NitroEnclaves}}
{{:Internships/ProjectIdeas/TCGBinaryTracing}}

== How to add a project idea ==
# Create a new wiki page under "Internships/ProjectIdeas/YourIdea" and follow [[#Project idea template]].
# Add a link from this page like this: <nowiki>{{:Internships/ProjectIdeas/YourIdea}}</nowiki>

This is the listing of suggested project ideas. Students are free to suggest their own projects, see [[#How to propose a custom project idea]] below.

== Project idea template ==

 <nowiki>=== TITLE ===
 
 '''Summary:''' Short description of the project
 
 Detailed description of the project.
 
 '''Links:'''
 * Wiki links to relevant material
 * External links to mailing lists or web sites
 
 '''Details:'''
 * Skill level: beginner or intermediate or advanced
 * Language: C
 * Mentor: Email address and IRC nick
 * Suggested by: Person who suggested the idea</nowiki>

= How to propose a custom project idea =

Applicants are welcome to propose their own project ideas.  The process is as follows:

# Email your project idea to qemu-devel@nongnu.org.  CC Stefan Hajnoczi <stefanha@gmail.com> and regular QEMU contributors who you think might be interested in mentoring.
# If a mentor is willing to take on the project idea, work with them to fill out the "Project idea template" above and email Stefan Hajnoczi <stefanha@gmail.com>.
# Stefan will add the project idea to the wiki.

Note that other candidates can apply for newly added project ideas.  This ensures that custom project ideas are fair and open.

= How to get familiar with our software =

See what people are developing and talking about on the mailing lists:
* [http://thread.gmane.org/gmane.comp.emulators.qemu/ qemu-devel]
* [https://www.redhat.com/archives/libvir-list/ libvir-list]
* [http://www.spinics.net/lists/kvm/ kvm]

Grab the source code or browse it:
* [http://git.qemu-project.org/?p=qemu.git;a=summary qemu.git]
* [http://libvirt.org/git/?p=libvirt.git;a=summary libvirt.git]
* [https://git.kernel.org/cgit/virt/kvm/kvm.git/ kvm.git]

Build QEMU and run it: [http://wiki.qemu-project.org/Hosts/Linux QEMU on Linux Hosts]

= Links =

* [https://google.github.io/gsocguides/student/ Student Manual]
* [https://developers.google.com/open-source/gsoc/faq FAQ]
* [https://developers.google.com/open-source/gsoc/timeline Timeline]
* [http://blog.vmsplice.net/2011/03/advice-for-students-applying-to-google.html Advice for students applying (from 2011 but still relevant!)]

= Information for mentors =

Mentors are responsible for keeping in touch with their intern and assessing progress. GSoC has evaluations where both the mentor and intern assess each other.

The mentor typically gives advice, reviews the intern's code, and has regular communication with the intern to ensure progress is being made.

Being a mentor is a significant time commitment, plan for 5 hours per week. Make sure you can make this commitment because backing out during the summer will affect the intern's experience.

The mentor chooses their intern by reviewing application forms and conducting IRC interviews with applicants. Depending on the number of candidates, this can be time-consuming in itself. Choosing the right intern is critical so that both the mentor and the intern can have a successful experience.

[[Category:GSoC]]