View source for Google Summer of Code 2022

= Introduction =

QEMU has been accepted into [https://summerofcode.withgoogle.com/ Google Summer of Code 2022]. 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.

= 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. Fill out the application form ===

The [https://summerofcode.withgoogle.com/ application form] asks for a problem description and outline of how you intend to implement a solution. You will need to do some background research (looking at source code, browsing relevant specifications, etc) in order to decide how to tackle the project. The form asks for an initial project schedule which you should create by breaking down the project into tasks and estimating how long they will take. The schedule can be adjusted during the summer so don't worry about getting everything right ahead of time.

=== 3. IRC interview including a coding exercise ===

You may be invited to an IRC interview. The interview consists of a 30-minute coding exercise, followed by technical discussion and a chance to ask questions you have about the project idea, QEMU, and GSoC. The coding exercise is designed to show fluency in the programming language for your project idea (QEMU projects are typically in C but could also be in Python or Rust).

Here is a C coding exercise we have used in previous years when interviewing applicants: [http://pastebin.com/6J1wwDhK 2014 coding exercise]

Try it and see if you can complete it comfortably. We cannot answer questions about the previous coding exercise but hopefully it should be self-explanatory.

If you find the exercise challenging, think about applying to other organizations where you have a stronger technical background and will be more competitive compared with other candidates.

== Key Dates ==

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

* March 7 - Organizations and project ideas announced
* April 4 to 19 18:00 UTC - Application period
* May 20 - Accepted applicants announced
* June 13 to September 12 - Coding period

= 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/VirtIOBlkZonedBlockDevices}}
{{:Internships/ProjectIdeas/VIRTIO_F_IN_ORDER}}
{{:Internships/ProjectIdeas/EncryptedStorageInVMBasedContainerRuntimes}}
{{:Internships/ProjectIdeas/S390xRISU/}}
{{:Internships/ProjectIdeas/SnapshotFuzzingDevice}}
{{:Internships/ProjectIdeas/CoverageGuidedDiskImageFuzzer}}
{{:Internships/ProjectIdeas/NVMePerformance}}
{{:Internships/ProjectIdeas/RustVMMReferenceAarch64}}
{{:Internships/ProjectIdeas/LibclangRefactoring}}
{{:Internships/ProjectIdeas/QEMUNitroEnclave}}

== 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>

Example idea from a previous year: [[Internships/ProjectIdeas/I2CPassthrough]]

== 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]]