Version 36 (modified by Richi Dubey, on 05/07/20 at 09:55:47) (diff) |
---|
Google Summer of Code 2020
Table of Contents
This page is for the students who make proposals as well as those who work on projects for RTEMS as part of GSoC 2020.
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 | Final Submitted |
NAME | Yes or No | nick on #rtems | Project Title | Link to Google Docs for proposal (shared with mentors) | Yes or No |
G. S. Niteesh Babu | Yes | niteesh | Beagle BSP: Add a flattened device tree based initialization | Beagle BSP: Add a flattened device tree based initialization | Yes |
Mritunjay Kumar Sharma | Yes | mritunjay394 | BSP Buildset for EPICS | BSP Buildset for EPICS Project Proposal | Yes |
Eshan Dhawan | Yes | eshandhawan51 | POSIX Complience | POSIX Complience Project Proposal (draft) | Yes |
Denil C Verghese | Yes | tupio[m] | RTEMS Release Notes Generator | Proposal Link(Draft) | No |
Suyash Singh | Yes | suyashsingh234 | Clang-analyzer and LLVM sanitizer Integration | Clang-analyzer and LLVM sanitizer Integration | Yes |
Anmol Mishra | Yes | anmol27katyani | RTEMS Python Standardization | Link to draft proposal(shared with mentors) | Yes |
Richi Dubey | Yes | richidubey | Improve the SMP scheduler with arbitrary processor affinity support | GSOC2020_Dubey_ProcessorAffinityinSMP | Yes |
Utkarsh Rai | Yes | ur10 | Memory Protection | https://docs.google.com/document/d/1AawmqbfCpRDHZ4cO5-UE1J7VacubNWmn3kae4rlPrZA/edit?usp=sharing | Yes |
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 mandatory Hello World project. Email your proof to Gedare, Joel, and Chris Johns.
- 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 proposal template should be copied and used as a baseline. This can be shared with mentors for review. Mentors can insert comments for you. You can use this as your Draft Proposal in the GSoC site.
- The Final Submitted should be set to Yes when you have submitted your Final PDF proposal on the official GSoC site. If you do not submit the final proposal via the Google 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 SoC Project Management.
Student Name | IRC Handle | Project Link | Repository Link on Github | Blog | Calendar |
NAME | nick on #rtems | Project Wiki | Project's Github repo | Blog | Project Schedule |
Richi Dubey | richidubey | Wiki | Github | Blog | TBD by 20th May |
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 on Github is a link to the Github repository for your project. It should be a specific repository, not just your github account!
- The Blog is a link to your blog with entries about your project. It should be updated regularly during the summer.
- The Calendar is a link to your Google Calendar with milestones and deliverables identified.
Student Status Updates
Each student has a section below for putting in notes from the weekly IRC meetings.
Gedare
- Jan 3: Tracking status page created.
Joel
- Jan 3: Let's get started!