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

Changes between Version 60 and Version 61 of GSoC


Ignore:
Timestamp:
02/04/22 18:36:30 (2 years ago)
Author:
Gedare Bloom
Comment:

Replace student with contributor to reflect new focus upstream.

Legend:

Unmodified
Added
Removed
Modified

  • GSoC

    v60 v61  
    77Currently, there has not been an announcement regarding editions of the European Space Agency Summer of Code In Space.
    88
    9 Please use this page as a jumping off point for participating in these student programs with RTEMS and ask questions. We want you to be a part of the RTEMS community!
     9Please use this page as a jumping off point for participating in these programs with RTEMS and ask questions. We want you to be a part of the RTEMS community!
    1010
    11 '''GSOC STUDENTS MUST FILL OUT A [https://summerofcode.withgoogle.com Google APPLICATION] AND FILL IN AN ENTRY ON THE RTEMS [wiki:GSoC/2021 GSOC TRACKING PAGE]'''
     11'''APPLYING GSOC CONTRIBUTORS MUST FILL OUT A [https://summerofcode.withgoogle.com Google APPLICATION] AND FILL IN AN ENTRY ON THE RTEMS [wiki:GSoC/2021 GSOC TRACKING PAGE]'''
    1212
    13 '''!!! MORE DETAILS BELOW!!! '''
     13'''!!! MORE DETAILS BELOW !!! '''
    1414
    15 '''Potential Students''':
     15'''Potential Contributors''':
    1616
    1717* Read through all the material on this page.
    … …  
    1919* Talk to us on Discord or the RTEMS mailing lists.
    2020
    21 * If accepted as an organization, students applying to the RTEMS Project will need to fill out an application at [https://summerofcode.withgoogle.com Google Summer of Code].
     21* If accepted as an organization, contributors applying to the RTEMS Project will need to fill out an application at [https://summerofcode.withgoogle.com Google Summer of Code].
    2222
    2323* You will also need to fill in and later update the information found on the [wiki:GSoC/2022 RTEMS GSoC] tracking page.
    … …  
    3232'''Potential Mentors''':
    3333
    34 * Share your knowledge and pledge to help a student.
     34* Share your knowledge and pledge to help a contributor.
    3535
    3636* Visit the [https://summerofcode.withgoogle.com Google Summer of Code] to register and open a connection with RTEMS Project.
    … …  
    3838* Update your information at the [wiki:GSoC/Mentors RTEMS Mentors] page.
    3939
    40 * Help the student succeed!
     40* Help the contributor succeed!
    4141
    4242
    … …  
    4444
    4545 *  [https://summerofcode.withgoogle.com Google's Starting Page for the Summer of Code]
    46  *  [http://www.booki.cc/gsocstudentguide/ GSoC Student Guide] - This is a community developed book.
    4746
    4847----
    … …  
    5049= RTEMS Specific Information =
    5150
    52  *  [wiki:GSoC/GettingStarted  GSoC Getting Started] - getting up to speed with RTEMS development for GSoC students.
     51 *  [wiki:GSoC/GettingStarted  GSoC Getting Started] - getting up to speed with RTEMS development for potential GSoC contributors.
    5352
    5453Be sure to add yourself to the table below.
    … …  
    6261 1. Projects would not meet the needs of the RTEMS project (and so would not be upstreamed).
    6362 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.
    64  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.
    65  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.
     63 1. Projects would be partially done without enough information for the next Summer of Code (or Google Code-In) contributor 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 1. Projects would be submitted as one giant patch at the end of summer, if rtems-devel reviewed the patch, the contributor would be busy with other work when it was time to make changes.
    6665 1. Projects were not documented well enough for someone to verify it works.
    6766 1. Projects would be done over and over again (instead of being new).
    … …  
    7473   a. Why is this better than what we have already done?
    7574 1. A sentence explaining how this project could be maintained (given developers have little time to maintain the code)
    76  1. Make documenting how the next summer of code student will pick up with developing the project in later years a project deliverable
    77  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.
     75 1. Make documenting how the next summer of code contributor will pick up with developing the project in later years a project deliverable
     76 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 contributor could get farther faster.
    7877 1. Make writing a tutorial to include a deliverable
    7978 1. Email the first draft to devel@rtems.org for feedback, and make adjustments before submitting '''(THIS IS A CRITICAL REQUIREMENT!!!)'''
    … …  
    8685 1. This is too much for you to complete in a summer... please remove these pieces from your proposal
    8786
    88 In 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.
     87In 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 contributor, and for RTEMS.
    8988
    9089We really want your project to be the first step in your successful and long term participation in our project.
    … …  
    9291----
    9392
    94 = Student Information =
     93= Contributor Information =
    9594
    96 Visit [wiki:Developer/OpenProjects Open Projects] to find an interesting project, or propose your own! Ask about your project idea on the email list or IRC. The project descriptions often require additional knowledge to flesh out a project proposal. Scoping a project is especially challenging as each student brings their own experience and capabilities to bear. Work with potential mentors to appropriately scope projects for the time available through the program.
     95Visit [wiki:Developer/OpenProjects Open Projects] to find an interesting project, or propose your own! Ask about your project idea on the email list or IRC. The project descriptions often require additional knowledge to flesh out a project proposal. Scoping a project is especially challenging as each contributor brings their own experience and capabilities to bear. Work with potential mentors to appropriately scope projects for the time available through the program.
    9796
    9897We want you to hit the ground running, so you need to build RTEMS, modify it a little, and run samples as a prerequisite. Please visit the RTEMS [wiki:GSoC/GettingStarted GSoC Getting Started] page for details.
    9998
    100 RTEMS is an operating system targeting embedded systems that are [http://en.wikipedia.org/wiki/Cross_compiler cross-compiled], meaning that you develop on a host system and run programs on a target system. In general, students working on code require no special hardware, because RTEMS runs on simulators like gdb, skyeye, and qemu. The development can all be done and tested using a GNU/Linux or other suitable host.
     99RTEMS is an operating system targeting embedded systems that are [http://en.wikipedia.org/wiki/Cross_compiler cross-compiled], meaning that you develop on a host system and run programs on a target system. In general, contributors working on code require no special hardware, because RTEMS runs on simulators like gdb, skyeye, and qemu. The development can all be done and tested using a GNU/Linux or other suitable host.
    101100
    102101Please read through the [wiki:Developer/GSoC/ProjectManagement  SoC Project Management] page to get a sense of our expectations from you for the summer of code.
    … …  
    108107= References =
    109108
    110  *   [https://code.google.com/p/google-summer-of-code/wiki/AdviceforStudents  Advice for Google Summer of Code Students] from GSoC pageHow
     109 *   [https://code.google.com/p/google-summer-of-code/wiki/AdviceforStudents  Advice for Google Summer of Code] from GSoC pageHow
    111110 *   HOWTO: [http://drupal.org/node/59037 Write a Summer of Code application] from Drupal.
    112111 *   [http://blog.gerv.net/2006/05/how_not_to_apply_for_summer_of/ How Not to Apply to GSoC]