= RTEMSSummerOfCode2013 = [[TOC(GSoC/2013, depth=2)]] [[Image(Soc-logo-google-blue.jpg)]]
[http://www.google-melange.com/gsoc/homepage/google/gsoc2013 Google Summer of Code 2013 Office Web Site]
RTEMS is happy that the Google will once again sponsor the Summer of Code in 2013 and that RTEMS plans to apply to be a participating organization. Please use this page as a jumping off point and ask questions. The most important thing is becoming a part of the community and participating. Potential Students: Read through all the material on this page, and be sure to add yourself to the table in the Student Information section. Remember to fill out an official GSOC application in addition to the informal application we request. We also require you build RTEMS, create an application, run it and post the result to the RTEMS mailing list. The Configure and Build RTEMS page has the details on how you do this. Information on what to post are found on the Prove You Can Work On RTEMS page. For new comers to RTEMS we recommend you use a proven Virtual Machine image. Potential Mentors: Share your knowledge and pledge to help a student. Visit the [1] URL for GSoC 2012 to register as a mentor and then add yourself to the list of RTEMS Mentors. Potential Students: Read through all the material on this page, and be sure to add yourself to the table in the Student Information section. Remember to fill out an official GSOC application in addition to the informal application we request. We also require you build RTEMS, create an application, run it and post the result to the RTEMS mailing list. The Configure and Build RTEMS page has the details on how you do this. Information on what to post are found on the Prove You Can Work On RTEMS page. For new comers to RTEMS we recommend you use a proven Virtual Machine image. Potential Mentors: Share your knowledge and pledge to help a student. Visit the [1] URL for GSoC 2012 to register as a mentor and then add yourself to the list of RTEMS Mentors. Information for prior years: * See RTEMS [wiki:GSoC/2012 Summer of Code 2012] * See RTEMS [wiki:GSoC/2011 Summer of Code 2011] * See RTEMS [wiki:GSoC/2010/Main **NAME** Summer of Code 2010] * See RTEMS [http://wiki.rtems.org/wiki/index.php/RTEMS_Summer_Of_Code_2009 Summer Of Code 2009] and [http://www.google-melange.com/gsoc/homepage/google/gsoc2009 Google Summer of Code 2009] * See RTEMS [http://wiki.rtems.org/wiki/index.php/RTEMS_Summer_Of_Code_2008 Summer Of Code 2008] = General Information = = General Program Information and Guidance = * [http://www.google-melange.com/ Google's Starting Page for the Summer of Code] * [http://www.booki.cc/gsocstudentguide/ GSoC Student Guide] - This is a community developed book. = RTEMS Specific Information = * [wiki:TBR/Delete/Virtual_Machines_for_RTEMS_Development Fedora 14 RTEMS 4.10 and 4.11 Virtual Machines] are pre-configured RTEMS development environment on Fedora 14. They are virtual machines playable with [http://www.virtualbox.org VirtualBox]. For students who do not have a dedicated Fedora 14 installation, this is a great way to work with RTEMS with a minimum of pain and setup. * [http://www.rtems.com/moodle/ RTEMS University] - included are presentations on GSoC and RTEMS as well as a presentation on GSoC from the RTEMS Project perspective. * [wiki:GSoC/GettingStarted GSoC Getting Started] - getting up to speed with RTEMS development for GSoC students. * [http://rtems.org/onlinedocs/doc-current/share/rtems/html/ RTEMS User Documentation (git daily)] Be sure to add yourself to the table below. = Project Ideas = [wiki:Developer/OpenProjects Open Projects] contains the open projects list for RTEMS. It is by no means an all inclusive list and we are open to suggestions. Submissions of ports to new architectures, new BSPs, new device drivers, and test improvements are always welcomed. = Student Information = [wiki:Developer/GSoC/ProjectManagement SoC Project Management] Please visit [wiki:Developer/OpenProjects Open Projects] to see if you can find a project that interests you. If you have any questions about the projects, feel free to ask on the email list or IRC. The project descriptions were usually written by someone with a high level of insight into the problem who would be happy to explain things in more detail to you. We have provided a [https://docs.google.com/document/d/1d_-wtMV_BH4WzkMoysTqFS8BtZhh3i7uCzoAWLqVSe4/edit?usp=sharing Google Docs template] for the Student Proposal. Feel free to copy it and invite potential mentors to review. Please be aware that this is NOT the official form to submit your proposal on. Your official application must be submitted through the GSOC Melange system. Periodically cut and paste your proposal into the student application form and save it in Melange. This avoids the last minute rush to do it. Typically the website is overloaded in the last few hours before the student proposal deadline. We want you to be able to hit the ground running and are asking you to show that you can actually build RTEMS, modify it a little, and run samples. Please visit the GSoC Getting Started page for details. Students working on code should require no special hardware. The development can all be done and tested using a GNU/Linux host (preferably RPM based). Between the simulators in gdb, skyeye, and qemu, there is plenty of simulated target hardware. RTEMS is an operating system targeting embedded systems. All development is cross-platform, meaning that you develop on a host system and run programs on a target system. Some of the projects are focused on improving the user development experience. Eclipse has proven popular for cross embedded development and one of the suggested projects is to bring those capabilities to RTEMS. RTEMS is designed to operate under tight resource restrictions. Some of the projects focus on breaking existing linkages between subsystems so those limits can be lowered further. Another area of effort is helping RTEMS fit into smaller systems. Even though it is targeted to embedded systems, developers still expect as many features as possible. RTEMS provides a robust set of POSIX primitives and what is now known as the Classic API which provides hard real-time functionality. Some of the projects are focused on implementing a few missing pieces of POSIX functionality. = References = * [https://code.google.com/p/google-summer-of-code/wiki/AdviceforStudents Advice for Google Summer of Code Students] from GSoC pageHow * HOWTO: [http://drupal.org/node/59037 Write a Summer of Code application] from Drupal. * [http://blog.gerv.net/2006/05/how_not_to_apply_for_summer_of/ How Not to Apply to GSoC] = Students Proposals = The final version of your proposal must be submitted via Melange at Google. But until then, please use Google Docs and put the link in this table. That way any mentor or RTEMS community member can request access and comment on your proposal. Students.. please don't peek at each other. :)
GSOC STUDENTS! PLEASE FILL IN THE APPLICATION AT http://www.google-melange.com! YOU CAN EDIT UNTIL THE DEADLINE! BUT YOU WILL NOT GET A SLOT IF YOU DO NOT APPLY THROUGH Google!!!
{| border="1" style="margin: 1em auto 1em auto;text-align: center;" |+ |- |'''Student''' || '''Completed Hello''' || '''IRC Handle''' || '''Proposal Title''' || '''Google Docs URL''' |- |NAME || Yes or No|| on #rtems || Title || Link to Google Docs for proposal | |- |Jin Yang || Yes || SYCrane || CAN driver and API for CAN stack || [https://docs.google.com/document/d/1PCJ4MAR03fH2tm22AA_OD-h5Xlh68yYL08y9bBOIkCM/edit# Proposal] |- |Prateek Tiwari || Yes || prateekt || Supercore Scheduler || Link to Google Docs for proposal | |- |Hesham ALmatary || Yes || Hesham || Enhance low-level API of libmm (Memory Protection & Caches) || Link to Google Docs for proposal | [https://docs.google.com/document/d/1zyhChVLTmNt1MEM1h4BTXlPAxATQx00trWXXIDNMsYQ/edit# Proposal] |- |Deng Hengyi || Yes || weiY || Atomic Operations and SMP lock debug tool for RTEMS || Link to Google Docs for proposal | [https://docs.google.com/document/d/1kZtTwyw8xBzGSz-n8xFcTuD5KSrEpnzzq860wMaQtCU/edit# Proposal] |- |Dhananjay Balan || Yes || dhananjay || Better RTEMS Support in GDB || Link to Google Docs for proposal | |- |Peng Fan || Yes || freenix || A framework design and implementation for RTEMS MMU || Link to Google Docs for proposal | [https://docs.google.com/document/d/1CEXw7LZv5loo2zcjDUsXBR56k-fvuuUK79hWWUEDgno/edit# Proposal] |- |Shubham Somani || Yes || S_Somani || Application Configuration GUI for RTEMS. || Link to Google Docs for proposal | [https://docs.google.com/document/d/1oFjUvydBm78fyIQzq2ol6M7tdkC_f6c21hzoHjXzuJc/edit?usp=sharing/edit# Proposal] |- |Philipp Eppelt || Yes || phipse || Paravirtualization of RTEMS || [https://docs.google.com/document/d/10SWiyYg6WEeMdAeysyahbS6XK5QwyIMlUvAr4aFOyX4/edit# Proposal] |- |Vipul Nayyar || Yes || vipulnayyar || Unified API || |- |Jaskaran Singh || Yes || || || | |} The ''Student'' column is for your name. The ''Completed Hello'' column lets us all know whether or not you completed the require Hello World project. Based upon our experience, students who have successfully compiled and run an RTEMS application have a MUCH MUCH higher chance of success on the proposed project. The ''IRC Handle'' column is your handle on IRC. RTEMS folks hang out in #rtems on freenode.net. The ''Proposal Title'' should be self-explanatory. If approved, we will ask you to create a code.google.com project to host your work and link to it here. You will need to give at least your mentor and [wiki:User:JoelSherrill Joel Sherrill] read/write access. The ''Google Docs URL'' is your proposal in Google Docs that can be reviewed and commented on by mentors. = RTEMS Mentors = See our [wiki:GSoC/Mentors RTEMS Mentors] page for a list of potential project mentors.