See http://modules.apache.org -----Original Message----- From: Bob Apthorpe [mailto:[EMAIL PROTECTED] Sent: Sun 3/7/2004 3:10 PM To: [EMAIL PROTECTED] Cc: Subject: Re: Plugin repository? On Sun, 7 Mar 2004 17:13:28 -0500 Theo Van Dinter <[EMAIL PROTECTED]> wrote:
> So I think we're going to find that after 3.0 comes out, more and more > people will be writing plugins to support a bunch of different things > we aren't going to support in the main line code (PGP/GPG whitelisting, > virus scanning, etc, etc.) > > This led me to wonder if we should have a repository available (something > off the wiki?) where people can upload their plugins for everyone to use, > or if people should host their own and can just point to it off a plugin > listing on the wiki? > > I don't think we should be accepting plugins and publishing them out > with the main code. > > Thoughts? Dumb question: how does Apache (the webserver) manage 3rd-party modules? (yes, I'm too lazy to look this up.) As a user, I'd rather browse the SA site for SA plugins than use a generic search engine like Google or Freshmeat (one-stop shopping.) My concerns are accessibility, version control, and licensing. We're getting to the point where the custom rules (BigEvil, Weeds, etc.) are running into version control and accessibility issues and I think matters will get worse when the plugin architecture starts getting popular. Which projects manage their 3rd-party plugins well and who can we steal good ideas from? :) -- Bob
