From Fedora Project Wiki

No edit summary
(page locked notice applied)
 
(37 intermediate revisions by one other user not shown)
Line 1: Line 1:
For information how to complete this form, refer to [[Summer Coding 2010 step-by-step for students]].
{{admon/important|Proposal deadline is passed. This page is locked.|Do not change any details on this page.  If must change something, talk with the project mentor first.}}


== Random list of application requirements ==
== About Me ==
 
# 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 ==


<!-- This is a transclusion, where the entire contents of another page are pulled in to be included as-is here.  You need to create a [[Summer Coding 2010 student application - Your Name]] that is pulled in here.  For more information, read [[Summer Coding 2010 step-by-step for students]]. -->
<!-- This is a transclusion, where the entire contents of another page are pulled in to be included as-is here.  You need to create a [[Summer Coding 2010 student application - Your Name]] that is pulled in here.  For more information, read [[Summer Coding 2010 step-by-step for students]]. -->
Line 13: Line 7:
{{:Summer Coding 2010 student application - karthika venkatesan}}
{{:Summer Coding 2010 student application - karthika venkatesan}}


== About your project ==
== About My project ==
=== Name of the project ===
GUI application for Cron job scheduler
 
=== Aim of the project ===
Cron is a time-based job scheduler in Unix-like computer operating systems. Cron jobs 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 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. The GUI is developed using Java, and the shell scripts are executed from the java program


# GUI application for Cron job scheduler
=== Schedule of the project ===
# 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
Week 1    : Requirements analysis and Feasibility study<br>Week 2    : Design and Module Identification<br>Week 3,4  : Coding and Unit Testing - Phase 1<br>Week 5    : Integration Testing and Documentation - Phase 1<br>Week 6,7  : Coding and Unit testing -  Phase 2<br>Week 8    : Integration Testing and Documentation - Phase 2<br>Week 9    : System testing<br>Week 10    : Packaging, Documentation and User manual preparation<br>Week 11    : Submission of project<br><br>


# Schedule for the project
=== Previous works ===
  Week 1      : Requirements analysis and Feasibility study
The schedule of the project ensures that the coding will start after analyzing and documenting the requirements. Since the project is developed in 2 phases, the actual development of the project is not postponed till the end. I prefer the methodology of incremental development so that it does not overwhelm the developer at the end of the project. Documentation and testing is done during each week of the project to avoid proceeding with defects. The projects that I developed earlier were submitted on schedule and were divided into modules for efficient development. The open source project that I developed is Quizzers suite which won 2nd place in the All India level competition, Code for freedom 2008. The documentation and source is available in the following link https://quizzersuite.dev.java.net/
  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 ==
== You and the community ==
 
=== Views on project ===
# 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.
# '''My View'''<br>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. Thus this application can be added in the next release of fedora that will provide an added feature.
# What will you do if you get stuck on your project and your mentor isn't around?
# '''What will you do if you get stuck on your project and your mentor isn't around?'''<br>Since I clearly list the requirements and analyze it in the week 1, I can proceed with the project even if the mentor is not around. Else if I get stuck with my project, I'll look for related forums to gather help from the online mentors
# 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?  
# '''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?'''<br> I can submit the the progress in my project by listing the work done in each week


== Miscellaneous ==
== Miscellaneous ==
# We want to make sure that you are prepared before the project starts
# We want to make sure that you are prepared before the project starts
#* Can you set up an appropriate development environment?
#* Can you set up an appropriate development environment? <br> Yes
#* Have you met your proposed mentor and members of the associated community?
#* Have you met your mentor? <br> yes
# What is your t-shirt size?
# What is your t-shirt size? <br> L
# 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?
 
<!-- Delete this paragraph and the following one when preparing your application. -->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 [http://dev.ryzom.com/projects/nel/wiki/GSoC2009WritingProposals writing proposals]. We encourage Summer Coding code to include tests.


== Comments ==
== Comments ==

Latest revision as of 16:57, 21 May 2010

Important.png
Proposal deadline is passed. This page is locked.
Do not change any details on this page. If must change something, talk with the project mentor first.

About Me

  1. Name : Karthika Venkatesan
  2. Email id : karthi.champ@gmail.com
  3. wiki username : champs
  4. IRC nickname : Nil
  5. primary language : Tamil, English
  6. Where are you located, and what hours do you tend to work? - India, 9 AM to 9 PM (IST : GMT+5.30)
  7. Open source projects :
  Quizzers suite : https://quizzersuite.dev.java.net/

About My project

Name of the project

GUI application for Cron job scheduler

Aim of the project

Cron is a time-based job scheduler in Unix-like computer operating systems. Cron jobs 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 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. The GUI is developed using Java, and the shell scripts are executed from the java program

Schedule of 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

Previous works

The schedule of the project ensures that the coding will start after analyzing and documenting the requirements. Since the project is developed in 2 phases, the actual development of the project is not postponed till the end. I prefer the methodology of incremental development so that it does not overwhelm the developer at the end of the project. Documentation and testing is done during each week of the project to avoid proceeding with defects. The projects that I developed earlier were submitted on schedule and were divided into modules for efficient development. The open source project that I developed is Quizzers suite which won 2nd place in the All India level competition, Code for freedom 2008. The documentation and source is available in the following link https://quizzersuite.dev.java.net/

You and the community

Views on project

  1. My View
    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. Thus this application can be added in the next release of fedora that will provide an added feature.
  2. What will you do if you get stuck on your project and your mentor isn't around?
    Since I clearly list the requirements and analyze it in the week 1, I can proceed with the project even if the mentor is not around. Else if I get stuck with my project, I'll look for related forums to gather help from the online mentors
  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?
    I can submit the the progress in my project by listing the work done in each week

Miscellaneous

  1. 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 mentor?
      yes
  2. What is your t-shirt size?
    L

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

Retrieved from "https://fedoraproject.org/w/index.php?title=Summer_Coding_2010_proposal_-_cron_job_scheduler&oldid=175695"