Differences between revisions 16 and 17
Revision 16 as of 2012-02-14 13:57:14
Size: 2713
Editor: ?Sylvestre Ledru
Comment:
Revision 17 as of 2012-02-14 14:07:31
Size: 2850
Editor: PaulWise
Comment: some rough ideas
Deletions are marked like this. Additions are marked like this.
Line 21: Line 21:
Line 32: Line 31:
Add your project here :)
Line 33: Line 33:
Add your project here :) Rough short ideas:

 * adding distromatch metadata to Debian infrastructure (PTS/packages/etc)
 * BTS: optimisation, RW API, RW web ui

The main page is at SummerOfCode2012. This page contains the available projects, all the the projects should follow the following template:


Title of the project

  • Description of the project: At least 8-10 lines describing what the project is about; it is really important to have a good description if you want to attract students who are interested by the idea. This does not need to be a very technical description, but something that stirs interest and is complete enough to allow a student to judge whether s/he wants to work on the particular project or not. It does not need to be a complete road map either and does not need to explain all the tiny details and whatnot -- the mentor can tell that to interested students, or they can work out the exact details together.

  • Confirmed Mentor: Name of the mentor

  • How to contact the mentor: (mail, IRC, etc)

  • Confirmed co-mentors: It is not compulsory to have co-mentors, but it is a good idea. Secondary mentors do not need to be as knowledgeable as the first one in the project, but they should be available to help the student if s/he is stuck and the main mentor is busy / not available.

  • Deliverables of the project:

  • Desirable skills: Skills that the student has or is willing to develop. Remember, the students do not have as much experience as the mentor.

  • What the student will learn: At least 2-3 lines telling the students the skills they develop and how they will improve Debian. Do not focus on the technologies rather use something that could motivate the prospective student to take your project.


clang support for build services

  • Description of the project: The idea of this project is to extend the Debian infrastructure to be able to build packages with clang instead of gcc/g++. clang has some advantages over gcc/g++ like better error messages, better warnings. Even if the short/mid term goal is not to replace gcc/g++, building packages with two compilers improves the detection of C/C++ or Objective C errors.

  • Confirmed Mentor: Sylvestre Ledru

  • How to contact the mentor: sylvestre@debian.org

  • Deliverables of the project: Build services with clang instead of gcc/g++. Integration in the Debian infrastructure. A clang based install of Debian (if time)

  • Desirable skills: Packaging, chroots and a bit of knowledge on the Debian infrastructure.

  • What the student will learn: How to use clang, how to package it, how the Debian build infrastructure works

Add your project here :)

Rough short ideas:

  • adding distromatch metadata to Debian infrastructure (PTS/packages/etc)
  • BTS: optimisation, RW API, RW web ui