If we don't end up forcing users into anything, at minimum let's give some strong encouragement to post to the dev list. It will at least allow for "have you seen module X?" dupe avoidance.
Might we all drop off the dev list if it gets any busier? Then we have the same problem. However, I see awfully good quality answers on this list, and it would work great if it didn't wear on the list. On Wed, Nov 18, 2009 at 9:58 AM, Ken Winters <kwinters@coalmarch.com> wrote:
The only alternative is to catch projects before they are even created by
requiring permission per project rather than a CVS account that can create an unlimited number of projects/modules. Not to mention the added benefit of introducing the module on the dev list to everyone which is a huge advantage.
If we don't end up forcing users into anything, at minimum let's give some strong encouragement to post to the dev list. It will at least allow for "have you seen module X?" dupe avoidance.
I've noticed that when there is contention on an issue it often results in no progress at all, but we can pull off some easy improvement with nothing but content changes in spite of that (but only if don't just let it drop).
- Ken Winters
-- Randy Fay Drupal Development, troubleshooting, and debugging randy@randyfay.com +1 970.462.7450