|
|
| Line 1: |
Line 1: |
|
| |
|
| {{:Summer Coding 2010 student application}}
| |
|
| |
| == 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 ==
| |
| # We want to make sure that you are prepared before the project starts
| |
| #* Can you set up an appropriate development environment?yes.
| |
|
| |
| #* Have you met your proposed mentor and members of the associated community?Yes.
| |
|
| |
| # What is your t-shirt size? L
| |
|
| |
| [[Category:Summer Coding 2010]]
| |
| [[Category:Summer Coding 2010 proposals]]
| |
