Wine and the Google Summer of Code
This page collects some tips for students who want to work on Wine during the Summer of Code, and provides a few ideas for projects.
- Do you:
- Know C?
- Perhaps have done some Win32 low-level Windows programming already (below MFC)?
- Have an idea to improve Wine and make it more useful and popular?
- Perhaps improve a specific application to run under Wine? (it however needs to be predictable ahead in scope for Summer of Code)
- If so, please introduce yourself on the wine-devel mailing list or the #winehackers IRC channel at freenode.net, and apply for a Google Summer of Code scholarship!
- Hint/reminders:
- Have a look at the developers page on the wiki and grab Wine's source code, try to get acquainted with it
- Look at Previous Summers Of Code for previously accepted proposals / their results
- Do not forget: we can only support one proposal per application. You can file multiple applications if you want to propose more than one idea.
- Copying proposals verbatim will get your proposal deleted without even looking at it twice. You have to make your own proposal. See also PostgreSQL's Summer Of Code Advice
- Read How can I prepare for GSoC for some general rules.
- Read How Not To Apply For Summer Of Code to save your time and save our time.
- Note: Applicants MUST have submitted a patch or testcase to wine-devel (see Submitting Patches) to be considered for acceptance.
To apply, go to the Google Summer of Code home page.
Important notes!
- Applicants MUST have submitted a patch or testcase to wine-devel (see Submitting Patches) to be considered for acceptance.
- Please first send a draft proposal and discuss it with us, don't send the final one directly.
- We cannot accept ReactOS proposals, so please only make proposals that will benefit Wine.
To apply, go to the Google Summer of Code home page.
Beware of Legal Requirements
You must state that you will follow these minimal legal requirements during the SoC (and have done so in the past):
- You are not allowed to read or reuse Windows source code (leaked source / Windows Research Kernel* / ...)
(* we are following the SFLC's advice)
- You are not allowed to reverse engineer Windows files by disassembling or decompiling them
- You are not allowed to analyze Windows files with the trace functions of Wine
- People who work or have worked for Microsoft should probably not participate
Other Outreach Programs
In addition to Google Summer of Code Wine also participates in:
- Outreachy is a program similar to GSoC organized by the Software Freedom Conservancy. The goal of Outreachy is to provide encouragement, experience, and networking opportunities for minorities that are underrepresented in tech. Unlike GSoC, it is not limited to students; you can read the Wine Wiki's Outreachy page for more information.
- Google Code-In is aimed at pre-university students and doesn't require any previous coding experience. As a result, the tasks for Code-In participants are more focused, smaller, and have a gentler learning curve. Some aren't even programming tasks but related to other aspects of an open-source project, such as market research, user-support, or documentation. For more details, see the Wine Wiki's Code-In page.
Ideas
Your own idea
Possible mentors: We'll provide you with the appropriate mentor
- If you have an idea, please post it on Wine Developers mailing list so we can help you with your idea and find out if it's realistic or not. Showing initiative and willing to discuss your idea greatly improves your chances of getting accepted. Even more so than taking one of the ideas below.
- As long as you work hard and interact with the community and your mentor in a positive and constructive way you don't have to worry about not meeting all your goals.