This recently happened with the themesettings project, actually, although the project author had taken the time to talk with me separately about it prior to project creation. The way to go suggested at the time, IIRC, was to announce any module project intent on this (archived) mailing list prior to project creation, so that any interested party could chime in. Another solution might be to add an issue category to the project tracker, like: - adding a "Future contributions" category - adding several "ideas" subcategories: - "project idea" - "theme idea" - "translation idea" - "profile idea" These could be closed just like other issues when the project was created. Maybe we could even require the project creation form to include a mandatory issue nid pointing to such an issue. This would allow persistence, traceability, and searchability. What do you think of it ? FGM ---- Original Message ---- From: darthsteven@gmail.com To: development@drupal.org Subject: Re: [development] New Module Ideas and Announcements Date: Tue, 7 Aug 2007 10:10:59 +0100

I think that that is the point that John is trying to make. People are duplicating work and code and polluting the namespace. If you could post to somewhere, saying: 'I've got this idea', then someone could let you down gently, and say they'd already done it. Then you'd be free to extend their work, and improve upon it, collaboratively. [...]