Drupal community processes

Moderator: Robert Douglass

The way Drupal is developed and evolves is highly influenced by the technical details of our infrastructure. From the issue queue to CVS to the mailing lists, the technological tools that we implement and use shape the way people contribute to Drupal.

Many proposals have been put forth for improving the cooperation between developers, the efficiency of the patch queue, and people's ability to find support on Drupal.org. This session will discuss one or more of these suggestions, analyse the technical requirements to support them, and explore a battle plan for implementation.

• Drupal Enhancement Proposals (DEPs) to foster coordination on large-scale projects, to build consensus on important ideas, and to better convey a sense of direction in development to the interested public, Adrian Rossouw has proposed that Drupal adopt a formalized procedure for handling new ideas.
  Modelled on the JEP system used by Jabber: http://www.jabber.org/jeps/jep-0143.html
• Project module, CVS module, Issue queue Many good ideas have been put forth on how to improve issue tracking at Drupal.org. These ideas must be put into code before they can benefit anyone, yet few people use or understand the Project or CVS modules, the existing code responsible for code and issue tracking at Drupal.org. How do we make these modules, central to the past and future success of Drupal, become more accessible to others so that the pace of development on them can increase?

Please contact me with suggestions concerning this session.