From Fedora Project Wiki
(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...")
 
No edit summary
Line 1: Line 1:


CONTACT INFORMATION- Michael Halinár
=== Contact Information ===
* '''Email Address''':    miso.halinar@gmail.com
* '''Freenode IRC Nick''':    -
* '''Code Forges (GitHub, GitLab, BitBucket, etc.)''': 
** Github : https://github.com/xhalin01
** Also have worked with SVN in private repository


miso.halinar@gmail.com +421948016629 FAS username-majkl IRC-
* '''Social Media Accounts''':
**Facebook : https://www.facebook.com/miso.halinar.5


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.
=== Questions to answer ===


CONTRIBUTION- I have joined the mailing list, IRC, got the FAS account, signed the CLA, and introduced myself on wiki.
==== Why do you want to work with the Fedora Project? ====
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.
==== Do you have any past involvement with the Fedora Project or another open-source project as a contributor? ====
No I have not, this will be my first time.


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.
==== Have you participated in GSoC in the past? If so, what year(s) and which organization(s)? ====
No.


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.
==== Do you plan to continue contributing to the Fedora Project after GSoC? If yes, what sub-project(s) are you interested with? ====
I will do my best. I am looking forward to new chalenges.


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.
==== Why should we choose you over other applicants? ====
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.
==== 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)? ====
No yet.  
==== Do you have any other open source experience (even if not coding-related)? ====
No.
==Proposal Description==


27June-31July: Continuing the Implementation and regular progress check-up.
===Overview and The Need===


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


FINAL DELIVERABLES- Developed Content, rpm-ostree and atomic
===Any relevant experience you have===
I have hands on experience in most of the things that you ask to implement the project.


Category: Summer coding 2016
* C
** I have 5+ years experience in C.
* Bash,php
** I have 1+ year experience in Bash. And some other skripting language like php.
 
===How do you intend to implement your proposal===
.
 
===A rough timeline for your progress===
 
* May 23 - May 30 (1 week)
** End Semester Examinations
 
* May 30 - June (4 weeks)
** Adding new features to the web frontend
** Adding new capabilities to the backend
** Fix UI bugs which already exists if time is enough (Extra)
 
* June 27 - July 10 (2 weeks)
** Writing and deploying new widgets
 
* July 11 - July 24 (2 weeks)
** Triaging and processing new widget ideas submitted by the community at large
 
* July 25- July 31 (1 week)
** Implementing existing (and thoroughly detailed) mockups from previous UI/UX interns and team members
 
* Aug 01 - Aug 07 (1 week)
** Mid Semester Examination
 
* Aug 08 - Aug 14 (2 weeks)
** Continue Implementing existing (and thoroughly detailed) mockups from previous UI/UX interns and team members
 
* Aug 15 - Aug 21 (1 week)
** Polishing the code base
** Implement unfinished parts if exists
** Fixed found bugs on the way if necessary
 
 
===Final deliverable===
Features which were discussed to implement during the summer with clean code base.
===Any other details you feel we should consider===
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 managed that only by my self, but I had team of my classmates.
 
[[Category:Summer coding 2016]]

Revision as of 20:38, 25 March 2016

Contact Information

  • Email Address: miso.halinar@gmail.com
  • Freenode IRC Nick: -
  • Code Forges (GitHub, GitLab, BitBucket, etc.):


Questions to answer

Why do you want to work with the Fedora Project?

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.

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

No I have not, this will be my first time.


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

No.

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

I will do my best. I am looking forward to new chalenges.


Why should we choose you over other applicants?

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.

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)?

No yet.

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

No.

Proposal Description

Overview and The Need

Any relevant experience you have

I have hands on experience in most of the things that you ask to implement the project.

  • C
    • I have 5+ years experience in C.
  • Bash,php
    • I have 1+ year experience in Bash. And some other skripting language like php.

How do you intend to implement your proposal

.

A rough timeline for your progress

  • May 23 - May 30 (1 week)
    • End Semester Examinations
  • May 30 - June (4 weeks)
    • Adding new features to the web frontend
    • Adding new capabilities to the backend
    • Fix UI bugs which already exists if time is enough (Extra)
  • June 27 - July 10 (2 weeks)
    • Writing and deploying new widgets
  • July 11 - July 24 (2 weeks)
    • Triaging and processing new widget ideas submitted by the community at large
  • July 25- July 31 (1 week)
    • Implementing existing (and thoroughly detailed) mockups from previous UI/UX interns and team members
  • Aug 01 - Aug 07 (1 week)
    • Mid Semester Examination
  • Aug 08 - Aug 14 (2 weeks)
    • Continue Implementing existing (and thoroughly detailed) mockups from previous UI/UX interns and team members
  • Aug 15 - Aug 21 (1 week)
    • Polishing the code base
    • Implement unfinished parts if exists
    • Fixed found bugs on the way if necessary


Final deliverable

Features which were discussed to implement during the summer with clean code base.

Any other details you feel we should consider

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 managed that only by my self, but I had team of my classmates.