User Tools

Site Tools


events:gsoc2013-application

This is an old revision of the document!


Google Sommer of Code 2013

This document is work in progress and has to be finalized by March 21st, 2013. Please contribute!

Administrators

  • Heinz-Markus Graesing (IRC: h1mg, Mail: heinz-m.graesing@obviously-nice.de)
  • Backup: Mike Gabriel (IRC: sunweaver, Mail: sunweaver@debian.org, Debian Developer)

Mentors

People available for mentoring are:

  • Mike Gabriel (IRC: sunweaver, Mail: sunweaver@debian.org, Debian Developer)
  • Moritz Strübe (IRC: morty, University of Erlangen-Nuremberg)
  • Heinz-Markus Graesing (IRC: h1mg, X2Go Project founder, backup mentor)
  • Reinhard Tartler (IRC: siretart, Mail: siretart@debian.org, Debian Developer, backup mentor)

X2Go Application for GSOC2013 (Draft)

  1. Describe your organization.
    • The X2Go project is currently mainly driven by three commercial companies, namely
    • and supported by
      • the Department of Computer Science 4 at the Friedrich-Alexander University, Erlangen-Nuremberg, Germany
      • the Department of Computer Science at Christian-Albrechts-University, Kiel, Germany
      • Fleten.net DK (Kjetil Fleten, CEO; Canonical Partner)
      • Lindix NL (Dick Kniep, CEO)
  2. Why is your organization applying to participate in Google Summer of Code 2013? What do you hope to gain by participating?
    • Our current interest is getting X2Go more known internationally and getting more and more people involved
    • Some of the coding projects we offer to GSOC2013 students are features targetting for company setups
    • Thus, our intent is making X2Go usable in business context and large scale deployments
    • Get focused the new markets and support new devices like Chromebooks, hybrid tablets and other typical “Bring Your Own Device” Hardware
    • Making it easier to access remote desktop applications targeting companies offering software as a service
  3. Has your organization participated in past Google Summer of Codes? (yes/no)
    • NO
  4. If you answered “yes” to the question above, please summarize your involvement and the successes and challenges of your participation. Please also list your pass/fail rate for each year.
    • (does not apply, as we answered NO above)
  5. If your organization has not previously participated in Google Summer of Code, have you applied in the past? If so, for what year(s)?
    • NO, we have not yet applied.
  6. What Open Source Initiative approved license(s) does your project use?
    • mostly GPL-2+ and AGPL-3+
  7. What is the URL for your Ideas list?
  8. What is the main development mailing list for your organization?
  9. What is the main IRC channel for your organization?
    • Channel #x2go on irc.freenode.net
  10. Who will be your backup organization administrator?
    • Mike Gabriel (IRC: sunweaver, Mail: sunweaver@debian.org, Debian Developer)
  11. What criteria did you use to select the mentors? Please be as specific as possible.
    • All selected mentors are active project supporters with lots of experience
    • All selected mentors are subscribed on our development list for more than 3 years
    • All selected mentors are supporting the projects target values
    • Mike Gabriel
    • Moritz (Morty) Strübe
    • Heinz-Markus Graesing (backup mentor)
    • Reinhard Tartler (backup mentor)
    • FIXME: if there are more mentors, update this field
  12. What is your plan for dealing with disappearing students? Please be as specific as possible.
    • To avoid students disappearing at all we will request a detailed time schedule and weekly reports.
      • The schedule will require the student to put some thought into whether he/she has sufficient time for the job.
      • The weekly report tries to countermeasure that a student slowly disappears.
    • To get a feeling for his/her progress, our project will be used as shared desktop and base for presentations
    • If possible we will try to schedule a chat with the mentor at least twice a week.
    • There will be a personal (video chat) interview with one of the mentors before the student applies
    • We will also have a close look at the student's backgound, whether she/he is capable of managing the task. For this the Department of Computer Science 4 will provide its experience in supervising students.
  13. What is your plan for dealing with disappearing mentors? Please be as specific as possible.
    • All mentors have a professional interest that the project makes progress.
    • If a mentor disappears one of the other mentors will take over.
  14. What steps will you take to encourage students to interact with your project's community before, during and after the program?
    • Contacting the community means contacting possible employer in future
    • Use Cases, feature requests and further needs of x2go are discussed inside our community
    • FIXME (Morty!) Students already interacting with the project and those who have a personal interest in the project.
  15. Are you a new organization who has a Googler or other organization to vouch for you? If so, please list their name(s) here.
    • NO
  16. Are you an established or larger organization who would like to vouch for a new organization applying this year? If so, please list their name(s) here.
    • NO
  17. What will you do to encourage that your accepted students stick with the project after Google Summer of Code concludes?
    • First, we hope to provide a team space where people feel at home
    • Then, we offer peole who are more deeply interested in X2Go to take over responsibility in the project
    • As the project has two Debian Developers on board, more knowledge and community insights are available to newcomers
events/gsoc2013-application.1364421516.txt.gz · Last modified: 2013/03/27 21:58 by sunweaver