On Wed, Feb 28, 2007 at 07:23:18AM -0700, mlist wrote:
> Sounds like a great idea to me. It would help if the patches were
> categorized . . . I guess kind of like how squirrelmail has their
> plugins section organized? http://www.squirrelmail.org/plugins.php
Yes, this is reasonable.
The idea is to create a system like the kernel, using a .config file
and a pool of #ifdef preprocessor directives.
I'm already working on a system to let the user to choose his patchset
with an interface similar to the kernel configuration process.
The user selects patch he is interested in, and the compile process
removes undesired code from the binary.
By the way each patch should be developed on its own, and one of my
principles for the project is that the code should no overlap if
possible (some patch behavior is unacceptable because it prevents
integration with other patches).
With this mood, each patch could be documented independently, and
categorized too (protocol enhancement, spam prevention, ecc..).
I'm waiting for feedback about collaboration (instead of starting a
new project with the same goal), and surely about the project name :)
Bye
Fabio
|