This is a page intended for brainstorming and outlining useful improvements to Debian as a whole, parts of its infrastructure, its packaging system, etc. If the description of the specific feature gets long, please create a new page and link to it instead and just keep the short description on this page (consider [wiki:HelpOnEditing/SubPages ?SubPages]). You might want to list "dependencies" and potential returns that this feature would provide. It would also be interesting to differentiate the low hanging fruits from the ones that require more work, so -- if you can -- you might want to add a tag like "big effort", "quick", "long term" or a timeframe you think might be appropriate. If you know people interested in working on this, even that could be useful to add.

A possible example might be Multiarch:


Multiarch directories

Using architecture, kernel and libc/abi specific directories to store libraries and plugins (e.g. /usr/lib/i486-linux-gnu). This way libraries and plugins using glibc and uclibc can be stored on the same system or kfreebsd and linux (since bsd can run them too), or mips and mips64, ....


Multiarch

Integrating mulitiple different binary architectures (e.g. i386 and amd64) in the same filesystem in a transparent way.


More Debtags support

[http://debtags.alioth.debian.org Debtags] is getting mature, and there are now working prototypes of [http://debtags.alioth.debian.org/ssearch.html smart search and navigation interfaces]. The algorithms are easy. Synaptic and Aptitude should benefit. Mail Enrico for instructions and help.


Faster Boot

Reducing boot and shutdown time, dependency/event based init scripts


Debian Desktop

The [http://www.debian.org/devel/debian-desktop Debian Desktop] subproject is composed now by members of pkg-gnome, pkg-kde, pkg-xfce and others. It has a common project and svn repository (debian-desktop) in alioth. Debian Desktop has input on desktop and laptop tasks package selection (tasksel project) and is working on common artwork as we speak (desktop-base package).

Single Sign On / Adaptability

We should make it as easy as possible to introduce a new service or a computer in the network, with full access to printers, files etc. There are a lot of different LDAP chemas and mechanisms to give users access to different system services as sound, direcotries etc. This leads to difficulties to access standard system resources when upgradring the system or integrating a new PC to the network. One example is handing [http://lists.debian.org/debian-devel/2006/10/msg00752.html device permissions] that removes sound support when upgrading from Debian Sarge to Etch. An other example is to integrate a Ubuntu-based or a Windows laptop on a Skolelinux network.

To improve the features that support this enterprise desktop requirement by harmonising directory settings and working on support for single sign on technology in relevant technology such as [http://docs.kde.org/stable/en/kdeutils/kwallet/index.html KWallet] and [http://ftp.acc.umu.se/pub/GNOME/sources/gnome-keyring/ GNOME Keyring].


Desktop Accessability

Accessibility is mandatory property for computer systems in private companies and public sector. Blind persons will prefer a text based interface reading the "screen" on a screen reader. Different projects has targeted accessibility that makes it easy for disabled people to use a computer system. As a part of The Portland Project (managed by OSDL) they are migrating the desktop messaging systems to D-BUS to enable cross-desktop interaction. Then KDE and GNOME got an outdated accessibility support. Both GNOME and KDE developers work together enabeling accessibility. The support should also be easy to install and use on a Debian based system. Since Debian is one of the major distributions in schools, we could be left out from public tenders if the accessability support lacks.

http://www.osdl.org/lab_activities/desktop_linux


Development Environment (out of the box)

Developer tool readiness student projects and free software developers programming end user applications in C++ or some other language. It often takes a day or two to configure a developer environment when installing a Debian system. Even if the tools are easy to install with apt-get, some additional configurations has to be done. Then people need 1-2 full days to configure the tools.

One Laptop per Child support

The One Laptop per Child project are targeting millions of pupils in development countries. The prototype runs a light weight destkop with full support for video streams and Internet. Memory footprint on the OLPC-device is 128 MB RAM and 512 MB HardDisk on flashRAM. Then programs as OpenOffice.org and other "fat" software is out of the question.

dpkg2

dpkg needs a rewrite and extensions


Translation Debs

Special packages that are language oriented. Each package has its own set of complementary .tdebs, one per each language. This feature was discussed at length during [wiki:I18n/Extremadura2006 the I18N meeting in Extremaduara] (Sept. 2006)

All localization information is split from the debs, allowing the binary packages to reduce their sizes to the minimum. The users get only the localization material (.mo files, localized sounds and images etc.) that they choose via specific settings, making [http://packages.debian.org/localepurge localepurge] obsolete.

This feature would be beneficial to:

Overview:


Less spammable addresses in Debian

It should be fairly trivial to list in the web interface of BTS and Debian mailing lists non-spammable email addresses instead of the legal ones.