Revision 8 as of 2012-02-18 21:42:06

Clear message


  1. Announce:

  2. Timeline:


FAQ entry about mentoring organisation application:

The questions below need to be filled out:

  1. Describe your organization.
  2. Why is your organization applying to participate in Google Summer of Code 2012? What do you hope to gain by participating?
  3. Did your organization participate in past Google Summer of Codes? If so, please summarize your involvement and the successes and challenges of your participation.
  4. If your organization has not previously participated in Google Summer of Code, have you applied in the past? If so, for what year(s)?
  5. What Open Source Initiative approved license(s) does your project use?
  6. What is the URL for your Ideas page?
  7. What is the main development mailing list for your organization?
  8. What is the main IRC channel for your organization?
    • freenode #ubuntu-devel
  9. Does your organization have an application template you would like to see students use? If so, please provide it now.
  10. Who will be your backup organization administrator?
  11. What criteria did you use to select your mentors for this year's program? Please be as specific as possible.
  12. What is your plan for dealing with disappearing students?
    • We will try once weekly for the duration of the summer period to contact the student.
  13. What is your plan for dealing with disappearing mentors?
    • If a student reports a mentor as unresponsive, we will ask the Ubuntu community to select someone to take the mentor's role.
  14. What steps will you take to encourage students to interact with your project's community before, during and after the program?
  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.
  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.

Project ideas

  • Improving Harvest
    • DanielHolbach

    • Harvest should be the number-one to-go place to find out what needs to be done in Ubuntu. A few things make this still a bit hard. One is searches and being able to bookmark them, the generated URLs are a bit problematic right now. This and some general cleanup would be a great project, Django and Javascript knowledge are important.

  • Implement syslog namespace
    • SergeHallyn

    • Containers share the host's syslog, and so can read, write, and clear them. A syslog namespace should prevent the container from accessing or clearing kernel messages. Userspace-generated messages should go to the container's own syslog. Ideally, a new ns_printk() kernel function should be provided to target certain kernel-generated messages (like iptables messages).

  • Improved multiple devpts mounts support
    • SergeHallyn

    • The current devpts mounts support is insufficient. Linus has proposed a very simple solution - make all devpts mounts newinstances. To do this requires some work both in kernel and userspace.

  • Implement cgroup fake root
    • SergeHallyn

    • Ideally, when a container mounted cgroups, it would see a namespaced view where the cgroup of the container's init was shown as the root ('/') cgroup. See for previous post and discussion.

  • Communtu appliance system and library
    • TorstenFranz and Till Mossakowski

    • Current Communtu LiveCDs are based on the Ubuntu Desktop edition. Appliances (like a LAMP, Joomla or Wikimedia installation) will by based on Ubuntu Server edition. An appliance library will store LiveCDs, DVDs and virtual machines, with discussion and support. Note that the CD for the server edition is technically very different from the CD for desktop edition. Required skills: ruby on rails; bash; Ubuntu internals

  • Dialogue system in Communtu
    • TorstenFranz and Till Mossakowski

    • The modern way of installing your computer should not be via endless googling and asking your friends what software you need, but through a dialogue system that asks you some questions about your needs, and based on that, makes suggestions for suitable software (which then can be bundled to a LiveCD or virtual machine using the other parts of Communtu). We have some existing linguistic ontology and some dialogue framework in mind that could be used, but are not commited to this. Required skills: ontologies; a bit of linguistics; AI; a bit of ruby on rails (where the latter could also be learned during the project)

  • Improving Clicompanion
    • Marek Bardoński

    • Clicompanion is a tool to store and run Terminal commands from a GUI. People unfamiliar with the Terminal will find CLI Companion a useful way to become acquainted with the Terminal and unlock its potential. Required skills: none (Learning basics of python is a goal of this project)

  • Expanding tasks in Algorithm School
    • Marek Bardoński

    • as This program is designed for novice programmers, who want to test and improve their skills. Currently we have only about 30 tasks for training. We need to expand tasks database, and add additional functions for program. Optional desired skills: QT, C++