GSOC 2016/Student Application irunika: Difference between revisions

Revision as of 12:53, 25 March 2016

This is a basic template of information you can use for filling out a GSoC application for the Fedora Project.

Template

Contact Information

Email Address: Preferably the one used when FAS account was setup (if not, please specify this)
Blog URL: personal or fedora planet link
Freenode IRC Nick: Beginner's Guide To IRC
Code Forges (GitHub, GitLab, BitBucket, etc.): both your personal handle and any orgs / previous projects you've worked on
Social Media Accounts:

NOTE: We require all students to blog about the progress of their project on a weekly basis. You are strongly encouraged to register on the Freenode network and participate in our IRC channels. For more information and other instructions, use the summer-coding mailing list for seeking clarification.

Questions to answer

Why do you want to work with the Fedora Project?

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

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

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

Why should we choose you over other applicants?

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

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

Proposal Description

Overview and The Need

Any relevant experience you have

As a contributor to glusterfs I have prior knowledge of the codebase,this would be helping me in integrating the new feature build for the geo-replication over the current features using C and Python wherever required.

How do you intend to implement your proposal

Refactoring will be done in the code base to a certain extent as discussed with the mentor and also the journaling feature - 'changelog' of glusterfs will be customised to serve the file-level synchronization.

A rough timeline for your progress

Final deliverable

Any other details you feel we should consider

I have keen interest increasing my Fedora and FOSS contribution. I also possess good knowledge of the project's codebase and I have been in regular touch with my mentor since path 2 months. link title

@@ Line 1: / Line 1: @@
-            '''GSOC-2016 PROPOSAL
+This is a basic template of information you can use for filling out a GSoC application for the Fedora Project.
-PROJECT-FEDORA INFRASTRUCTURE WEB APPLICATION DEVELOPMENT: COMMUNITY OPERATIONS    (CommOps)'''
-'''CONTACT INFORMATION'''-
+== Template ==
-Olaitan Igbagbo Awe
-laitanawe@gmail.com
+=== Contact Information ===
-+234-8051069772, +234-8060132876
+* '''Email Address''':    Preferably the one used when FAS account was setup (if not, please specify this)
-FAS username-laitanawe
+* '''Blog URL''': personal or fedora planet link
-IRC-laitanawe
+* '''Freenode IRC Nick''':     [https://fedoramagazine.org/beginners-guide-to-irc Beginner's Guide To IRC]
+* '''Code Forges (GitHub, GitLab, BitBucket, etc.)''':   both your personal handle and any  orgs / previous projects you've worked on
+**
+**
+* '''Social Media Accounts''':
+**
+**
-'''WHY FEDORA'''- I want to work with FEDORA as I found your work very interesting. I visited all your pages like Fedora CommOps, Community Blog, Wiki, Fedora Badges, Storytelling, Hubs etc. After visiting all the pages and carefully studying, I found that Fedora CommOps is the most versatile project to work with as it connects to all the other things automatically and my skills are best suitable for this project.
+'''NOTE''': We require all students to blog about the progress of their project on a weekly basis. You are strongly encouraged to register on the Freenode network and participate in our IRC channels. For more information and other instructions, use the {{fplist|summer-coding}} mailing list for seeking clarification.
-'''GSOC PARTICIPATION-''' This is the first time I’m taking part in GSOC and I’m really excited to work with your organisation.
+=== Questions to answer ===
-'''CONTRIBUTION'''- I have already started contributing to FEDORA and I will continue my efforts for making it better. I have joined the mailing list, IRC, got the FAS account, signed the CLA, and introduced myself on wiki, applied for FEDORA AMBASSADOR, applied for group membership. I also interacted with the mentors on mailing list and found them really supporting. I also checked the tools and utilities section.
+==== Why do you want to work with the Fedora Project? ====
-'''WHY CHOOSE ME'''- For this project (CommOps), you need someone who is self-motivated, self-sufficient and   the one who has curiosity to learn. I am a hard worker and I am ambassador for Mozilla, African Society for Bioinformatics and Computational Biology (asbcb.org). I am member of the International Society for Computational Biology (ISCB). I write contents for asbcb.org and beyond news. I am comfortable in working with JAVA, C/C++, PHP, MySQL, HTML5, CSS3, JavaScript, JQuery and Android Studio. I have made a Mobile Application for Nigerian Students as a mini project three years ago.
+==== Do you have any past involvement with the Fedora Project or another open-source project as a contributor? ====
-'''WHERE I BELONG'''- As I have already mentioned CommOps is a very versatile and flexible project, I can help you by editing the documents or writing the blog for Fedora community. I can help you in designing part and also in collecting and analysing data. I found that my interest lies in Messaging (fedmsg), Metrics, Badges, Hubs, Culture and Wiki.  And I am very curious for learning new things so definitely I’m going to improve myself according to the instructions provided by my mentor.
+==== Have you participated in GSoC in the past? If so, what year(s) and which organization(s)? ====
+==== Do you plan to continue contributing to the Fedora Project after GSoC? If yes, what sub-project(s) are you interested with? ====
-'''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.
+==== Why should we choose you over other applicants? ====
-March-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 joining the CommOps community.
+==== 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)? ====
-April-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.
-May-24June: Weekly target completion and submission of work report to the mentor. Submissions for Mid-term evaluation.
+==== Do you have any other open source experience (even if not coding-related)? ====
-June-31July: Continuing the Implementation and regular progress check-up.
+==Proposal Description==
-August-15 August: Final brush up, full integration testing, documentation and submission for final evaluation.
+===Overview and The Need===
-'''FINAL DELIVERABLES'''- Developed Content, Bug Free environment, Campaign Development and Implementation, Design Improvements, collected and well-organised data, improvements with wok related to metrics gathering and real-time messaging integration.
-[[Category:Summer_coding_2016]]
+===Any relevant experience you have===
+As a contributor to glusterfs I have prior knowledge of the codebase,this would be helping me in integrating the new feature build for the geo-replication over the current features using C and Python wherever required.
+===How do you intend to implement your proposal===
+Refactoring will be done in the code base to a certain extent as discussed with the mentor and also the journaling feature - 'changelog' of glusterfs will be customised to serve the file-level synchronization.
+===A rough timeline for your progress===
+===Final deliverable===
+===Any other details you feel we should consider===
+I have keen interest increasing my Fedora and FOSS contribution. I also possess good knowledge of the project's codebase and I have been in regular touch with my mentor since path 2 months.
+[http://www.example.com link title]
+[[Category:Summer coding 2016]]

Search