Changes between Version 31 and Version 32 of GSoC


Ignore:
Timestamp:
Nov 24, 2014, 10:14:01 PM (5 years ago)
Author:
Amar Takhar
Comment:

Fix some markup

Legend:

Unmodified
Added
Removed
Modified
  • GSoC

    v31 v32  
    11= RTEMSSummerOfCode =
    22
    3 
     3[[TOC(GSoC, depth=2)]]
    44
    55RTEMS 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!
    66
    77
    8 [[TOC(GSoC, depth=2)]]
    9 
    10 [[Image(Soc-logo-google-blue.jpg)]]
     8[[Image(Soc-logo-google-blue.jpg, 450px)]]
    119
    1210Potential 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.
     
    2523 *  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]
    2624 *  See RTEMS [http://wiki.rtems.org/wiki/index.php/RTEMS_Summer_Of_Code_2008 Summer Of Code 2008]
     25
    2726= General Program Information and Guidance =
    2827
     
    3837Be sure to add yourself to the table below.==  Writing Proposals and Doing Projects  ==
    3938
    40 '''Problem:''' Over the years of participating in Summers of Code, the RTEMS project has noticed some recurring themes with Summer of Code projects:
    41 # Projects would not meet the needs of the RTEMS project (and so would not be upstreamed).
    42 # 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 # 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.
    44 # 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.
    45 # Projects were not documented well enough for someone to verify it works.
    46 # Projects would be done over and over again (instead of being new)
     39'''Problem:'''
     40  Over the years of participating in Summers of Code, the RTEMS project has noticed some recurring themes with Summer of Code projects:
     41 1. Projects would not meet the needs of the RTEMS project (and so would not be upstreamed).
     42 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.
     44 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.
     45 1. Projects were not documented well enough for someone to verify it works.
     46 1. Projects would be done over and over again (instead of being new)
    4747
    48 '''Solution:''' In the proposal the following MUST be included:
    49 # A paragraph explaining what the project is trying to accomplish
    50 ## What is the core problem being solved?
    51 ## Why is this better than what we have already done?
    52 # A sentence explaining how this project could be maintained (given developers have little time to maintain the code)
    53 # Make documenting how the next summer of code student will pick up with developing the project in later years a project deliverable
    54 # 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.
    55 # Make writing a tutorial to include a deliverable
    56 # email the first draft to rtems-devel@rtems.org for feedback, and make adjustments before submitting '''(THIS IS A CRITICAL REQUIREMENT!!!)'''
     48'''Solution:'''
     49  In the proposal the following MUST be included:
     50
     51 1. A paragraph explaining what the project is trying to accomplish
     52   a. What is the core problem being solved?
     53   a. Why is this better than what we have already done?
     54 1. A sentence explaining how this project could be maintained (given developers have little time to maintain the code)
     55 1. Make documenting how the next summer of code student will pick up with developing the project in later years a project deliverable
     56 1. 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.
     57 1. Make writing a tutorial to include a deliverable
     58 1. Email the first draft to rtems-devel@rtems.org for feedback, and make adjustments before submitting '''(THIS IS A CRITICAL REQUIREMENT!!!)'''
    5759
    5860Expect the following questions from the email list:
    59 # We really need ''something else specific'' done instead... could you do ''something else specific''?
    60 # What's the maintainence plan?
    61 # How will we test it?
    62 # We did this already... How is this an improvement?
    63 # This is too much for you to complete in a summer... please remove these pieces from your proposal
     61 1. We really need ''something else specific'' done instead... could you do ''something else specific''?
     62 1. What's the maintainence plan?
     63 1. How will we test it?
     64 1. We did this already... How is this an improvement?
     65 1. This is too much for you to complete in a summer... please remove these pieces from your proposal
    6466
    6567In 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.
     68
    6669= Project Ideas =
    6770