Differences between revisions 12 and 13
Revision 12 as of 2014-02-07 16:32:07
Size: 7486
Comment: switching to ProjectsNew, which come with page inclusion
Revision 13 as of 2014-02-07 16:33:10
Size: 2330
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
'''OLD PAGE, DON'T USE'''

'''PLEASE USE [[SummerOfCode2014/Projects]] INSTEAD'''

Line 28: Line 33:
--------
== Debian based on clang ==

'''Description of the project:''' During the last couple years, important efforts have been produced to [[http://clang.debian.net|build Debian with Clang]] instead of gcc. Clang is now ''features completed'' and compiles most of the archive. However, clang being stricter than gcc, it rejects a lot of packages.

The goal of this project is to patch all packages failing to build with clang. Forwarding to upstream the patches will be part of the project.

To have an idea of the common errors, see [[http://clang.debian.net]]

 * '''Confirmed Mentor''': Sylvestre Ledru
 * '''How to contact the mentor:''' sylvestre@debian.org
 * '''Deliverables of the project''': A repository of all Debian packages built with clang.
 * '''Desirable skills''': Patching upstream code, good understanding of C and C++, etc
 * '''What the student will learn:''' Impact on the whole distribution, common C/C++ mistakes, compiler issues, etc
Line 44: Line 35:
== libc++-based Debian ==
Line 46: Line 36:
'''Description of the project:''' In the context of LLVM project, a new C++ standard library called [[http://libcxx.llvm.org/|libc++]] has been developed and maintained. This package is already [[http://packages.qa.debian.org/libc/libc++.html|in Debian]]. The main goal is rebuild Debian using libc++ as C++ runtime.
Note that the libstdc++ and libc++ are not ABI-compatible.

This project will take advantages of the [[https://alioth.debian.org/projects/pkg-debile/|debile infrastructure]].


 * '''Confirmed Mentor''': Sylvestre Ledru
 * '''How to contact the mentor:''' sylvestre@debian.org
 * '''Deliverables of the project''': A repository of Debian packages running with libc++
 * '''Desirable skills''': Packaging (especially of libraries), strong understanding of API/ABI compatibility
 * '''What the student will learn:''' Impact on the whole distribution, library management, compilations, etc


--------
== Archive built with asan ==

'''Description of the project:''' In the context of Clang project, [[http://clang.llvm.org/docs/AddressSanitizer.html|ASAN]], Address Sanitizer is a fast memory error detector. It consists of a compiler instrumentation module and a run-time library. It will compile any code which built with gcc or clang and insert a static library in the binary.

This library will automatically check some common memory errors. Example: [[http://sylvestre.ledru.info/blog/2013/01/12/some_more_cool_stuff_with_llvm_clang|More information]]

This project will take advantages of the [[https://alioth.debian.org/projects/pkg-debile/|debile infrastructure]].



 * '''Confirmed Mentor''': Sylvestre Ledru
 * '''How to contact the mentor:''' sylvestre@debian.org
 * '''Deliverables of the project''': A repository of Debian packages built with ASAN
 * '''Desirable skills''': Packaging (especially of libraries), building packages
 * '''What the student will learn:''' Strong improvement of the quality and error detection

--------
== Provide some metrics in Debile ==

'''Description of the project:''' Because everybody loves meaningless stats, the goal of this project is to extend the [[https://alioth.debian.org/projects/pkg-debile/|debile infrastructure]] to provide some metrics on the packages. For example, build time, size of the binaries, etc.

This projets would also extend to propose graphics over time (number of failure, number of errors/warnings detected, etc).

Graphics should be provided using the [[http://d3js.org/|d3js]] or [[http://www.elasticsearch.org/overview/kibana/|Kibana]] library

 * '''Confirmed Mentor''': Sylvestre Ledru
 * '''How to contact the mentor:''' sylvestre@debian.org
 * '''Deliverables of the project''': A debile version with plenty of stats and graphics
 * '''Desirable skills''': Some knowledge of packaging, javascript, database, etc
 * '''What the student will learn:''' plenty of things relative to packages, build, etc

--------
Line 95: Line 39:
--------

== Package elementary software ==

'''Package elementary's Pantheon shell, GUI framework (Granite), applications, icon theme, and gtk theme.''' [[http://elementaryos.org|elementary]] is a project devoted to delivering a great user experience on the desktop computer. elementary's main product is elementary OS, which is currently Ubuntu based (although the developers are looking towards a Debian base in the future). Packaging this set of software in Debian will offer another great choice of desktop environments for Debian's many desktop computer users, as well as supplement current DE's offerings. Furthermore, a pure spin of Debian that uses elementary's suite of software by default will be much easier to implement.

 * '''Deliverables of the project''': elementary's shell and apps installable with near complete functionality through Debian's repositories.
 * '''Desirable skills''': Some experience with [[https://wiki.gnome.org/Projects/Vala/|Vala]], a similar object oriented programming language (such as Java or C#), or C with GObject. Some knowledge of debian packaging.
 * '''What the student will learn:''' The student will learn how a large project is interconnected, and he or she will broaden Debian's repositories with new, exciting software.

OLD PAGE, DON'T USE

PLEASE USE SummerOfCode2014/Projects INSTEAD

The main page is at SummerOfCode2014 and OutreachProgramForWomen. (Depending on your program)

Project template

All the project descriptions 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.


Projects with confirmed mentors

Please keep this section clear of project ideas without confirmed mentors, to avoid any confusion for prospective students. Such projects should be published in the next section.


Projects ideas without confirmed mentors

Please find mentors for those projects. If no confirmed mentor shows up before the student application period starts, the project will not happen.