Changes between Version 3 and Version 4 of GSoC/2012


Ignore:
Timestamp:
Mar 4, 2013, 10:03:49 PM (7 years ago)
Author:
JoelSherrill
Comment:

First hack at recreating it from archive.org

Legend:

Unmodified
Added
Removed
Modified
  • GSoC/2012

    v3 v4  
    33
    44FIX ME - Retrieve from archives somehow. This needs to be the RTEMSGoogleSummerofCode page as it was on 1 March 2013.
     5
     6This is a cut and paste from archive.org on 15 July 2012 which should be close enouugh.
     7==  ===================
     8
     9OfCode
     10From RTEMSWiki
     11Contents [hide]
     121 General Information
     131.1 General Program Information and Guidance
     141.2 RTEMS Specific Information
     151.3 Project Ideas
     161.4 RTEMS Mentors
     172 Student Information
     182.1 References
     193 Students Proposals
     20
     21
     22Google Summer of Code 2012 Office Web Site
     23RTEMS is happy that the Google will once again sponsor the Summer of Code in 2012 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.
     24Potential 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.
     25Potential 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.
     26Information for prior years:
     27 *  See RTEMS Summer of Code 2011
     28 *  See RTEMS Summer of Code 2010
     29 *  See RTEMS Summer Of Code 2009 and Google Summer of Code 2009
     30 *  See RTEMS Summer Of Code 2008
     31= General Information =
     32
     33= General Program Information and Guidance =
     34
     35 *  Google's Starting Page for the Summer of Code
     36 *  GSoC Student Guide - This is a community developed book.
     37= RTEMS Specific Information =
     38
     39 *  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.
     40 *  Virtual_Machines_for_RTEMS_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.
     41 *  RTEMS University includes presentations on GSoC and RTEMS as well as a presentation on GSoC from the RTEMS Project perspective.
     42 *  RTEMS User Documentation
     43= Project Ideas =
     44
     45Open_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 =
     46
     47See our RTEMS Mentors page for a list of potential project mentors.
     48= Student Information =
     49
     50= SoC Project Management =
     51
     52Please visit 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.
     53
     54We have provided a 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.
     55
     56We 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.
     57Students 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.
     58
     59RTEMS 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.
     60
     61RTEMS 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.
     62
     63Even 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.
     64= References =
     65
     66 *  Drupal has some information on the writing applications that looks promising
     67The following link contains some information about how to write a proposal: How Not To Apply For Summer Of Code
     68= Students Proposals =
     69
     70
     71The 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. :)
     72GSOC 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!!!
     73
     74Student Completed Hello IRC Handle      Proposal Title  Google Docs URL
     75RTEMS Student    Yes     myircnick       Sample Project Proposal
     76Wiktor Langowski         Yes     Wik     ARINC 653 API  Proposal
     77Deng Hengyi      Yes     WeiY    Atomic Operations      Proposal
     78Hesham Moustafa Yes      Hesham  RTEMS MMU/MPU support for ARM architecture     Proposal
     79Kevin Polulak   Yes      soh_cah_toa     Update the RTEMS TCP/IP Stack  Proposal
     80Zhongwei Yao    Yes      zw_yao  Use hash or map in POSIX keys  Proposal
     81Xi Yang  Yes     yangxi  RTEMS on Asymmetric Multicore Platform (Panda Board)   Proposal
     82Hongyu Tian     Yes      stove90tihuy    Deferred Memory Management for Multi-core      Proposal
     83Xiang Cui       Yes      medivhc         Bdbuf Improvements     Proposal
     84Jiang Hong Bo   Yes      jianghongbob    Port RTEMS to STM32    Proposal
     85Claas Ziemke    Yes      claas   Code a BSP for BeagleBoard and/or BeagleBone   Proposal
     86Xiaochen Pan    Yes      Deb     RTEMS Testing  Proposal
     87Alex-Sever Horin        Yes      alseh   Porting NXLib & updating libraries ... Proposal
     88
     89The Student column is for your name.
     90
     91The 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.
     92The IRC Handle column is your handle on IRC. RTEMS folks hang out in the #rtems channel on irc.freenode.net.
     93
     94The Proposal Title should be self-explanatory. If approved, we will ask you to create a 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.
     95
     96The Google Docs URL is your proposal on Google Docs that can be reviewed and commented on by mentors.