From Fedora Project Wiki
(Created page with '= Contact Information == Email Address: hiemanshu at fedoraproject (dot) org Telephone: +91 99(zero)27 66(nine)62 Blog URL: http://hiemanshu.wordpress.com/ Freenode IRC Nick: hi...')
 
No edit summary
Line 1: Line 1:
= Contact Information ==
== Contact Information ==


Email Address: hiemanshu at fedoraproject (dot) org
Email Address: hiemanshu at fedoraproject (dot) org

Revision as of 16:57, 29 March 2011

Contact Information

Email Address: hiemanshu at fedoraproject (dot) org Telephone: +91 99(zero)27 66(nine)62 Blog URL: http://hiemanshu.wordpress.com/ Freenode IRC Nick: hiemanshu

Why do you want to work with our team?

I have been involved with Fedora for over a year now and also did FSC last year. The team has been very helpful in my progress so far and would love to continue working with the very helpful team who help me learn a huge portion of what I know today.

Do you have any past involvement with our team or another open source project?

Yes, I am in involed with quite a few groups within Fedora some of which include marketing, websites, packaging and ambassadors.

Why should we choose you over other applicants?

I have worked on Dorrie/Django before. The base template for dorrie was written by me during FOSS.IN 2009.

Proposal Description

Please describe your proposal in detail. Include:

* An overview of your proposal

The proposal is to extend dorrie to add an auth system, queuing, managing downloads, making it more intutive and also bringing it to a production ready state so it can be deployed to the fedora servers.

* The need you believe it fulfills

This would help a lot of people who want to create pre-configured live cds for installtion on more than one system or to distribute them to people who cannot create the live cds by themselves and also create it with added extra packages like mp3 support, multiple DEs, etc so that people without an internet connection can have a working system OOTB.

* Any relevant experience you have

I have experience with web frameworks and django and also with the process of building live cds and configuring kickstart files (I along with Aditya Patwari wrote the KDE Netbook spin last summer)

* How you intend to implement your proposal

Since most of the basic code is in place it will be easier to extend it to add an auth system and the other necessary items in the list. I will start with the auth system that will be tied up with the current FAS system and anyone who has an account should be able to use dorrie to create a live cd and have the link available to them for 24 hours (this can be changed later depending on the needs)

* A rough timeline for your progress

Week 0 - 4 : Lay out the basic details of work to be done, and finish the auth system, queuing, download manager (the server backend), and lay foundation for the admin system Week 4 - 8 : Create an admin backend (for managing settings, adding new repos, blocking/unblocking users, etc), write a new template to match the newer fedora website templates being used Week 8 - 11 : Write a qemu{,-kvm} frontend for it so the created live cds can be run and tested on the system before they are sent out to the evil outer world, this has to be scheduled for each person, and everyone should be allowed only 10 mins of access of the frontend to preserve users Week 11 - 13 : Finish up anything need to be, squash any bugs remaining, and finish the documentation

* Any other details you feel we should consider

None

Have you communicated with a potential mentor? If so, who?

Yes, I have spoken to Shreyank Gupta over IRC and spoke to him about the features he was looking at being implemented.