-
Notifications
You must be signed in to change notification settings - Fork 211
gsoc2011
Here's where we'll work out our application to GSoC. Feel free to edit the below if you're confident that your edits are an improvement. If you want to suggest a change but you think it needs more discussion, put your suggestion below the section it refers to, as a "quote":
> Like this.
>> Or respond like this.
> Respond to responses like this.
Pyjamas
Pyjamas is a way to run Python on web clients. You can think of it as like GWT, but with Python instead of Java - a better fit for Javascript. Pyjamas apps can run either as pure Python using the installed Pyjamas Desktop UI, or be compiled using a Python-to-javascript compiler and viewed in a standard web client.
Apache V2
Why is your organization applying to participate in GSoC 2011? What do you hope to gain by participating (required)
We hope to raise our profile as an open-source project, and bring new members into our community. If we don't get in this year, we hope to learn from the experience so that we can get in next year.
Yes, although the project has had one GSoc2007 student: http://code.google.com/p/pyjamas/wiki/GsocLlpamies
Did your organization participate in past GSoCs? If so, please summarize your involvement and the successes and challenges of your participation.
We did not, although one student did.
If your organization participated in past GSoCs, please let us know the ratio of students passing to students allocated, e.g. 2006: 3/6 for 3 out of 6 students passed in 2006.
NA
What is the main development mailing list for your organization? This question will be shown to students who would like to get more information about applying to your organization for GSoC 2011. If your organization uses more than one list, please make sure to include a description of the list so students know which to use.
pyjamasdev@pyjs.org
The mailing list is also visible at http://groups.google.com/group/pyjamas-dev
pyjamas at irc dot freenode dot net
Does your organization have an application template you would like to see students use? If so, please provide it now. Please note that it is a very good idea to ask students to provide you with their contact information as part of your template. Their contact details will not be shared with you automatically via the GSoC 2011 site.
What criteria did you use to select the individuals who will act as mentors for your organization? Please be as specific as possible. (required)
We have had a number of contributors willing to step up to help themselves, and we have a policy of trusting anyone who asks, allowing them write access to the git repository (substituting a "telling off" in the form of describing in excruciating detail the consequences of their actions, rather than mistrusting them in the first place). Many people successfully pass this test (and even those who don't still actually manage to provide useful patches).
These contributors have demonstrated that they are willing to learn a completely new type of web-development framework from scratch, and then, when they find that it doesn't quite do what they want, are willing to delve in, find out what's going on, make it work and then contribute it back so that others can benefit. Some of those people have then disappeared, or, being introverted, remain useful but silent, and dedicated and valued nevertheless, and others just become plain too busy.
Some of those people that have stuck around, and often write ideas, discuss them and implement them, they are the ones who have been volunteered as mentors. They are intelligent, have proven themselves to be self-motivated, shown that they are willing to let people know what they are doing, can confidently discuss ideas in the all-important "ego-less" manner by demonstrating that they can take on-board input from others.
The project uses git, and the student will be advised to use a branch. As an absolute last resort, their work would be simply left, for others in the project to pick up as they wished. The status report would be completed and the work reviewed up to that point by the Project's Lead Developer and the mentor, with a view to assessing how far along it was, and what needed to be completed (and how), such that anyone else wishing to pick up the work may do so hitting the ground running. Although the list is non-essential, because pyjamas has reached "stable" status, the list of ideas is work that needs to be done, regardless, at some point, and so chances are high that it will be picked up and used (dependent on review).
As "backup", the Project Lead Developer will work with the student, publicly, on the mailing list, with the informal and additional assistance of any of the other 500 or so people on the list (of whom approximately 10-15 or so are regular contributors, including those people who have volunteered as mentors). The student will therefore be treated with the respect given to anyone that is an informal but self-motivated free software developer, contributing just as anyone else does, to the Pyjamas Free Software Project.
What steps will you take to encourage students to interact with your project's community before, during and after the program? (required)
The students will be afforded the same respect and status as is given to other independent and self-motivated Free Software Developers, and will be welcomed and encouraged to participate in the public forums, as equals and peers. We tend to find that those people who "get" pyjamas absolutely love it, and stick around.
If you are a small or new organization applying to GSoC, please list a larger, established GSoC organization or a Googler that can vouch for you here.
The Python Software Foundation and Web2py are willing to vouch for us.
If you are a large organization who is vouching for a small organization applying to GSoC for their first time this year, please list their name and why you think they'd be good candidates for GSoC here:
N/A
Pyjamas rocks :) It covers an extremely broad range of modern and cutting-edge computer science, from computer technology and language translation (high-level compiler) including java to python as well as python to javascript, five different types of web browsers, five different types of web browser engines, Python on Win32 using DCOM to its absolute maximum extent (which is very rare - even the Microsoft IE Team Leader had never heard of anyone making such extensive and complete use of IWebBrowser2 before), DOM bindings written in c and c++, using both perl as well as python code-generators with 400+ IDL files to provide *two* sets of python bindings to Webkit; XULRunner from the Mozilla foundation (python-xpcom and hulahop from OLPC) - the list of other projects leveraged, the skills that can be learned, and the opportunities that can be had to learn about "practical" Computer Science are far, far higher than is apparent at first glance.
Fortunately, not all of these skills are required all at once! Pyjamas is about providing a very powerful and simple framework, almost exclusively written in pure python, behind which there is an extraordinary amount going on that the application writer simply does not need to know about. Any student working on pyjamas however will get a glimpse of what's going on, and will know that they're working on something that makes application writers lives just that little bit easier when it comes to developing GUI applications that happen to work on both the web as well as the desktop.
TODO