--- Organization description
Libgdx is a cross-platform game development framework. You write your game in Java, and have it working instantly on Windows, Linux, Mac, Steam , Android , iOS , Facebook  and HTML/WebGL . The entire Java code base is shared across all these platforms.
Libgdx was born 3 years ago, out of a desire to target multiple platforms with a single code base. It has since grown into a big OSS project with over 100 professional and amateur contributors , and is used by thousands of developers to create the games of their dreams. From entries for the 48 hour Ludum Dare challenge , to top grossing mobile games  to augmented reality experiments like Google's Ingress .
Libgdx has achieved wide adoption, especially on Android where it is powering 3.2% of all installed applications , with numerous top-grossing games.
Our community as well as the entire libgdx development team are looking forward to welcome Google Summer of Code students among us. We hope students will enjoy the learning experience while contributing to a framework that powers thousands of games that bring joy to millions of users!
--- Why is your organization applying to participate in Google Summer of Code 2013? What do you hope to gain by participating?*
We believe that Google Summer of Code is beneficial both for our project as well as for participating students. We describe possible benefits for students on our idea list.
[Exploring New Features]
We have seen tremendous growth in both our user base as well as in the number of contributors over the last year. As such we feel that we have a bigger responsibility when it comes to stability of the framework. Time is the most valuable resource across the development team, and we favor improving the existing code base over adding new features.
By participating in Google Summer of Code, we hope to be able to gain some fresh blood that can explore features we'd love to implement but currently have no time doing so.
[Feedback on API Design]
While we assume that many students applying for our project have had previous experience with libgdx, we are also trying to get some feedback on the frameworks API design from newcomers. On top of the status reports we'll gather, the mentors, which are all core contributors, will also look out for any difficulties students had when exploring and using the existing APIs.
It is our hope that we can improve the design and documentation of the library by getting this first hand feedback through Google Summer of Code.
Many of our mentors had previous teaching experience, be it in class, workshops or by writing books.
Accordingly, we are eager to mentor motivated students and hope that through Google Summer of Code we can combine teaching with our work on libgdx.
--- What criteria did you use to select your mentors for this year's program? Please be as specific as possible.
Mentors where selected based on three aspects.
We only allow core developers to be mentors for our first Google Summer of Code. A core developer is
1) Participating on the forums, IRC and code reviews on Github
2) Contributing on a weekly or even daily basis
3) Can work on any part of the code base
This attributes guarantee that the mentor has knowledge not only about the technical aspects of the projects, but can also be a guide to introduce students to the community and its behaviour as well as the overall distributed workflow.
Potential mentors were briefed on their responsibilities and where given time to decide whether they can commit to the position. About half of the potential mentors declined. The rest of the mentors are committed to put in the required resources. We also made sure that we can allocate at least one backup mentor for every project idea, not including ideas students have come up with themselves.
While verbal and written commitments exist, mentors and administrators must trust each other to do their part. Our mentor team is composed of individuals who have worked with each other over the years and hence have trust that this experience extends to the Google Summer of Code program.
--- What is your plan for dealing with disappearing students?
Students are supposed to report on their progress twice a week, by keeping a log on the forums as well as sending e-mails to their mentor and backup mentors.
Should a student fail to do so for a week, we'll use the information we ask for in our student proposal template (phone number, e-mail address, IM info) to directly contact the student. We give the student 3 days to respond, after which we'll alert the Google Summer of Code organizers. Unless the student can provide a good reason for his absence, we'll fail her.
--- What is your plan for dealing with disappearing mentors?
If a mentor is reported missing by either a student or by other mentors and admins, we'll try to contact him through his personal contact information (phone number, e-mail address, IM info). While we try to reach the mentor, the backup mentor picks up the mentoring task immediately, synching up with the student as soon as possible if necessary. If the mentor does not respond, the student will be mentored by the backup mentor for the rest of the Google Summer of Code. We'll also try to allocate another backup mentor.
--- What steps will you take to encourage students to interact with your project's community before and during the program?
We have already been reaching out to potential students via our blog, Twitter, on IRC and the forums, with quite a few responses. 
Participation in the community (registering on the forums, introducing yourself on the forum and IRC, interaction with potential mentors, sending a pull request on Github) are requirements for our student applications.
During the program, students will have to report on their progress publically on our forums, which means core developers as well as other members of the community can interact with the student, giving feedback and encouragement.
Interaction with other core developers will be had on Github, where pull requests will be reviewed and discussed.
--- What will you do to encourage that your accepted students stick with the project after Google Summer of Code concludes?*
We believe that a student has to conclude herself that the project is worth her sparetime. As such, we will try to provide fun challenges, a friendly and satisfying environment to work in, and the oportunity to make new friends all around the globe. We strongly believe that the libgdx project can offer all three of these things.
--- Are you a new organization who has a Googler or other organization to vouch for you? If so, please list their name(s) here.
We've been giving some support to parts of the Catrobat team for their Android app Catdroid over the years. They are using libgdx within Catroid. Professor Wolfgang Slany (project lead) and Sercan Akpolat (GSoC admin this year) are vouching for us this year.
Our friend, contributor and Google employee Talin also puts his vote in for us. He's reachable through xxxx FIXME Talin's Family name.
Users browsing this forum: No registered users and 1 guest