Difference between revisions of "Summer of Code/2015/Kushan Javascript"
Kushan2020 (talk | contribs) |
Kushan2020 (talk | contribs) |
||
| Line 15: | Line 15: | ||
<h3>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?</h3> | <h3>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?</h3> | ||
<br> | <br> | ||
| − | <p>I have been contributing to open source frequently. | + | <p>I have been contributing to open source frequently. Below is my profile of bugzilla at Mozilla Foundation.</p> |
<div style="border:1px solid #ccc; padding:6px 12px; color:#333; background-color:; margin:1px; font-size:100%; margin-left:30px; margin-right:30px; text-indent:"> | <div style="border:1px solid #ccc; padding:6px 12px; color:#333; background-color:; margin:1px; font-size:100%; margin-left:30px; margin-right:30px; text-indent:"> | ||
<p><b>Bugzilla profile</b> | <p><b>Bugzilla profile</b> | ||
| Line 22: | Line 22: | ||
</div> | </div> | ||
<ul> | <ul> | ||
| − | <li><b>Adding touch action regions:</b> This bug involved implementing declaring candidate regions for default touch behaviours as set by w3 consortium.[http://www.w3.org/TR/pointerevents/#declaring-candidate-regions-for-default-touch-behaviors [ | + | <li><b>Adding touch action regions [https://bugzilla.mozilla.org/show_bug.cgi?id=1101627 [1<nowiki>]</nowiki>]:</b> This bug involved implementing declaring candidate regions for default touch behaviours as set by w3 consortium.[http://www.w3.org/TR/pointerevents/#declaring-candidate-regions-for-default-touch-behaviors [2<nowiki>]</nowiki>].Firefox as of yet hasn't implemented pointer events for default touch action regions, this bug required me to create touch action regions, and forward them to composter. The regions were further divided into no_Action_Region, horizontal_Pan_Region and vertical_Pan_region , which had to be processed separately. This bug was quite interesting as it had me working on the components of CSS implementation of the browser. |
</li> | </li> | ||
| + | <li><b>Use of new xpcshell test cases [https://bugzilla.mozilla.org/show_bug.cgi?id=1022342 [3<nowiki>]</nowiki>]:</b> The use of new globally available xpcshell tests, retired change in the code of calendar and lighting app of mozilla suite. In this bug I am upgrading the unit testing code of the suite to follow the change in Assert.jsm. </li> | ||
| + | |||
| + | <li><b>Using getters/setters[https://bugzilla.mozilla.org/show_bug.cgi?id=1116008 [4<nowiki>]</nowiki>] : </b> This was fairly simply bug which required upgradation of existing firefox code to use getters/setters method. | ||
| + | </ul> | ||
About your project[edit | edit source] What is the name of your project? 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 Summer of Code work period is from May 19 - August 22; 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 (27 June); the last steps always take longer than you think, and we will consider cancelling projects which are not mostly working by then. 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[edit | edit source] If your project is successfully completed, what will its impact be on the Sugar Labs 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 Sugar Labs community, at least one of whom should be a Sugar Labs GSoC mentor. Provide email contact information for non-GSoC mentors. What will you do if you get stuck on your project and your mentor isn 't around? How do you propose you will be keeping the community informed of your progress and any problems or questions you might have over the course of the project? Miscellaneous[edit | edit source] We want to make sure that you can set up a development environment before the summer starts. Please do one of the following: Send us a link to a screenshot of your Sugar development environment with the following modification: when you hover over the XO-person icon in the middle of Home view, the drop-down text should have your email in place of "logout". Send us a link to a pull request or merge request you have made on a Sugar or Sugar activity bug. It's normal to need assistance with this, so please visit our IRC channel, #sugar on irc.freenode.net, and ask for help. 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? Please include the category tag at the bottom of your page the Catagory tag for 2015 GSoC applications. | About your project[edit | edit source] What is the name of your project? 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 Summer of Code work period is from May 19 - August 22; 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 (27 June); the last steps always take longer than you think, and we will consider cancelling projects which are not mostly working by then. 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[edit | edit source] If your project is successfully completed, what will its impact be on the Sugar Labs 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 Sugar Labs community, at least one of whom should be a Sugar Labs GSoC mentor. Provide email contact information for non-GSoC mentors. What will you do if you get stuck on your project and your mentor isn 't around? How do you propose you will be keeping the community informed of your progress and any problems or questions you might have over the course of the project? Miscellaneous[edit | edit source] We want to make sure that you can set up a development environment before the summer starts. Please do one of the following: Send us a link to a screenshot of your Sugar development environment with the following modification: when you hover over the XO-person icon in the middle of Home view, the drop-down text should have your email in place of "logout". Send us a link to a pull request or merge request you have made on a Sugar or Sugar activity bug. It's normal to need assistance with this, so please visit our IRC channel, #sugar on irc.freenode.net, and ask for help. 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? Please include the category tag at the bottom of your page the Catagory tag for 2015 GSoC applications. | ||
Revision as of 08:18, 19 March 2015
About me
What is your name?
Kushan Joshi
What is your email address?
0o3ko0@gmail.com, ikushan@me.com
What is your Sugar Labs wiki username?
Kushan2020
What is your IRC nickname on irc.freenode.net?
kepta
What is your first language? (We have mentors who speak multiple languages and can match you with one of them if you'd prefer.)
English
Where are you located, and what hours (UTC) do you tend to work? (We also try to match mentors by general time zone if possible.)
India, 8:30am - 12:30pm (UTC) & 3:30pm- 7:30 (UTC)
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?
I have been contributing to open source frequently. Below is my profile of bugzilla at Mozilla Foundation.
Bugzilla profile https://bugzilla.mozilla.org/user_profile?user_id=500998
- Adding touch action regions [1]: This bug involved implementing declaring candidate regions for default touch behaviours as set by w3 consortium.[2].Firefox as of yet hasn't implemented pointer events for default touch action regions, this bug required me to create touch action regions, and forward them to composter. The regions were further divided into no_Action_Region, horizontal_Pan_Region and vertical_Pan_region , which had to be processed separately. This bug was quite interesting as it had me working on the components of CSS implementation of the browser.
- Use of new xpcshell test cases [3]: The use of new globally available xpcshell tests, retired change in the code of calendar and lighting app of mozilla suite. In this bug I am upgrading the unit testing code of the suite to follow the change in Assert.jsm.
- Using getters/setters[4] : This was fairly simply bug which required upgradation of existing firefox code to use getters/setters method.
About your project[edit | edit source] What is the name of your project? 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 Summer of Code work period is from May 19 - August 22; 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 (27 June); the last steps always take longer than you think, and we will consider cancelling projects which are not mostly working by then. 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[edit | edit source] If your project is successfully completed, what will its impact be on the Sugar Labs 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 Sugar Labs community, at least one of whom should be a Sugar Labs GSoC mentor. Provide email contact information for non-GSoC mentors. What will you do if you get stuck on your project and your mentor isn 't around? How do you propose you will be keeping the community informed of your progress and any problems or questions you might have over the course of the project? Miscellaneous[edit | edit source] We want to make sure that you can set up a development environment before the summer starts. Please do one of the following: Send us a link to a screenshot of your Sugar development environment with the following modification: when you hover over the XO-person icon in the middle of Home view, the drop-down text should have your email in place of "logout". Send us a link to a pull request or merge request you have made on a Sugar or Sugar activity bug. It's normal to need assistance with this, so please visit our IRC channel, #sugar on irc.freenode.net, and ask for help. 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? Please include the category tag at the bottom of your page the Catagory tag for 2015 GSoC applications.