Summer Coding 2010 student proposal Kronikarz Tool

About me

For information how to complete this form, refer to Summer Coding 2010 step-by-step for students.

Random list of application requirements

1. Must include a schedule that was worked out with mentor
2. Keep on eye on the Talk: page that is associated with the proposal page you create. Click on the discussion link on the top of your proposal page. The Talk: page is where mentors comment on your proposal.
3. Make sure you have clicked on the watch link on the top of your proposal page(s) and Talk: page(s). Use the link to my preferences at the top of the page to set your Watchlist preferences to email you when changes are made.

About you

1. What is your name?
2. What is your email address?
3. What is your wiki username?
4. What is your IRC nickname?
5. What is your primary language? (We have mentors who may speak your preferred languages and can match you with one of them if you request.)
6. Where are you located, and what hours do you tend to work? (We also try to match mentors by general time zone if possible.)
7. Have you participated in an open-source project before? If so, please send us URLs to your profile pages for those projects, or some other demonstration of the work that you have done in open-source. If not, why do you want to work on an open-source project this summer?

About your project

1. What is the name of your project?
2. Does your project come from an idea on the Summer Coding 2010 ideas page? If so, provide a link for reference, as well as a link to any discussions with mentors about your proposal.
3. Describe your project in 10-20 sentences. What are you making? Who are you making it for, and why do they need it? What technologies (programming languages, etc.) will you be using?
4. What is the timeline for development of your project? The Fedora Summer Coding work period is 11 weeks long, May 24 - August 9; tell us what you will be working on each week. (As the summer goes on, you and your mentor will adjust your schedule, but it's good to have a plan at the beginning so you have an idea of where you're headed.) Note that you should probably plan to have something "working and 90% done" by the midterm evaluation (July 5-12); the last steps always take longer than you think, and we will consider canceling projects that are not mostly working by then.
   • If your project development progresses differently so there is not 90% functionality by the mid-term, you must be in regular contact with your mentor about this. Your mentor must not be surprised about the state of your project when the mid-term comes.
   • If you are not progressed this far in mid-term, you must have a plan with your mentor to fix the situation.
5. Convince us, in 5-15 sentences, that you will be able to successfully complete your project in the timeline you have described. This is usually where people describe their past experiences, credentials, prior projects, schoolwork, and that sort of thing, but be creative. Link to prior work or other resources as relevant.

You and the community

1. If your project is successfully completed, what will its impact be on the Fedora community? Give 3 answers, each 1-3 paragraphs in length. The first one should be yours. The other two should be answers from members of the Fedora community, at least one of whom should be a Fedora Summer Coding mentor. Provide email contact information for non-Summer Coding mentors.
2. What will you do if you get stuck on your project and your mentor isn't around?
3. In addition to the required blogging minimum of twice per week, how do you propose to keep the community informed of your progress and any problems or questions you might have over the course of the project?

Miscellaneous

1. We want to make sure that you are prepared before the project starts
   • Can you set up an appropriate development environment?
   • Have you met your proposed mentor and members of the associated community?
2. What is your t-shirt size?
3. Describe a great learning experience you had as a child.
4. Is there anything else we should have asked you or anything else that we should know that might make us like you or your project more?

Kronikarz

Description

Kronikarz is a Simple and convenient program for the user.

The program will contain 2 options: 1) the main application, the most simple interface for create a backup of the working user-space

2) low background customer service (service, daemon) for create backups on a schedule.

The mechanism of archiving involves creating customizations. The program checks the installed packages/applications and existing hook file (XML) configuration data applications and offers the user to choose what from him (the user) should be and what is not, on the basis of this contemplate a plan of archiving and made the process of archiving on a certain button (or in case of service (2) a pre-established user schedule.

In the settings the user can choose: - Path to the folder with files (default is something like ~ / .kronikarz / Backups); - File type (zip, tar.gz, tar.bz2, possibly others); - Applications, settings which should be archived; - Additional files that the program should be able to maintain (just files / folders user); - Species generated archive "simple / savings account," in one file archive / for different archive file "; - Schedule daily / weekly / monthly / yearly / every N days, time, day, month to create an archive, or when you start / stop systems; - The number of stored files (only for treatment schedules); May appear and more settings.

Counts 2 functions the main application (Backup / Restore), access that should be simple and clear for any level user.

XML File Example

Hook a configuration file XML (example): <name> Samba </ name> <folders_files> <folder_1> / etc / samba </ folder_1> <file_1> / etc / smb.conf </ file_1> <! - this is just example -> </ Folders_files> <packages> <fedora> samba </ fedora> <fedora> samba-common </ fedora> <fedora> samba-client </ fedora> <fedora> samba-winbind-clients </ fedora> </ Packages> <commands> <command_1> service smb start </ command_2> <! - also, as an example, opportunity to run commands should be, but under the user -> </ Commands>

To restore the program should offer a list to create an archive copies one of which user can select. And / or select a folder with files user samomtoyatelno. In the case of a storage of archives, offers a choice should be a tree and data recovery process should be carried out starting with the first archive, coasting, if the recovery is complete or separate copy of the date.

Since the idea is supposed to implement in python, it should be implement: - Backend with basic functional backup / recovery; - Frontend main application (remember that we use as graphic library Qt); - Frontend service / service / daemon (2) as a convenient user may user daemon and an applet to him for Gnome / KDE, or application, which will be located in the tray.

Timeline

1) one week (7 days) on the harmonization of technical specifications and definition of roles;

2) 20 days to implement backend functionality to the basic archiving / reconstruction;

3) 20 days to implement basic frontend GUI-applications (draft Alternatively, alpha-version);

4) 10 days for implementation frontend service / daemon (draft version alpha);

5) 15 days for debugging frontends (3, 4);

6) 7 days for final release testing;

7) 2 days on a package of RPM. The general plan of work: 81 days.

Convincing

I’m a phd student of instate of acoustics ,CAS. I have done many projects about speech,cell phone and games. The list is about some of my projects and publications:

Your Coding Skills What language are you familiar with? My programing languages are C, C++, java, perl ,python and linux shell. What platform are you developing on? Linux , WinCE, Symbian, Windows Show past projects and code examples of your own.

1. Use C and C++ language to write the code of HMM speech recognition and synthesis system for my lab.
2. Use Perl to write the text-processing codes.
3. As a Intern of SamSang China Research center, write the voice-control game on the platform of Windows mobile.
4. Write the VOIP client programs via G.729.
5. Write the UI of speech recognition products.
6. Linux shell program in C for the HMM training module of our speech recognition system
7. Build the speech synthesis system of our lab.
8. Write the code of Signal processing, extracting the features of MFCC, LPCC, LSP.
9. Transfer the code of speech enhancement from matlab to C.
10. implementing the famous straight speech synthesis matlab code to realtime useage

...

Some of my Publications

[1] <Discrimination Between Pathological and Normal Voices Using GMM-SVM Approach>, xiang wang, 2010 Elsivier

[2] Supporting Vector Machine Of Part Of Speech in Speech Synthesis System, 2010 ICBECS ...

Last summer I participated in GSOC working on vlc. But at the end of this summer I hope to contribute to the Fedora Project as a regular contributer.

Me and the community

Impact

If your project is successfully completed, what will its impact be on the Fedora community? Give 3 answers, each 1-3 paragraphs in length. The first one should be yours. The other two should be answers from members of the Fedora community, at least one of whom should be a Fedora Summer Coding mentor. Provide email contact information for non-Summer Coding mentors.

Miscellaneous

1. Can you set up an appropriate development environment?yes.
2. Have you met your proposed mentor and members of the associated community?Yes.
3. What is your t-shirt size? L