From Fedora Project Wiki

< GSOC 2016

Revision as of 10:10, 25 March 2016 by Majkl (talk | contribs) (Created page with " CONTACT INFORMATION- Michael Halinár miso.halinar@gmail.com +421948016629 FAS username-majkl IRC- WHY FEDORA- I want to work with fedora because I am seeking for new chale...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

CONTACT INFORMATION- Michael Halinár

miso.halinar@gmail.com +421948016629 FAS username-majkl IRC-

WHY FEDORA- I want to work with fedora because I am seeking for new chalenges. I choosed project for novices Support for end-of-life notification since this will be the first project that I will work on. I have the required skills which are C language(other languages too) and knowlegde of Linux systems.

GSOC PARTICIPATION- I am looking forward to new chalenges.

CONTRIBUTION- I have joined the mailing list, IRC, got the FAS account, signed the CLA, and introduced myself on wiki.

WHY CHOOSE ME- I am really excited to work with fedora on this project for novices, since it will be my first project. I find it very useful to spend my holydays learning and contributing with my skills to fedora.

WHERE I BELONG- I choosed this project because it is nice opportuny to work and learn. I have good experience with C language, my biggest goal was C++(only subset) interpret written in C. I did not work on that only by my self, but I had team of my classmates.

TIMELINE- There are many things for which I can work during my project and according to the guidance of my mentor but I think a rough timeline is required to make sure that the project gets completed in a stipulated period of time. For that purpose I have prepared a rough and flexible timeline which can be modified later after discussing with the mentor.

18March-25March: Applying through GSOC’s website. Familiarizing with the code, community and documentation. Try to contribute something to CommOps project by creating an FAS account and creating wiki page

22April-22May: GSOC Results. Confirming and discussing the project details with the mentor and understanding the workflow properly and planning the weekly tasks. Also getting started with the implementation of project.

23May-24June: Weekly target completion and submission of work report to the mentor. Submissions for Mid-term evaluation.

27June-31July: Continuing the Implementation and regular progress check-up.

1August-15 August: Final brush up, full integration testing, documentation and submission for final evaluation.

FINAL DELIVERABLES- Developed Content, rpm-ostree and atomic

Category: Summer coding 2016