|
|
| Line 1: |
Line 1: |
| − | The ReactOS Project seeks to participate in the 2011 Google Summer of Code not only to improve ReactOS but also to help increase the pool of developers knowledgeable about Windows system development and interoperability. Unlike platforms like Linux and BSD, Windows is not open to easy experimentation and exploration, resulting in a decreased number of developers familiar with its internals. This often results in complications for open source projects that wish to provide Windows versions of their software due to a lack of expertise on the Windows NT architecture. By providing an open source implementation of the Windows NT family, ReactOS hopes to provide an environment that promotes experimentation and collaboration in Windows system development, thus helping developers from all backgrounds better understand the NT system and adopt better practices for software development targeting Windows.
| |
| − |
| |
| − | = 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. | | 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. | | 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. |
| Line 10: |
Line 6: |
| | 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. |
| | | | |
| − | == ReactOS GSoC Adminstrators ==
| + | = ReactOS GSoC Adminstrators = |
| | * [[Ged Murphy]] | | * [[Ged Murphy]] |
| | * [[Aleksey Bragin]] | | * [[Aleksey Bragin]] |
| | | | |
| − | == ReactOS GSoC Mentor Candidates ==
| + | = ReactOS GSoC Mentor Candidates = |
| − | * Aleksey Bragin | + | * [[Aleksey Bragin]] |
| − | * Art Yerkes | + | * [[Art Yerkes]] |
| − | * Colin Finck | + | * [[Colin Finck]] |
| − | * Ged Murphy | + | * [[Ged Murphy]] |
| − | * Giannis Adamopoulos | + | * [[Giannis Adamopoulos]] |
| − | * Hervé Poussineau | + | * [[Hervé Poussineau]] |
| − | * Jérôme Gardou | + | * [[Jérôme Gardou]] |
| − | * Johannes Anderwald | + | * [[Johannes Anderwald]] |
| − | * Kamil Hornicek | + | * [[Kamil Hornicek]] |
| − | * Roel Messiant | + | * [[Roel Messiant]] |
| − | * Sylvain Petreolle | + | * [[Sylvain Petreolle]] |
| − | * Timo Kreuzer | + | * [[Timo Kreuzer]] |
| − | | |
| − | = Application Form =
| |
| − | | |
| − | ;Organization Name
| |
| − | ReactOS
| |
| − | | |
| − | ;Description
| |
| − | The ReactOS Project develops an open source operating system which closely follows the Windows NT architecture and is binary compatible with its applications and drivers.
| |
| − | Home page
| |
| − | | |
| − | http://www.reactos.org
| |
| − | | |
| − | ;Main Organization License
| |
| − | | |
| − | GNU General Public License (GPL)
| |
| − | | |
| − | == Why is your organization applying to participate in GSoC 2011? What do you hope to gain by participating? ==
| |
| − | We seek to improve the state of open source software in the Windows community, both in awareness and overall code quality. By providing an open source implementation of Windows, we provide a first level example of what open source development can achieve in the Windows world. Participating in the Google Summer of Code 2011 presents us with an opportunity to engage with students worldwide who may have an interest in Windows development and potentially increase the number of open source developers that will possess Windows expertise.
| |
| − | | |
| − | == If accepted, would this be your first year participating in GSoC? ==
| |
| − | | |
| − | No
| |
| − | | |
| − | == Did your organization participate in past GSoCs? If so, please summarize your involvement and the successes and challenges of your participation. ==
| |
| − | | |
| − | In 2006, ReactOS was accepted as a mentoring organisation. A total of (4) students participated for “Remote Desktop client application and ActiveX Control”, “ReactOS Print Spooler Service”, “Login System” and “Clipboard Server API Implementation”.
| |
| − | | |
| − | The Remote Desktop client application and the Clipboard Server API Implementation projects have been completed successfully.
| |
| | | | |
| − | For the Print Spooler Service project, Google considered the work on this project to be unsatisfactory and unlisted it. The student stated that he was unable to meet the target goals due to unforeseen problems though he wished to continue with the project. As of today, we still have no Print Spooler Service.
| + | = Student Application Form = |
| − | | |
| − | The “Login System” was considered abandoned but the project itself was continued by one of our developers after GSoC ended. Attempts to contact the student failed, so we were not able to rectify the situation.
| |
| − | | |
| − | == If your organization participated in past GSoCs, please let us know the ratio of students passing to students allocated, e.g. 2006: 3/6 for 3 out of 6 students passed in 2006. ==
| |
| − | | |
| − | 2006 : 2 out of 4 students passed
| |
| − | | |
| − | == What is the URL for your ideas page? ==
| |
| − | | |
| − | [[Google_Summer_of_Code_2011]]
| |
| − | | |
| − | == What is the main development mailing list for your organization? This question will be shown to students who would like to get more information about applying to your organization for GSoC 2011. If your organization uses more than one list, please make sure to include a description of the list so students know which to use. ==
| |
| − | | |
| − | ros-dev@reactos.org (see http://www.reactos.org/mailman/listinfo/ros-dev)
| |
| − | | |
| − | == What is the main IRC channel for your organization? ==
| |
| − | | |
| − | #reactos on Freenode
| |
| − | Does your organization have an application template you would like to see students use? If so, please provide it now. Please note that it is a very good idea to ask students to provide you with their contact information as part of your template. Their contact details will not be shared with you automatically via the GSoC 2011 site.
| |
| − | | |
| − | == Student Application Form ==
| |
| | === General Information === | | === General Information === |
| | ;Full Name | | ;Full Name |
| Line 99: |
Line 46: |
| | 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. | | 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. |
| | | | |
| − | == What criteria did you use to select the individuals who will act as mentors for your organization? Please be as specific as possible. == | + | = Ideas List = |
| − | | + | [[Google Summer of Code 2011 Ideas]] |
| − | Our mentors were selected based on availability and familiarity with various parts of the Windows NT architecture, including but not limited to networking, filesystems, graphics, the registry, and hardware interfaces. In addition we place emphasis on the ability of a developer to act in a teaching role, who know how to guide students but provide enough freedom to allow the student to explore and learn how to achieve their goals through their own efforts. We will also encourage our mentors to be available to not just their assigned students, but also other students that have projects under ReactOS. Many of our mentor candidates are knowledgeable about a wide range of Windows NT technologies and can provide advice for topics beyond their assigned student’s project.
| |
| − | | |
| − | == What is your plan for dealing with disappearing students? ==
| |
| − | | |
| − | While every effort will be made to select students who are unlikely to disappear, we recognize that unpredictable circumstances are always possible. As such, we will require that all students provide backup contact information that we will verify as a failsafe in case students drop out of contact and are unable to inform us directly. Based on the situation, we will try to work with the student to accommodate any special circumstances that arise to ensure a project’s success, but if a student is unable to complete their project we will contact the GSoC team to consider any necessary actions, including marking a project as failed.
| |
| − | | |
| − | == What is your plan for dealing with disappearing mentors? ==
| |
| − | | |
| − | While the mentor candidates we have selected are considered highly reliable, we again recognize that life can result in unexpected circumstances. As noted above, the mentor candidates we have selected are knowledgeable in more than just one specific part of Windows NT, and we will encourage students to consult with not just their assigned mentor but also others taking part in the GSoC program. As such, students will always have advisers available to them even if their assigned mentor is unable to continue with the project.
| |
| − | | |
| − | == What steps will you take to encourage students to interact with your project's community before, during and after the program? ==
| |
| − | | |
| − | Students whose projects are selected will be introduced to the greater ReactOS community by their mentors. They will also be put in touch with several community members that are actively engaged in regression and feature testing, whom will be invaluable in helping students find a wider audience for testing their code. Students will also be encouraged to provide status updates to the community, which will provide opportunities for feedback and further engagement. Even after a project is completed, a student will have learned a great deal about Windows development and will know that the ReactOS project is available as a resource for any future development work they may pursue on Windows.
| |
| − | | |
| − | == If you are a small or new organization applying to GSoC, please list a larger, established GSoC organization or a Googler that can vouch for you here. ==
| |
| − | | |
| − | During a brief conversation between Aleksey Bragin and Chris DiBona at the IT-Spring 2009 Conference in Moscow, Mr. DiBona was rather surprised ReactOS was not taking advantage of the Google Summer Of Code program and suggested we do our best to participate.
| |
| − | | |
| − | == If you are a large organization who is vouching for a small organization applying to GSoC for their first time this year, please list their name and why you think they'd be good candidates for GSoC here: ==
| |
| − | | |
| − | N/A
| |
| − | | |
| − | == Anything else you'd like to tell us? ==
| |
| − | We would like to thank Google for sponsoring the Summer of Code program, as it provides an entry to students to the open source world.
| |
| − | | |
| − | We would also like to thank our friends at Haiku, especially Matt Madia and Urias McCullough, for their help in putting together this year’s GSoC proposal. Collaboration between our respective projects has slowly grown over the years and we greatly appreciate their advice and guidance for the application.
| |
| | | | |
| − | == Backup Admin (Link ID): == | + | = FAQ = |
| | + | == How do we interact with developers? == |
| | + | : ros-dev@reactos.org (see http://www.reactos.org/mailman/listinfo/ros-dev) |
| | + | : #reactos on Freenode |
| | | | |
| − | [[Aleksey Bragin]]
| + | == Besides my mentor, who else is available to help me? == |
| | + | Besides developers not directly involved as mentors, we encourage all of our mentors to interact with students. As such, consider any mentor or developer as a resource to field questions and help as needed. |
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 Ged Murphy.
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.
ReactOS GSoC Adminstrators
ReactOS GSoC Mentor Candidates
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
- 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.
Ideas List
Google Summer of Code 2011 Ideas
FAQ
How do we interact with developers?
- ros-dev@reactos.org (see http://www.reactos.org/mailman/listinfo/ros-dev)
- #reactos on Freenode
Besides my mentor, who else is available to help me?
Besides developers not directly involved as mentors, we encourage all of our mentors to interact with students. As such, consider any mentor or developer as a resource to field questions and help as needed.
