This page provides a workspace where we can prepare our application. Here's a link to our application from last year: Google Summer of Code 2012 Application Questions
Clojure/dev, as a GSoC mentoring organization, includes projects from all parts of the Clojure ecosystem, from IDE tooling to logic programming libraries.
Home page URL: http://clojure.org
Main License: Eclipse Public License
Backup Admin: dnolen
Last year was our first year as GSoC mentoring organization. We had four students, who all passed. I think the most important success from our participation from last year is the work that was completed by our students which has gone on to be further developed (such as Typed Clojure and the ClojureScript improvements from Clojure/Lua) or used by people to do real work (like Clojure/Android). We believe that our students have helped to grow the Clojure community in addition to their software contributions.
Despite the successes from last year, there is still plenty of room for improvement. We think it is important that people know about our student's work, so we will plan on making it easier for the community to keep up to date about our student's progress. Additionally, we will ensure that students publish short updates about their work for the community. We also ran into some difficulties with one of our student/mentor pairings, so we will try to avoid some of these problems by ensuring every project has a couple of mentors.
The Clojure community has been growing at a healthy rate since the initial language announcement in 2007. The Clojure mailing list now has over 7500 subscribers, the Freenode IRC channel sees greater than 400 participants, and there were three conferences scheduled last year dedicated to Clojure. At these conferences, the question is no longer ‘Do you get to use Clojure at work?’ but ‘Are you using Clojure in production?’ All of this activity means many open source initiatives in the community need help, from projects for development of web and mobile applications using ClojureScript to advanced creative authoring environments like Overtone. This coupled with evident interest from students and mentors on the mailing list has encouraged us to apply again for GSoC 2013.
Project Ideas 2013
clojure on Google Groups
#clojure on Freenode
We select mentors based on their prior participation in the Clojure community. A mentor for a given student project will usually be a lead developer for an existing open source project related to the student's project. This will help ensure the mentor has both an interest in success of the GSoC project as well as the necessary expertise to be an effective mentor.
Our mentors are generally leaders within Clojure community who 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.
The most critical aspect is of course preventing such a scenario entirely. This needs to happen at 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 prior to the student selection process. We prefer students who have already started developing a working relationship with their mentor and interacting with the community. 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.
Ideally, all projects will have at least one backup mentor. Even so, mentors are selected from the community precisely for their history of involvement in the community and the issues surrounding proposal.
We will be clear that community involvement prior to selection will be a strong factor for being considered for a proposal. Our experience last year taught us that those students with the strongest community/mentor involvement before the program performed the best. We believe that open source contribution is not solely a summer time affair. Students should be talking with mentors from the start in order to develop the adequate understanding and material required to tackle the proposal. This may include, but is not limited to, showing familiarity with an API, submitting patches, and reading papers and discussing them with mentors. We believe that a well considered proposal/mentor/student combination reinforces student engagement during the GSoC period.
We will strongly encourage students to provide updates to the community at large about the work they are doing on a weekly or semimonthly basis. To increase the effectiveness of this, we will make it easy for the community to be able to follow our students' progress. Last year, a number of students were interviewed in community electronic publications, and we would like to encourage that once more.
Most of the proposal are significant enough that students should feel a sense of ownership about their accomplishment. At the same time, the proposals are significant enough to the Clojure community that community members can provide support once the intensive GSoC period is done and the student must focus more time on academic responsibilities. We will encourage students to submit talks about their work to community conferences, and we will take the opportunity to use GSoC's travel stipend to get our students to conferences.
Type answer here
Type answer here