Difference between revisions of "Google Summer of Code 2012"
(Created page with "= Ideas = See the Google Summer of Code 2012 Ideas page for our project ideas in 2011. = Student Guide = Every student new to ReactOS should begin by obtaining the code thro…") |
Heis Spiter (talk | contribs) |
||
| Line 1: | Line 1: | ||
= Ideas = | = Ideas = | ||
| − | See the [[Google Summer of Code 2012 Ideas]] page for our project ideas in | + | See the [[Google Summer of Code 2012 Ideas]] page for our project ideas in 2012. |
= Student Guide = | = Student Guide = | ||
| Line 6: | Line 6: | ||
Also every student should subscribe to the [http://www.reactos.org/mailman/listinfo/ros-dev ros-dev] mailing list and optionally could join the [irc://irc.freenode.net/#reactos #reactos] channel on Freenode’s IRC network for a live discussion with developers. | Also every student should subscribe to the [http://www.reactos.org/mailman/listinfo/ros-dev ros-dev] mailing list and optionally could join the [irc://irc.freenode.net/#reactos #reactos] channel on Freenode’s IRC network for a live discussion with developers. | ||
| − | By default, students will receive a branch in SVN to work on their code. If you prefer a different version control system like Git or Mercurial, please contact our Summer of Code administrator [[ | + | By default, students will receive a branch in SVN to work on their code. If you prefer a different version control system like Git or Mercurial, please contact our Summer of Code administrator [[Amine Khaldi]]. |
MSDN and plenty of available Windows publications serve as the primary reference for functionality ReactOS seeks to implement. However, there are parts of Windows that are poorly documented or completely undocumented. In these instances, the ReactOS [[Techwiki]] may possess descriptions of the data structures or interfaces. The student may have to conduct some research, following project guidelines on respecting intellectual property, and write some documentation of their own if none exists however, though mentors will try to help with any missing gaps. | MSDN and plenty of available Windows publications serve as the primary reference for functionality ReactOS seeks to implement. However, there are parts of Windows that are poorly documented or completely undocumented. In these instances, the ReactOS [[Techwiki]] may possess descriptions of the data structures or interfaces. The student may have to conduct some research, following project guidelines on respecting intellectual property, and write some documentation of their own if none exists however, though mentors will try to help with any missing gaps. | ||
Revision as of 22:13, 9 March 2012
Contents
Ideas
See the Google Summer of Code 2012 Ideas page for our project ideas in 2012.
Student Guide
Every student new to ReactOS should begin by obtaining the code through our Subversion repository and performing a first build using our ReactOS Build Environment. This environment ensures consistent build results, eliminates the need to setup your own toolchain and makes ReactOS one of the easiest operating systems to build. These first steps are also exemplified in this video. Also every student should subscribe to the ros-dev mailing list and optionally could join the #reactos channel on Freenode’s IRC network for a live discussion with developers.
By default, students will receive a branch in SVN to work on their code. If you prefer a different version control system like Git or Mercurial, please contact our Summer of Code administrator Amine Khaldi.
MSDN and plenty of available Windows publications serve as the primary reference for functionality ReactOS seeks to implement. However, there are parts of Windows that are poorly documented or completely undocumented. In these instances, the ReactOS Techwiki may possess descriptions of the data structures or interfaces. The student may have to conduct some research, following project guidelines on respecting intellectual property, and write some documentation of their own if none exists however, though mentors will try to help with any missing gaps.
Our GSoC Adminstrators
Our Mentor Candidates
- Fill in
Student Application Form
General Information
- Full Name
- Languages You Speak
- Timezone
- myReactOS Account Name
- IRC Nickname on Freenode
Time Commitment
Please outline any additional obligations you may have during the summer and how much of your time you will be able to commit to your GSoC project.
Optional (But Suggested)
- Proposed Project
Please provide a brief description of, or a link to, the project you are interested in
- Proposed Milestones
For projects that are relatively easy to quantify, please propose milestones that can be used to gauge progress on the project.
- Legal Requirements
Students are required to affirm that the following is true. I hereby swear that I have not used nor seen the source code to any version of the Windows operating system nor any Microsoft product that may be related to the proposed project that is under a license incompatible with contribution to ReactOS, including but not limited to the leaked Windows 2000 source code and the Windows Research Kernel.
