In my opinion the main problem of Debian is it doesn't have a formal way to create a way for a group of developers and users to communicate about specific wide reaching issues within the Debian community.

There are thousands of DD, most of them working on packages, some on infrastructure or QA, but basically everyone works solo.

In my point of view this does not scale well because of the following reasons:

These points are the reason why I think that Debian should slightly change the current structure. Therefore I propose a set of groups:

My proposal is different from the already existing Debian subprojects since these are based on application type (only for kids, for architecture xy, for servers, the desktop, whatever). My solution would be problem-based (working groups).

The starting point for such a working group would be debian-devel. As soon as a problem pops up which is of interest for many of the debian developers (such as the problem which programs should be included into Debian, cf the hot-babes thread, or a slow release cycle, or too much spam on the mailing lists, etc).

Working on a separate mailing list has the advantage that one could get to know the other group members, learning to appreciate their opinion. The group would present the solutions found to the Debian community through the debian-devel mailing list, so this list would still be the starting and the end point for problems.

As soon as a consensus is found and the solution is integrated into the Debian infrastructure the working group can be dissolved if it is a one time issue. -- What Thomas (Debian user) is really trying to say --MikeFedyk.



For some discussion see DebianNotHierarchicalEnough

Back to ReleaseProposals