= European Space Agency Summer of Code in Space 2016 =

[[TOC(SOCIS/2016, depth=2)]]

This page captures the students who make proposals as well as those who work on projects for RTEMS as part of ESA SOCIS 2016.


= Students' Proposals =

Start filling in this table for yourself as soon as possible and update as needed.

|| '''Student''' || '''Completed Hello''' || '''IRC Handle''' || '''Proposal Title''' || '''Google Docs URL''' 
||NAME || Yes or No || nick on #rtems || Project Title  || Link to Google Docs for proposal (shared with mentors) 
|| Saeed Ehteshamifar || Yes || salpha || RTEMS Fault tolerance: Get a fault injection tool to work with RTEMS (continuation from [https://devel.rtems.org/wiki/SOCIS/2015 last year]) || [https://docs.google.com/document/d/14hNEIi-FaywfvpB71yll-3FvzgbhUS2nhiiWZ8V7s7A/edit?usp=sharing Proposal]

The columns are to be filled in as follows:
* 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. The [https://docs.google.com/document/d/1F5XCodvX8AYNqWX5ssu7dfjkmFT__83uf8ABKbB_Pkg/edit?usp=sharing proposal template] should be '''copied''' and used as a baseline. This can be shared with mentors for review. Mentors can insert comments for you. 

'''WARNING''': The Google Docs version of the proposal is a '''WORKING''' copy. You '''MUST''' submit the official and final proposal using the ESA SOCIS site. If you do not submit the final proposal via the ESA SOCIS site, you cannot be considered

= Students' Summer of Code Tracking Table =

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].
||'''Student''' || '''IRC Handle''' || '''Project Link''' || '''Repository Link''' || '''Blog'''
||NAME || nick on #rtems || Link to Project Wiki page  || Link to project's public Github repository || Link to your development blog
|| Saeed Ehteshamifar || salpha || [https://devel.rtems.org/wiki/SOCIS/2015/FaultTolerance Wiki] || [https://github.com/salpha2004/GRINDER-RTEMS GitHub-GRINDER] [https://github.com/salpha2004/slingshot GitHub-Slingshot] || [http://rtems-fi.blogspot.de/ Blog]
The columns are to be filled in as follows:
* The ''Student'' column is for your name. 
* The ''IRC Handle'' column is your handle on IRC.  RTEMS folks hang out in #rtems on freenode.net.
* The ''Project Link'' is a link to the Wiki page for your project.
* The ''Repository Link'' is a link to the github repository for your project.
* The ''Blog'' is a link to your blog with entries about your project. It should be updated regularly during the summer.

= Student Status Updates =
Each student has a section below for putting in notes from the weekly IRC meetings.

== Saeed ==
* May 27: Added the Status Updates page and added the link to my proposal.
* Jun 08: Got up-to-date with latest project's status. Republished slingshot as a stand-alone repository. Updated the Github repository and build instructions. Going to start integrating GRINDER's function (test suite execution and storing results) into slingshot.
* Jun 15: Prepared RTEMS development environment. Tried to redirect pc386's output to console (didn't work), used SPARC architecture instead. Thought about how to handle test case crash scenario. Updated the blog.