From Fedora Project Wiki

< GSOC 2016

Revision as of 11:00, 25 March 2016 by Dhanvi (talk | contribs) (A rough timeline for your progress)


Contact Information

Questions to answer

Why do you want to work with the Fedora Project for GSoC ?

I chose Fedora as first OS that I installed into my laptop (off-course after removing windows 8) because I liked the Fedora Symbol very much (Fedora Design team has done a great job for doing the same). After when I came to know that the F means Infinite Freedom plus voice I always thought of contributing to the project.

  1. Improve my coding skills. (I am currently doing my computer science graduate so ability to build software is a skill must for me.)
  2. To be a part of the bigger community and Improve my communication skills (Ability to work with people from all over world and in different time zones is a big plus point for me)
  3. Opportunities with Red Hat (Who doesn't want to get paid for doing what they love to do!)
  4. Stipend by Google (Good enough to spend my summer coding without the need of taking money from my parents or working)

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

  • Fedora
    • I have recently joined the CommOps Team[1] and working on couple of tickets right now
    • I have joined the Security Team as a Apprentice
  • Mozilla
    • I am one of the Mozilla Core Contributors[2].
    • Here is my Mozillians Profile [3] just like our fedorapeople.org
    • I have fixed bugs in many projects of Mozilla here [4]
    • I am currently working with the Automation team[5] and security team.
    • I have also contributed to Mozilla in various other ways such as Firefox Student Ambassador[6] Trainee[7] level and done some non-coding things such as Bugs Triaging[8] and
  • Debian
    • I have done little bit of Ruby packaging in Debian[9]
  • Kernel
    • I have fixed few coding style bugs in the Kernel using CheckPatch[10]
  • Git and other
    • I tried contributing to Git but couldn't get and code merged but did a minor bug report[11]
    • I have also reported 2 minor bugs in Gnome[12] and Chromium[13]

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

  • No, this is the first time that I am applying for GSOC and I am very much exited about the same

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

  • Yes I am very much interested in contributing to the Fedora Project after completing my GSoC. I am very much interested in Fedora Security team and I am already working with CommOps and am interested in Ambassadors and Campus Ambassadors.

Why should we choose you over other applicants?

  • Strong believer in FREEdom[14] software and privacy.
  • Contributions to various Open Source organisations[15].
  • Strong grip on Version Control system and have a good understanding of how to work in the open source way (Mailing List, IRC etc.)
  • Expertise in various domains Programming,Cyber security etc..
  • Ability to speak (code!) in Multiple Languages including but not limited to C,C++,Python,JavaScript and basic Go.
  • Academic Scores : A+ in both Computer programming and Java Programming, and have at-least a grade of B+ (equivalent of A- in our University) in other core computer courses
  • Hard Working nature and Enthusiasm to contribute
  • Actively participate/volunteer for conferences in Open Source conferences in South India

Proposal Description

Overview and The Need

  • Anerist : the documentation indifference engine
  • Anerist is a software framework using which we can convert the documentation in various formats such as ReStructuredText, XML, or plain text into a neatly indexed html pages with common style and theme.


  • The reason we need this frame work is to reduce the manual work in converting the old formatted documentation into beautiful html pages.
  • Also to have a common place for documentation.

Any relevant experience you have

  • I haven't worked on this project as it's relatively new project, but I have good experience with static generators in common. I have forked[16] the code on Github and started hacking on the code.

How do you intend to implement your proposal

A rough timeline for your progress

  • Community Bonding Period:
    • April 23 - May 22 :
      • Understand the source-code.
      • Discuss about the project with mentor.
  • Coding Period:
    • May 23 - May 29 (1 week) :
      • Create a blog about the project and what I am gonna do.
      • Start working with the code.
    • May 30 - June 19 (3 weeks):
      • Work on my first part of project.
    • June 20 - June 26 (1 week) :
      • Mid-term Evaluation
      • Make sure I have working code
    • June 27 - July 17 (3 weeks) :
      • Work on second part of the project.
    • July 18 - August 7 (3 weeks) :
      • Work on the third part of project.
    • August 8 - August 21 (2 weeks) :
      • Pencils down time.
      • Testing the working of code and do hot fixes.
  • After GSoC:
    • If any bits of the project is left I will continue working on it.
    • I would continue contributing to Fedora project and would like to become on of the Core contributor of the project


Final deliverables :

  • Create a common html template for Fedora Documents
  • Anerist should be able to convert at-least few formats of docs to beautiful html pages.
  • Convert the possible documentation into html pages.
  • I can be flexible with these terms and will discuss about the same with mentors.

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