View source for Outreach Program for Women 2014 DecemberMarch

= Introduction =

QEMU is seeking funding to participate as a mentoring organization for [https://wiki.gnome.org/OutreachProgramForWomen/2014/DecemberMarch Outreach Program for Women 2014 December-March]. This page contains our ideas list and information for candidates and mentors.

'''Next deadline: September 8''' for initial list of project ideas and mentors.

= Find Us =

* IRC (OPW & GSoC specific): #qemu-gsoc on irc.oftc.net

* IRC (development):
** QEMU: #qemu on irc.oftc.net
** libvirt: #virt on irc.oftc.net
** KVM: #kvm on chat.freenode.net

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

Please contact the mentor for the project idea you are interested in.  IRC is usually the quickest way to get an answer.

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

* [[User:Stefanha|Stefan Hajnoczi]] (stefanha on IRC)

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

= Project Ideas =

This is the listing of suggested project ideas. Candidates are free to suggest their own projects by emailing qemu-devel@nongnu.org and (optionally) CCing potential mentors.

'''Note:''' These project ideas are also available to candidates applying for [[Outreach_Program_for_Women_Summer_2014|Outreach Program for Women]].

== QEMU projects ==

== KVM projects ==

== Libvirt projects ==


=== More intelligent virsh auto-completion ===

Even though there's already some auto-completion in virsh, it is not enough.
For better user experience, virsh should auto complete objects to virsh
commands, e.g. "start <TAB><TAB>" lists not only options that the start command
knows, but list of inactive domains as well. Moreover, the same applies to
command options. There already has been some attempts that can be taken as starting point.

Some useful threads to read before trying this:
[https://www.redhat.com/archives/libvir-list/2008-July/msg00175.html]
[https://www.redhat.com/archives/libvir-list/2011-October/msg00141.html]
[https://www.redhat.com/archives/libvir-list/2012-February/msg00649.html]
[https://www.redhat.com/archives/libvir-list/2013-January/msg00475.html]

* Skill level: beginner


=== Introducing job control to the storage driver ===

Currently, libvirt support job cancellation and progress reporting on domains.
That is, if there's a long running job on a domain, e.g. migration, libvirt
reports how much data has already been transferred to the destination and how
much still needs to be transferred. However, libvirt lacks such information
reporting in storage area, to which libvirt developers refer to as the storage
driver. The aim is to report progress on several storage tasks, like volume
wiping, file allocation an others.

* Skill level: intermediate


=== Your own idea ===

Just catch me (Michal Privoznik) on IRC and we can discuss what interests you.

'''Links:'''
* http://libvirt.org/
* http://wiki.libvirt.org/page/Main_Page
* http://www.ibm.com/developerworks/linux/library/l-libvirt/index.html?ca=drs-
* https://www.berrange.com/topics/libvirt/
* https://www.redhat.com/archives/libvir-list/

'''Details:'''
* Component: libvirt
* Skill level: (see description to each item)
* Language: C
* Mentor: Michal Privoznik <mprivozn@redhat.com>, mprivozn on IRC (#virt OFTC)
* Suggested by: Michal Privoznik <mprivozn@redhat.com>


=== Abstracting device address allocation ===

'''Summary:''' There are many types of addresses that devices can have in libvirt's XML description.  Not all address types are properly assigned and checked for duplicates.  The goal of this is to have an abstract data structure that would handle assigning all kinds of addresses, handle duplicates, etc.

'''Links:'''
* http://libvirt.org/formatdomain.html#elementsAddress
* https://www.redhat.com/archives/libvir-list/

'''Details:'''
* Skill level: beginner
* Language: C
* Mentor: Martin Kletzander <mkletzan@redhat.com>; mkletzan on IRC (OFTC and freenode)
* Suggested by: Martin Kletzander

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

= Information for mentors =

Mentors are responsible for keeping in touch with their candidate and assessing the candidate's progress.

The mentor typically gives advice, reviews the candidate's code, and has regular communication with the candidate 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 candidate's experience.

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