Google Summer of Code

Discussions for core devs and contributors. Read only for normal forum members to keep the noise low

Google Summer of Code

Postby mzechner » Mon Mar 11, 2013 10:17 am

So, we've setup a wiki page for GSoC, ... OfCode2013

We have a few ideas listed, we have interest from the community. What's lacking is a commitment of core developers to be mentors, the application text for our organization, and the application template for students.

I'd have to do #2 and #3 this week, application for organizations starts on the 18th of march. I won't waste time during my "break" week, if there's no interest, or if we think we aren't ready for GSoC yet.

Let me know what you think until wednesday.
Site Admin
Posts: 4879
Joined: Sat Jul 10, 2010 3:50 pm

Re: Google Summer of Code - should we do it?

Postby BurningHand » Mon Mar 11, 2013 11:40 pm

I'd love to give it a shot, and can commit to making myself available for maybe 5-10 hours a week. Not sure how much time is necessary, but if that's sufficient, great.
IRC: nexsoftware / mobidevelop; GitHub: MobiDevelop;
Posts: 2812
Joined: Mon Oct 25, 2010 4:35 am

Re: Google Summer of Code - should we do it?

Postby bitiotic » Tue Mar 12, 2013 6:43 pm

While GSoC is a great project, I can't really commit to being a mentor. I'm happy to help out when I can, but I can't make the necessary commitment to it for the whole summer. Sorry!
Posts: 81
Joined: Tue Feb 05, 2013 2:59 pm

Re: Google Summer of Code - should we do it?

Postby xoppa » Tue Mar 12, 2013 7:33 pm

I agree with BurningHand. From what I read, being a mentor isn't that much of an impact in matter of time. So I can commit for that, but it would be nice to have a confirmation of the estimated amount of time required.
Posts: 689
Joined: Thu Aug 23, 2012 11:27 pm

Re: Google Summer of Code - should we do it?

Postby mzechner » Tue Mar 12, 2013 11:03 pm

Nex' estimate is probably close to reality. I suggest everyone read the GSoc mentor guide linked to on the GSoC wiki page.

We have 5 more days, i'll wait for more feedback from core devs. I'll prepare the application on saturday, so please reserve 15 minutes to read it and give feedback on sunday if possible. I want the application to be send out asap.
Site Admin
Posts: 4879
Joined: Sat Jul 10, 2010 3:50 pm

Re: Google Summer of Code - should we do it?

Postby mzechner » Sat Mar 16, 2013 10:07 pm

I updated the gsoc site: ... OfCode2013

And i also update the student application template: ... pplication

Anyone who wants to be a mentor should:

- say so here (counting nex and xoppa so far)
- add them to the ideas on the wiki page above, irc nick suffices
- send me an e-mail with full contact info, we have to pass that on to the Google. Full contact info includes your full name, e-mail, maybe phone and address.

If you have more ideas, put them on the wiki!

[b]I aim at sending the organization application on wednesday next week. So please respond in a timely manner![/]

Site Admin
Posts: 4879
Joined: Sat Jul 10, 2010 3:50 pm

Re: Google Summer of Code - should we do it?

Postby noblemaster » Mon Mar 18, 2013 5:39 am

Hi Mario, count me in too! I noted my name is already in the list, so I guess I am just here to confirm :P

My time is somewhat limited like everyone else's, but I'll try my best. Definitely the IAP system/iOS backend are fine with me. Also on a side note, it appears Apple has tightened its rules for LITE apps, so it's now not legal anymore to link to your full version that directly (you can, but it got limited). It's going to be "IAP or die" for iOS soon! :lol:

PS: I emailed you my contact info too. Please check if you received it. Last time it bounced back!?
Posts: 122
Joined: Thu Dec 09, 2010 6:49 pm
Location: Tokyo, Japan

Re: Google Summer of Code - should we do it?

Postby mzechner » Mon Mar 18, 2013 8:25 pm

Cool, we now have Bach, Xoppa, nex, Noblemaster, Nate and myself as mentors. Arielsan, Ruben and are undecided yet. I haven't heard form Davedes yet, would love to have him on board. Tamas also said he'd want to help. I think we have a strong setup here.
Site Admin
Posts: 4879
Joined: Sat Jul 10, 2010 3:50 pm

Re: Google Summer of Code - should we do it?

Postby mzechner » Mon Mar 18, 2013 9:31 pm

Here's our entire application form so far, feedback welcome:

Code: Select all
--- 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 [1], Android [2], iOS [3], Facebook [4] and HTML/WebGL [5]. 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 [6], and is used by thousands of developers to create the games of their dreams. From entries for the 48 hour Ludum Dare challenge [7], to top grossing mobile games [8] to augmented reality experiments like Google's Ingress [9].
Libgdx has achieved wide adoption, especially on Android where it is powering 3.2% of all installed applications [10], 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.
[Personal Motivation]
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. [1]
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.
Site Admin
Posts: 4879
Joined: Sat Jul 10, 2010 3:50 pm

Re: Google Summer of Code - should we do it?

Postby mzechner » Mon Mar 18, 2013 9:48 pm

Hey, we should maybe do something like this as well:

Site Admin
Posts: 4879
Joined: Sat Jul 10, 2010 3:50 pm


Return to Libgdx Development

Who is online

Users browsing this forum: No registered users and 1 guest