Contact Information
Email Address: vish92m@gmail.com Blog URL: http://vish92m.blogspot.in/ Freenode IRC Nick: VISH
Why do you want to work with the Fedora Project?
I have been a Fedora user for the past 2 years and I have always got attracted to their aim i.e. Freedom,Friends,Features,First . Due to the absence of a dedicated audio spin, it is not Features,First there, which is why I want to contribute and make Fedora head and shoulders above the others.
Do you have any past involvement with the Fedora project or another open source project as a contributor?
No, I have no past involment. Did you participate with the past GSoC programs, if so which years, which organizations?
No.
Will you continue contributing/ supporting the Fedora project after the GSoC 2012 program, if yes, which team(s), you are interested with?
Definitely yes , I will be contributing even after the completion of the program.My work will be to maintain the packages in my distro and submit any new packages for review.I am interested in Audio Creation SIG.
Why should we choose you over other applicants? 1.First of all I am myself a music enthusiast. So, I am very much interested in this project.My enthusiasm for this project can't be described in words. 2.I am very good at C, C++ , and also have essential knowledge about python. 3.I know how to implement all the servers in RHEL and I am a CCNA and MCP. 4.Also,my other knowledge includes Shell Scripting using Bash,RCS,CVS,make,Linux IPC,Process Management in Linux,gdb,RPM packaging and Building and running modules. 5.My other experiences include Pspice,Matlab,VHDL, EAGLE
Proposal Description
Overview
My aim is to collect all the package sources(tarballs) and create RPMs as per the Fedora Packaging Guidelines and hence create a spin which contains all the packages that I have created and the packages already in the main repository. All the packages will be audio related, other than that there will be some packages like editors etc.
The need
Making people move their Music Production to Fedora . Also, allowing many enthusiasts to do what was impossible(due to paid third-party applications). The Live-CD version makes it possible for enthusiasts and professionals to carry this in their USB stick or have a CD which will allow for for music development/production on the go.
Experience
I have experience writing shell scripts(Bash). I have basic understanding of Python. Although I am new to RPM packaging I am learning it at a fast pace and have tried out some it with some tarballs.
Implementation
Searching and adding relevant packages to the final list by holding IRC meetings and talking with the mentor.
PHASE I 1.Creating the final list of final packages/tarballs to be added to the spin. 2.The packages are those which are chosen from the main RPMFusion and CCRMA. 3.Other packages will be created using rpmbuild and source Tarballs. 4.Submit multiple packages for review( It is the lenghthiest process of all !) and hence add them to the main repository. 5.Add additional documentation to Musicians guide if required(Documentation will be done as per timeline)
PHASE II
1.Configure the kernel i.e. configuring a low latency kernel which can be done by 1.getting IRQ settings right 2.Adding some Realtime-Preemption patches No one wants Frame Skipping while watching a movie,so a low latency kernel is ideal for Audio/Video applications. HIGH PRIORITY
2.Pulseaudio to jack bridging(a serious issue reported by many users) and device configuration support must be provided from the start using Fedora Musicians guide and other documents.Cadence in Kxstudio collection can make the task easier by providing an alternate solution only if it does not ask for LADISH support and is released as a final version. HIGH PRIORITY
3.Creating the spin as per the Fedora spin guidelines, which will come in two flavours, 1.A DVD containing a full blown GUI and all applications 2.A Live-CD containing most of the packages and a simple GUI. Note: The GUI and themes will be finalized only after having discussions with mentor and IRC meetings.
Timeline 1.April 23 - May 15 : Getting Started (Community Bonding Period) During this I will compile the list of final packages.
2.May 16-June 1 : End-Semester Exams Note:My exam dates may shift two or three days or even a week due to my college administration changing it at the last minute,I will contact my mentor and inform him about the new dates(if any) a week before so we can reschedule anything if required.
3.June2 - June23 : Creating and submitting RPM packages for review and adding them to main repository.
4.June-24 - July 13 : Completing at least Phase II -1,2 i.e. configuring the kernel. and pulse->jack bridging
5.July 13 : Mid Term Evaluations
6.July 13-30 : Creating the spin and documentation.
7.July 31- August 13 : Adding additional features like KXStudio(See Phase II-2) if a stable version is released.
August 13 : Suggested "pencils down" date
August 15 - August 20 : Final polishing and documentation.
August 20 : Firm "pencils down" date
Other details Other than the details mentioned above , I will be a part of the community forever and will be maintaining the packages that I have packaged during this program and will add new packages.
Have you communicated with a potential mentor? If so, who?
I have been in constant touch with Mr.Brendan Jones (brendan.jones.it@gmail.com).