Changes between Version 35 and Version 36 of GSoC


Ignore:
Timestamp:
Feb 12, 2015, 4:52:45 PM (5 years ago)
Author:
Joel Sherrill
Comment:

Delete 2014 projects and clean up

Legend:

Unmodified
Added
Removed
Modified
  • GSoC

    v35 v36  
    33[[TOC(GSoC, depth=2)]]
    44
    5 RTEMS is a participating organization of the [http://www.google-melange.com/gsoc/homepage/google/gsoc2014 Google Summer of Code 2014]! Please use this page as a jumping off point and ask questions. We want you to be a part of the RTEMS community!
     5RTEMS is proud to have participated in multiple editions of the Google Summer of Code and ESA Summer of Code in Space. We have applied to be a participating organization in [http://www.google-melange.com/gsoc/homepage/google/gsoc2015 Google Summer of Code 2015]! Please use this page as a jumping off point and ask questions. We want you to be a part of the RTEMS community!
    66
     7'''Potential Students''': Read through all the material on this page. If accepted as an organization, students applying to the RTEMS Project will need to fill out at application at [http://www.google-melange.com/gsoc/homepage/google/gsoc2015 Google Summer of Code 2015] and update the information found on the [wiki:GSoC/2015 Google Summer of Code 2015] RTEMS tracking page. We also require you build RTEMS, create an application, run it and post the result to the RTEMS mailing list. The [wiki:GSoC/GettingStarted GSoC Getting Started] page has some more information.
    78
    8 [[Image(Soc-logo-google-blue.jpg, 450px)]]
     9Potential Mentors: Share your knowledge and pledge to help a student. Visit the [http://www.google-melange.com/gsoc/homepage/google/gsoc2015 GSoC2015] Melange system to register and open a connection with RTEMS Project.
    910
    10 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 [http://www.google-melange.com/gsoc/homepage/google/gsoc2014 official GSOC application] in addition to the informal proposal we request. We also require you build RTEMS, create an application, run it and post the result to the RTEMS mailing list. The [wiki:GSoC/GettingStarted GSoC Getting Started] page has some more information.
    11 
    12 Potential Mentors: Share your knowledge and pledge to help a student. Visit the [http://www.google-melange.com/gsoc/homepage/google/gsoc2014 GSoC2014] Melange system to register and open a connection with RTEMS Project.
    13 = General Information =
    14 
     11= Historical Information =
    1512
    1613The RTEMS Community is proud to have participated in previous editions of the [https://developers.google.com/open-source/soc/ Google Summer of Code] as well as [https://developers.google.com/open-source/gci/ Google Code-in (GCI)].
    1714
    1815Information for prior years:
     16 *  RTEMS [wiki:GSoC/2014 Summer of Code 2014]
    1917 *  RTEMS [wiki:GSoC/2013 Summer of Code 2013]
    2018 *  RTEMS [wiki:GSoC/2012 Summer of Code 2012]
     
    3028= RTEMS Specific Information =
    3129
    32  *  [wiki:TBR/Delete/Virtual_Machines_for_RTEMS_Development  Virtual Machines (VMs)] are pre-configured RTEMS development environments playable with [http://www.virtualbox.org VirtualBox]. For students who do not have a dedicated development platform, the VMs are great for minimizing the pain of setup for RTEMS development.
    33  *  [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.
    3430 *  [wiki:GSoC/GettingStarted  GSoC Getting Started] - getting up to speed with RTEMS development for GSoC students.
    3531 *  [http://rtems.org/onlinedocs/doc-current/share/rtems/html/ RTEMS User Documentation (git daily)]
     
    3834
    3935'''Problem:'''
    40   Over the years of participating in Summers of Code, the RTEMS project has noticed some recurring themes with Summer of Code projects:
     36Over the years of participating in Summers of Code, the RTEMS project has noticed some recurring themes with Summer of Code projects:
    4137 1. Projects would not meet the needs of the RTEMS project (and so would not be upstreamed).
    4238 1. Projects would be completed in such a way as they were not maintainable (external projects would make use of the RTEMS build system [http://home.gwu.edu/~cssmith/LuaRtems/ see:LUA], as opposed to using the external software's own build system [http://git.rtems.org/rtems-addon-packages/ see:rtems-addon-packages]), or projects would be hardcoded based on the RTEMS tree at one point in time see:[wiki:Building/MingwTools BuildingMingwTools] the NSIS installer.
    43  1. Projects would be partially done without enough information for the next summer of code (or google code in) student to continue the work.  For example: a change would be made for one architecture, but the way to generalize for the others was not documented.
     39 1. Projects would be partially done without enough information for the next Summer of Code (or Google Code-In) student to continue the work.  For example: a change would be made for one architecture, but the way to generalize for the others was not documented.
    4440 1. Projects would be submitted as one giant patch at the end of summer, if rtems-devel reviewed the patch, the student would be busy with schoolwork when it was time to make changes.
    4541 1. Projects were not documented well enough for someone to verify it works.
     
    4743
    4844'''Solution:'''
    49   In the proposal the following MUST be included:
     45In the proposal the following MUST be included:
    5046
    5147 1. A paragraph explaining what the project is trying to accomplish
     
    8682 *   HOWTO: [http://drupal.org/node/59037 Write a Summer of Code application] from Drupal.
    8783 *   [http://blog.gerv.net/2006/05/how_not_to_apply_for_summer_of/ How Not to Apply to GSoC]
    88 = Students' Proposals =
    8984
    90 '''The final version of your proposal must be submitted via Melange at Google.'''
    91 We have provided a [https://docs.google.com/document/d/1ECsmPB0ngIrVNXHlJFz0ArwN6GfkDURvpKKVHIl_0vo/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 copy and paste your proposal into the student application form and save it in Melange to avoid any last minute problems.
    92 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. :)
    93 
    94 <strong>
    95 <center>
    96 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!!!
    97 </center>
    98 </strong>
    99 
    100 {{{#!comment COPY The next line and replace with your contents in the table below
    101 ||First Last || Yes || IAmAStudent || My Project || [https://docs.google.com/document/d/1PCJ4MAR03fH2tm22AA_OD-9bBOIkCM/edit?usp=sharing Proposal]
    102 }}}
    103 
    104 || '''Student''' || '''Completed Hello''' || '''IRC Handle''' || '''Proposal Title''' || '''Google Docs URL'''
    105 ||NAME || Yes or No|| nick on #rtems || Project Title  || Link to Google Docs for proposal (shared with mentors)
    106 ||Zhang wenjie || Yes || Json || Condition Variables for RTEMS || [https://github.com/cloud-hot/proposal Proposal]
    107 ||Youren Shen || Yes || Sched || Paravirtualization Layer in RTEMS || [https://docs.google.com/document/d/10ehcM1f2eKNwcNgv5stphGtsVAnYc_K7KLhxmjvE1k8/edit?usp=sharing Proposal]
    108 ||Hesham AL-Matary || Yes || Hesham || Porting RTEMS to OpenRISC || [https://docs.google.com/document/d/1vZHLcEZvqidIpFAadbyMGLt5oLKrr2O4I5zmxWYL1lE/ Proposal]
    109 ||Andre Marques || Yes || asuol || Raspberry Pi BSP Peripherals || [https://docs.google.com/document/d/13HiNH_EjnzbA3HJ86Cmd2Ooi0YOsehSGkTILD_M-REw Proposal]
    110 ||Yang Jin || Yes || jinyang || Porting CAN driver, LinCAN, to RTEMS || [https://docs.google.com/document/d/12T2Sd9vDBGfMhlansaW0Ti2OmtrpRPgAXxdPuOHbM78 Proposal]
    111 ||Janek van Oirschot || Yes || !JustJanek|| ARINC 653 compliance on RTEMS using POK || [https://docs.google.com/document/d/15M-TEwhhABJj7e_C-54eMhLNSdgS-lazLyzWKDMC2lo Proposal]
    112 ||Premysl Houdek || Yes || AoLaD|| RTEMS port to Cortex – R4f || [https://docs.google.com/document/d/1qaGgjSLxNgNH0rDeG3dyJNrNE-cNEm6J7A0yEmJ-jsk Proposal]
    113 
    114 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. The ''Google Docs URL'' is your proposal in Google Docs that can be reviewed and commented on by mentors.
    115 = Students' Summer of Code Tracking Table =
    116 
    117 Students whose GSoC project is accepted by RTEMS shall fill in a slot with their information in the following table, which helps to centralize [wiki:Developer/GSoC/ProjectManagement  SoC Project Management].
    118 ||'''Student''' || '''IRC Handle''' || '''Project Link''' || '''Repository Link''' || '''Blog'''
    119 ||NAME || nick on #rtems || Link to Project Wiki page  || Link to project's public Github repository || Link to your development blog
    120 ||Hesham ALMatary || Hesham || [http://www.rtems.org/wiki/index.php/OpenRISC_Port Wiki page]  || [https://github.com/heshamelmatary?tab=repositories github] || [http://heshamelmatary.blogspot.com/ Blog]
    121 || Andre Marques || asuol || [http://www.rtems.org/wiki/index.php/Raspberry_Pi_BSP_Peripherals Wiki page]  || [https://github.com/asuol/rtems github] || [http://asuolgsoc2014.wordpress.com/ Blog]
    122 ||Youren Shen || Sched || [http://www.rtems.org/wiki/index.php/GSOC_2014_-_Paravirtualization_of_RTEMS Wiki page] || [https://github.com/HuaiYuSched/rtems_GSoC github] || [https://Huaiyusched.github.io Blog]
    123 ||Janek van Oirschot || !JustJanek/JustJNK|| [http://www.rtems.org/wiki/index.php/ARINC653_on_RTEMS_(using_POK) Wiki page] || [https://github.com/JustJanek github] || [http://justjnk.blogspot.nl/ Blog]
    124 ||Premysl Houdek || AoLaD|| [http://wiki.rtems.org/wiki/index.php/RTEMSPortToCortexR4 Wiki page] || [https://github.com/AoLaD/rtems github] || 
    125 ||Krzysztof Miesowicz || krzysiekm13 || TODO: make wiki || [https://github.com/krzysiekm13 github] || [http://kmiesowicz.blogspot.com/p/esa-socis-2014.html Blog]
    12685= RTEMS Mentors =
    12786