= European Space Agency Summer of Code in Space 2015 =

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


= 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) 
||Hermann Felbinger || Yes || hermann_19829 || Improve Code Coverage Analysis Meeting Aviation and Automotive Standards || [https://docs.google.com/document/d/14akfj6AIc0HBZ1ZSTc8Hp7MX8k7wrh495Jl3ngvTJDQ/edit?usp=sharing Proposal]
|| Saeed Ehteshamifar || Yes || salpha || RTEMS Fault tolerance: Get a fault injection tool to work with RTEMS || [https://docs.google.com/document/d/1rVEhyHXajAVMcqgrOR-0t84596QUkYOnifoaYpa8QYM/pub?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 Google Melange site. If you do not submit the final proposal via the Google Melange 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
|| Hermann Felbinger || hermann_19829 || [https://devel.rtems.org/wiki/SOCIS/2015/CoverageAnalysis Wiki] || [https://github.com/hermann19829/rtems-tools GitHub] || [http://socis2015rtems.blogspot.com Blog]
|| Saeed Ehteshamifar || salpha || [https://devel.rtems.org/wiki/SOCIS/2015/FaultTolerance Wiki] || [https://github.com/salpha2004/GRINDER-RTEMS GitHub] || [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.

== Gedare ==
* May 19: Added the Status Updates page, and created this subsection as an example. For next week, I will talk to any students who missed the meeting and follow-up on any problems that were identified.

== Hermann ==
* May 19: Was notified that I am selected to be part of SOCIS 2015. Gedare asked me to provide some links to coverage reports after the release of RTEMS 4.11.
* May 26: Unfortunately missed the meeting. Analyzed the QEMU emulator capabilities to check which BSPs are supported. To get familiar with the tools I am working on building the tool set for LEON2 CPU which should work with the QEMU Sparc32 emulator. To execute the test cases and run a coverage analysis I have to define a proper config file for covoar which currently only exists for pc386 BSP.
* June 2: Still working on building and cofiguring the coverage reporting tool for LEON2. Because LEON2 is outdated I should build the tool also for LEON3.
* June 9: Cleaned up my setup and rebuilt everything. Found an error in the framebuffer for the pc386 build. Filed a ticked explaining the configure command I used. The ticked is already closed providing a patch. Continue building the coverage reporting tool for LEON2/LEON3 now.

== Saeed ==
* May 19: Not yet admitted.
* May 26: Admitted. Updated this page to add an entry for my proposal. Built RTEMS build tools via RSB.
* Jun 02: Built RTEMS 4.11, gone through GRINDER, found the abstraction layer to modify (and re-implement) in order to invoke Qemu (running RTEMS). Made a repository and a blog and put the links above.
* Jun 09: Missed meeting and spending time on project due to overbooked schedule for the week.
* Jun 16: Got more knowledge about GRINDER and overall fault injection (FI) process and updated the blog accordingly. Going to model failures and tests.