Error formatting macro: pagetree: java.lang.NullPointerException
Skip to end of metadata
Go to start of metadata
You are viewing an old version of this page. View the current version. Compare with Current  |   View Page History

Why is your organization applying to participate in Google Summer of Code 2012? What do you hope to gain by participating?

The Clojure community has been growing at a healthy rate since the initial language announcement in 2007: the Clojure mailing list now has over 6000 subscribers, the freenode IRC channel sees greater than 400 participants, and there are three conferences scheduled this year dedicated to Clojure. All of this activity means many open source initiatives in the community that need help - these range from new platforms like ClojureCLR and ClojureScript to advanced creative authoring environment like Overtone. This coupled with evident interest from students on the mailing list has encouraged us to apply for GSoC 2012. 

By participating we hope to accomplish several things. Of foremost importance, students get an opportunity to contribute to projects that would require far more sophistication in programming languages with more complex semantics than a Lisp - for example constraint logic programming over finite domains or improving the minimalistic ClojureScript compiler to produce optimal JavaScript code. We believe this kind of knowledge is incredibly useful outside the context of the Clojure language or community in particular. Taking a proposal gives students the critical opportunity to own a highly visible project and become a community leader. The Clojure community largely consists of practitioners so there often many projects of moderate difficultly with large community benefits that do not get addressed simply for lack of time. By participating as a sponsoring organization Google Summer of Code 2012, Clojure/core can contribute back to its community in a vital way given that we are not an academic institution nor have any infrastructure in place to encourage community members to sets aside two to three focused months to work on useful projects.  

Does your organization have an application template you would like to see students use? If so, please provide it now

  • Who are you (include links to Google Code, Github, Bitbucket, etc)? What are you studying?
  • Which proposal are you interested in? What exactly do you intend to do? What will not be done?
  • Why are you the right person for this task?
  • To what extent are you familiar with the software you're proposing to work with? Have you used it? Have you read the source? Have you modified the source?
  • How many hours are you going to work on this a week? 10? 20? 30? 40?
  • Do you have other commitments that we should know about? If so, please suggest a way to compensate if it will take much time away from Summer of Code.
  • Are you comfortable working independently under a supervisor or mentor who is several thousand miles away, not to mention 12 time zones away? How will you work with your mentor to track your work? Have you worked in this style before?
  • If your native language is not English, are you comfortable working closely with a supervisor whose native language is English? What is your native language, as that may help us find a mentor who has the same native language?
  • Where do you live, and can we assign a mentor who is local to you so you can meet in a coffee shop for lunch?

What criteria did you use to select your mentors for this year's program? Please be as specific as possible.

Mentors are generally leaders of existing Clojure community projects that have been involved in the development of the programming language more than three years. These community leaders have shown a dedication and level of involvement that is simple to verify.

What is your plan for dealing with disappearing students?

The most critical aspect is of course preventing such a scenario entirely. This needs to happen at the level of the selection of the proposal, the selection of the mentor, and the selection of student. A proposal of proper scope, a dedicated mentor, and a student with a visible history of seeing projects to their end is critical to success. Also critical is observing their involvement in the community up to the student selection process. Finally a proper interview is probably required in order to find out whether the mentor/student pairing is ideal and whether the student will be free of time conflicts during the GSoC time period to see their project to completion.

What is your plan for dealing with disappearing mentors?

Most projects will have a backup mentor. Even so, the mentors are selected from the community precisely for their history of involvement in the proposal.

What steps will you take to encourage students to interact with your project's community before, during and after the program?

It will be made clear that community involvement prior to selection will be strong factor for being considered for a proposal. We believe that open source contribution is not a summer time affair. Students should be talking with mentors from the start in order to amass the adequate material required to tackle the proposal. This may include showing familiarity with an API, submitting patches, and reading papers.

Are you a new organization who has a Googler or other organization to vouch for you? If so, please list their name(s) here.

Labels: