GSOC 2016/Student Application maditparis

Contact Information

• Email Address:

maditparis@gmail.com

• Blog URL: personal or fedora planet link

https://maditparis.wordpress.com/

• Freenode IRC Nick: Beginner's Guide To IRC

maditparis

• Code Forges (GitHub, GitLab, BitBucket, etc.):

https://github.com/madiparis

Questions to answer

Why do you want to work with the Fedora Project?

I would like to work with the Fedora Project because I’ve been a Fedora enthusiast who uses Fedora on all of my personal computers for quite a while and would like to start giving back to the community and I think getting started with the Fedora Project during GSOC would be the best way to start!

Do you have any past involvement with the Fedora Project or another open-source project as a contributor?

Yes, I have experience contributing to Systers, an Anita Borg Institute Community’s Automated Unit Testing project but no involvement yet with the Fedora Project.

Have you participated in GSoC in the past? If so, what year(s) and which organization(s)?

Yes, with Systers, an Anita Borg Institute Community in 2015

Do you plan to continue contributing to the Fedora Project after GSoC? If yes, what sub-project(s) are you interested with?

Yes, I would love to continue contributing to Fedora after GSOC either in the packaging or documentation projects.

Why should we choose you over other applicants?

You should choose me because I am incredibly interested in getting involved in Fedora and I have plenty of time to dedicate to GSOC this summer. I would be really interested in contributing to the project even after GSOC ends and it would be a great opportunity for me to gain more experience with open source development and linux systems in general.

Have you contributed to any other open source organizations or projects? If so, do you have artifacts you can show so we can see your skill set(s)?

Yes, https://github.com/madiparis/automated-testing/tree/develop/PLTTests

Do you have any other open source experience (even if not coding-related)?

Nope, all I’ve done that has been open source related was my work on the Automated Unit Testing Project for Systers.

Proposal Description

Overview and The Need

Fedora Atomic: Support for end-of-life notification Work on adding support for having an “end-of-life” notification to inform users if a particular branch is not supported anymore.

Any relevant experience you have

I have an advanced knowledge of C having been working on projects using it for classes and personal projects for a few years along with experience as a Red Hat system administrator for my university during the school year where I have developed a deep understanding of the inner working of Linux systems along with troubleshooting and fixing problems that arise plus debugging and developing scripts to improve user experience on our systems. While working there, I have worked on packaging extensively, creating brand new rpms and updating existing ones.

How do you intend to implement your proposal

I would consult with my mentor and decide on the best approach would be. I’d get familiar with the libraries and software that are to be used including atomic cli and rpm-ostree and any other parts of the project’s codebase that I would be working with and then start cleaning up the codebase if necessary/implementing the new features.

A rough timeline for your progress

April 22nd - May 22rd: Reading through documentation, discussing project with mentor, getting to know the community May 23rd - August 14th: Working on implementing end-of-life notification feature, documenting, and debugging issues that arise. August 15th - August 23rd: Finish cleaning up code and documentation.

Final deliverable

Support for end-of-life notification and good documentation with it. As requested, I would set it up so there is rpm-ostree and atomic command output that would explain when a version of an upgraded tree branch is at the end of life and it would be packaged.

Proposal Description

Overview and The Need

Fedora Atomic: Improve Ability to Monitor Running/Canceled Transactions The need is rpm-ostree client termination doesn’t block the command execution on the rpm-ostree.

Any relevant experience you have

I have an advanced knowledge of C having been working on projects using it for classes and personal projects for a few years along with experience as a Red Hat system administrator for my university during the school year where I have developed a deep understanding of the inner working of Linux systems along with troubleshooting and fixing problems that arise plus debugging and developing scripts to improve user experience on our systems. While working there, I have worked on packaging extensively, creating brand new rpms and updating existing ones. I also am involved in our universities Linux/UNIX user group where I help manage our own shell server along with my own personal spare PC that I use to mess with packaging and the ability to spin-up VMs.

How do you intend to implement your proposal

I would consult with my mentor and decide on the best approach would be. I’d get familiar with the libraries and software that are to be used including rpm-ostree and research any aspects of the project I have not encountered and then work on implementing the ability to monitor running/canceled transactions with the goal outcomes being a better understanding of what transactions are currently occuring in the daemon and to re-attach and get the status of the transaction.

A rough timeline for your progress

April 22nd - May 22rd: Reading through documentation, discussing project with mentor, getting to know the community May 23rd - August 14th: Working on implementing the ability to monitor transactions along with debugging and documentation. I’d discuss my decisions in regards to the project with my mentor at every step to ensure that I try to produce the best and most time-efficient project possible. August 15th - August 23rd: Finish cleaning up code and documentation.

Final deliverable

The final deliverables would be rpm-ostree to be changed to be notified of the status of the current transaction and the ability to attach to it.

Any other details you feel we should consider

I just think it would be a really neat experience to get to work with the Fedora Project for GSOC 2016 and hope to use it as an experience to get started contributing back to Fedora and get more involved in Open Source!