Changes

I've started a small project on freshmeat called statusPidgin that fetched text from various sources and made it a status message in Pidgin. It's now abandoned, but you can find the source [http://linux.softpedia.com/get/Communications/Chat/statusPidgin-31896.shtml  on softpedia ]<br />

I've started a small project on freshmeat called statusPidgin that fetched text from various sources and made it a status message in Pidgin. It's now abandoned, but you can find the source [http://linux.softpedia.com/get/Communications/Chat/statusPidgin-31896.shtml  on softpedia ]<br />

I have also released one of my school projects as open source (a small web imap/pop3 client) and you can get it from [http://dl.getdropbox.com/u/317039/easymail.zip my dropbox]. I haven't contributed in a significant way to open source projects before, beside bug reports and small patches. <br />

I have also released one of my school projects as open source (a small web imap/pop3 client) and you can get it from [http://dl.getdropbox.com/u/317039/easymail.zip my dropbox]. I haven't contributed in a significant way to open source projects before, beside bug reports and small patches. <br />

I am however a user of open source (linux, KDE, gcc, python, firefox, webkit) and am absolutely delighted by the concept. I am convinced it is the most efficient way of developing software, and perhaps not only.<br />

I am a user of open source (linux, KDE, gcc, python, firefox, webkit) and am absolutely delighted by the concept. I am convinced it is the most efficient way of developing software, and perhaps not only.<br />

I am especially interested in the Sugar project, as I have myself experienced the closed-mindedness that schools instill in their students by teaching them using closed source software. I have been fortunate enough to get some exposure to linux and kde and then used them for a few years.

I am especially interested in the Sugar project, as I have myself experienced the closed-mindedness that schools instill in their students by teaching them using closed source software. I have been fortunate enough to get some exposure to linux and kde early enough and I would like to help others by showing them the alternatives.

====About your project====

====About your project====

* What is the timeline for development of your project? The Summer of Code work period is 7 weeks long, May 23 - August 10; 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 6-13); the last steps always take longer than you think, and we will consider cancelling projects which are not mostly working by then.

* What is the timeline for development of your project? The Summer of Code work period is 7 weeks long, May 23 - August 10; 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 6-13); the last steps always take longer than you think, and we will consider cancelling projects which are not mostly working by then.

I plan to get Gears integration, dbus access and a nicer js wrapper on top of that done in the first 2-3 weeks. This would create a template for web-based activities, what web developers would use when starting web activities. A small utility that generates sugarified web applications would also use that template. <br />The utility and small demo of using the APIs directly(second usage of the toolkit) could then be made in a few days, one week at most. The rest of the time could then be spent for polishing things up, if nothing unexpected crops up.

I plan to get Gears integration, dbus access and a nicer js wrapper on top of that done in the first 2-3 weeks. This would create a template for web-based activities, what web developers would use when starting web activities. A small utility that generates sugarified web applications would also use that template. <br />The utility and small demo of using the APIs directly(second usage of the toolkit) could then be made in a few days, one week at most. The rest of the time could then be spent for polishing things up or for emergencies.

# Browse can successfully "sugarize" GMail.

* 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.

* 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.

I absolutely adore the web and I absolutely adore open source. Python is my favourite programming language and I JavaScript is a close enough second.  

Python is my favourite programming language and JavaScript is a close enough second.

 

====You and the community====

====You and the community====