Post what it is you you think is lacking in the current aggregation modules and let's all collaborate. My aggregation module would welcome a patch anytime :-p<br><br><div><span class="gmail_quote">On 4/30/07, <b class="gmail_sendername">
Mohammed Sameer</b> <<a href="mailto:msameer@foolab.org">msameer@foolab.org</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
[snip]<br>On Mon, Apr 30, 2007 at 01:09:16AM +0300, Ashraf Amayreh wrote:<br>> IMHO, we should make it compulsive that every module developer post to the<br>> mailing list before setting on a new module. This may prevent the
<br>> catastrophe of so much repeated modules and repeated code.<br><br>There's a point I want to say. Writing your own module/code is sometimes a lot easier<br>than spending your time to understand the current code. I'm not sure what lead to having
<br>all those aggregator modules around. It even becomes worse when you find that most of<br>them are either unmaintained, not working for you or your setup or not ported to the<br>latest drupal. Then you end up writing your own.
<br>I had this problem with the stock aggregator module bringing my server to its<br>knees. No time to push changes to core aggregator. The solution ? I have my own 100th<br>aggregator module (Yes, I'm serious) and I'm thinking about releasing it since I know I'll
<br>maintain it and keep it up to date.<br><br>I guess we need to work on the core one to fix it.<br><br>My 0.02 Euros!<br><br>--<br>GPG-Key: 0xA3FD0DF7 - 9F73 032E EAC9 F7AD 951F 280E CB66 8E29 A3FD 0DF7<br>Debian User and Developer.
<br>Homepage: <a href="http://www.foolab.org">www.foolab.org</a><br></blockquote></div><br>