| Line 27: | Line 27: | ||
==== Why should we choose you over other applicants? ==== | ==== Why should we choose you over other applicants? ==== | ||
==== Have you worked for ANY open source orgs / project and have artifacts we can see / judge your skillset(s) off? ==== | |||
==== Do you have any other `heatwave` open source or otherwise (even if not coding related) ? ==== | |||
==Proposal Description== | ==Proposal Description== | ||
Revision as of 13:41, 16 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 worked for ANY open source orgs / project and have artifacts we can see / judge your skillset(s) off?
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