From Fedora Project Wiki
For information how to complete this form, refer to Summer Coding 2010 step-by-step for students.
Random list of application requirements
- Must include a schedule that was worked out with mentor
- 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.
- 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
- Name : Karthika Venkatesan
- Email id : karthi.champ@gmail.com
- wiki username : champs
- IRC nickname : Nil
- primary language : Tamil, English
- Where are you located, and what hours do you tend to work? - India, 9 AM to 9 PM (IST : GMT+5.30)
- Open source projects :
Quizzers suite : https://quizzersuite.dev.java.net/
About your project
- GUI application for Cron job scheduler
- Cron is a time-based job scheduler in Unix-like computer operating systems. Cron job are used to schedule commands to be executed periodically i.e. to setup commands which will repeatedly run at a set time, you can use the cron jobs. Cron is driven by a crontab, a configuration file that specifies shell commands to run periodically on a given schedule. The crontab files are stored where the lists of jobs and other instructions to the cron daemon are kept. Users can have their own individual crontab files and often there is a systemwide crontab file (usually in /etc or a subdirectory of /etc) which only system administrators can edit. Currently there is no proper GUI for scheduling cron jobs and it is still done using Terminal commands. Thus I would like to provide a GUI so that administrators can easily schedule their jobs in the GUI application
- Schedule for the project
Week 1 : Requirements analysis and Feasibility study Week 2 : Design and Module Identification Week 3,4 : Coding and Unit Testing - Phase 1 Week 5 : Integration Testing and Documentation - Phase 1 Week 6,7 : Coding and Unit testing - Phase 2 Week 8 : Integration Testing and Documentation - Phase 2 Week 9 : System testing Week 10 : Packaging, Documentation and User manual preparation Week 11 : Submission of project
- 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.
- 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
- On successful completion of this project, the scheduling of jobs becomes simple, easy scheduling and managing of jobs can be done. This proves to be an good solution as there is no current GUI based scheduler for cron jobs
- What will you do if you get stuck on your project and your mentor isn't around?
- 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
- 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?
- What is your t-shirt size?
- Describe a great learning experience you had as a child.
- 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?
Note: you will post this application on the wiki in the category Category:Summer Coding 2010 applications. We encourage you to browse this category and comment on the talk page of other applications. Also, others' comments and your responses on the talk page of your own application are viewed favorably, and, while we don't like repetitive spam, we welcome honest questions and discussion of your project idea on the mailing list and/or IRC.
The NeL project has some good general recommendations for writing proposals. We encourage Summer Coding code to include tests.
Comments
Use the Talk:Summer Coding 2010 student proposal application to actually make comment, which then appear here on the main proposal page. You can use this link to make a new comment].
plus talk