= European Space Agency Summer of Code in Space 2017 =

[[TOC(SOCIS/2017, 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 2017.


= 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) 
|| Mikail Yayla || Yes || myay || Software-based Fault Tolerance || [https://docs.google.com/document/d/1k5tNn44xJ0k033JtJ_t0OWVWUEFhr1XBp6N8Cncys7Q/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 SOCIS 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
|| Mikail Yayla || myay || TBA || [https://github.com/myay/rtems_faulttolerance_SOCIS2017 Github] || [http://socis-rtems17.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.

== Mikail ==
* May 31 
 * Created page and added the link to my proposal

* June 7
 * Set up blog (two wip entries) and Github repository
 * Met with mentor Kuan, very helpful in giving me pointers on how to prepare for our project
 * Introduced my project in SOC meeting: Since hardware in space is subject to transient faults, the project's goal is to implement a fault tolerant scheduler which is based on soft-error handling techniques in the literature
 * For next week: refine proposal and add details, read the RTEMS C user manual to further familiarize with the subject matter
 * Preparing to fully involve in the project on schedule (according to SOCIS: probably 15th June)

* June 14
 * Wrote first blog entry about the project
 * Read resources about the scheduler in rtems (papers, documentation, blogs) to learn how components of it work
 * Begin implementing the fault tolerant scheduler

* June 21
 * What was done:
  * Updated blog about which faults the fault tolerant scheduler can protect the system from, and explained how the schedulability can still be guaranteed despite different execution versions of a task 
  * read various papers and documentation on the scheduling in rtems
 * The current issues:
  * waiting for the official SoC start
 * Plans for the next week:
  * get a sufficient understanding of the scheduler infrastructure in rtems
  * finish the blog post on how the fixed priority scheduler is implemented in rtems
  * find out where exactly the ft scheduler can be implemented

= Final Report (RTEMS Fault Tolerance) =
* /

== Future Works ==
* /