= RTEMSSummerOfCode2012 = FIX ME - Retrieve from archives somehow. This needs to be the RTEMSGoogleSummerofCode page as it was on 1 March 2013. This is a cut and paste from archive.org on 15 July 2012 which should be close enough. [[TOC(GSoC/2012, depth=2)]] [[Image(GSOC12logo.png)]]
[http://www.google-melange.com/gsoc/homepage/google/gsoc2012 Google Summer of Code 2012 Office Web Site]
RTEMS was proud to be a participating organization in the Google Summer of Code in 2012. This page is a historical record. = 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:GSoC/GettingStarted GSoC Getting Started] helps students get up to speed with RTEMS development for GSoC and outlines how to accomplish the "Hello world" requirement for applying as a student. * [wiki:TBR/Delete/Virtual_Machines_for_RTEMS_Development Virtual Machines Development] are pre-configured RTEMS development environments inside of virtual machines playable with VirtualBox. For students who do not have a dedicated development installation virtual machines are a great way to work with RTEMS with a minimum of pain and setup. * [http://www.rtems.com/moodle/ RTEMS University] includes presentations on GSoC and RTEMS as well as a presentation on GSoC from the RTEMS Project perspective. * [http://rtems.org/onlinedocs/doc-current/share/rtems/html/ RTEMS User Documentation] = 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.= RTEMS Mentors = See our [wiki:GSoC/Mentors RTEMS Mentors] page for a list of potential project mentors. = 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/1iJuF2MQUHFU72WirZByifdpzIOLrOC-JUqXpcSS4srE/edit?authkey=COi90NwI&authkey=COi90NwI&pli=1 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 = * Drupal has some information on the writing applications that looks promising The following link contains some information about how to write a proposal: How Not To Apply For Summer Of Code = Students Proposals = The final version of your proposal must be submitted via Melange at Google. 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 IT 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''' |- | RTEMS Student || Yes|| myircnick|| Sample Project||Proposal |- |Wiktor Langowski|| Yes || Wik|| ARINC 653 API || [https://docs.google.com/document Proposal] |- | Deng Hengyi || Yes || WeiY|| Atomic Operations || [https://docs.google.com/document Proposal] |- | Hesham Moustafa|| Yes|| Hesham|| RTEMS MMU/MPU support for ARM architecture|| [https://docs.google.com/document Proposal] |- | Kevin Polulak|| Yes|| soh_cah_toa|| Update the RTEMS TCP/IP Stack||[https://docs.google.com/document Proposal] |- | Zhongwei Yao|| Yes|| zw_yao|| Use hash or map in POSIX keys||[https://docs.google.com/document Proposal] |- | Xi Yang|| Yes|| yangxi|| RTEMS on Asymmetric Multicore Platform (Panda Board)|| [https://docs.google.com/document Proposal] |- | Hongyu Tian|| Yes|| stove90tihuy|| Deferred Memory Management for Multi-core|| [https://docs.google.com/document Proposal] |- | Xiang Cui|| Yes|| medivhc|| Bdbuf Improvements|| [https://docs.google.com/document Proposal] |- | Jiang Hong Bo|| Yes|| jianghongbob|| Port RTEMS to STM32|| [https://docs.google.com/document Proposal] |- | Claas Ziemke|| Yes|| claas || Code a BSP for BeagleBoard and/or BeagleBone|| [https://docs.google.com/document Proposal] |- | Xiaochen Pan|| Yes|| Deb|| RTEMS Testing|| [https://docs.google.com/document Proposal] |- | Alex-Sever Horin|| Yes|| alseh|| Porting NXLib & updating libraries ...|| [https://docs.google.com/document Proposal] |- |} The Student column is for your name. The Completed Hello column lets us all know whether or not you've completed the required Hello World project (see GSoC Getting Started). 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 the #rtems channel on irc.freenode.net. The Proposal Title should be self-explanatory. If approved, we will ask you to create a [http://code.google.com/ Google Code] project to host your work and link to it here. You will need to give at least your mentor and Joel Sherrill read/write access. The Google Docs URL is your proposal on [http://docs.google.com/ Google Docs] that can be reviewed and commented on by mentors.