From Fedora Project Wiki

Line 17: Line 17:
# The name of my project is Beacon
# The name of my project is Beacon
# This project come from Idea Beacon mentioned on this[https://fedoraproject.org/wiki/Summer_Coding_2010_Ideas_-_Beacon] page? I contacted the mentors about this project and they helped me in getting better understanding about the idea and I am drafting the proposal accordingly as per the goals of the idea.
# This project come from Idea Beacon mentioned on this[https://fedoraproject.org/wiki/Summer_Coding_2010_Ideas_-_Beacon] page? I contacted the mentors about this project and they helped me in getting better understanding about the idea and I am drafting the proposal accordingly as per the goals of the idea.
# As zikula support plugins , my plan is to create a Beacon plugin for Zikula. This plugin will provide the user the choice between editors , if he chooses beacon ,then he can proceed editing in it. Also I will enhance the wiki type editing support in beacon which will include improving beacon to add new functionality. This will include using codemirror which can be quite helpful in adding html parsing support to docbook.   
# As zikula support plugins , my plan is to create a Beacon plugin for Zikula. This plugin will provide the user the choice between editors. If he chooses beacon then he can proceed editing in it. Also I will enhance the wiki type editing support in beacon which will include improving beacon to add new functionality. This will include using codemirror libraries which can be quite helpful in adding html parsing support to docbook. This project will help  which uses beacon editor and can prove out to be a major step towards development of beacon editor so that it quickly comes out of its beta status and become available worldwide. This project is utmost importance because the beacon editor has the potential to become a power editor within browser and can challenge other proprietary solutions. The major technologies to be used during this project are XML,Ajax,JavaScript,PHP and XSL.  
# 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?
 
# 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.
# 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 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.

Revision as of 14:39, 15 May 2010

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. My name is Subodh Rohilla
  2. Email : subodh.rohilla@gmail.com
  3. Wiki Use name : Subodh
  4. IRC Nick : sr_rules
  5. Primary Languages : English , Hindi
  6. Location : Delhi ( India) , Time of work : 11:00 am to 9 pm ( GMT + 5:30 )
  7. I have good coding skills and I take regular part in coding events of Local ACM chapter events and spoj.pl . I have lot of experience in PHP and AJAX. My major projects include IBM TGMC 2009 and web designing internship at "A PLUS Solutions Pvt.Ltd."[1] . As far as my contribution to open source is concerned :-
    • I help users in IRC and mailing list by troubleshooting their Problems .
    • I maintain my Institute's LUG Mailing List ( http://groups.google.co.in/group/bit-lug?hl=en ).
    • I use beta releases and report issues to make suggestions to make the software better.

About your project

  1. The name of my project is Beacon
  2. This project come from Idea Beacon mentioned on this[2] page? I contacted the mentors about this project and they helped me in getting better understanding about the idea and I am drafting the proposal accordingly as per the goals of the idea.
  3. As zikula support plugins , my plan is to create a Beacon plugin for Zikula. This plugin will provide the user the choice between editors. If he chooses beacon then he can proceed editing in it. Also I will enhance the wiki type editing support in beacon which will include improving beacon to add new functionality. This will include using codemirror libraries which can be quite helpful in adding html parsing support to docbook. This project will help which uses beacon editor and can prove out to be a major step towards development of beacon editor so that it quickly comes out of its beta status and become available worldwide. This project is utmost importance because the beacon editor has the potential to become a power editor within browser and can challenge other proprietary solutions. The major technologies to be used during this project are XML,Ajax,JavaScript,PHP and XSL.
  1. 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.
  2. 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?

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