Notice: We have migrated to GitLab launching 2024-05-01 see here: https://gitlab.rtems.org/

Changes between Version 70 and Version 71 of GSoC/2013


Ignore:
Timestamp:
12/02/14 10:21:33 (10 years ago)
Author:
Chris Johns
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GSoC/2013

    v70 v71  
    1212Potential 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.
    1313
    14 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.
     14Potential Mentors: Share your knowledge and pledge to help a student. Visit the URL for GSoC 2012 to register as a mentor and then add yourself to the list of RTEMS Mentors.
    1515
    1616= General Information =
     
    2222 *  See RTEMS [wiki:GSoC/2012  Summer of Code 2012]
    2323 *  See RTEMS [wiki:GSoC/2011  Summer of Code 2011]
    24  *  See RTEMS [wiki:GSoC/2010/Main **NAME**  Summer of Code 2010]
    25  *  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]
    26  *  See RTEMS [http://wiki.rtems.org/wiki/index.php/RTEMS_Summer_Of_Code_2008 Summer Of Code 2008]= GSOC =
     24 *  See RTEMS [wiki:GSoC/2010  Summer of Code 2010]
     25 *  See RTEMS [wiki:GSoC/2009 Summer Of Code 2009] and [http://www.google-melange.com/gsoc/homepage/google/gsoc2009 Google Summer of Code 2009]
     26 *  See RTEMS [wiki:GSoC/2008 Summer Of Code 2008]
     27= GSOC =
    2728
    28 In [wiki:GSoC/2012 2012], we had ten students. In [wiki:GSoC/2011 2011] and [wiki:GSoC/2010/Main **NAME**  2010], we had eight students each year. In [wiki:RTEMSSummerOfCode2009_ 2009] there were six students with a seventh sponsored by a combination the mentor donation and a donation from [http://www.oarcorp.com OAR Corporation,]. In our first GSOC experience, [wiki:GSoC/2008  2008] we received four student slots with one failing.  These students have contributed great code and some have continued to be a part of the community.  We have been impressed with the quality of both high school and college students who have participated in the GSOC and GCI programs.
     29In [wiki:GSoC/2012 2012], we had ten students. In [wiki:GSoC/2011 2011] and [wiki:GSoC/2010 2010], we had eight students each year. In [wiki:GSOC/2009 2009] there were six students with a seventh sponsored by a combination the mentor donation and a donation from [http://www.oarcorp.com OAR Corporation,]. In our first GSOC experience, [wiki:GSoC/2008  2008] we received four student slots with one failing.  These students have contributed great code and some have continued to be a part of the community.  We have been impressed with the quality of both high school and college students who have participated in the GSOC and GCI programs.
    2930= GCI =
    3031
    3132Google Code-In has been an incredibly challenging experience for the RTEMS Community. The tasks are much smaller that those in GSOC with a target of 2-4 hours for a skilled developer. Plus they should be achievable by a high school student and meaningful to the community. We gathered some statistics to give an idea of the magnitude of what they accomplished.
    3233
    33 {| border="1" style="margin: 1em auto 1em auto;text-align: center;"
    34 |+
    35 |-
    36 |'''Year''' || '''Students''' || '''Tasks''' || '''Tasks By Top Student''' || '''Students with Over Ten Tasks'''
    37 |-
    38 | 2011 || 22 || 65 || 12 || 1
    39 |-
    40 | 2012 || 31 || 245 || 67 || 4
    41 |-
    42 |}
     34
     35|| '''Year''' || '''Students''' || '''Tasks''' || '''Tasks By Top Student''' || '''Students with Over Ten Tasks'''
     36|| 2011 || 22 || 65 || 12 || 1
     37|| 2012 || 31 || 245 || 67 || 4
    4338
    4439The increase in tasks performed is likely due to just ten free software organizations participating in the 2012 edition (twenty in 2011) combined with our improved ability to define tasks which students could perform.
     
    5651 *  [http://rtems.org/onlinedocs/doc-current/share/rtems/html/ RTEMS User Documentation (git daily)]
    5752
    58 Be sure to add yourself to the table below.==  Writing Proposals and Doing Projects  ==
     53Be sure to add yourself to the table below.
     54==  Writing Proposals and Doing Projects  ==
    5955
    6056'''Problem:''' Over the years of participating in Summers of Code, the RTEMS project has noticed some recurring themes with Summer of Code projects:
    61 # Projects would not meet the needs of the RTEMS project (and so would not be upstreamed).
    62 # 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.
    63 # 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.
    64 # 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.
    65 # Projects were not documented well enough for someone to verify it works.
    66 # Projects would be done over and over again (instead of being new)
     571. Projects would not meet the needs of the RTEMS project (and so would not be upstreamed).
     581. 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.
     591. 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.
     601. 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.
     611. Projects were not documented well enough for someone to verify it works.
     621. Projects would be done over and over again (instead of being new)
    6763
    6864'''Solution:''' In the proposal the following MUST be included:
    69 # A paragraph explaining what the project is trying to accomplish
    70 ## What is the core problem being solved?
    71 ## Why is this better than what we have already done?
    72 # A sentence explaining how this project could be maintained (given developers have little time to maintain the code)
    73 # Make documenting how the next summer of code student will pick up with developing the project in later years a project deliverable
    74 # Break the project up into increments, so that if time runs out, each increment could be upstreamed, or at least written up on a wiki page so the next year's student could get farther faster.
    75 # Make writing a tutorial to include a deliverable
    76 # email the first draft to rtems-devel@rtems.org for feedback, and make adjustments before submitting '''(THIS IS A CRITICAL REQUIREMENT!!!)'''
     651. A paragraph explaining what the project is trying to accomplish
     66 a. What is the core problem being solved?
     67 a. Why is this better than what we have already done?
     681. A sentence explaining how this project could be maintained (given developers have little time to maintain the code)
     691. Make documenting how the next summer of code student will pick up with developing the project in later years a project deliverable
     701. Break the project up into increments, so that if time runs out, each increment could be upstreamed, or at least written up on a wiki page so the next year's student could get farther faster.
     711. Make writing a tutorial to include a deliverable
     721. email the first draft to rtems-devel@rtems.org for feedback, and make adjustments before submitting '''(THIS IS A CRITICAL REQUIREMENT!!!)'''
    7773
    7874Expect the following questions from the email list:
    79 # We really need ''something else specific'' done instead... could you do ''something else specific''?
    80 # What's the maintainence plan?
    81 # How will we test it?
    82 # We did this already... How is this an improvement?
    83 # This is too much for you to complete in a summer... please remove these pieces from your proposal
     751. We really need ''something else specific'' done instead... could you do ''something else specific''?
     761. What's the maintainence plan?
     771. How will we test it?
     781. We did this already... How is this an improvement?
     791. This is too much for you to complete in a summer... please remove these pieces from your proposal
    8480
    8581In addition, the RTEMS project will furnish not only a mentor, but a co-mentor, and one or two additional people to help with keeping the project on a topic that is both meaningful for the student, and for RTEMS.
     
    115111Until 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. :)
    116112
    117 <strong>
    118 <center>
    119 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!!!
    120 </center>
    121 </strong>
     113'''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!!!
    122114
    123 {| border="1" style="margin: 1em auto 1em auto;text-align: center;"
    124 |+
    125 |-
    126 |'''Student''' || '''Completed Hello''' || '''IRC Handle''' || '''Proposal Title''' || '''Google Docs URL''' || '''Blog'''
    127 |-
    128 |NAME || Yes or No|| on #rtems || Title  || Link to Google Docs for proposal ||
    129 |-
    130 |Jin Yang || Yes || SYCrane || CAN driver and API for CAN stack || [https://docs.google.com/document/d/1PCJ4MAR03fH2tm22AA_OD-h5Xlh68yYL08y9bBOIkCM/edit# Proposal] ||  http://jin-yang.github.io/2013/06/24/rtems.html
    131 |-
    132 |Prateek Tiwari || Yes || prateekt || Supercore Scheduler || [https://docs.google.com/document/d/17WgBhqSX3gQDkA_RDSzgQtFtrMEFLm0jgb2hmGVg6Vg/edit?usp=sharing Proposal] ||
    133 |-
    134 |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] || http://heshamelmatary.blogspot.com/
    135 |-
    136 |Deng Hengyi || Yes || weiY || Atomic Operations and SMP lock debug tool for RTEMS  || [https://docs.google.com/document/d/1kZtTwyw8xBzGSz-n8xFcTuD5KSrEpnzzq860wMaQtCU/edit# Proposal] || http://weiy.github.io/
    137 |-
    138 |Dhananjay Balan || Yes || dhananjay || Better RTEMS Support in GDB   || Link to Google Docs for proposal | [https://docs.google.com/document/d/1RbFYZl8lk9d-BoGxjiDdASBm3ucSkXZ7Mey_7tyuz2Y/edit?usp=sharing Proposal] || http://dbalan.github.io/blog/categories/rtems/
    139 |-
    140 |Peng Fan || Yes || freenix || RTEMS Runtime Loader || [https://docs.google.com/document/d/1HBkRU7_kUOvoiCQWTUxQ151kvX--3x_E7r0rTerxYbo/edit# Proposal] || http://freenixfan.wordpress.com/
    141 |-
    142 |Shubham Somani || Yes || S_Somani || Application Configuration GUI for RTEMS.   || [https://docs.google.com/document/d/1oFjUvydBm78fyIQzq2ol6M7tdkC_f6c21hzoHjXzuJc/edit?usp=sharing/edit# Proposal] || http://shubhamsomani.blogspot.in/
    143 |-
    144 |Philipp Eppelt || Yes || phipse || Paravirtualization of RTEMS || [https://docs.google.com/document/d/10SWiyYg6WEeMdAeysyahbS6XK5QwyIMlUvAr4aFOyX4/edit# Proposal] || http://phipse.github.io/rtems/
    145 |-
    146 |Vipul Nayyar || Yes || vipulnayyar || Unified API  || [https://docs.google.com/document/d/1oDp4E9_Wof4wBJaMJJIFoPqtu5fbTdsKwEcz-5qkazw/edit?usp=sharing Proposal] || http://www.vipulnayyar.com/
    147 
    148 |-
    149 <!-- |Jaskaran Singh || Yes ||    ||    ||    ||
    150 |- -->
    151 <!-- |Vivek Krishnamurthy || Yes || Vivekkmurthy || RTEMS BenchMark Kit  || [https://docs.google.com/document/d/1Li3h9c9ScKQQsWw-yctkazmhlaKx-CvXtPO4t4C8F3M/edit Proposal] ||
    152 |- -->
    153 |Ye Xu || Yes || AresHsu || Fault Tolerance / Power Aware Scheduling   || [https://docs.google.com/document/d/12IGs6_M6DM3sYpyKRTLUZag_i9bKbaVVnMFeqeoBtqk/edit Proposal] ||
    154 |-
    155 |Dinesh Rathinasamy Thangavel|| Yes || rtdin ||  Implementation of Condition Variable Classic API || ||
    156 |-
    157 |Sree Harsha Konduri || Yes || sreekonduri || SMP Aware Scheduler || [https://docs.google.com/a/buffalo.edu/document/d/1bie3BUOfFHJTkoJuktOjo7QHuPsZetGr__bOdM-hnCY/edit?usp=sharing Proposal] || http://sreeharshakonduri.blogspot.com/
    158 |}
     115|| '''Student''' || '''Completed Hello''' || '''IRC Handle''' || '''Proposal Title''' || '''Google Docs URL''' || '''Blog'''
     116|| NAME || Yes or No || on #rtems || Title  || Link to Google Docs for proposal || ||
     117|| Jin Yang || Yes || SYCrane || CAN driver and API for CAN stack || [https://docs.google.com/document/d/1PCJ4MAR03fH2tm22AA_OD-h5Xlh68yYL08y9bBOIkCM/edit# Proposal] ||  http://jin-yang.github.io/2013/06/24/rtems.html
     118|| Prateek Tiwari || Yes || prateekt || Supercore Scheduler || [https://docs.google.com/document/d/17WgBhqSX3gQDkA_RDSzgQtFtrMEFLm0jgb2hmGVg6Vg/edit?usp=sharing Proposal] || ||
     119|| 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] || http://heshamelmatary.blogspot.com/
     120|| Deng Hengyi || Yes || weiY || Atomic Operations and SMP lock debug tool for RTEMS  || [https://docs.google.com/document/d/1kZtTwyw8xBzGSz-n8xFcTuD5KSrEpnzzq860wMaQtCU/edit# Proposal] || http://weiy.github.io/
     121||Dhananjay Balan || Yes || dhananjay || Better RTEMS Support in GDB   || Link to Google Docs for proposal | [https://docs.google.com/document/d/1RbFYZl8lk9d-BoGxjiDdASBm3ucSkXZ7Mey_7tyuz2Y/edit?usp=sharing Proposal] || http://dbalan.github.io/blog/categories/rtems/
     122|| Peng Fan || Yes || freenix || RTEMS Runtime Loader || [https://docs.google.com/document/d/1HBkRU7_kUOvoiCQWTUxQ151kvX--3x_E7r0rTerxYbo/edit# Proposal] || http://freenixfan.wordpress.com/
     123|| Shubham Somani || Yes || S_Somani || Application Configuration GUI for RTEMS.   || [https://docs.google.com/document/d/1oFjUvydBm78fyIQzq2ol6M7tdkC_f6c21hzoHjXzuJc/edit?usp=sharing/edit# Proposal] || http://shubhamsomani.blogspot.in/
     124|| Philipp Eppelt || Yes || phipse || Paravirtualization of RTEMS || [https://docs.google.com/document/d/10SWiyYg6WEeMdAeysyahbS6XK5QwyIMlUvAr4aFOyX4/edit# Proposal] || http://phipse.github.io/rtems/
     125|| Vipul Nayyar || Yes || vipulnayyar || Unified API  || [https://docs.google.com/document/d/1oDp4E9_Wof4wBJaMJJIFoPqtu5fbTdsKwEcz-5qkazw/edit?usp=sharing Proposal] || http://www.vipulnayyar.com/
     126|| Jaskaran Singh || Yes ||    ||    ||    || ||
     127|| Vivek Krishnamurthy || Yes || Vivekkmurthy || RTEMS !BenchMark Kit  || [https://docs.google.com/document/d/1Li3h9c9ScKQQsWw-yctkazmhlaKx-CvXtPO4t4C8F3M/edit Proposal] || ||
     128|| Ye Xu || Yes || !AresHsu || Fault Tolerance / Power Aware Scheduling   || [https://docs.google.com/document/d/12IGs6_M6DM3sYpyKRTLUZag_i9bKbaVVnMFeqeoBtqk/edit Proposal] || ||
     129|| Dinesh Rathinasamy Thangavel || Yes || rtdin ||  Implementation of Condition Variable Classic API || || ||
     130|| Sree Harsha Konduri || Yes || sreekonduri || SMP Aware Scheduler || [https://docs.google.com/a/buffalo.edu/document/d/1bie3BUOfFHJTkoJuktOjo7QHuPsZetGr__bOdM-hnCY/edit?usp=sharing Proposal] || http://sreeharshakonduri.blogspot.com/
    159131
    160132The ''Student'' column is for your name.
     
    164136The ''IRC Handle'' column is your handle on IRC.  RTEMS folks hang out in #rtems on freenode.net.
    165137
    166 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.
     138The ''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 Joel Sherrill read/write access.
    167139
    168140The ''Google Docs URL'' is your proposal in Google Docs that can be reviewed and commented on by mentors.